PunchOut catalog: what it is and how it works

A PunchOut catalog is a supplier's online catalogue that a buyer reaches from within their own ERP or e-procurement system. When the buyer clicks the catalogue, the ERP opens a live session to the supplier's site — the buyer 'punches out' — and shops the catalogue there. At checkout, instead of placing an order, the cart is returned to the ERP as a populated requisition.

The contrast is with a hosted catalog, where the supplier's product and price data is uploaded into the buyer's ERP and stored there. A hosted catalog is self-contained but goes out of date the moment prices or availability change; a PunchOut catalog is always current because it is the supplier's live site. That live pricing is the main reason PunchOut has become the standard for anything beyond a small, stable product list.

PunchOut relies on messaging standards, chiefly cXML (Commerce eXtensible Markup Language) and OCI (Open Catalog Interface). These define the setup request that opens the session and the order message that returns the cart, so buyers and suppliers on different systems can interoperate.

A PunchOut session is a defined round trip between the buyer's system and the supplier's catalogue. It feels seamless to the buyer, but a specific message exchange happens underneath.

PunchOut solves the central tension of catalogue procurement: buyers want a rich, current catalogue, but organisations need buying to happen inside their own controls. A hosted catalog gives control but goes stale; buying on the supplier's public site is current but escapes governance. PunchOut gives both — a live catalogue accessed inside the ERP's approval, budget and audit framework.

For suppliers, being PunchOut-ready is often a condition of doing business with large enterprises and GLCs, which standardise procurement on ERPs and expect suppliers to fit that workflow. For buyers, PunchOut is what makes a broad external catalogue usable without sacrificing pricing accuracy, spend visibility or compliance.

In a working example, a buyer in their ERP selects a connected supplier's PunchOut catalogue. The ERP sends a setup request; the supplier authenticates it and returns a session URL; the buyer shops the live catalogue and checks out; the cart returns as a requisition carrying the exact items and contracted prices. From there the requisition is approved and issued as a purchase order — all without the buyer leaving their system or anyone re-keying a line.

For a Malaysian supplier, offering a PunchOut catalog is what makes its products buyable by enterprises standardised on SAP, Oracle, NetSuite and similar systems. The commercial route to a connection is on the PunchOut and ERP integration solution page; the platform-specific detail is in the SAP and Oracle pillars; and the full technical treatment of cXML, OCI and integration levels is in the PunchOut integration guide linked below.

A PunchOut catalog lets a buyer shop a supplier's live, hosted catalogue from inside their ERP and return the cart as a requisition, using standards such as cXML and OCI. Unlike a hosted catalog that goes stale, PunchOut keeps pricing and availability current while keeping buying inside the ERP's controls.

This resolves the tension between a rich catalogue and organisational governance, which is why it is the standard for supplier catalogues and often a condition of enterprise business. The keys are a live catalogue, standard protocols, clean data and per-buyer testing. The commercial and technical detail lives in the ERP, SAP and Oracle pillars and the PunchOut integration guide linked below.