PunchOut and procurement, wired into the buying process.
OCI and cXML catalog patterns, buyer authentication, basket transfer, order handoff and the ERP follow-through that makes procurement work.
When punchout becomes a commercial requirement
A major customer requires ordering through their procurement platform or the business goes elsewhere. Orders arrive by email and are re-keyed, creating errors and delay. Each new customer procurement system becomes a bespoke project. Invoices are rejected because they do not match the purchase order structure.
What we implement
cXML punchout: Setup request handling, authenticated session start, cart transfer and order message processing. OCI punchout: SAP SRM and OCI-based procurement integration with the expected field mapping. Ariba Network: Supplier connectivity, catalogue delivery and order and invoice document exchange. Customer-specific catalogues: Contract catalogues and pricing per buying organisation. Purchase order handling: PO numbers, cost centres, account assignment and validation carried through to the ERP. Electronic invoicing: Invoice documents matching PO structure so they clear the customer's matching rules.
Engineering considerations
Session security: Credential handling, session lifetime and protection against replay. Cart round-trip: Reliable transfer back to the procurement system, including edits and re-punchout. Field mapping: Customer-specific requirements handled through configuration rather than forked code. Testing with buyers: Joint testing against the customer's actual procurement environment. Error visibility: Failures surfaced to your team, not silently returned to the buyer. Onboarding repeatability: A repeatable setup so the second and third customer are far quicker than the first.
How punchout projects run
Confirm the customer's protocol, platform and technical contact early. Agree catalogue scope, pricing rules and PO field requirements. Build against the specification, then test jointly in the customer's test environment. Validate the full loop: punchout, cart transfer, order, confirmation, invoice. Document the setup so onboarding the next customer is a configuration exercise.
Punchout questions
What is punchout? Punchout lets a buyer start in their own procurement system, browse your catalogue in an authenticated session on your storefront, and return the basket into their approval and ordering process. The order then arrives electronically. Which protocols do you support? cXML — used by Ariba Network, Coupa and similar platforms — and OCI, used by SAP SRM and related procurement systems. Do buyers see their contract prices? Yes. The punchout session is authenticated against the buying organisation, so catalogue scope and contract pricing follow the same rules as a logged-in B2B session. How long does onboarding a new customer take? The first implementation carries the design effort; after that, onboarding another buyer is largely configuration and joint testing, which is much faster.