What a punchout catalog actually does
A punchout session runs in four steps. Each one crosses a boundary between two companies' systems.
- The buyer punches out: their procurement system sends a request identifying the buyer and their organization, so the supplier site opens already knowing who is shopping
- Pricing resolves per account: the storefront shows that buyer's contracted prices and current availability, not a public catalog
- The cart returns as a requisition: the buyer transfers the cart back into their procurement system rather than checking out on the supplier site
- Approval and ordering happen buyer-side: the requisition follows the buyer's internal approval chain, then arrives as a purchase order
The order never gets placed on the supplier's storefront. That is the part suppliers find counterintuitive, and it is exactly why the buyer's procurement team insists on it.
Why do enterprise buyers insist on punchout?
Procurement software exists to enforce policy. Spend gets categorized against budgets, approvals route by value, and every commitment lands in one auditable place. A buyer who leaves that system to order on a supplier site has stepped outside all of it.
Large organizations respond by mandating that purchasing happens inside the procurement system. Buying anywhere else becomes maverick spend, which procurement teams are measured on reducing. At that point the supplier webshop is not competing with other webshops. It is competing with the buyer's own policy, and it loses.
Punchout resolves the conflict rather than fighting it. The supplier keeps the catalog, the pricing logic, and the product experience. The buyer keeps the approval chain and the audit trail. Neither side gives up the thing they cannot give up.
What do suppliers lose without a punchout catalog?
A supplier without punchout does not get a slower channel. It gets excluded from accounts that would otherwise buy. The loss shows up in a recognizable order:
- Lost from the approved vendor list: procurement teams shortlist suppliers their system can reach, and a supplier that cannot be punched out to gets filtered before any commercial conversation
- Orders that arrive as work: without punchout, large accounts send purchase orders by email or EDI, and someone re-keys them into the ERP
- Pricing disputes at invoice: when the buyer ordered from a spreadsheet or a PDF catalog, the price they expected and the price you invoice diverge, and finance absorbs the difference
- No visibility into the account: orders arrive without the browsing behavior, quote history, or product interest that a connected storefront would capture
What punchout demands from your systems
Punchout looks like an e-commerce feature and behaves like an integration requirement. Four things have to be true at the moment the buyer is browsing.
- Account-specific pricing on request: the contracted price for that buyer, resolved live from the ERP rather than served from a synchronized table that ages
- Real availability: stock that accounts for allocations and inbound receipts, since a punchout cart that fails at fulfillment damages the account relationship more than a slow site would
- Identity handled correctly: the punchout request carries credentials that must map to the right account and contract in your systems, every time
- The right document formats: most procurement platforms speak cXML, some speak OCI, and the requisition and order have to be readable by both sides
Only the fourth is really about punchout as a standard, and it sits next to the EDI integration most suppliers already run for their largest accounts. The first three are ordinary integration problems that punchout makes visible. A buyer inside their own procurement system has no patience for a page that takes six seconds to price.
How an integration platform serves a punchout catalog
Suppliers reach punchout three ways. A procurement network or supplier portal will host the catalog for you, which works and charges per transaction while keeping the buyer relationship one step away. Some e-commerce platforms offer punchout modules, which handle the protocol and still need connecting to the ERP that holds the contract prices. Building it directly against each buyer's procurement system is possible and multiplies with every new large account.
An integration platform-as-a-service (iPaaS) connects the storefront to the systems holding the answers. On the Alumio iPaaS that work takes four forms:
- Priced while the buyer waits: a real-time Proxy checks contract pricing and stock in the ERP while the buyer is browsing, so the number on screen is the number in the ERP
- Formats translated both ways: a data Transformer converts cXML or OCI documents into what the ERP expects and back again, so procurement standards do not dictate your back-office design
- Held when a system is slow: a built-in Storage keeps reference data ready and queues returning orders, so an ERP under load does not break a live buyer session
- Traceable per session: detailed Logs record which buyer saw which price and when, which is what settles an invoice dispute without an investigation
Those flows are configured rather than hand-built per buyer, with the Code Transformer available where configuration cannot express a rule, and writing code is preferred. Leeuwerik Plaat, a Dutch B2B supplier of sheet materials, sells on customer-specific contract prices. Alumio moves its products, stock, and per-customer pricing in real time between the Kerridge ERP and Adobe Commerce. Buyers order around the clock against the price their contract carries.
What a punchout catalog is worth to a supplier
Punchout is rarely funded on its own merits. It gets funded when a large account asks for it, and the answer decides whether that account stays.
The suppliers who treat it as infrastructure rather than a one-off build end up somewhere better. Run through an integration platform, each new enterprise buyer connects to a pattern that already exists. Procurement teams stop routing around them, and the pricing that reaches the buyer is the pricing finance expects to invoice.
What the business gets back is access to accounts that were previously unreachable, orders that arrive structured instead of as email attachments, and a channel that scales with the sales team rather than with the integration backlog.
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
