Your major customer requires PunchOut: from shop to procurement system.
Connect your shop to a business customer's procurement system. Check the catalogue, commercial terms and cart transfer together.
Read the German originalDescribe the handover first
One possible workflow starts when a buyer opens the supplier's shop from their procurement software, selects items and returns the cart to the procurement system. Approval and ordering follow there. Separating these stages in advance lets you explain precisely which part the shop connection handles.
SAP describes OCI as an open catalogue interface. Other partners require cXML/PunchOut, for example. The umbrella term alone is therefore not enough for a quote: request the specific partner documentation and a contact for testing.
The right items are not enough
A unit in the shop may mean a box to the procurement partner. Discounts, currencies, pack quantities and external item numbers must retain the same meaning across the handover. A test with a single arbitrary product can easily miss these differences.
Define five informative carts: a standard item, a different unit, a customer-specific price, an unavailable line item and a cancelled session. Agree the expected results before implementation and compare them on both sides.
Validate cart transfer and ordering separately
Returning a cart does not confirm an order. Clarify whether the order arrives later through EDI, an API or an existing procedure. Otherwise, an apparently successful test can lead to missing or duplicate orders in everyday use.
A sensible starting point connects one shop with one procurement partner. Expand to other business customers once sign-in, transfer, cancellation and the subsequent order are traceable. For each partner, record who reports changes to commercial terms and interfaces.
What does this look like in your work?
We can turn the idea into a sensible next step with you.
OCI & PunchOut for your B2B shop · Packages