> 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/cockpit.md).

# Punchout Cockpit

Every entry of the Punchout Cockpit, ordered from what you use daily to what you set once.

The cockpit is a perspective of the Management Dashboard. Its entries are listed here in the order of the sidebar, which is also the order from simple to advanced.

## Daily work

| Entry                                                                                                                     | What it is for                                         |
| ------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ |
| [Overview](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/overview.md)                  | Counts, the latest cart returns, orders and errors     |
| [Punchout Cart Returns](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/cart-returns.md) | Every cart a buyer took back to the procurement system |
| [Punchout Orders](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/orders.md)             | Every purchase order and the Emporix order it became   |

## Buyers

| Entry                                                                                                               | What it is for                                                            |
| ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| [Punchout Customers](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/customers.md) | The buyer organisations, their protocols and shared secrets               |
| [Punchout Users](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/users.md)         | Accounts of single requisitioners, if a buyer uses one account per person |

## Mapping

Needed when a buyer's system expects other units, codes or part numbers than your store uses.

| Entry                                                                                                                                | What it is for                      |
| ------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------- |
| [UOM Mapping](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/mapping/uom.md)                       | Units of measure of the buyer       |
| [Classification Mapping](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/mapping/classification.md) | UNSPSC and eClass codes in the cart |
| [Buyer Part Numbers](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/mapping/buyer-part-numbers.md) | The buyer's own material numbers    |

## Advanced Mapping

Needed when a buyer asks for further fields, own delivery addresses or special order rules.

| Entry                                                                                                                                   | What it is for                                                      |
| --------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| [Field Mapping](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/advanced-mapping/field-mapping.md)     | Further fields in the cart return                                   |
| [Address Mapping](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/advanced-mapping/address-mapping.md) | Buyer address codes and the Emporix company of a buyer              |
| [Order Fields](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/advanced-mapping/order-fields.md)       | Buyer fields written into the Emporix order                         |
| [Order Handling](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/advanced-mapping/order-handling.md)   | Payment, shipping, price check and unknown items of purchase orders |

## Settings

| Entry                                                                                                                           | What it is for                                                       | Who sees it        |
| ------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | ------------------ |
| [Tenant Settings](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/settings/tenant-settings.md) | Router, access for employees, Emporix objects, value stream receiver | ANT Punchout Admin |
| [Site Settings](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/settings/site-settings.md)     | Sites, storefront URL, protocols and processors                      | ANT Punchout Admin |
| [Logs](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/settings/logs.md)                       | Every request the router handled                                     | everyone           |
| [Audit log](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/settings/audit-log.md)             | Who changed what                                                     | everyone           |

## Tools

| Entry                                                                                                          | What it is for                                              | Who sees it        |
| -------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ------------------ |
| [Open Router](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/open-router.md) | The router's own admin with testers for punchout and orders | ANT Punchout Admin |
| [Setup](https://developer.emporix.io/partner-library/partner-components/punchout/getting-started/setup.md)     | The three setup steps                                       | ANT Punchout Admin |

{% hint style="info" %}
**Scope of a mapping.** Every mapping table is per site: pick the site at the top of the page. A row applies to all customers, to a group of customers, or to one customer — the most specific row wins. The group is the tag you give a customer under [Punchout Customers](https://developer.emporix.io/partner-library/partner-components/punchout/cockpit/customers.md).
{% endhint %}

{% hint style="info" %}
**Changes apply within 30 seconds.** The cockpit stores everything in your tenant; the router picks a change up within half a minute.
{% endhint %}


---

# 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/cockpit.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.
