OCI PunchOut explained: process, fields and setup | PunchCommerce                       ![](//analytics.punchcommerce.de/matomo.php?idsite=1&rec=1)

  [Skip to content](#main-content)

  Know-how · OCI OCI PunchOut explained. Deliver your OCI catalog in under an hour.
====================================================================

 Your customer wants to jump from their SAP system or another procurement solution straight into your range and take the cart back as a purchase requisition. This page explains how an OCI PunchOut works, which data is transferred and how you deliver it without an IT project: with or without your own online shop.

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

30 days free · no credit card · cancel anytime

  OCI versions 4.0 &amp; 5.0

 setup, no IT project &lt; 1 h

 free trial 30 days

 What is OCI

 Open Catalog Interface: the link between purchasing and the supplier catalog
------------------------------------------------------------------------------

In short

 OCI is SAP’s PunchOut standard: the buyer jumps from their procurement system into your catalog and sends the cart back through the browser to a return address as form fields. No order is created at this point; it follows once the requisition has been approved in your customer’s system.

 An OCI PunchOut is a process in which a buyer switches from their procurement system to a supplier’s [PunchOut catalog](https://www.punchcommerce.de/en/punchout-catalog) and returns the cart as form fields via SAP’s Open Catalog Interface (OCI). SAP defined the interface in the late 1990s so that buyers can use external supplier catalogs without first importing and maintaining the catalog data. The buyer opens your catalog, searches and compares there with your current prices and descriptions and, at the end, adds only what they actually want to order.

 The word PunchOut describes exactly this jump: the user “punches out” of their system into your catalog and returns with a filled cart. No order is created at this point. Your customer receives a purchase requisition that runs through their internal approvals. Only then do they send you the actual order, for example by email or as an electronic message from their SAP system (IDoc or EDI). How the process works regardless of the protocol is explained on the page “[What is PunchOut?](https://www.punchcommerce.de/en/punchout)”.

 Purchasing departments insist on OCI because of their processes: every order is meant to go through the same approvals, to the right cost center and with traceable prices. Orders by email, phone or fax bypass these processes. With your OCI catalog, the buyer stays in their familiar process, and you no longer have to create and send catalog files that are already outdated at the next price change.

 Technically, OCI is deliberately simple. Communication runs over ordinary HTTPS in the buyer’s browser. There is no permanent server-to-server connection and no XML document, just form fields with fixed names. This simplicity is why OCI is so widespread in German-speaking countries – and also the reason for a few quirks you will meet further down in the process and the fields.

 For comparison: in a [cXML PunchOut](https://www.punchcommerce.de/en/cxml-punchout), the other widely used PunchOut method, the cart is transferred as an XML document, and cXML can also exchange orders, whereas OCI is limited to handing over the cart via a form. All differences at a glance: [OCI vs. cXML](https://www.punchcommerce.de/en/oci-vs-cxml).

### OCI 4.0

The most widespread version and the standard in SAP SRM, the classic SAP purchasing system. Cart and return run via HTML form fields. If your customer just says “OCI”, they usually mean this version.

### OCI 5.0

The newer version of the interface. PunchCommerce supports OCI 4.0 and 5.0 with the same field mapping, so you don’t have to maintain anything twice.

### Procurement systems with OCI

A selection of the systems from which your customers start a OCI PunchOut; linked systems have their own page on connecting them:

- [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)
- [PunchOut for Onventis](https://www.punchcommerce.de/en/punchout-onventis)
- [PunchOut for Coupa](https://www.punchcommerce.de/en/punchout-coupa)
- [PunchOut for Jaggaer](https://www.punchcommerce.de/en/punchout-jaggaer)
- Oracle Procurement
- Basware
- Synertrade
- Proactis
- Unite (formerly Mercateo)
- Ivalua
- AskLio

Which protocol other systems speak: [procurement systems at a glance](https://www.punchcommerce.de/en/procurement-systems).

 Process

How an OCI PunchOut works
-------------------------

From the click in the procurement system to the purchase requisition, the buyer often needs only a few minutes. Behind the scenes, this is what happens:

1. 1 Buyer### Call with HOOK\_URL

    The buyer clicks on your catalog in their system. The browser calls your PunchOut URL with username, password and the `HOOK_URL` that the cart will later be sent back to.
2. 2 Your catalog### Authentication

    Your catalog checks the credentials, identifies the customer from them and keeps the `HOOK_URL` and target window for the whole session.
3. 3 Buyer### Catalog or shop

    The buyer sees your range with their customer prices and searches, filters and compares just like in a regular online shop.
4. 4 Buyer### Cart

    They add items to the cart and click “Transfer”. Nothing is paid, and no order is created yet.
5. 5 Your catalog### Return via form

    Your catalog generates an invisible HTML form with the `NEW_ITEM-` fields for each line item and sends it via POST to the `HOOK_URL`.
6. 6 Procurement system### Purchase requisition

    The procurement system reads the fields and creates a purchase requisition. Once it is approved, you receive the order.

 The OCI fields

 Which data is transferred on return
-------------------------------------

 OCI transfers each cart line item as a set of form fields. Every field name starts with `NEW_ITEM-` and carries the line number in square brackets, so `NEW_ITEM-QUANTITY[1]` is the quantity of the first line item. The long text follows its own notation with the line number and line length in the name.

 PunchCommerce processes all 34 fields with the `NEW_ITEM-` prefix of OCI 4.0 and 5.0, so besides the fields in the table also `NEW_ITEM-ATTACHMENT`, `NEW_ITEM-EXT_CATEGORY_ID`, `NEW_ITEM-EXT_SCHEMA_TYPE`, `NEW_ITEM-CONTRACT` as well as `NEW_ITEM-ITEM_TYPE` and `NEW_ITEM-PARENT_ID` for bills of materials. The “Per standard” column shows which fields OCI lists as required, the “PunchCommerce” column that every field is supported and which fields are already filled in the default configuration (Default): all required fields plus `NEW_ITEM-VENDORMAT`, `NEW_ITEM-EXT_PRODUCT_ID` and `NEW_ITEM-LEADTIME`. Every other field you assign in the field mapping per customer, with a value from your item data or a fixed value. Which fields your customer actually expects is up to them. You often receive a short specification from their purchasing department. You adjust the mapping in PunchCommerce without changing anything in your shop.

  OCI cart fields with classification per standard, support by PunchCommerce, sample value and meaning   Field Per standard PunchCommerce Example Meaning      NEW\_ITEM-DESCRIPTION  Required supported, Defaultfilled by default  Example: Nitrile protective glove, size 9 Short text of the item. The field is limited to 40 characters; PunchCommerce shortens longer titles automatically.   Required    supported, Defaultfilled by default   Nitrile protective glove, size 9 Short text of the item. The field is limited to 40 characters; PunchCommerce shortens longer titles automatically.    NEW\_ITEM-QUANTITY  Required supported, Defaultfilled by default  Example: 2 Quantity of the line item.   Required    supported, Defaultfilled by default   2 Quantity of the line item.    NEW\_ITEM-UNIT  Required supported, Defaultfilled by default  Example: PCE Unit of measure as an ISO code, for example PCE for piece. PunchCommerce translates entries such as “pcs.” into the code.   Required    supported, Defaultfilled by default   PCE Unit of measure as an ISO code, for example PCE for piece. PunchCommerce translates entries such as “pcs.” into the code.    NEW\_ITEM-PRICE  Required supported, Defaultfilled by default  Example: 12.90 Price per price unit, as agreed between you and your customer.   Required    supported, Defaultfilled by default   12.90 Price per price unit, as agreed between you and your customer.    NEW\_ITEM-CURRENCY  Required supported, Defaultfilled by default  Example: EUR Currency as an ISO code, for example EUR.   Required    supported, Defaultfilled by default   EUR Currency as an ISO code, for example EUR.    NEW\_ITEM-VENDORMAT  optional supported, Defaultfilled by default  Example: 4711-09 Your item number. It lets you match the later order to your item.   optional    supported, Defaultfilled by default   4711-09 Your item number. It lets you match the later order to your item.    NEW\_ITEM-EXT\_PRODUCT\_ID  optional supported, Defaultfilled by default  Unique key of the item in the catalog. Required so that the procurement system can later display the item in the catalog again or check its price.   optional    supported, Defaultfilled by default    Unique key of the item in the catalog. Required so that the procurement system can later display the item in the catalog again or check its price.    NEW\_ITEM-LEADTIME  optional supported, Defaultfilled by default  Example: 3 Delivery time in days.   optional    supported, Defaultfilled by default   3 Delivery time in days.    NEW\_ITEM-PRICEUNIT  optional supported,  Example: 100 Price unit if the price does not apply per piece, for example per 100 pieces.   optional    supported,   100 Price unit if the price does not apply per piece, for example per 100 pieces.    NEW\_ITEM-MATGROUP  optional supported,  Material group according to your customer’s scheme, often based on a classification standard such as eCl@ss or UNSPSC.   optional    supported,    Material group according to your customer’s scheme, often based on a classification standard such as eCl@ss or UNSPSC.    NEW\_ITEM-MATNR  optional supported,  Material number in your customer’s system. Only fill it if the customer provides it to you.   optional    supported,    Material number in your customer’s system. Only fill it if the customer provides it to you.    NEW\_ITEM-MANUFACTMAT  optional supported,  Manufacturer’s item number, complemented by `NEW_ITEM-MANUFACTCODE` for the manufacturer.   optional    supported,    Manufacturer’s item number, complemented by `NEW_ITEM-MANUFACTCODE` for the manufacturer.    NEW\_ITEM-LONGTEXT  optional supported,  Detailed description as plain text, without HTML formatting.   optional    supported,    Detailed description as plain text, without HTML formatting.    NEW\_ITEM-CUST\_FIELD1–5  optional supported,  Five freely assignable fields for details your customer additionally requires, such as cost center or contract number.   optional    supported,    Five freely assignable fields for details your customer additionally requires, such as cost center or contract number.

### What a cart line item looks like

 The form fields of one line item, as they are sent via POST to the `HOOK_URL`. Every field carries the line number in square brackets; further line items follow with `[2]`, `[3]` and so on.

 ```
[1] NEW_ITEM-DESCRIPTION[1]=Nitrile protective glove, size 9
    NEW_ITEM-QUANTITY[1]=2
[2] NEW_ITEM-UNIT[1]=PCE
[3] NEW_ITEM-PRICE[1]=12.90
[4] NEW_ITEM-CURRENCY[1]=EUR
[5] NEW_ITEM-VENDORMAT[1]=4711-09
```

1. Short text, at most 40 characters; PunchCommerce shortens longer titles.
2. Unit of measure as an ISO code; PCE stands for piece.
3. Price per price unit, net, with a dot as the decimal separator.
4. Currency as an ISO code.
5. Your item number, which you use to match the later order.

### Additional functions via the `FUNCTION` parameter

 Besides regular purchasing, the procurement system can call the catalog with a specific intent. PunchCommerce recognizes these calls and responds accordingly:

### Direct entry to the item

`DETAIL` directly opens the detail page of an item transferred earlier. Prerequisite: `NEW_ITEM-EXT_PRODUCT_ID` was filled on the first return; PunchCommerce fills the field by default.

### Search with a search term

`SOURCING` starts a search in your catalog with a supplied search term.

### Search across several catalogs

`BACKGROUND_SEARCH` searches several catalogs at once without the buyer opening each of them.

### Check before the transfer

`VALIDATE` checks before the transfer whether price and availability are still correct. SAP S/4HANA uses the call if your customer switches it on.

 The direct entry is what procurement systems call [PunchOut Level 2](https://www.punchcommerce.de/en/punchout-level-1-vs-level-2). How SAP SRM uses these calls and which indicators your customer sets for them is shown on the page [PunchOut for SAP SRM](https://www.punchcommerce.de/en/punchout-sap-srm); what else applies to SAP S/4HANA on the page [PunchOut for SAP S/4HANA](https://www.punchcommerce.de/en/punchout-sap-s4hana).

### Pitfalls from practice

- At the customer’s end, the catalog often runs in an embedded window. Security headers and cookies must be set in a way that lets the browser allow the session.
- Prices, units and short texts must arrive in exactly the expected format, otherwise the procurement system rejects the line item or imports it incorrectly.

PunchCommerce takes care of both.

 Implementation

How to deliver OCI with PunchCommerce
-------------------------------------

You neither have to implement the protocol yourself nor hire an agency. PunchCommerce accepts the call from the procurement system, checks the credentials, shows your range and sends the cart back in the correct OCI format. All you decide is where the items come from. Setup usually takes under an hour, and hosting is GDPR-compliant in Germany.

 With your own online shop### Install the plugin, create the customer, done

Ready-made plugins are available for nine shop systems, including [PunchOut for Spryker](https://www.punchcommerce.de/en/spryker), [PunchOut for Shopware](https://www.punchcommerce.de/en/punchout-shopware), [PunchOut for Magento](https://www.punchcommerce.de/en/punchout-magento), [PunchOut for Vendure](https://www.punchcommerce.de/en/punchout-vendure), [PunchOut for JTL-Shop](https://www.punchcommerce.de/en/punchout-jtl) and [PunchOut for Medusa](https://www.punchcommerce.de/en/punchout-medusa). Your customer jumps directly into your existing shop and sees their prices and the range you make available to them there. PunchCommerce handles the return and translates the cart into the OCI fields your customer expects.

PunchCommerce Business: €49 per customer per month, plus VAT.

 [See plugins for your shop system](https://www.punchcommerce.de/en/integrations)

 Without your own online shop### Provide items in the Hosted Catalog

You don’t have a shop or don’t want to connect it? Then upload your items as a list to the PunchCommerce Hosted Catalog. Your customer jumps into this catalog, makes a selection and transfers the cart just as with a shop. You define customer-specific ranges and prices per customer.

Business plus the Hosted Catalog add-on for €50 per customer per month, each plus VAT.

 [See the Hosted Catalog](https://www.punchcommerce.de/en/hosted-catalog)

### What you should prepare

- Item numbers, units and the prices agreed with the customer
- PunchOut URL plus the username and password you create for the customer in PunchCommerce
- A contact in your customer’s IT department who enters URL and credentials in the procurement system
- Your customer’s OCI version: 4.0 or 5.0
- Fields your customer additionally expects, such as material group or cost center
- A joint test date with your customer’s purchasing department

 You connect many corporate customers and need an SLA and dedicated infrastructure? Then the [make-or-buy analysis](https://www.punchcommerce.de/en/punchout-make-or-buy) compares in-house development and PunchCommerce Enterprise over five years.

 Which data flows in the process and how to answer your customer’s security questionnaire is explained on the page [PunchOut security and data protection](https://www.punchcommerce.de/en/punchout-security).

 FAQ

Frequently asked questions about OCI PunchOut
---------------------------------------------

What suppliers want to know before their first OCI catalog: requirements, testing, customer requests and costs.

 ###   My customer uses SAP Ariba. Is an OCI catalog enough? +

 No. SAP Ariba works with cXML, not OCI. For you, this changes little: PunchCommerce Business includes OCI and cXML, and you choose the protocol per customer. Your shop or Hosted Catalog stays the same; only the format of the return changes. So always ask your customer first which protocol and which version their procurement system expects.

###   What do I need to send my customer for the OCI catalog? +

 Your customer needs the PunchOut URL plus a username and a password, which you create for them in PunchCommerce. Their IT department stores these details in the catalog configuration of the procurement system. If the customer asks for further parameters, such as a specific OCI version or additional fields, it is best to clarify this with their purchasing department before the first test.

###   How do I test the OCI PunchOut before my customer uses it? +

 PunchCommerce includes a simulator that reproduces the call from a procurement system. You use it to start a session, add items to the cart and then see exactly which fields would be sent back with which values. This lets you spot missing item numbers, wrong units or overly long short texts before your customer transfers the first real cart.

###   Can I show a customer different prices or a smaller range? +

 Yes. Every customer logs in with their own credentials, so the catalog knows who is buying. In the shop, your existing customer prices and customer groups apply; in the Hosted Catalog, you define range and prices per customer. Many purchasing departments expect exactly that: they only want to see the agreed items on the agreed terms, not your entire offering. How wholesalers organise this for many customers is shown in [PunchOut for wholesalers](https://www.punchcommerce.de/en/punchout-wholesale).

###   My customer requires their own field assignment. Is that a problem? +

 No, that is the norm. Many companies expect additional details, such as a material group according to their scheme, a contract number or a specific format for the unit. In PunchCommerce, you create a separate field mapping per customer and determine which value from your item data ends up in which OCI field. Nothing changes in your shop or your item maintenance.

###   How long does it take until the OCI PunchOut is live? +

 Your side is usually set up in under an hour: install the plugin or import items, create the customer, send the credentials. The overall duration mostly depends on your customer, because their IT has to store and approve the catalog in the procurement system. In our experience, it helps to agree on a joint test date right at the first contact.

###   What does an OCI PunchOut with PunchCommerce cost? +

 PunchCommerce Business costs €49 per connected customer per month, plus VAT. It includes OCI 4.0 and 5.0 as well as cXML, so you do not pay per protocol. If you provide items without your own shop, the Hosted Catalog add-on is added at €50 per customer per month, also plus VAT. You can test it free for 30 days, without a credit card.

  Get started

 Your customer is waiting for the OCI catalog. Deliver it today.
-----------------------------------------------------------------

 €49 per customer per month, plus VAT; without your own shop, plus the Hosted Catalog add-on at €50 per customer per month. Install the plugin or add items to the Hosted Catalog, 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
