cXML PunchOut explained: process, credentials, cart | PunchCommerce                       ![](//analytics.punchcommerce.de/matomo.php?idsite=1&rec=1)

  [Skip to content](#main-content)

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

 Your customer buys through SAP Ariba, Coupa or Jaggaer and asks for a cXML catalog that returns the cart from your range to their system as an XML message. This page explains the process, the credentials and the cart message – and how you deliver the cXML PunchOut 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

  supported version cXML 1.2

 setup, no IT project &lt; 1 h

 free trial 30 days

 What is cXML

 Commerce eXtensible Markup Language: business documents as XML
----------------------------------------------------------------

In short

 cXML is SAP Ariba’s PunchOut standard: the procurement system signs in directly with your server using identities and a SharedSecret, the buyer shops in the browser, and the cart goes back as an XML document. The order follows after approval, optionally as a cXML document as well.

 A cXML 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 then returns the cart as an XML document in cXML format. cXML stands for Commerce eXtensible Markup Language. Ariba published the standard in the late 1990s to exchange catalogs, orders and other business documents between purchasing and suppliers. Today Ariba is part of SAP. cXML is the standard PunchOut protocol of SAP Ariba and is also supported by [PunchOut for Coupa](https://www.punchcommerce.de/en/punchout-coupa), [PunchOut for Jaggaer](https://www.punchcommerce.de/en/punchout-jaggaer) and many other purchasing platforms. What a PunchOut is regardless of the protocol is covered in the [PunchOut basics](https://www.punchcommerce.de/en/punchout).

 A cXML PunchOut uses two channels. First, the systems talk to each other directly: the procurement system sends your server a request with its credentials and receives an address where the shopping session starts. Only then does your catalog open in the buyer’s browser; if the request contains a SelectedItem, the item page opens directly, which procurement systems call [PunchOut Level 2](https://www.punchcommerce.de/en/punchout-level-1-vs-level-2). At the end, the cart goes back through the browser, as a complete cXML document in a form field.

 Because sender and recipient identify themselves with every request, cXML is stricter than simpler methods. Each side has its own identity, and a shared password, the SharedSecret, confirms the connection. This makes the setup slightly more involved, but it ensures that only your customer’s procurement system can open a session in your catalog.

 Many corporations rely on cXML because the same standard can later carry the approved order to you as a separate document, the OrderRequest. For the PunchOut itself, the exchange described on this page is sufficient. For comparison: in an [OCI PunchOut](https://www.punchcommerce.de/en/oci-punchout), login and cart run through the browser as simple form fields, without a direct connection between the servers. All differences at a glance: [OCI vs. cXML](https://www.punchcommerce.de/en/oci-vs-cxml).

### PunchOutSetupRequest and response

The procurement system’s request with credentials, session ID and return address. Your server replies with a status and the `StartPage` where the buyer lands. If the request contains a `SelectedItem`, they jump straight to the item.

### PunchOutOrderMessage

The cart as a cXML document: for each line item the item number, quantity, price, description, unit and commodity code, plus the total amount.

### Procurement systems with cXML

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

- [PunchOut for SAP Ariba](https://www.punchcommerce.de/en/punchout-sap-ariba)
- [PunchOut for SAP S/4HANA](https://www.punchcommerce.de/en/punchout-sap-s4hana)
- [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
- GEP SMART
- Workday Procurement
- Medius
- Ivalua

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

 Process

How a cXML PunchOut works
-------------------------

For the buyer, it is one click on your catalog. Between the systems, two messages travel directly and one through the browser:

1. 1 Procurement system### PunchOutSetupRequest

    The procurement system sends your server a cXML document with `From`, `To` and `Sender` including the `SharedSecret`, a `BuyerCookie` for the session and the `BrowserFormPost` address for the return.
2. 2 Your catalog### Authentication

    The `To` identity identifies you as the supplier, `From` and the `SharedSecret` identify your customer. If anything does not match, your server replies with a cXML error status instead of a session.
3. 3 Your catalog### PunchOutSetupResponse

    If successful, your server replies with status 200 and a `StartPage` URL. The procurement system opens this address in the buyer’s browser.
4. 4 Buyer### Catalog or shop

    The buyer sees your range with their prices, searches, compares and adds items to the cart just like in a regular online shop.
5. 5 Your catalog### PunchOutOrderMessage

    On transfer, your catalog generates the cart as a cXML document and sends it via an HTML form through the browser to the `BrowserFormPost` address.
6. 6 Procurement system### Purchase requisition

    The procurement system matches the message to the session via the `BuyerCookie` and creates a purchase requisition. Once it is approved, you receive the order.

 Elements and credentials

 What the request and the cart contain
---------------------------------------

 A cXML PunchOut consists of two documents you should know: the `PunchOutSetupRequest`, which starts the session, and the `PunchOutOrderMessage`, which brings back the cart. It contains one `ItemIn` element per line item. The “Per standard” column shows whether the cXML DTD, the schema of cXML, requires an element or leaves it optional.

 The “Filled by PunchCommerce” column shows which elements PunchCommerce evaluates in the request and which it fills in the cart by default. PunchCommerce always requires a `SharedSecret` in the Sender credential and sends the cart to the address from `BrowserFormPost`. It processes the operations `create` for a new cart and `edit` for an existing one. In its default configuration, PunchCommerce fills all required elements plus `LeadTime` and the manufacturer name, if available. You adjust the mapping per customer.

  cXML elements from PunchOutSetupRequest and PunchOutOrderMessage with classification per cXML DTD, filling by PunchCommerce, sample value and meaning   Element Per standard Filled by PunchCommerce Example Meaning     `PunchOutSetupRequest`: request and credentials    From  Required filled by PunchCommerce  Your customer’s identity, for example their Ariba Network ID.   Required   yes, in the default configuration   Your customer’s identity, for example their Ariba Network ID.    To  Required filled by PunchCommerce  Your identity as the supplier, as your customer has stored it in their system.   Required   yes, in the default configuration   Your identity as the supplier, as your customer has stored it in their system.    Sender  Required filled by PunchCommerce  Sender of the request with identity and user agent. If the request runs through a network such as the Ariba Network, the network appears here.   Required   yes, in the default configuration   Sender of the request with identity and user agent. If the request runs through a network such as the Ariba Network, the network appears here.    Credential domain + Identity  Required filled by PunchCommerce  Example: NetworkID Every identity consists of a domain such as NetworkID or DUNS and the actual value.   Required   yes, in the default configuration  NetworkID Every identity consists of a domain such as NetworkID or DUNS and the actual value.    SharedSecret  optional filled by PunchCommerce  Shared password in the Sender credential. The DTD alternatively allows other methods; PunchCommerce always requires it.   optional   yes, in the default configuration   Shared password in the Sender credential. The DTD alternatively allows other methods; PunchCommerce always requires it.    BuyerCookie  Required filled by PunchCommerce  Session ID of the procurement system. It must come back unchanged in the cart.   Required   yes, in the default configuration   Session ID of the procurement system. It must come back unchanged in the cart.    BrowserFormPost  optional filled by PunchCommerce  Address to which the browser sends the cart at the end.   optional   yes, in the default configuration   Address to which the browser sends the cart at the end.    operation  Required filled by PunchCommerce  Example: create Type of session: `create` for a new cart, `edit` for an existing one.   Required   yes, in the default configuration  create Type of session: `create` for a new cart, `edit` for an existing one.     `PunchOutOrderMessage`: cart    ItemIn quantity  Required filled by PunchCommerce  Example: 2 Quantity of the line item.   Required   yes, in the default configuration  2 Quantity of the line item.    SupplierPartID  Required filled by PunchCommerce  Example: 4711-09 Your item number. It lets you match the later order.   Required   yes, in the default configuration  4711-09 Your item number. It lets you match the later order.    SupplierPartAuxiliaryID  optional  Additional key if the item number alone is not unique.   optional   –no, only via mapping   Additional key if the item number alone is not unique.    UnitPrice / Money currency  Required filled by PunchCommerce  Example: 12.90 EUR Price per unit with the currency as an ISO code.   Required   yes, in the default configuration  12.90 EUR Price per unit with the currency as an ISO code.    Description xml:lang  Required filled by PunchCommerce  Example: en-US Item description with language code, for example en-US.   Required   yes, in the default configuration  en-US Item description with language code, for example en-US.    UnitOfMeasure  Required filled by PunchCommerce  Example: EA Unit of measure per UN/CEFACT Recommendation 20, for example EA for each.   Required   yes, in the default configuration  EA Unit of measure per UN/CEFACT Recommendation 20, for example EA for each.    Classification domain  Required filled by PunchCommerce  Example: UNSPSC 46181504 Commodity code based on a classification standard, usually UNSPSC.   Required   yes, in the default configuration  UNSPSC 46181504 Commodity code based on a classification standard, usually UNSPSC.    ManufacturerPartID  optional  Manufacturer’s item number.   optional   –no, only via mapping   Manufacturer’s item number.    LeadTime  optional filled by PunchCommerce  Example: 3 Lead time in days.   optional   yes, in the default configuration  3 Lead time in days.    Total  Required filled by PunchCommerce  Total amount of the cart in the message header.   Required   yes, in the default configuration   Total amount of the cart in the message header.

### What a cart line item looks like

 A shortened excerpt from a `PunchOutOrderMessage`. PunchCommerce sends the complete document Base64-encoded in the form field `cxml-base64`; the specification alternatively provides the field `cxml-urlencoded`.

 ```

[1]     4711-09

[2]     12.90
        Nitrile protective glove, size 9
[3]     EA
[4]     46181504
[5]     3

```

1. Your item number, which lets you match the later order.
2. Price per unit, net, with the currency as an ISO code.
3. Unit of measure as a UN/CEFACT code; EA stands for each.
4. Commodity code per UNSPSC.
5. Lead time in days.

 Implementation

How to deliver cXML with PunchCommerce
--------------------------------------

You neither have to implement the protocol yourself nor hire an agency. PunchCommerce accepts the PunchOutSetupRequest, checks the identities and the SharedSecret, answers the request, shows your range and builds the PunchOutOrderMessage at the end. 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 cXML message 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)

### Credentials for your customer

- PunchOut URL, which you receive from PunchCommerce
- Domain and identity, which you define per customer
- SharedSecret, which you assign per customer
- Buyer identity, which your customer gives you
- A contact in your customer’s IT department who stores the details in the procurement system
- The commodity code scheme your customer expects

 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 cXML PunchOut
----------------------------------------------

What suppliers want to know before their first cXML catalog: SAP Ariba, troubleshooting, testing, additional fields and costs.

 ###   My customer buys through SAP Ariba. What is different there? +

 Nothing about the protocol: SAP Ariba speaks cXML. Three things are Ariba-specific: your identity is your Ariba Network ID (ANID), test and production accounts are separate in Ariba, and your customer must approve every published catalog version before their buyers see it. Supplier account, test account and troubleshooting in detail: [PunchOut for SAP Ariba](https://www.punchcommerce.de/en/punchout-sap-ariba).

###   The request is rejected. What is usually the cause? +

 Almost always the credentials do not match: an identity spelled differently, a SharedSecret altered while copying, or a different buyer identity than agreed. In these cases, PunchCommerce responds with cXML status 401 and a plain-text message in the procurement system’s log. Then check the To identity, the From identity and the SharedSecret character by character against the values in PunchCommerce.

###   My customer uses two procurement systems. Do I need a second catalog? +

 No. Range, prices and shop stay the same. Each connection gets its own credentials in PunchCommerce and, if needed, its own field mapping, because two systems rarely expect the same details. This also applies if one system speaks OCI and the other cXML. For the buyer, the catalog looks the same in both cases.

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

 PunchCommerce includes a simulator that creates a PunchOutSetupRequest with the respective customer’s credentials and takes on the role of the procurement system. You go through the session like a buyer, transfer the cart and then see the complete PunchOutOrderMessage. This lets you check item numbers, units and commodity codes before your customer’s IT department starts the first real test.

###   Can I transfer additional details such as cost center or contract number? +

 Yes. cXML provides Extrinsic elements for this, freely named additional fields per line item. PunchCommerce offers you five such fields, which you fill per customer with fixed values or data from your item master. Your customer specifies which names and contents are expected, often in a short connection specification from their purchasing department.

###   What does a cXML PunchOut with PunchCommerce cost? +

 The same price applies to the cXML PunchOut as to every other protocol: €49 per connected customer per month on the Business plan, plus VAT. Whether your customer connects via SAP Ariba, Coupa or Jaggaer makes no difference, and there is no surcharge for cXML. Without your own shop, the Hosted Catalog add-on is added at €50 per customer per month, plus VAT. You test the first 30 days free of charge and without a credit card.

  Get started

 Your customer is waiting for the cXML 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
