cXML and OCI: A Complete Guide to PunchOut Catalog Integration
Discover how cXML and OCI enable PunchOut catalog integrations between eCommerce platforms and procurement systems such as SAP Ariba, SAP ERP, and Coupa.
Modern B2B procurement requires efficient communication between buyers, suppliers, and their respective software platforms.
PunchOut technology makes this possible by connecting a supplier’s eCommerce catalog directly to a buyer’s procurement system.
Two of the most widely used technologies for these integrations are cXML (Commerce eXtensible Markup Language) and OCI (Open Catalog Interface).
Although both technologies support PunchOut purchasing processes, they use different communication methods and are typically associated with different procurement environments.
Understanding their differences is essential for businesses looking to implement a reliable PunchOut catalog integration.
What is cXML PunchOut?
cXML PunchOut is a procurement integration method that allows buyers to access a supplier’s online catalog from their purchasing system and return selected products to their procurement workflow.
cXML stands for Commerce eXtensible Markup Language.
It is an XML-based protocol designed to exchange business documents and procurement information between organizations.
In a PunchOut integration, cXML is commonly used to establish the connection between a buyer’s procurement platform and a supplier’s eCommerce website.
A typical cXML PunchOut process involves:
- The buyer accesses their procurement platform.
- The buyer selects a supplier’s PunchOut catalog.
- The procurement system sends a cXML PunchOutSetupRequest.
- The supplier’s system authenticates the request and provides a catalog session URL.
- The buyer browses the supplier’s eCommerce catalog.
- The buyer selects products and adds them to the shopping cart.
- The cart information is returned to the procurement system through a cXML PunchOutOrderMessage.
- The buyer completes the purchasing approval process within their procurement platform.
The purchase order may subsequently be transmitted to the supplier through a separate electronic document exchange.
This approach enables buyers to use the supplier’s product catalog while maintaining control over their internal purchasing procedures.
What is OCI PunchOut?
OCI (Open Catalog Interface) is a catalog integration interface commonly used in SAP procurement environments.
Like cXML, OCI allows buyers to access external supplier catalogs directly from their procurement systems.
The main difference lies in how the information is exchanged.
OCI traditionally relies on HTTP-based communication and form submissions to transfer selected shopping cart information back to the purchasing application.
A typical OCI PunchOut process includes:
- The buyer opens an external supplier catalog from the procurement system.
- The supplier’s eCommerce platform receives the session parameters.
- The buyer browses the catalog and selects products.
- The supplier’s website prepares the shopping cart data.
- The cart information is returned to the procurement system using the required OCI fields.
- The buyer continues the purchasing process within their SAP environment.
OCI is particularly relevant for suppliers working with organizations that use SAP purchasing applications.
cXML vs OCI: What Are the Main Differences?
Both cXML and OCI connect supplier catalogs to procurement systems, but they differ in their communication methods and technical requirements.
|
Feature |
cXML PunchOut |
OCI PunchOut |
|---|---|---|
|
Full name |
Commerce eXtensible Markup Language |
Open Catalog Interface |
|
Main purpose |
Electronic procurement communication |
External catalog integration |
|
Data exchange |
XML-based messages |
HTTP parameters and form-based data exchange |
|
Common environments |
SAP Ariba, Coupa and other compatible platforms |
SAP procurement environments |
|
Catalog access |
PunchOut session |
External catalog session |
|
Cart transfer |
PunchOutOrderMessage |
OCI field submission |
|
Purchase order exchange |
Supported through separate cXML messages |
Typically managed through separate procurement processes |
|
Integration requirements |
cXML message processing and authentication |
OCI parameter and field mapping |
Free up your resources and accelerate your time-to-market. Let PunchOut Rocket manage the complexity of cXML and OCI, and focus on growing your B2B sales.
Which technology should suppliers choose?
The correct choice depends primarily on the procurement systems used by their customers.
Suppliers serving multiple enterprise customers may need to support both protocols.
Rather than implementing separate custom integrations for every customer, businesses can use a PunchOut integration solution that manages the required communication protocols.
How Does cXML PunchOut Integration Work?
A cXML PunchOut integration establishes a connection between two separate environments:
- The buyer’s procurement platform.
- The supplier’s eCommerce platform.
The integration allows the buyer to interact with the supplier’s catalog without leaving the controlled purchasing workflow.
Step 1: PunchOut Session Request
The buyer initiates a PunchOut session from their procurement platform.
A cXML PunchOutSetupRequest is sent to the supplier’s integration endpoint.
The request typically contains information required to identify the buyer, authenticate the connection, and establish the session.
Step 2: Supplier Authentication
The supplier’s PunchOut integration validates the incoming request.
Depending on the configuration, the integration can identify the purchasing organization and associate the session with a specific customer account.
This makes it possible to apply customer-specific purchasing conditions where supported by the eCommerce platform.
Step 3: Catalog Browsing
Once authenticated, the buyer accesses the supplier’s online catalog.
The catalog may provide:
- Product descriptions and technical specifications.
- Product images.
- Customer-specific pricing.
- Available product variants.
- Product availability information.
- Shopping cart functionality.
The information displayed depends on the supplier’s eCommerce configuration and the capabilities of the integration.
Step 4: Shopping Cart Transfer
After selecting the required products, the buyer transfers the shopping cart back to the procurement system.
The supplier’s platform generates a cXML PunchOutOrderMessage containing the relevant cart information.
This may include product identifiers, descriptions, quantities, prices, and other required fields.
Step 5: Procurement Approval
The buyer’s procurement platform receives the shopping cart and continues the purchasing process.
Internal approval workflows, purchasing policies, and budget controls remain managed by the buyer’s procurement system.
The actual purchase order is typically issued after the appropriate approvals have been completed.
cXML PunchOut Integration with SAP Ariba
SAP Ariba is one of the best-known enterprise procurement environments supporting cXML PunchOut integrations.
For suppliers, integrating an eCommerce catalog with SAP Ariba can make it easier for enterprise customers to purchase products through their existing procurement workflows.
The buyer starts the purchasing process in SAP Ariba and accesses the supplier’s external catalog through a PunchOut session.
After selecting products, the shopping cart is transferred back to SAP Ariba for approval and order processing.
Benefits for Suppliers
A SAP Ariba PunchOut integration can provide several advantages:
- Allow enterprise customers to access the supplier’s online catalog.
- Reduce the need to maintain separate static catalogs.
- Support customer-specific pricing and product assortments.
- Reduce manual product entry during purchasing.
- Improve consistency between the supplier’s catalog and the buyer’s purchasing workflow.
- Support a more efficient B2B purchasing experience.
Do Suppliers Need to Replace Their eCommerce Platform?
Not necessarily.
A PunchOut integration layer can connect an existing eCommerce platform to SAP Ariba without requiring the supplier to replace its entire online store.
The exact implementation depends on the platform, the procurement configuration, and the buyer’s technical requirements.
cXML PunchOut Catalog Integration: Technical Requirements
Implementing a cXML PunchOut catalog requires communication between the procurement system and the supplier’s eCommerce platform.
Typical requirements include:
Authentication and session management
The integration must identify incoming requests and establish authorized purchasing sessions.
cXML message processing
The supplier’s system must correctly interpret PunchOut setup requests and generate the required responses.
Customer-specific catalog access
Where supported, the integration should associate each PunchOut session with the appropriate customer account, pricing conditions, and product visibility rules.
Shopping cart mapping
Product identifiers, descriptions, quantities, prices, units of measure, and other required attributes must be transferred in the expected format.
Error handling
The integration should handle invalid credentials, missing parameters, session expiration, and other communication errors.
Testing and validation
Each buyer connection should be tested against the specific requirements of the procurement platform.
These requirements explain why PunchOut implementations can become complex when suppliers must support multiple customers and procurement environments.
cXML PunchOut Example: Understanding the Data Exchange
A typical PunchOut session begins with a cXML request similar to the following simplified example:
<cXML payloadID="example-123"
timestamp="2026-10-15T10:00:00Z">
<Header>
<From>
<Credential domain="NetworkID">
<Identity>BUYER_ID</Identity>
</Credential>
</From>
<To>
<Credential domain="NetworkID">
<Identity>SUPPLIER_ID</Identity>
</Credential>
</To>
<Sender>
<Credential domain="NetworkID">
<Identity>BUYER_ID</Identity>
<SharedSecret>EXAMPLE_SECRET</SharedSecret>
</Credential>
<UserAgent>Procurement System</UserAgent>
</Sender>
</Header>
<Request>
<PunchOutSetupRequest operation="create">
<BuyerCookie>EXAMPLE_SESSION</BuyerCookie>
<BrowserFormPost>
<URL>https://buyer.example.com/return</URL>
</BrowserFormPost>
</PunchOutSetupRequest>
</Request>
</cXML>This is an illustrative, incomplete request. Production messages require the appropriate protocol version, complete mandatory elements, secure credentials, and buyer-specific configuration.
The supplier’s integration processes the request and returns a response containing the URL used to start the PunchOut catalog session.
When the buyer finishes shopping, the selected products are transferred back to the procurement platform using a PunchOutOrderMessage.
Integrating PunchOut with Existing eCommerce Platforms
Many suppliers already operate sophisticated B2B eCommerce websites.
Replacing these systems solely to support PunchOut procurement would introduce unnecessary complexity and costs.
A more practical approach is to integrate PunchOut capabilities into the existing eCommerce environment.
Depending on the integration solution, PunchOut functionality can be added to platforms such as:
WooCommerce PunchOut Integration
WooCommerce-based B2B stores can use a compatible PunchOut integration to connect their product catalogs with enterprise procurement systems.
This approach allows suppliers to retain their existing WordPress and WooCommerce infrastructure.
Magento PunchOut Integration
Magento and Adobe Commerce are frequently used for complex B2B commerce requirements.
PunchOut integration can extend these platforms to support procurement-driven purchasing workflows.
PrestaShop PunchOut Integration
Suppliers using PrestaShop can connect their existing catalogs to compatible procurement systems through a dedicated PunchOut integration.
nopCommerce PunchOut Integration
nopCommerce provides an eCommerce environment for businesses operating on Microsoft technologies.
PunchOut integration enables suppliers to connect their nopCommerce catalogs with supported enterprise purchasing systems.
How PunchOut Rocket Simplifies cXML and OCI Integration
PunchOut Rocket helps suppliers connect their existing eCommerce platforms with enterprise procurement systems using PunchOut technology.
Instead of developing and maintaining separate custom integrations for each purchasing environment, suppliers can adopt a dedicated solution designed to simplify PunchOut connectivity.
PunchOut Rocket provides integrations for popular eCommerce platforms, including WooCommerce, Magento, PrestaShop, and nopCommerce.
This allows businesses to extend their existing online stores with PunchOut capabilities while preserving their established product catalogs and eCommerce processes.
Why Choose PunchOut Rocket?
Keep your existing eCommerce platform
Extend your current online store without rebuilding your entire eCommerce infrastructure.
Connect with enterprise procurement environments
Enable PunchOut purchasing workflows with compatible procurement systems using the required integration protocols.
Simplify B2B purchasing
Allow customers to select products from your online catalog and transfer their shopping carts back to their purchasing systems.
Reduce custom development
Use a dedicated PunchOut solution rather than building every integration from scratch.
Support your B2B growth
Make your existing catalog more accessible to organizations that rely on enterprise procurement software.
Ready to Enable PunchOut on Your eCommerce Store?
Discover how PunchOut Rocket can help connect your product catalog with your customers’ procurement systems.
[Explore PunchOut Rocket Integrations]
Frequently Asked Questions About cXML and OCI PunchOut
What is cXML PunchOut?
cXML PunchOut is an integration method that connects a supplier’s online catalog with a buyer’s procurement platform. It allows buyers to select products on the supplier’s website and transfer their shopping carts back to the procurement system.
What is the difference between cXML and XML?
XML is a general-purpose markup language used to structure data. cXML is an XML-based protocol specifically designed for exchanging business and procurement documents.
What is the difference between cXML and OCI?
cXML uses structured XML messages to support electronic procurement communication, while OCI traditionally uses HTTP-based mechanisms and defined fields to integrate external supplier catalogs with SAP purchasing environments.
Does SAP Ariba support cXML PunchOut?
Yes. SAP Ariba supports cXML PunchOut integrations, allowing buyers to access external supplier catalogs and transfer selected products back to their procurement workflows.
Can WooCommerce support cXML PunchOut?
Yes. WooCommerce can support cXML PunchOut through an appropriate integration solution or plugin that connects the online store with compatible procurement systems.
Do I need a separate catalog for PunchOut?
Not necessarily. A PunchOut integration can allow customers to access products directly from an existing eCommerce catalog, reducing the need to maintain separate catalog copies.
Is PunchOut the same as EDI?
No. PunchOut allows buyers to access supplier catalogs and return shopping cart information to procurement systems. EDI is commonly used to exchange structured business documents such as purchase orders, invoices, and shipping notices. The two technologies can complement each other.
Can a supplier support both cXML and OCI?
Yes. Suppliers can support both protocols when their integration architecture and software provide the necessary capabilities. This can be useful when serving customers that use different procurement platforms.
Conclusion: Choosing the Right PunchOut Integration
cXML and OCI play an important role in connecting B2B eCommerce catalogs with enterprise procurement systems.
Although their technical approaches differ, both help suppliers provide customers with a more efficient purchasing experience.
For suppliers already using WooCommerce, Magento, PrestaShop, or nopCommerce, adopting a dedicated PunchOut integration can be a practical alternative to building complex custom connections.
PunchOut Rocket helps businesses extend their existing eCommerce platforms with PunchOut capabilities and support the purchasing requirements of enterprise customers.
Free up your resources and accelerate your time-to-market. Let PunchOut Rocket manage the complexity of cXML and OCI, and focus on growing your B2B sales.
