SAP Ariba punchout integration guide for suppliers

An SAP Ariba punchout integration lets a buyer open a supplier's ecommerce catalogue from Ariba, shop using current contract pricing and return the cart to the buyer's requisition workflow.

Understand the Ariba punchout flow

Ariba creates a cXML PunchOutSetupRequest and routes it to the supplier's punchout endpoint, commonly through SAP Business Network. The supplier authenticates the request and returns a start-page URL. After shopping, the supplier posts the cart back as cXML so Ariba can create requisition lines.

The approved purchase order can then be delivered separately through cXML, EDI or another agreed channel.

1. Confirm the buyer's requirements

Obtain the buyer's SAP Ariba realm or network details, required credential domains, test schedule and catalogue rules. Confirm whether they need store-level punchout or Level 2 search visibility, and whether orders, confirmations and invoices are included.

2. Prepare the supplier catalogue

The ecommerce site must identify the buying organisation, apply the correct assortment and contract pricing, and preserve required values when returning the cart. Product identifiers, units of measure, commodity classifications and supplier auxiliary data need to match the buyer's expectations.

3. Configure cXML authentication and routing

Set up test and production identities, shared-secret or certificate authentication as required, and the appropriate punchout URLs. Keep credentials separate between environments and avoid placing secrets in logs.

4. Map the returned cart

Agree on mandatory item fields and test configured products, taxes, freight, attachments and special characters where relevant. The buyer should verify that returned items create valid requisition lines and route through approvals correctly.

5. Test the complete process

• Valid and invalid authentication
• Customer-specific pricing and assortment
• Single and multi-line carts
• Changed quantities and cancelled sessions
• Purchase order delivery and acknowledgement
• Error monitoring and support escalation

Common integration problems

Most issues come from credential mismatches, missing mandatory fields, invalid units or classifications, incorrect return URLs and differences between test and production configuration. Capturing message identifiers and validation errors makes troubleshooting much faster.