> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/partner-library/partner-components/punchout.md).

# B2B Punchout (cXML, OCI, IDS)

Let the procurement systems of your B2B customers shop in your Emporix storefront and send their purchase orders straight into Emporix.

With punchout, a buyer does not log in to your shop. They start in their own procurement system — SAP Ariba, Coupa, SAP SRM, JAGGAER and others — jump into your storefront, fill a cart and take that cart back with them. After approval, their system sends the purchase order, and it arrives in Emporix as a regular order.

This documentation takes you from buying the component to the first order, and then explains every menu entry of the Punchout Cockpit.

## What you get

| Part                                             | What it does                                                                            | Where you find it                                           |
| ------------------------------------------------ | --------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
| **Punchout Cockpit**                             | Setup, buyers, mappings, cart returns, orders and logs                                  | Management Dashboard, perspective **Punchout Cockpit**      |
| **Punchout Router**                              | Speaks cXML, OCI and IDS with the procurement systems and Emporix APIs with your tenant | Hosted service, your tenant is connected to it during setup |
| **Custom entities `ANT_PUNCHOUT_*`**             | Hold the punchout configuration and data in your tenant                                 | Settings → Custom Entities                                  |
| **Value stream “Punchout Trigger Confirmation”** | Connection check between the router and the Orchestration Engine                        | Value Streams                                               |

## How a punchout works

{% stepper %}
{% step %}

#### The buyer starts in the procurement system

The procurement system sends a setup request with the buyer's credentials to the router.
{% endstep %}

{% step %}

#### The router logs the buyer in

The router checks the credentials, signs the buyer in to Emporix and answers with a link into your storefront.
{% endstep %}

{% step %}

#### The buyer shops in your storefront

Your prices, your assortment, your search. Instead of a checkout, the storefront offers **Transfer cart**.
{% endstep %}

{% step %}

#### The cart goes back

The storefront hands the cart to the router, the router translates it into the format of the procurement system — units, classification codes and part numbers included.
{% endstep %}

{% step %}

#### The purchase order arrives

After approval, the procurement system sends the purchase order to the router. The router creates the order in Emporix.
{% endstep %}
{% endstepper %}

## Start here

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th align="center"></th><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><i class="fa-flag-checkered">:flag-checkered:</i></td><td align="center"><strong>Getting started</strong></td><td align="center">Four steps, each in one place of the Management Dashboard or your storefront.</td><td><a href="https://developer.emporix.io/partner-library/partner-components/punchout/getting-started.md">Getting started</a></td></tr><tr><td align="center"><i class="fa-gauge-high">:gauge-high:</i></td><td align="center"><strong>Punchout Cockpit</strong></td><td align="center">Every entry of the Punchout Cockpit, ordered from what you use daily to what you set once.</td><td><a href="https://developer.emporix.io/partner-library/partner-components/punchout/cockpit.md">Punchout Cockpit</a></td></tr><tr><td align="center"><i class="fa-book">:book:</i></td><td align="center"><strong>Reference</strong></td><td align="center">Facts to look up — addresses, scopes, events and what to do when something fails.</td><td><a href="https://developer.emporix.io/partner-library/partner-components/punchout/reference.md">Reference</a></td></tr></tbody></table>

## Supported protocols

| Protocol | Typical systems                   | Punchout                                      | Purchase order |
| -------- | --------------------------------- | --------------------------------------------- | -------------- |
| **cXML** | SAP Ariba, Coupa, JAGGAER, Oracle | PunchOutSetupRequest                          | OrderRequest   |
| **OCI**  | SAP SRM, SAP ERP                  | Login with `USERNAME`, `PASSWORD`, `HOOK_URL` | —              |
| **IDS**  | IDS Connect (German wholesale)    | Login and cart return                         | —              |

A new site starts with cXML. Further protocols are switched on per site under [Site Settings](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/settings/site-settings.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.emporix.io/partner-library/partner-components/punchout.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
