Punchout and EDI explained for commerce teams
What cXML, OCI and the core EDI documents do, and how they connect to your storefront.
Punchout
- ProcurementBuyer starts
- Your catalogJumps in
- CartBuyer fills it
- Approval and POCart returns
Best when buyers shop your catalog from their own procurement system.
EDI
- Buyer system
- Purchase orderStructured file
- Your ERPOrder lands
- Sent backConfirm, ship, invoice
Best when the order, ship notice, and invoice move as files between systems.
Your largest customers often don’t want to log in to your website. Their procurement teams buy through systems such as SAP Ariba, Coupa or Jaggaer, and their finance teams expect orders and invoices to arrive electronically. Punchout and EDI are how a distributor meets them there.
They solve different problems, and they’re often confused, so here’s what each one does and how both connect to the commerce platform you already run.
Punchout: shopping from inside the buyer’s procurement system
With punchout, a buyer starts in their own procurement system, clicks your company in a supplier list, and “punches out” to your site. They shop with their contract pricing and catalog, then the cart is sent back to their system for approval. The order is placed only after it’s approved on their side.
The flow usually looks like this:
- Setup request. The procurement system sends a request to your punchout endpoint identifying the buyer and their organization.
- Session. Your site authenticates the request, logs the buyer in to the right company account and returns a URL to start shopping.
- Cart return. When the buyer checks out, your site sends the cart contents back to the procurement system instead of taking payment.
- Approval and purchase order. The buyer’s internal approvals run. The approved order then reaches you as a purchase order, often by cXML or EDI.
cXML and OCI
The two common punchout protocols are:
- cXML (commerce XML): an XML-based standard used by Ariba, Coupa and many others. It covers the setup request (
PunchOutSetupRequest), the cart return (PunchOutOrderMessage) and can also carry the purchase order itself (OrderRequest). - OCI (Open Catalog Interface): a protocol from the SAP world. The procurement system opens your site with parameters including a return address (the
HOOK_URL), and your site posts the cart back as form fields.
Each customer’s setup differs in details such as credentials, required fields and how units of measure and their own part numbers are mapped. Expect configuration and testing per trading partner.
EDI: exchanging business documents system to system
EDI (electronic data interchange) replaces paper and email documents with structured messages between your systems and your customers’. In North America the common standard is ANSI ASC X12, where each document type has a number. The four that matter most in an order-to-cash flow:
| Document | X12 | What it does |
|---|---|---|
| Purchase order | 850 | The customer’s order: items, quantities, prices, ship-to. |
| PO acknowledgment | 855 | Your confirmation: accepted, changed or rejected lines. |
| Advance ship notice | 856 | What shipped, when, in which cartons and on which carrier. |
| Invoice | 810 | The bill, matched against the PO and shipment. |
Most exchanges also use the 997 functional acknowledgment, which confirms a document was received and could be read (not that the business content was accepted). Outside North America, the UN/EDIFACT equivalents are ORDERS, ORDRSP, DESADV and INVOIC.
Documents travel over a transport such as AS2, SFTP or a value-added network (VAN). Many distributors use an EDI provider to handle translation and partner connections, and integrate that provider with their ERP.
How punchout and EDI connect to your storefront
Punchout and EDI are channels, like your website. The mistake we see most often is building them as separate systems with their own pricing and order logic. Keep them on one pipeline:
- One catalog and one price source. The prices a buyer sees in a punchout session should come from the same logic as your logged-in site, scoped to that customer’s contract.
- One order pipeline. Web orders, punchout purchase orders and EDI 850s should land in the ERP through the same validation: customer, ship-to, item, unit of measure and price checks.
- Cross-references. Customers often order using their own part numbers and units. Store those mappings once and use them for punchout, EDI and the website.
- Status back out. The 855, 856 and 810 are generated from ERP events. If your site shows order status, it should read the same events, so a buyer sees the same truth in every channel.
Before you onboard your first trading partner
- Collect each customer’s implementation guide. It specifies the fields, codes and rules they require.
- Agree who owns testing on both sides, and plan a test cycle per document.
- Confirm labeling requirements for shipments. Some partners require GS1-128 carton labels that match the ASN.
- Decide how exceptions are handled: a rejected 855 line, a price mismatch, a short shipment. Someone has to see and resolve them.
- Monitor every document. A silent failure in EDI is a missed order or an unpaid invoice.
Punchout and EDI aren’t glamorous, but for many distributors they carry a large part of the revenue from their biggest accounts. Treat them as first-class channels, built on the same foundations as the website.