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.
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
Navigate to Ask KIT (Intake) and type in your request.

Upload any supporting details via the file and click Get Started.
Confirm Pre Triage Elements

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.
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
Add Punchout Catalog Details

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.
Managing Existing Punchouts
Last updated
Was this helpful?