PunchOut is the procurement protocol that large institutional buyers — hotel chains, universities, hospital systems — use to order from suppliers without leaving their own procurement platform. Understanding how it works is essential for any food distributor serving managed accounts.
What PunchOut Is and Why It Exists
PunchOut is a procurement integration standard that allows a buyer to “punch out” from their procurement system (the internal platform where all purchasing happens) into a supplier’s catalog, shop with their specific pricing, build a cart, and return that cart to their procurement system as a purchase requisition — all without logging into a separate supplier system or handling the order outside their normal approval workflow.
The protocol was developed in the late 1990s as part of the cXML (Commerce eXtensible Markup Language) standard, which was designed to enable machine-to-machine communication between procurement systems and supplier catalogs. Despite being over two decades old, cXML PunchOut remains the dominant standard for B2B procurement integration, with the major procurement platforms (Coupa, SAP Ariba, Workday, Jaggaer) all supporting it.
PunchOut exists because large institutional buyers need every purchase to flow through their internal procurement workflow. The workflow exists for good reasons:
- Budget control: Purchase orders generate financial commitments that need to be tracked against department budgets
- Approval routing: Purchases above a threshold require manager or director approval before commitment
- Spend visibility: All purchases are captured in a single system that finance and procurement can analyze for supplier consolidation, contract compliance, and audit purposes
- Contract compliance: Buyers can restrict which products appear in PunchOut catalogs, enforcing use of contracted items and preventing maverick purchasing of off-contract goods
For a hospital system, a university, or a hotel chain with dozens of properties and millions of dollars in annual food purchasing, this visibility and control is not optional. Any supplier that cannot integrate with their procurement workflow is not viable as a vendor.
How cXML PunchOut Works: The Three-Step Flow
The PunchOut session flow follows a standardized sequence that is consistent across all platforms and suppliers implementing the cXML standard.
Step 1: Setup Request. The buyer’s procurement system sends a PunchOut Setup Request to the supplier’s PunchOut URL. This message is an XML document that identifies the buyer (using credentials established during the PunchOut connection setup), provides a return URL where the cart data should be sent when shopping is complete, and establishes the session. The supplier’s system authenticates the buyer, identifies their account and pricing configuration, and returns a URL where the buyer’s browser should be redirected.
Step 2: Browse. The buyer’s browser is redirected to the supplier’s catalog — a Confinus-hosted environment that looks and behaves like the distributor’s normal ordering portal, but is pre-authenticated with the buyer’s specific account context. The buyer sees their contracted pricing, their specific product assortment, their order guide, and all the standard catalog features. They build a cart just as they would in a normal ordering session.
Step 3: Transfer. When the buyer clicks “Send Cart to Procurement System” (or equivalent), the supplier’s PunchOut system sends a PunchOut Order Message back to the buyer’s procurement system via the return URL established in Step 1. This message contains the full cart contents: items, quantities, descriptions, unit prices, line totals. The buyer’s procurement system receives this data and creates a purchase requisition from it. From there, the requisition follows the buyer’s normal approval workflow — exactly as if the buyer had created a manual order in their own system.
The supplier does not receive a committed order from the PunchOut session. They receive the order only after it has been approved in the buyer’s procurement system and converted to a purchase order (PO) — which is then transmitted back to the supplier via a separate PO transmission, also typically in cXML format.
PunchOut in Food Distribution: Specific Considerations
Standard PunchOut implementations work well for commoditized goods with stable prices. Food distribution introduces several complications that require specific handling.
Catch-weight products. As covered in detail in our guide to catch-weight pricing, food products with variable weight per unit cannot be represented with a fixed unit price. A PunchOut catalog that correctly handles catch-weight products must display estimated pricing at session time and handle the invoice reconciliation when actual weights are confirmed. This requires custom implementation beyond standard cXML PunchOut — most generic PunchOut platforms do not support it natively.
Daily price changes. Commodity-priced products change price daily. A PunchOut catalog must reflect current prices at session time, not cached prices from a periodic sync. For protein-heavy procurement, a buyer placing an order at 7am needs to see prices that were valid as of that morning’s market, not last night’s ERP batch.
Deep assortment with personalized filtering. A hospital dietary department punching out to a broadline distributor’s catalog does not want to see the full 15,000-SKU assortment — they want their approved, clinician-reviewed formulary items. The PunchOut experience must respect account-specific catalog configurations, including assortment restrictions, preferred items, and brand-standard requirements.
Return quantity and unit handling. When a buyer adds “10 cases” of chicken to their PunchOut cart, the PO that comes back to the distributor must specify the correct unit of measure, catch-weight handling, and pricing basis. This data mapping — between the buyer’s procurement system’s data model and the distributor’s ERP — requires careful implementation.
Common PunchOut Procurement Systems
Distributors serving hospitality, healthcare, education, and corporate dining will encounter these platforms most frequently:
BirchStreet. Purpose-built for hospitality procurement. Widely deployed in hotel chains (Marriott, Hilton, IHG, and independent groups). Confinus maintains a tested PunchOut integration that handles the hospitality-specific requirements.
Coupa. General enterprise procurement platform, widely deployed in corporate and institutional settings. Strong PunchOut support and a large network of supplier connections.
Workday Procurement. Increasingly common as Workday’s ERP footprint has grown. PunchOut integration through the Workday Supplier Portal.
Jaggaer (formerly SciQuest). Common in higher education and healthcare. Strong RFx and contract management capabilities with PunchOut catalog support.
SAP Ariba. The dominant enterprise procurement platform at Fortune 500 and large institutional accounts. Ariba’s supplier network (Ariba Network) is the largest buyer-supplier connection platform in the world.
Adaco. Hospitality-specific procurement platform competing with BirchStreet in the hotel segment.
Craftable / IBuyEfficient. Restaurant and hospitality-focused procurement tools with PunchOut support used by restaurant groups and smaller hotel operators.
What PunchOut Means for Distributor Strategy
For distributors serving managed accounts — hotel chains, university systems, hospital networks, corporate dining operators — PunchOut connectivity is not optional. It is a requirement to be on the approved vendor list.
But beyond the compliance requirement, PunchOut creates a competitive lock-in mechanism. Once a distributor is integrated with a buyer’s procurement system via PunchOut, the relationship is embedded in the buyer’s workflow. Switching to a different supplier requires a new PunchOut setup, change management within the procurement team, and the disruption of replacing a tested integration. This is not an insurmountable barrier, but it is a meaningful friction that favors incumbent suppliers.
Distributors who invest in PunchOut capability and achieve integration with their largest buyers’ procurement systems are building a relationship infrastructure that is much harder to dislodge than a phone-based account relationship.
Confinus supports PunchOut integration with BirchStreet, Coupa, Workday, Adaco, and other major procurement platforms. Learn more on our integrations overview page or explore Confinus for hospitality buyers.