# Punchouts

With Punchout Catalogs, Fairmarkit allows requestors to access and shop from external supplier catalogs directly through the platform using cXML punchout integration. This reduces context switching and provides a unified intake experience across hosted, standard, and punchout catalogs.

{% hint style="info" %}
**Access**: To manage punchout catalogs, you must be assigned the **Admin** role and have the Punchout Catalogs feature enabled.
{% endhint %}

## Using Punchouts in Intake

As a requestor, you can browse punchout catalogs directly from the **Ask KIT** flow. Punchout catalogs can be used alongside hosted catalogs and redirect you to the supplier’s shopping site. Items you add to the cart return automatically to Fairmarkit for submission.

#### Start a New Request

{% stepper %}
{% step %}
Navigate to Ask KIT (Intake) and type in your request.

<figure><img src="/files/Nj0wf97yUqvM7UML0N2q" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Upload any supporting details via the file and click **Get Started**.
{% endstep %}
{% endstepper %}

#### Confirm Pre Triage Elements

<figure><img src="/files/hdJq5htuIuV9GqL1fW8v" alt=""><figcaption></figcaption></figure>

{% stepper %}
{% step %}

#### Confirm Request Type and Category Recommendation

AI will predict the correct request type and category, but validation is always recommended.
{% endstep %}

{% step %}

#### Select Purchasing Location

Select the correct location where your purchase will be shipped to/delivered at for the correct punchouts to be recommended.
{% endstep %}
{% endstepper %}

### Browse Recommended Punchouts & Launch

Review the recommended punchouts choose the one that applies to your purchase. If none apply, move on to the next step without selecting one.

{% stepper %}
{% step %}

#### Select and Launch

<figure><img src="/files/EYUxJ9le4fzxQCxHCapK" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Checking out with Punchout (Different depending on Punchout)

<figure><img src="/files/vwN2dQecDppjmzcSSC3g" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Return Items and Submit Request

<figure><img src="/files/VXojeqHb0jrlP1rnb78G" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## Managing Punchout Catalogs

Admins can manage punchout catalog configurations directly from the Fairmarkit admin console. This includes adding new catalogs, editing connection settings, testing punchouts, and assigning visibility by business unit or region.

#### Add New Punchout

{% stepper %}
{% step %}

#### Navigate to the Punchout Catalogs Tab in the Admin Experience and Click Create Catalog

<figure><img src="/files/5kCq45EbCJmrbFOXOwpK" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Add Punchout Catalog Details

<figure><img src="/files/6Y0jLPVyvMAa4fXNIV8M" alt="" width="188"><figcaption></figcaption></figure>

{% hint style="info" %}
Ask your supplier for these details, as they will have these details available for punchout setup for other systems as well.
{% endhint %}

#### **Detail Descriptions**

**Title:** Name of the Punchout

**Description:** Provide a written description of when this punchout should be used. The AI recommendation will use this to recommend the punchout.

**From Domain:** Identifies the type of identity (e.g., DUNS, NetworkID) used by the buyer's system when initiating the punchout. This helps the supplier know how to interpret the buyer's identity.

**To Domain:** Specifies the type of identity used by the supplier's system. It tells the buyer how to interpret the supplier's identity in the response.

**From Identity:** A unique identifier (like a DUNS number or custom ID) that represents the buyer's system. It's used by the supplier to authenticate and authorize the incoming punchout request.

**To Identity:** A unique identifier for the supplier’s system that the buyer uses to direct the punchout request. It ensures the message reaches the correct supplier endpoint.

**Sender Domain:** Indicates the identity type of the system sending the cXML message, often reflecting the platform or protocol used (e.g., email, NetworkID).

**Sender Identity:** The actual ID of the sender system or user initiating the punchout request—commonly an email address, user ID, or system identifier.

**Setup Request URL:** The URL endpoint provided by the supplier where the cXML punchout setup request should be sent to initiate a punchout session.

**Shared Secret:** A confidential string known to both buyer and supplier used to authenticate the punchout connection and ensure secure communication.

**Supplier:** Select the relevant supplier to be associated with this punchout.
{% endstep %}
{% endstepper %}

### Managing Existing Punchouts

{% stepper %}
{% step %}

#### Editing Existing Punchout Details

<figure><img src="/files/b51jxkwKByq0A2LoG6SD" alt=""><figcaption></figcaption></figure>

Click the menu next to the punchout you want to manage. When clicking edit you can edit all the connection details, the description and title of the punchout
{% endstep %}

{% step %}

#### Clone Punchout&#x20;

Cloning a punchout brings across all the details ready for editing.
{% endstep %}

{% step %}

#### Active/Deactivate

Deactivating a punchout will no longer make it available for use in Intake
{% endstep %}

{% step %}

#### Test Punchout

The test punchout flow will open up the punchout with the currently logged in user for testing. Upon successful checkout, a pop up will show up with the items successfully brought back.
{% endstep %}
{% endstepper %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fairmarkit.com/buyers/administration/punchouts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.