Let's Talk
Your customer's procurement team has asked whether you support punchout, and somewhere in the email are the letters cXML or OCI. Before anyone on your side tries to work out which is better, here is the short version: you do not get to choose. The customer's procurement platform has already decided.
Punchout is the method that lets a buyer leave their procurement system, shop on a supplier's website and bring the basket back into their system as a requisition. cXML and OCI are the two standards that make that round trip possible. Which one you are asked for tells you a lot about who you are dealing with and what "ready" will mean.
Two protocols, one idea
cXML stands for commerce XML. It was published by Ariba in 1999 as an open standard, so that suppliers could connect to buyers without a bespoke build for each one. Ariba was later acquired by SAP, and the standard is still maintained and published openly today.
OCI stands for Open Catalog Interface. It is SAP's own method, developed for its procurement products, and it is the native route into SAP's purchasing systems. The version most organisations still use dates back to the mid-2000s, which tells you how stable this corner of enterprise software is.
Both do the same job from the buyer's point of view: open the supplier's catalogue from inside the procurement system, fill a basket, bring it back. They work differently under the hood, and that difference is the integration partner's problem rather than yours. What matters commercially is which one your customer's platform speaks.
Which platforms use which
The split is not perfectly clean, because several platforms support both and the buyer's own configuration decides. As a working guide:
- Predominantly cXML: SAP Ariba (now part of SAP Business Network), Coupa, Oracle Procurement Cloud and Oracle iProcurement, GEP, Jaggaer and Unimarket.
- Predominantly OCI: SAP SRM and SAP S/4HANA procurement, which is to say most organisations whose purchasing runs natively on SAP.
- Commonly both, depending on configuration: Jaggaer, Unimarket and Oracle iProcurement offer OCI as a second option, and SAP Ariba can accommodate OCI alongside its own cXML.
- Ask: Basware and Proactis are both common in UK procurement and both support punchout, but which protocol applies depends on how the buyer has set them up.
Vendor support changes over time, so treat this as a guide to the question rather than the final answer. The final answer comes from the customer.
Why it matters commercially
It is tempting to file cXML and OCI under "technical detail" and move on. The protocol does, however, shape several things that land on the commercial side of the business.
- Different people on the buyer side. A cXML request usually comes through a supplier enablement team or a procurement network. An OCI request more often comes from the buyer's own SAP team or their implementation partner. Knowing which tells you who will be on the other end of the call.
- Different testing processes. Each platform has its own way of checking a supplier connection before go-live. The shape and length of that phase varies, and it affects when you can start taking orders.
- Different onboarding timelines. Network-driven onboarding tends to follow a formal sequence. Buyer-driven onboarding depends on how busy their internal team is. Neither is faster in every case, but they feel different.
- Reuse for the next customer. Once you have a working cXML connection, the next cXML customer is a variation on something you already have. If the next customer is on OCI, that is a second connection, not a copy of the first. Knowing early lets you plan for both.
A supplier set up for both standards through a single punchout integration can say yes to whichever platform the next large customer happens to use. That is the position most B2B suppliers eventually want to be in, and it is easier to design for from the start than to bolt on later.
What you will hear from each kind of customer
The vocabulary differs, and the vocabulary is often the first clue. A customer on SAP Ariba will talk about supplier enablement, the Ariba Network or SAP Business Network, and a test account. We cover how the main networks differ in Ariba, Coupa and Oracle: how the punchout experience differs. A customer on native SAP procurement will talk about OCI, catalogues and their SAP team, and the conversation will usually be with their IT function rather than a network. If you sell into organisations running SAP, our SAP punchout page covers what that relationship looks like.
If the terms in the email are unfamiliar, our punchout glossary translates the ones procurement teams use most.
The one question to ask on the first call
Everything in this article reduces to a single sentence you can put to the customer before anything is agreed:
"Which procurement platform do you use, and do you connect suppliers via cXML or OCI?"
The answer tells you who you will be working with, what the onboarding will feel like, and whether your existing setup covers it. It is a far better question to ask in week one than to discover in week six.
Been asked for cXML or OCI punchout?
Takeoff Digital connects Magento and Shopify stores to Ariba, Coupa, Oracle, SAP and other procurement platforms, and has done it for suppliers across construction, facilities and the public sector. If a customer has just asked you the question, talk to us and we will tell you what it involves for your business.
