01 / 07
SHOPIFY × OCI / SAP
European buyers run OCI. Connect your Shopify catalog with HOOK_URL round trips, contract pricing, and the custom NEW_ITEM fields their ERP demands.
02 / 07
THE GAP
cXML gets the attention, but a large share of European procurement, above all in DACH, runs SAP's Open Catalog Interface. OCI is older and simpler: the ERP calls your catalog URL with a HOOK_URL return address, the buyer shops, and the cart posts back as NEW_ITEM form fields.
Simple is where the trouble hides. Every ERP speaks its own field dialect: ISO units, material groups, MATNR blank or filled, and the custom NEW_ITEM extensions that decide whether a cart books cleanly into a requisition or lands on a support desk. PunchRelay maps fields per buyer instead of hardcoding one SAP's expectations.
PunchRelay connects Shopify B2B catalogs to OCI procurement workflows. If your buyers run SAP SRM, S/4HANA or Onventis and your store runs Shopify, this page exists for you.
↳ SOUNDS FAMILIAR?
03 / 07
THE ARTIFACT
HOOK_URL=https://buyer-erp.example.com/oci/return
USERNAME=shop_user
PASSWORD=***
OCI_VERSION=4.0
returntarget=_parent
<form method="post" action="{HOOK_URL}">
<input name="NEW_ITEM-DESCRIPTION[1]" value="Nitrile gloves, box of 100">
<input name="NEW_ITEM-VENDORMAT[1]" value="SKU-4711">
<input name="NEW_ITEM-QUANTITY[1]" value="50">
<input name="NEW_ITEM-UNIT[1]" value="BX">
<input name="NEW_ITEM-PRICE[1]" value="25.00">
<input name="NEW_ITEM-CURRENCY[1]" value="USD">
<input name="NEW_ITEM-MATGROUP[1]" value="46181504">
</form>Round trip
A punchout request opens the catalog. The cart returns to the buyer's system as a document. The purchase order that follows is checked against that cart and waits for your review. The XML is the product.
04 / 07
THE ROUND TRIP
SAP SRM, S/4HANA or another OCI system opens your PunchRelay URL by HTTP GET or form POST, passing HOOK_URL, USERNAME, PASSWORD and OCI_VERSION. We validate the credentials and open a session mapped to the buyer's Shopify B2B company location.
The buyer browses the PunchRelay catalog, with products and contract prices from the Shopify B2B catalog assigned to their company location.
PunchRelay renders the self-submitting return form to HOOK_URL: NEW_ITEM-DESCRIPTION, VENDORMAT, QUANTITY, ISO units, PRICE, MATGROUP, indexed per line item, plus whatever custom fields your buyer's ERP requires.
The transferred cart becomes a shopping cart or requisition (the BANF, in SAP terms) and goes through approval there. OCI itself only moves the cart. The purchase order is a separate step, on the buyer's terms.
cXML purchase orders are accepted durably, checked against the transferred cart and placed in the Purchase orders inbox in the PunchRelay app. Nothing is created in Shopify until someone on your team reviews the PO and clicks Create Shopify order. The order is then created unpaid, with payment pending, ready to fulfill. OCI returns a cart only; the purchase-order leg is agreed and tested separately for each buyer.
05 / 07
THE CHECKLIST
01 / 03
Configure UOM, an 8-digit UNSPSC/MATGROUP, buyer material numbers and five OCI custom fields per SKU or variant. Values are connection settings; validate the returned fields in the buyer’s ERP before going live.
02 / 03
Minimums, maximums and case increments from your B2B settings run in the cart, before the NEW_ITEM post fires. Carts arrive in the ERP already bookable.
03 / 03
Setup calls and NEW_ITEM posts are logged with credentials redacted. When the buyer's SAP basis team asks what was sent, you forward the actual payload, field by field.
Works with
06 / 07
07 / 07
READY
We are onboarding a small group of Shopify B2B merchants and building their first buyer connections with them. Tell us where to reach you.
THE ON-RAMP
A complete punchout readiness roadmap for your exact catalog, ERP, and buyer procurement systems before you commit to live deployment.
↳ NO SLIDE DECK