Is SAP punchout the same as Ariba punchout?

No. SAP SRM, ERP and S/4HANA use OCI (a form-post protocol); SAP Ariba uses cXML. They’re different standards with different handshakes. We build both in a single integration, so you’re covered whichever your buyer runs.

Which OCI versions do you support?

OCI 4.0 and 5.0, including the fields and behaviours S/4HANA self-service procurement expects, and OCI background search where the buyer uses it.

How do purchase orders come back from SAP?

OCI itself only covers the catalogue round-trip. The PO is sent separately — commonly cXML, email or EDI depending on the buyer’s setup. Where the buyer can send electronically, we create the order in your store automatically.

Our buyer says our prices must match their SAP units of measure — can you handle that?

Yes, that’s core OCI work: mapping your shop units to SAP UOM codes (EA, PCE, BOX, etc.) and pricing per the buyer’s price-unit conventions so requisitions match to the penny.

Which ecommerce platforms can you connect to SAP?

Magento / Adobe Commerce (ready-made plugin with OCI built in), Shopify, and custom platforms — BigCommerce, WooCommerce, headless or bespoke — as a tailored build.

SAP SRM · S/4HANA · OCI Punchout

SAP Punchout Integration (OCI)

Buyers on SAP SRM, S/4HANA or SAP ERP punch out over OCI — a different protocol from the cXML world of Ariba and Coupa. We build both, so whichever SAP flavour your customer runs, your store connects: OCI round-trip for SAP catalogues, cXML for the Ariba Network.

OCI 4.0/5.0SAP SRMS/4HANAHOOK_URL round-tripcXML for Ariba

0330 043 2162

Get a Free SAP Punchout Quote

Tell us your platform and we'll scope it. No obligation.

Free consultation

No obligation

Reply today

What is SAP OCI punchout?

SAP OCI punchout gives buyers on SAP SRM, SAP ERP (MM) or S/4HANA a live route into your store. Instead of you maintaining catalogue files for their SAP system, the buyer opens your catalogue from inside SAP and lands on your site — signed in, browsing real products and stock at their contract prices. When they check out, the basket drops straight into their SAP shopping cart or purchase requisition, with no rekeying on either side.

Under the hood, OCI (Open Catalog Interface) is SAP’s native punchout standard: SAP calls your store’s OCI entry URL with login parameters and a HOOK_URL, and at checkout your store posts the basket back as OCI fields — item text, quantity, price, unit, vendor material number. It’s a simpler protocol than cXML, but the field mapping is where projects succeed or fail: SAP expects precise NEW_ITEM naming, SAP units of measure, material group mapping and exact price formatting. That mapping is the bulk of what we do — and why our integrations pass buyer testing first time.

How it works

From click to purchase order — the SAP punchout flow

Buyer opens your catalogue in SAP

From SAP SRM or S/4HANA the buyer clicks your catalogue. SAP calls your store’s OCI entry URL with credentials and a HOOK_URL return address, landing them on your site logged in.

They shop your live store

Live products, live stock, their contract pricing — on your own storefront, with no static catalogue files to maintain.

The basket returns to SAP

At checkout your store posts the basket to SAP’s HOOK_URL as OCI NEW_ITEM fields, mapped to the buyer’s SAP units, material groups and currency.

The requisition becomes a PO

The basket lands as an SAP shopping cart or requisition and runs through approval. The resulting purchase order reaches you by cXML, email or EDI — we automate order creation where the buyer supports it.

The SAP-specific details we handle

OCI looks simple on paper. In practice, every SAP buyer’s configuration differs — these are the areas we’ve solved repeatedly.

OCI field mapping

NEW_ITEM-DESCRIPTION, MATNR, MATGROUP, UNIT, PRICE, CURRENCY, LEADTIME — mapped to your buyer’s SAP conventions, including SAP UOM codes and material group taxonomies.

OCI versions & background search

OCI 4.0 and 5.0 support, plus OCI background search (SOURCING / validation calls) where the buyer’s SRM configuration uses it.

SRM, S/4HANA and ERP variants

Classic SRM, S/4HANA self-service procurement and direct ERP (MM) calls each behave slightly differently around sessions and return handling. We test against the buyer’s actual system.

Ariba too, in the same build

Many SAP buyers are migrating to Ariba. Our integrations speak OCI and cXML side by side, so a buyer moving from SRM to Ariba doesn’t need a new project.