Punchout catalog & EDI integration for B2B distributors
Procurement teams at large accounts order inside SAP Ariba, Coupa, Jaggaer or Oracle iProcurement, because that is where approvals and PO numbers live. The CS Order Suite makes your online store reachable from those systems: as a cXML or OCI punchout catalog with each customer’s contract pricing, and via EDI 850/855/856/810 for accounts that exchange documents rather than browse.
What is a punchout catalog?
A punchout catalog is your live web store, opened from inside the buyer’s procurement system. Instead of a static catalog file you re-send every quarter, the buyer “punches out” to your store, sees their negotiated prices and availability, builds a cart – and the cart travels back as a requisition. Approval and the purchase order happen on their side.
How does the CS Order Suite handle punchout?
Punchout is part of the platform, not a plug-in on a retail store. Both protocols run on the same storefront and customer accounts, so a punchout session shows exactly the price your ERP holds for that account.
Which EDI documents flow – and how do they reach your ERP?
Some accounts never punch out: their ERP sends purchase orders as EDI and expects acknowledgments, ship notices and invoices back the same way. The CS Order Suite covers the four X12 documents of the order-to-invoice cycle:
Connectivity runs through the customer’s EDI provider (VAN) or a direct AS2 connection. The platform maps each document to your ERP – for SAP Business One through the ready ERP integration – so an 850 lands as a sales order and 855, 856 and 810 go out from what your ERP confirmed, shipped and invoiced. Mapping follows each trading partner’s implementation guide.
Punchout vs. EDI vs. API – which one does a customer need?
Usually the customer decides. Punchout is for people who select; EDI is for systems that transmit; an API is for integrations you build yourself. Many distributors run all three side by side.
| Punchout (cXML / OCI) | EDI (850 / 855 / 856 / 810) | API | |
|---|---|---|---|
| What it does | Buyer browses and selects in your live catalog from inside their procurement system | Two systems exchange structured documents; nobody browses | Your systems or middleware read and write platform data |
| Who initiates | The buyer, from Ariba, Coupa, Jaggaer, Oracle or SAP SRM | The buyer’s ERP via their EDI provider or AS2 | Your integration project |
| Best for | Catalog buying with many SKUs and contract pricing | Repeat POs, replenishment, high volume on fixed item lists | Custom workflows, middleware, automation platforms |
| Setup per customer | Typically a few days per buyer, paced by their procurement team | Days to weeks per trading partner (mapping, test transactions) | Scoped per project |
| In the CS Order Suite | Standard – cXML and OCI 4.0 | Standard – via EDI provider or direct | Provided per project; no public self-service API. See integrations & API |
cXML punchout catalog integration, step by step
What is cXML punchout?
cXML PunchOut is a standard protocol that lets a buyer open a supplier’s web store from inside their e-procurement system – SAP Ariba, Coupa, Jaggaer or Oracle iProcurement – shop there with their own contract pricing, and return the cart as a cXML PunchOutOrderMessage, where it becomes a requisition in the buyer’s approval flow. No re-keying, no separate login. The SAP-side counterpart of the protocol is OCI.
A cXML punchout catalog runs on four messages. Two open the session, one returns the cart, one delivers the order – and every one of them is standard cXML, so the same setup works across Ariba, Coupa, Jaggaer and Oracle iProcurement:
cXML punchout example: the PunchOutSetupRequest
This is what arrives at your punchout URL when a buyer clicks your catalog in Ariba, Coupa or Jaggaer – trimmed to the fields that matter:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cXML SYSTEM "http://xml.cxml.org/schemas/cXML/1.2.014/cXML.dtd">
<cXML payloadID="1728551400.4711@buyer.example.com" timestamp="2026-10-10T09:30:00+00:00">
<Header>
<From><Credential domain="NetworkID"><Identity>AN01000012345</Identity></Credential></From>
<To><Credential domain="DUNS"><Identity>123456789</Identity></Credential></To>
<Sender>
<Credential domain="NetworkID">
<Identity>AN01000012345</Identity>
<SharedSecret>agreed-at-onboarding</SharedSecret>
</Credential>
<UserAgent>Buyer procurement system</UserAgent>
</Sender>
</Header>
<Request>
<PunchOutSetupRequest operation="create">
<BuyerCookie>34234234ADFSDF234234</BuyerCookie>
<Extrinsic name="UserEmail">j.miller@buyer.example.com</Extrinsic>
<BrowserFormPost><URL>https://buyer.example.com/punchout/return</URL></BrowserFormPost>
</PunchOutSetupRequest>
</Request>
</cXML>
From / To– who is calling and which supplier is meant – Ariba Network IDs, DUNS numbers or agreed custom domains.SharedSecret– the password agreed at onboarding; the store rejects the session if it does not match.BuyerCookie– the session key that has to come back unchanged with the cart.BrowserFormPost– where the PunchOutOrderMessage is posted when the buyer clicks “return cart”.- The store answers with a
PunchOutSetupResponsecontaining aStartPageURL – the buyer is redirected there, already signed in.
SAP-side procurement (SRM, S/4HANA) covers the same flow with OCI instead of cXML – the CS Order Suite speaks both, so one catalog serves both worlds. And for Level 2 punchout, an index file makes your items show up directly in the buyer’s own search, deep-linking into your store.
OCI punchout in detail – and which platform uses what
OCI (Open Catalog Interface) is SAP’s punchout protocol. It does the same job as cXML with far less ceremony: the buyer’s SAP system calls your catalog URL with login parameters and a HOOK_URL – the address the cart has to go back to. On “return cart”, the store posts an HTML form to that HOOK_URL with one set of NEW_ITEM fields per cart line. The core fields of OCI 4.0:
| OCI field | Content |
|---|---|
NEW_ITEM-DESCRIPTION[n] |
Short text of the item |
NEW_ITEM-VENDORMAT[n] |
Your item number (supplier part number) |
NEW_ITEM-QUANTITY[n] / -UNIT[n] |
Quantity and ISO unit of measure |
NEW_ITEM-PRICE[n] / -PRICEUNIT[n] / -CURRENCY[n] |
Net price from the customer’s contract, price unit, currency |
NEW_ITEM-MATGROUP[n] |
Material group, so the requisition lands in the right cost and approval path |
NEW_ITEM-LEADTIME[n] |
Delivery time in days |
Punchout by procurement platform
| Buyer platform | Protocol | What to know |
|---|---|---|
| SAP Ariba | cXML | Runs over the Ariba Network; the supplier needs an Ariba Network account. |
| Coupa | cXML | The buyer sets up the punchout in Coupa with your URL and credentials. |
| Jaggaer | cXML | Common in higher education, research and healthcare purchasing. |
| Oracle Procurement (iProcurement / Fusion) | cXML | Punchout catalogs configured per supplier on the buyer side. |
| Workday Procurement | cXML | Punchout suppliers are set up by the buyer’s Workday team. |
| JD Edwards EnterpriseOne | cXML | Punchout from JDE procurement to the supplier’s store. |
| SAP SRM / SAP S/4HANA | OCI 4.0 | SAP’s own procurement speaks OCI; S/4HANA buyers often route through Ariba (cXML) instead. |
| Onventis, Simple System and other European suites | OCI | Most also accept cXML – agreed per customer. |
The CS Order Suite serves cXML and OCI 4.0 from the same catalog, so one store covers every row of this table – with each buyer’s contract pricing from the ERP.
Where do procurement teams demand a punchout catalog?
The request rarely comes from your sales contact. It comes from the customer’s procurement group, often during a supplier review or RFP: “Are you punchout-enabled?” These categories hear it most:
Ready to be a punchout-enabled supplier?
In a live demo we walk through a punchout session end to end – from the buyer’s procurement system into the store and back, to the order arriving in SAP Business One. Pricing is something we cover personally.
Book a live demo
CS Management & IT-Beratung GmbH
Ulrichsberger Str. 17 · 94469 Deggendorf · Germany