B2B Punchout Catalogs: How Punchout Works With Procurement Systems

Punchout lets a buyer inside a procurement system shop on a supplier's site and return the cart to procurement for approval. With cXML, the procurement system sends a PunchOutSetupRequest; the supplier returns a start URL; the buyer shops with their account's catalog and prices; the supplier posts a PunchOutOrderMessage back to the return URL; and the approved order later arrives as an OrderRequest. SAP OCI follows a similar roundtrip using a HOOK_URL. The purchase order, not the returned cart, creates the sales order.

Punchout is one channel in a B2B platform; see B2B platform architecture. Catalog entitlements are covered in customer-specific catalogs and general integration patterns in API integration and B2B ERP integration.

Large organizations control purchasing through procurement systems: approved suppliers, budgets, approvals, purchase orders and invoice matching. Punchout gives their buyers the supplier's live catalog, search and configuration while keeping purchasing inside those controls. For suppliers, it is often a requirement to sell to such customers.

With SAP's Open Catalog Interface, the procurement system opens the supplier catalog URL with parameters including a HOOK_URL (the return address) and agreed login parameters. When the buyer transfers the cart, the supplier's site posts line item fields (such as description, quantity, unit, price, currency and supplier part number) to the HOOK_URL. OCI covers the catalog and cart roundtrip only; the purchase order is transmitted separately.

The setup request carries credentials (in cXML, identities and a shared secret) that the supplier validates and maps to a customer account and, where provided, a user. The buyer usually does not log in separately. Sessions should apply the account's catalog, prices and rules, restrict actions that do not belong in punchout (such as direct checkout or account changes), and handle timeouts gracefully.

The approved purchase order arrives as a cXML OrderRequest, EDI message or another agreed format. Validate it against the original cart and current prices, create the sales order in the commerce platform or ERP, send an acknowledgement and handle mismatches (price changes, quantity changes) according to agreed rules. Later documents such as ship notices and invoices may also be exchanged electronically.

A punchout layer sits between procurement systems and the commerce platform: an endpoint for setup requests, credential and account mapping, session creation in the storefront, cart serialization to cXML or OCI fields, and an order intake endpoint that turns OrderRequests into sales orders. Some suppliers build it themselves; others use specialist punchout connectors. Log every message for troubleshooting.

An illustrative scenario, not a client case: a laboratory supplier wins a contract that requires cXML punchout. The first integration works, but the buyer rejects carts because units of measure and UNSPSC codes are missing. The team adds UOM mapping and classification codes to product data, tests the full cycle including OrderRequest intake with the buyer's procurement team, and documents the configuration so the next customer can be onboarded faster.

Punchout connects a supplier's catalog to buyers' procurement controls: authenticate the session, apply the customer's catalog, return a well-formed cart and create orders from the purchase order. Related: B2B platform architecture and API integration.