ProductPlatform OverviewPunchOutPurchase OrdersInvoicesMulti-Store ControlTransactionsHow It Works
IntegrationsShopify ReadyCoupaSAP AribaJAGGAEROracle ProcurementIvaluaGEP SMARTcXMLOCI
SolutionsB2B SuppliersMulti-Store CommerceBuyer OnboardingEcommerce Agencies
cXML guide

What is cXML? A supplier guide to PunchOut messages.

Understand where cXML fits in a procurement-to-commerce flow, which message boundaries matter, and what to confirm before testing a buyer connection.

Resource guidePunchOut Central
01UnderstandDefine the buyer question
02MapConnect store and protocol
03ValidateTest the full transaction

cXML in plain language

cXML, or Commerce XML, is a structured protocol used to exchange commerce and procurement information between applications. The standard includes setup and transaction documents, including the PunchOut interactions commonly used to open a supplier catalog and return a cart.

A cXML connection is not a generic promise that every buyer uses the same fields. The buyer environment, identifiers, endpoint expectations and document requirements still need to be agreed for the specific connection.

The messages around a PunchOut session

  1. 01

    Setup request

    The procurement system sends the information needed to start a supplier catalog session.

  2. 02

    Setup response

    The supplier-side connection responds with the session destination or result expected by the buyer.

  3. 03

    Cart return

    The supplier site returns the selected cart to the procurement application for review.

  4. 04

    Order request

    After buyer approval, the buyer sends the purchase order document required by its process.

  5. 05

    Later documents

    Order confirmations, invoices or other documents depend on the buyer agreement and the supported transaction scope.

cXML questions to collect from the buyer

  • Which cXML version and document types does the buyer expect?
  • Which sender, receiver and shared-secret or credential rules apply?
  • Which URL, return behavior and line-item fields must the cart contain?
  • Which identifiers must be preserved from the buyer request through the PO?
  • How will the buyer test approval, PO receipt and any invoice requirement?

cXML support is not the same as buyer compatibility

PunchOut Central supports cXML procurement workflows, but a buyer connection still needs buyer-specific configuration and testing. Do not infer compatibility from the protocol name alone. Confirm the procurement platform, workflow, required fields and test environment before promising a go-live date.

Use the cXML commercial integration page for the product connection path; use this guide when you need to understand the protocol vocabulary and implementation questions.

Reference material

These primary-source references explain the general protocol or catalog concepts. Buyer-specific implementation requirements still take precedence.

Put the guide into practice

Need to translate a cXML requirement?

Share the buyer platform and required transaction flow so the connection can be scoped accurately.