PunchOut is a technical interface procedure. It connects a purchasing system directly with a supplier’s e-commerce website. The data exchange uses the OCI or cXML standards. This technology automates the transfer of shopping cart data within digital catalogue procurement.
PunchOut in brief
- Definition: PunchOut is a protocol interface, not a static catalogue.
- The jump-off: The buyer starts in the e-procurement platform. One click forwards them to the supplier’s online shop.
- The selection: The user picks products in the online shop, using the conditions stored for them individually.
- The return: The online shop sends the cart data back to the customer system automatically.
- The goal: The interface transfers real-time data without a manual import.
Primus PunchOut – purchasing straight from the supplier catalogue
Integrate supplier catalogues into your ERP or e-procurement system. Primus PunchOut gives your buyers an ordering process with no media breaks. The solution works securely and across systems.
Simply arrange a free demo appointment or read more about the product here:
What is a PunchOut catalogue? (B2B catalogue procurement)
The term “PunchOut catalogue” describes dynamic access to an online shop from within a customer system. Technically, PunchOut is a live interface to the buyer’s e-procurement platform.
How does the PunchOut process work?
The technical handling follows four steps. The OCI interface (Open Catalog Interface) or the cXML standard governs the data flow between purchasing system and online shop.
Step 1: starting in the e-procurement system
Login & selection
- You log in to your own procurement system as usual.
- You select the desired partner from the list of approved suppliers.
- In the background the system prepares an authenticated PunchOut connection to the webshop.
Step 2: a secure jump to the supplier
Authenticated forwarding
- One click forwards you directly to the supplier’s online shop.
- The login there happens automatically and securely through a cryptographic procedure (shared secret).
- You are immediately signed in to the correct shop area released for you.
Step 3: shopping in the webshop
Product selection & cart
- You choose the products you need from the supplier’s range.
- All data such as prices, availability and product information is shown in real time.
- The cart is filled with everything relevant for the later order.
Step 4: return & completion
Transfer & approval
- One click sends the filled cart back to your e-procurement system through the PunchOut interface.
- The data transfer happens in a standardised format.
- The order then runs through your company’s usual internal approval process.
Also worth reading: technical integration with the Unite Mercateo procurement platform
Which PunchOut interfaces exist?
The choice of protocol determines the depth of information and the security of the transaction.
cXML PunchOut (commerce eXtensible Markup Language)
cXML is the standard for cloud platforms. The protocol enables complete PunchOut transactions and is an XML-based format. Systems such as Coupa or SAP Ariba use cXML to exchange order documents and catalogue data.
OCI 4.0 (Open Catalog Interface)
OCI 4.0 is the classic SAP standard. The interface enables straightforward catalogue integration. Data is transferred as URL parameters by HTTP request to the customer system. This protocol carries the base fields of the product data.
Technical specification: OCI 4.0: details of the interface architecture
OCI 5.0 (extended SAP standard)
OCI 5.0 supports PunchOut with integrated catalogue search and secured authentication. This version allows additional account assignment information and more detailed product data to be transferred. The interface represents the current state of the art for SAP environments.
Difference between cXML and OCI
| Characteristic | cXML PunchOut | OCI PunchOut |
|---|---|---|
| Data format | XML structure | URL parameters |
| Originator | Ariba | SAP |
| Main systems | Coupa, Oracle, Jaggaer, Amazon Business | SAP SRM, SAP S/4HANA, SAP Ariba |
| Transfer method | XML documents | HTTP GET/POST |
| Adoption | Global, cross-platform | SAP environments |
How is a PunchOut connection set up?
Integrating a PunchOut interface requires technical mapping. A modern SaaS solution such as Primus PunchOut handles this process efficiently.
Configuration at the supplier
The supplier first stores the URL of the procurement platform in their system and sets up authentication via shared secret. They then prepare the product data from their merchandise management system for transfer and configure the mapping that assigns their internal data fields to the standardised formats.
Configuration at the buyer
In parallel the buyer enters the supplier’s PunchOut URL and credentials into the procurement system. They also define system-specific parameters such as cost centres, budget assignments and approval workflows that should apply to all orders with this supplier.
Validation and activation
Before productive use both sides verify the connection with test orders, confirming that cart, product data and prices are transferred correctly and that all data mappings work. After successful validation they release the connection for regular ordering.
Technical documentation: the OCI integration process in existing IT landscapes
Read everything about BMEcat validation
Areas of application for PunchOut
PunchOut optimises procurement scenarios in industry and wholesale:
- C-parts management: automating high-frequency orders to reduce process costs.
- Product configurators: selecting complex items directly on the manufacturer’s e-commerce website.
- Real-time prices: access to same-day conditions without a manual catalogue update.
Advantages of the PunchOut interface
- Highest data quality: removing manual data entry reduces typing errors.
- Process speed: order data reaches the ERP system without delay.
- Compliance: internal approval workflows and budget limits stay intact.
- No maintenance overhead: suppliers maintain product data centrally in the online shop. A SaaS solution makes individual IT projects unnecessary.
Solutions for PunchOut integration
Primus PunchOut
This SaaS solution generates PunchOut interfaces in under a minute. Full integration of new customers and going live happen within 24 hours. The technology supports OCI and cXML natively.
Primus Catalog
The tool automates the creation of static catalogues (BMEcat) as the basis for hybrid procurement scenarios.
Primus Exclusion
This technology enables cloud-based range filtering. It controls the visibility of items in the online shop individually for different buyers.
See PunchOut live: technical provisioning in seconds
In a personal demo we show you concrete use cases and advise you on integration, processes and best practices.
Set up a PunchOut connection in under a minute. Check your BMEcat catalogue beforehand for free in the validator.
Summary: PunchOut in procurement
PunchOut procedures optimise catalogue procurement through automated processes. The connection between purchasing system and online shop safeguards data quality. A modern SaaS solution minimises the technical effort for suppliers and buyers alike.