OCI vs. cXML: the difference for suppliers | PunchCommerce                       ![](//analytics.punchcommerce.de/matomo.php?idsite=1&rec=1)

  [Skip to content](#main-content)

   Know-how · Comparison  OCI vs. cXML. Your customer chooses the protocol. You deliver both.
=====================================================================

 Whether it is OCI or cXML is decided by your customer’s procurement system, not by you. PunchCommerce delivers both protocols from the same catalog, on the Business plan for €49 per customer per month, plus VAT.

 [ Start free trial ](https://www.punchcommerce.de/register) [ See the comparison ](#comparison)

30 days free · no credit card · cancel anytime

  in one plan 2 protocols

 setup, no IT project &lt; 1 h

 free trial 30 days

 Short answer

The difference in brief
-----------------------

 The difference between OCI and cXML lies in login and return: in an OCI PunchOut, everything runs through the buyer’s browser; in a cXML PunchOut, the procurement system first contacts your server directly. Which protocol you deliver is determined by your customer’s procurement system; neither one is better or worse.

### OCI

  Standard owner SAP, Open Catalog Interface

 Login username and password in the call, which runs entirely in the buyer’s browser

 Cart returned as form fields to your customer’s HOOK\_URL

  [Go to OCI PunchOut](https://www.punchcommerce.de/en/oci-punchout)

### cXML

  Standard owner Ariba, Commerce XML, by now part of SAP

 Login identities and a SharedSecret, server to server first, then in the browser

 Cart returned as an XML document, the PunchOutOrderMessage

  [Go to cXML PunchOut](https://www.punchcommerce.de/en/cxml-punchout)

For you, only the credentials and the format in which the cart is returned change. Catalog, prices and maintenance stay the same.

### Stays the same

- your catalog: shop via plugin or Hosted Catalog
- prices and range per customer
- the field mapping you adjust per customer

### Differs

- the credentials: username and password or identities with a SharedSecret
- the format in which the cart is returned

 What lies behind the process and which side you provide as a supplier is explained in the [PunchOut basics](https://www.punchcommerce.de/en/punchout).

 Comparison

OCI and cXML side by side
-------------------------

The overview shows how the two protocols differ and what remains of that for you in PunchCommerce. You do not need the table to decide, but it helps when your customer’s IT department uses terms such as HOOK\_URL or SharedSecret.

  Comparison of OCI and cXML by criterion   Criterion OCI cXML     Standard owner  OCI SAP (Open Catalog Interface)   cXML Ariba (Commerce XML), now part of SAP    Procurement systems with only one of the protocols  OCI SAP SRM, Unite (formerly Mercateo)   cXML SAP Ariba, GEP SMART, Workday Procurement, Medius    Procurement systems with both protocols  OCI and cXML SAP S/4HANA, Onventis, Coupa, Jaggaer, Oracle Procurement, Basware, Synertrade, Proactis, Ivalua    Login  OCI username and password as parameters in the call   cXML identities in From, To and Sender, confirmed by the SharedSecret    Route of the request  OCI only through the buyer’s browser   cXML first directly from server to server, then in the browser    Cart format  OCI form fields `NEW_ITEM-*` per line item   cXML XML document `PunchOutOrderMessage`, at PunchCommerce Base64-encoded in the field `cxml-base64`    Return address  OCI `HOOK_URL`   cXML `BrowserFormPost`    Editing an existing cart  OCI no edit mode; the buyer creates the cart again   cXML with `operation=edit` PunchCommerce restores the cart from the transmitted line items    Direct entry to an item (Level 2)  OCI call with `FUNCTION=DETAIL` and the item key   cXML call with `SelectedItem` and the item key, known as [PunchOut Level 2](https://www.punchcommerce.de/en/punchout-level-1-vs-level-2)    Additional fields  OCI `NEW_ITEM-CUST_FIELD1` to `NEW_ITEM-CUST_FIELD5`   cXML Extrinsic elements, five per line item in PunchCommerce    Order after approval  OCI outside the protocol, for example by email, IDoc or EDI   cXML optionally as an `OrderRequest` in the same standard    Versions  OCI OCI 4.0 and 5.0, with the same field mapping in PunchCommerce   cXML cXML 1.2    Implementation in PunchCommerce  OCI and cXML set up in under an hour, protocol selectable per customer, both on the Business plan at no extra charge

### Same content, different packaging

 In terms of content, both protocols transfer the same per line item: item number, description, quantity, unit and price with currency. Only the names differ: `NEW_ITEM-VENDORMAT` becomes `SupplierPartID`, `NEW_ITEM-UNIT` becomes `UnitOfMeasure`. The unit also follows a different convention: by default, PunchCommerce uses PCE for piece with OCI and EA with cXML, and translates entries such as “Stck.” automatically. The commodity code is required with cXML and optional with OCI. You still maintain your item data only once.

 Decision guide

Which protocol does your customer need?
---------------------------------------

Your customer’s first email usually already reveals which protocol is meant. What matters is what their procurement system expects, not what your shop can do. Three typical cases:

If your customer …

### says “SAP Ariba”

 → cXMLAriba expects a PunchOutSetupRequest with identities and a SharedSecret, which your customer enters in the Ariba supplier form. If the request runs through the Ariba Network, its identity appears in the Sender.

 [PunchOut for SAP Ariba](https://www.punchcommerce.de/en/punchout-sap-ariba) [Go to cXML PunchOut](https://www.punchcommerce.de/en/cxml-punchout)

If your customer …

### says “SAP SRM” or mentions a HOOK\_URL

 → OCIThe HOOK\_URL is the address the cart is returned to as a form, and a reliable sign of OCI. Your customer then only needs the URL, username and password from you. With SAP S/4HANA, OCI applies as long as your customer has not put SAP Ariba in front of it; more under [PunchOut for SAP S/4HANA](https://www.punchcommerce.de/en/punchout-sap-s4hana).

 [PunchOut for SAP SRM](https://www.punchcommerce.de/en/punchout-sap-srm) [Go to OCI PunchOut](https://www.punchcommerce.de/en/oci-punchout)

If your customer …

### names no protocol

 → ask for the procurement systemYou then set the protocol per customer. Until then, you can already fully prepare the catalog and prices.

#### How to ask

- name and version of the procurement system
- if a HOOK\_URL is mentioned: OCI
- if a Network ID or SharedSecret is mentioned: cXML

 [Procurement systems at a glance](https://www.punchcommerce.de/en/procurement-systems)

### One protocol per customer, one catalog for all

 The protocol applies per customer: one customer calls your catalog via OCI, another via cXML, both from the same range, without a second shop and without a second catalog. For both protocols, PunchCommerce includes a simulator that reproduces your customer’s procurement system; you use it to check the returned cart before your customer starts the first test.

PunchCommerce Business costs €49 per customer per month, plus VAT, for OCI and cXML alike. Without your own shop, the Hosted Catalog add-on is added at €50 per customer per month, also plus VAT.

 FAQ

Frequently asked questions about OCI and cXML
---------------------------------------------

What suppliers want to know when the customer names a protocol, or none.

 ###   My customer uses SAP S/4HANA. OCI or cXML? +

 If your customer buys directly in SAP S/4HANA, OCI applies; if they have put SAP Ariba in front of it, cXML applies. If in doubt, ask their IT. Until you have the answer, prepare the catalog, prices and customer in PunchCommerce; you set the protocol at the end. How to recognize this is shown on the page [PunchOut for SAP S/4HANA](https://www.punchcommerce.de/en/punchout-sap-s4hana).

###   My customer only said “PunchOut”. How do I find out the protocol? +

 Ask for the name and version of the procurement system. The documents your customer sends also help: if they mention a HOOK_URL, it is OCI. If they mention a Network ID, identity or SharedSecret, it is cXML. If both are open, ask which protocol your customer’s IT department prefers.

###   Is cXML the more modern protocol? Should I switch? +

 No, neither is more modern; both standards date from the same period. cXML is broader in scope and can exchange further documents besides the cart; for the PunchOut itself, both do the same. Switching on your own initiative brings you no advantage, because your customer would have to change their connection as well. Deliver the protocol their system expects, and only switch if they ask you to.

###   What happens if my customer later switches to cXML? +

 Then you switch the protocol for this customer in PunchCommerce and issue new credentials, that is identities and a SharedSecret instead of username and password. Catalog, prices and range remain unchanged. Your customer enters the new details in their procurement system, and then you test a cart together.

  Get started

 Your customer has decided. Deliver the right protocol today.
--------------------------------------------------------------

 €49 per customer per month, plus VAT, for OCI and cXML. Install the plugin or add items to the Hosted Catalog, choose the protocol, send the credentials to your customer, done.

 [ Start free trial ](https://www.punchcommerce.de/register)30 days free · no credit card · cancel anytime

 ![Patrick Dornbusch, founder of PunchCommerce](https://www.punchcommerce.de/static/patrick-dornbusch.webp)Patrick Dornbusch

Founder of PunchCommerce

Prefer to talk first? In 30 minutes we’ll work out which option suits your shop, your ERP and your customers’ procurement systems.

 [ Schedule a consultation  (opens in a new window) ](https://account.netzdirektion.de/appointments/punchcommerce)30 min · remote · with the founder

 PunchCommerce® is a product of [ ![netzdirektion | Gesellschaft für digitale Wertarbeit mbH](https://www.punchcommerce.de/static/netzdirektion-logo.png) (opens in a new window) ](https://netzdirektion.de) ![DEKRA seal: quality management according to ISO 9001](https://www.punchcommerce.de/static/dekra-netzdirektion-iso-9001.png) **ISO 9001:2015**
certified quality management

 netzdirektion | Gesellschaft für digitale Wertarbeit mbH · © 2020 - 2026
