cXML / OCI / PunchOut2Go integration, how deep does it go with Coupa, Ariba, Workday, SAP Concur?
The four procurement platforms you must integrate with, in order of B2B office-supply contract frequency:
- Coupa, dominant in mid + large enterprise. cXML 1.2.040 punchout setup + cXML OrderRequest for PO ingest + cXML InvoiceDetailRequest for e-invoicing. ~50% of my office-supply punchout work is Coupa first.
- SAP Ariba, dominant in Fortune 500 + global enterprise. cXML PunchOutSetupRequest is the standard but Ariba Network Cloud also supports OCI 5.0 for some buyer configurations. Integration timeline: 2-4 weeks once Ariba supplier registration is approved.
- Workday Strategic Sourcing (formerly Scout RFP) and Workday Procurement, growing fast in 2024-2026. Native cXML support, simpler buyer-side configuration than Ariba.
- SAP Concur Invoice / Spend, mostly travel + expense but more spend is moving here. Uses cXML + Concur Open API for line-item ingest.
The integration shape: PunchOutSetupRequest authenticates the buyer + delivers identity context (customer ID, contract ID, buyer cost center), Magento applies their tiered pricing automatically, customer fills a cart, hits “send to procurement”, the cart returns as a PunchOutOrderMessage with itemized lines + UNSPSC codes + ship-to address. The buyer’s procurement system runs approval routing, then sends back a cXML OrderRequest as a PO that auto-imports into Magento.
For the long tail of smaller procurement platforms (Jaggaer, GEP, Ivalua, Procurify, Tradeshift), PunchOut2Go is the bridge, one integration on the Magento side, they handle the translation to 200+ buyer platforms. ~$500, $1,500/mo per active buyer. Worth it once you have 3+ small punchout customers.