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

# Getting started

Four steps, each in one place of the Management Dashboard or your storefront.

First get the component in the Partner Library — see [Purchase Component](https://developer.emporix.io/partner-library/customers-flow/purchase-component.md). Then work through the steps in this order. Each page is grouped by the menu entry you click, and each step ends with something you can see.

| Step                                                                                                                               | Where you work                                             | What you have afterwards                                                               |
| ---------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| 1. [Set up punchout](https://developer.emporix.io/partner-library/partner-components/punchout/getting-started/setup.md)            | Punchout Cockpit → **Setup**                               | Tenant connected to the router, first buyer with its credentials                       |
| 2. [Adjust the storefront](https://developer.emporix.io/partner-library/partner-components/punchout/getting-started/storefront.md) | Your storefront code                                       | A punchout entry that logs the buyer in, and **Transfer cart** instead of the checkout |
| 3. [First punchout](https://developer.emporix.io/partner-library/partner-components/punchout/getting-started/first-punchout.md)    | Punchout Cockpit → **Setup** and **Punchout Cart Returns** | A cart that travelled from your storefront back to the buyer                           |
| 4. [First order](https://developer.emporix.io/partner-library/partner-components/punchout/getting-started/first-order.md)          | Punchout Cockpit → **Setup** and **Punchout Orders**       | An Emporix order created from a purchase order                                         |

## What you need before you start

* A user of the Management Dashboard who may manage access controls and groups in the tenant. The setup creates two groups for punchout.
* Access to the **Developer Portal** of the tenant for two API keys. [Step 1](https://developer.emporix.io/partner-library/partner-components/punchout/getting-started/setup.md#what-you-need) tells you which.
* Someone who can change the storefront. [Step 2](https://developer.emporix.io/partner-library/partner-components/punchout/getting-started/storefront.md) is the only step with code.

{% hint style="info" %}
Step 1 needs no code and no access to the router. If your storefront is the Emporix B2B showcase storefront, step 2 is already done.
{% 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/getting-started.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.
