{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":50251,"path":"source-to-pay-operations/sourcing-and-procurement-operations/configure-supplier-punchout.md","title":"Configure punchout for third-party site purchases","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure punchout for third-party site purchases\n\nSet up punchout configuration to allow shoppers or employees to make third-party site purchases​.\n\n## Before you begin\n\nRole required: sn\\_shop.procurement\\_administrator\n\n## Procedure\n\n1.  Navigate to **All** &gt; **ShoppingHub** &gt; **Primary Data** &gt; **Suppliers**.\n\n    You can also navigate to **Sourcing and Purchasing Automation** &gt; **Primary Data** &gt; **Supplier**.\n\n2.  Ensure that the **Punchout** check box is selected for the designated third-party supplier.\n\n    \\[Omitted image \"spo-configure-punchout-supplier.png\"\\] Alt text: Punchout check box is selected for the designated third-party supplier in the Purchasing view.\n\n    **Note:** This **Punchout** option is only available in the Purchasing view. For more information on adding suppliers, see [Add a supplier](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/create-supplier.md).\n\n3.  Navigate to **All** &gt; **Procurement Integrations** &gt; **Catalog** &gt; **Third-Party Categories**.\n\n4.  Do the following:\n\n    -   Add the required mapping records between SPO's model category and the punchout supplier's product category.\n    -   Add the required mapping records between SPO's predefined units and the punchout supplier's units of measure.\n    For more information, see [Mapping Product Categories and Units of Measure for seamless checkout in Shopping Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/product-category-mapping-shoppinghub.md)\n\n5.  Navigate to **All** &gt; **Procurement Integrations** &gt; **Setup** &gt; **Third-Party Registration**.\n\n6.  From the **Supplier** list, search for and select a supplier.\n\n7.  Do either or both of the following depending on your implementation requirements.\n\n    -   Select the **cXML punchout support** check box and fill in the fields in the **cXML punchout setup** tab.\n\n        \\[Omitted image \"spo-configure-punchout-cxml-settings.png\"\\] Alt text: Entering cXML settings in the cXML punchout setup tab.\n\n        The suppliers that do not have Search API and Order API or do not want to use them can upload catalog index files containing product catalog data. The uploaded data is stored in the Third-party Catalog \\(sn\\_spend\\_intg\\_third\\_party\\_catalog\\) table. For more information, see [Add third-party catalog data in an Excel file](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/add-third-party-catalog-spo.md).\n\n<table id=\"table_pdz_njg_xcc\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nRequire catalog index file upload?\n\n</td><td>\n\nOption that enables you to upload the catalog index CSV file. For more information, see [Add third-party catalog data in an Excel file](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/add-third-party-catalog-spo.md).\n\n</td></tr><tr><td>\n\ncXML domain\n\n</td><td>\n\nThe domain name associated with your organization for the punchout transaction.\n\n</td></tr><tr><td>\n\ncXML identity\n\n</td><td>\n\nA unique identifier used to represent your organization in the punchout transaction.\n\n</td></tr><tr><td class=\"sub-head\" colspan=\"2\">\n\nThird-party cXML - connections\n\n</td></tr><tr><td>\n\nOrder request URL\n\n</td><td>\n\nThe URL endpoint where the cXML order request is sent to the supplier.\n\n</td></tr><tr><td>\n\nPunchout group\n\n</td><td>\n\nThe specific group for which this punchout configuration applies.\n\n</td></tr><tr><td>\n\nPunchout inbound credentials\n\n</td><td>\n\nThe credentials that SPO uses to validate incoming cXML payloads from the supplier for Order Confirmation and Shipping Confirmation. Select a credential record of type **Basic Auth**. **Important:** Although the credential type is labelled **Basic Auth** in the UI, the fields carry cXML-specific values used to validate incoming supplier payloads:\n\n-   **Username**: Enter the value that the supplier places in `<Header><To><Credential><Identity>` of its confirmation cXML payload. This must match exactly — SPO validates this value against the incoming `<To>` Identity.\n-   **Password**: Enter the Shared Secret that the supplier places in `<Header><Sender><Credential><SharedSecret>` of its confirmation cXML payload. SPO decrypts and validates this value against the incoming payload.\nInbound credentials are required for Order Confirmation and Shipping Confirmation flows. If the inbound credential record is missing or invalid, SPO returns a validation error when the supplier sends a confirmation payload. Configure these credentials before going live with a cXML punchout supplier that sends order or shipping confirmations.\n\n</td></tr><tr><td>\n\nPunchout outbound credentials\n\n</td><td>\n\nThe credentials that SPO uses to authenticate when sending cXML requests to the supplier system. Select a credential record of type **Basic Auth**. **Important:** Although the credential type is labelled **Basic Auth** in the UI, it does not function as standard HTTP Basic Authentication for punchout. The two fields in the credential record carry cXML-specific values:\n\n-   **Username**: Enter the Sender Identity that identifies your organization in the punchout transaction. This value is written verbatim into both `<From><Credential><Identity>` and `<Sender><Credential><Identity>` in the cXML payload. If left blank, an empty `<Identity/>` element is transmitted.\n-   **Password**: Enter the Shared Secret provided by the supplier for authentication. This value maps to `<Sender><Credential><SharedSecret>` in the cXML payload.\nThe **cXML identity** and **cXML domain** fields on this form identify the supplier's `<To>` side of the cXML transaction and are separate from the outbound credential fields described above.\n\n</td></tr><tr><td>\n\nPunchout start URL\n\n</td><td>\n\nThe URL used to initiate the punchout session to the supplier system.\n\n</td></tr></tbody>\n</table>    -   Select the **APIs exchange** check box and fill in the fields in the **APIs configuration** tab.\n\n        This option is designed for punchout suppliers using the Search API, Order API, and Product Details API, enabling shoppers to search for products, place orders, and view product details seamlessly within the Shopping Hub experience.\n\n        |Field|Description|\n        |-----|-----------|\n        |Access token API|The URL/API used to authenticate and obtain an access token for API requests.|\n        |API Key/Client ID|The unique identifier or key provided by the supplier to authenticate API requests.|\n        |Order detail API|The endpoint URL for retrieving detailed information about a specific product.|\n        |Place order request API|The endpoint URL for placing orders with the supplier.|\n        |Product details API|The endpoint URL for retrieving detailed information about a specific product.|\n        |Product search API|The endpoint URL for searching products within the supplier's catalog. For more information, see [Configure extension point for Product search API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/configure-ext-point-punchout.md).|\n        |Punchout group|The specific group for which this punchout configuration applies.|\n\n    **Important:** If a supplier uses the Search API for product searches and cXML for order placement, you should select both the **cXML punchout support** and **APIs exchange** check boxes and fill in the required fields in each corresponding section.\n\n8.  Select **Submit**.\n\n\n## What to do next\n\nWhen integrating with a punchout supplier, customers are required to provide specific URLs for Order Confirmation and Shipping Confirmation. For more information, see [Providing Order and Shipping Confirmation URLs to Punchout Suppliers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/punchout-urls.md).\n\n-   **[Providing Order and Shipping Confirmation URLs to Punchout Suppliers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/punchout-urls.md)**  \nWhen integrating with a punchout supplier, customers are required to provide specific URLs for Order Confirmation and Shipping Confirmation.\n-   **[Configure extension point for Product search API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/configure-ext-point-punchout.md)**  \nThe sn\\_spend\\_intg.ThirdPartySystemApiExtension scripted extension point provides the configuration that punchout suppliers can use to ensure that all details about their product, such as product's name, brand, manufacturer, price, availability, SKU, and so on, is displayed in Shopping Hub.\n-   **[Mapping Product Categories and Units of Measure for seamless checkout in Shopping Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/product-category-mapping-shoppinghub.md)**  \nYou can map the product categories and units of measure for third-party products to the corresponding model categories. This ensures that during checkout, Shopping Hub accurately considers and displays the product category for the purchase order lines \\(POL\\) and purchase requisition lines \\(PRL\\) based on your predefined mappings.\n-   **[Add third-party catalog data in an Excel file](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/add-third-party-catalog-spo.md)**  \nYou can download and add third-party catalog data in an Excel file template.\n\n**Parent Topic:**[Configuring Sourcing and Procurement Operations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/configuring-spo.md)\n\n**Related topics**  \n\n\n[Sourcing and Procurement Operations product tile]()\n\n[Sourcing and Procurement Operations Product Hub]()\n\n[Install Sourcing and Procurement Operations]()\n\n[Sourcing and Procurement Operations Configuration Console]()\n\n[Configure Sourcing and Procurement Operations]()\n\n[Setting up primary data for ShoppingHub]()\n\n[Configuring work prioritization]()\n\n[Add a button in Shopping Hub]()\n\n[Add a footer link in Shopping Hub]()\n\n[Customize your top suppliers on Shopping Hub]()\n\n[Configure conditions for merging purchase requisitions]()\n\n[Service portal configuration for ShoppingHub]()\n\n[Install ShoppingHub Mobile]()\n\n[Advanced Work Assignment for Source-to-Pay Operations]()\n\n[Install Universal Request for Sourcing and Procurement Operations]()\n\n[Install Sourcing and Procurement Operations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/install-spo-ai.md)\n\n[Setting up primary data for ShoppingHub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/set-up-master-data-shopping-hub.md)\n\n[Service portal configuration for ShoppingHub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/service-portal-configuration-for-shoppinghub.md)\n\n[Customize your top suppliers on Shopping Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/customize-top-suppliers.md)\n\n[Using Shopping Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/use-shoppinghub-portal.md)\n\n[My purchases on Shopping Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/my-purchases.md)\n\n"}}