Punchout catalog: what it means when a customer buys through their own procurement system
A supplier's hosted catalog that a corporate buyer accesses from inside their own procurement system, with completed baskets returning as purchase requisitions rather than orders placed on the supplier's site.
A punchout catalog is a supplier's hosted product catalog that a corporate buyer reaches from inside their own procurement platform - SAP Ariba, Coupa, Jaggaer, or Oracle - rather than visiting the supplier's website directly. Unlike a regular web store or company store, where the buyer places an order that is processed on the supplier's platform, a punchout session ends with the buyer's basket returning to their own system as a purchase requisition. That requisition routes through internal approvals before becoming a formal purchase order, which is then transmitted electronically back to the supplier.
How the punchout process works
When a buyer punches out, they click through from their procurement system to your catalog. They browse, select products, configure options, and build their basket exactly as they would on any online store. The key difference comes at the end. Instead of checking out on your site, they submit their cart back to their own system. That action - the punch back - converts the basket into a requisition document inside the buyer's procurement platform.
The requisition then passes through whatever approval chain the buyer's organisation has configured: line managers, budget holders, finance. Once approved, the procurement system generates a formal purchase order and transmits it electronically to the supplier using a standard protocol - most commonly cXML. The supplier receives a structured, machine-readable PO without any manual re-keying required on either side.
How it differs from a company store or web store
A company store is a branded portal a buyer visits directly, logs into, and orders from - the transaction is managed on the supplier's side from start to finish. A web store or eCommerce channel works the same way but at a public-facing level. A punchout catalog connects to the buyer's system rather than replacing it. Their procurement platform remains in control of the transaction; your catalog is a data source they reach from inside it.
This distinction matters for corporate buyers operating under strict procurement governance. Many large organisations prohibit purchasing outside their procurement system regardless of how convenient or well-priced an alternative might be. A punchout-enabled supplier fits inside that governance. A supplier without punchout capability is effectively invisible to buyers working within those constraints, regardless of price or service record.
Approved supplier advantage
Once registered as a PunchOut-enabled supplier inside a buyer's procurement system, removing you requires months of technical and procurement work on their side. For suppliers in promotional merchandise, office furniture, or branded workwear, a handful of enterprise punchout accounts can represent a significant and predictable portion of annual revenue.
Suppliers that support punchout can also use Customer Pricing API capabilities to embed per-buyer contracted rates inside the catalog session, so each corporate buyer sees their correct prices without manual intervention. Zigaflow's PunchOut integration connects to SAP Ariba, Coupa, and Jaggaer and routes approved purchase orders directly into the orders pipeline, following the same fulfilment workflow as any other job.
Common in
Frequently asked questions
Ready to put this into
practice?
Book a free demo and see how Zigaflow fits your team.