Punchout Catalog

How a punchout catalog works

A punchout session runs in four steps, all inside the buyer’s normal purchasing workflow:

1. Launch. A requester (e.g. a lab manager) clicks a supplier tile inside the institution’s e-procurement portal — SAP Ariba, Coupa, Jaggaer, and similar systems all support this.
2. Punch out. The buyer’s system passes an authenticated session request to the supplier, and the requester is redirected into that supplier’s own hosted storefront — not a static page inside the procurement system, but the supplier’s real e-commerce site, pre-configured to show the institution’s negotiated contract pricing, restricted product list, and available stock.
3. Shop and punch in. The requester browses and builds a cart on the supplier’s site, then clicks “checkout” or “submit,” which transmits the cart contents back to the buyer’s procurement system as structured line-item data (SKU, description, unit price, quantity).
4. Requisition. The returned cart becomes a normal requisition inside the buyer’s system, carrying GL coding and cost-center information, and re-enters the institution’s standard approval chain, budget check, and purchase-order issuance — the supplier interaction is over; everything downstream is the buyer’s own procurement process.

The technical standards behind it: cXML and OCI

Two protocols carry punchout sessions between buyer and supplier systems:

• cXML (commerce eXtensible Markup Language) — originally developed for the Ariba Network and now supported broadly across e-procurement platforms, including SAP Ariba and Coupa, for punchout setup requests and returned cart messages.
• OCI (Open Catalog Interface) — developed by SAP for its SRM and Ariba-connected environments, used as an alternative (or in parallel) to cXML for the same round-trip.

Both do the same job: pass authentication and session parameters out to the supplier, and pass a structured cart back. Which one a given supplier integration uses is a technical detail negotiated between the institution’s procurement/IT team and the supplier, largely invisible to the end requester.

Why research institutions use punchout catalogs

Punchout is the standard mechanism by which universities, hospitals, and research institutes buy reagents, consumables, and lab supplies from major scientific distributors — Fisher Scientific, VWR (part of Avantor), and Sigma-Aldrich/MilliporeSigma (part of Merck KGaA) all offer punchout catalog integrations with common institutional procurement platforms. For a lab, this solves a real problem: catalogs from these suppliers run to hundreds of thousands of SKUs with pricing and availability that changes constantly, which makes a static, uploaded price list impractical to maintain. Punchout lets the researcher shop the supplier’s live, full catalog at the institution’s actual contract pricing, while the institution keeps every dollar routed through its own budget checks, approval hierarchy, and purchase-order and payment systems — the spend never leaves the institution’s financial controls just because the shopping experience happens on the supplier’s website.

Punchout catalog vs. hosted (static) catalog

Not every supplier integration in an e-procurement system is a punchout catalog. The alternative is a hosted or static catalog: a price file the supplier sends periodically (daily, weekly, or less often), which is loaded directly into the buyer’s own procurement system. Requesters search and select items without ever leaving the buyer’s platform. Hosted catalogs work well for smaller, stable supplier relationships with a limited, slow-changing item list; they break down for large scientific distributors whose pricing, promotions, and stock levels change too fast for a periodic upload to stay accurate. A punchout catalog avoids that problem entirely by keeping the item data live, on the supplier’s own system, and only exchanging the final cart.

Frequently asked questions

What is a punchout catalog?

A punchout catalog is a live, supplier-hosted online catalog linked into a buyer’s e-procurement system, so a requester can shop the supplier’s real-time inventory and contract pricing and have the finished cart flow back automatically into the buyer’s own purchase-requisition and approval process.

What does “punchout catalog” mean, exactly?

The name describes the mechanic: the requester “punches out” of the buyer’s procurement system into the supplier’s website, and the completed order “punches back in” as a structured requisition. It is a session-based redirect and data hand-off, not a stored list of items.

What is a Coupa punchout catalog?

It’s the same punchout mechanism — a live redirect to a supplier’s hosted storefront with a structured cart returned afterward — implemented inside Coupa’s procurement platform. Coupa supports punchout via cXML, and many of the same scientific suppliers that punch out through SAP Ariba (Fisher Scientific, VWR, Sigma-Aldrich/MilliporeSigma) offer equivalent Coupa integrations.

How does an Ariba punchout catalog work?

Inside SAP Ariba (both Ariba Network and Ariba Procurement/Guided Buying), a supplier is set up as a punchout vendor rather than a hosted-catalog vendor. Clicking that supplier’s catalog tile launches a cXML or OCI session that redirects the requester to the supplier’s site; the returned cart populates an Ariba requisition, which then follows the institution’s normal Ariba approval workflow.

Is “SAP Ariba punchout catalog” different from a standalone Ariba punchout catalog?

No — “SAP Ariba” and “Ariba” refer to the same product family (SAP acquired Ariba in 2012), so a punchout catalog set up in SAP Ariba Buying / Ariba Network functions identically whether it’s described as an “Ariba punchout catalog” or “SAP Ariba punchout catalog.”

Related terms

See also sustainable procurement (research) for how institutions weigh environmental criteria inside catalog and vendor selection, and the 2 CFR 200 procurement standards guide for the federal competitive-bidding rules that apply once a punchout requisition becomes a purchase order on a federal award. For the vendor-facing side of institutional supply-buying decisions, see the comparison of medical and lab supply buying apps. Punchout catalog integration and vendor management sit within CASRAI’s Laboratory Operations & Safety coverage.