At a glanceCompare the two models
QuestioncXMLOCI
Where it startsOften launched from a procurement application or network using structured cXML setup messages.Often launched from an SAP or compatible procurement/ERP context using OCI catalog interface parameters.
What comes backA structured response and cart return, followed by buyer-specific order documents.Mapped catalog and line-item fields returned to the buyer application.
What varies by buyerVersions, identifiers, credentials, endpoints, fields and document requirements.Version, form fields, return target, mapping and buyer-side authentication.
What the supplier should testSession launch, cart return, approval, PO receipt and any agreed downstream documents.Catalog launch, field mapping, cart return, buyer approval and the resulting PO path.
The buyer usually determines the protocol
A supplier normally does not choose cXML or OCI in isolation. The enterprise customer's procurement platform and integration standard determine the connection contract. Ask the buyer which protocol it requires before designing a test or quoting implementation work.
PunchOut Central supports both cXML and OCI workflows. That lets the supplier keep one Shopify or Shopify Plus catalog while supporting different buyer connection requirements.
Questions that resolve the choice quickly
- Which procurement or ERP product is the buyer using?
- Does the buyer provide a cXML or OCI setup document and test account?
- Which catalog access and store should the buyer receive?
- What fields, identifiers and PO references must be retained?
- What invoice format and delivery requirement applies after ordering?