Punchout & Procurement
Large purchasing organisations order from their own procurement systems — suppliers not integrated there are simply considered less often.
Overview
We connect your Shopware shop via OCI punchout or cXML to your customers' SAP Ariba, Coupa, or other procurement platforms. The buyer switches seamlessly into your shop, builds their basket, and transfers it back to the approval system.
The essentials at a glance
- We connect your Shopware shop via OCI punchout or cXML to your customers' procurement systems such as SAP Ariba or Coupa.
- The buyer switches into your shop seamlessly via single sign-on, builds their basket, and transfers it back to the approval system — without really leaving their own system.
- We configure the setup per customer, because OCI and cXML are only framework specifications and every procurement system implements the standards slightly differently.
- We test the complete flow in a test environment and support acceptance testing by the buyer or their IT team.
- Punchout is often the prerequisite for being considered a supplier at all by large companies and public sector buyers.
OCI Punchout Implementation
OCI is the standard protocol for integrating supplier shops into SAP procurement systems. We implement the complete OCI punchout flow in Shopware: single sign-on from the procurement system, cart session in the shop, and return transfer of the filled basket via standardised basket transfer. The buyer never really leaves their system.
cXML & Further Protocols
Beyond OCI, many procurement systems support cXML for order transmission and catalogue updates. We implement cXML punchout setups and CIF catalogue transfers so your catalogue in your customers' procurement systems is always current — without manual catalogue uploads.
Customer-Specific Setup
Every punchout customer has their own technical requirements: different protocol versions, specific mandatory fields in the basket transfer, and individual authentication methods. We configure punchout setups per customer, test the complete flow in a test environment, and support acceptance testing by the buyer or their IT team.
Pricing in Punchout
In the punchout context, each customer's individual pricing agreements apply. We ensure the punchout session loads the correct customer conditions — framework agreement prices, special discounts, and approved catalogue — so the buyer sees exactly what their contract entitles them to.
The Punchout Flow at a Glance
A punchout integration follows a clearly defined sequence — from leaving the procurement system to transferring the approved basket back. Every phase must work seamlessly for the integration to be adopted in day-to-day purchasing.
Authentication & SSO
The buyer initiates from within the procurement system — a single sign-on passes session parameters, no separate login required.
Seamless Shop Entry
The Shopware shop opens in the buyer's context: customer-specific prices, approved assortments, and individual terms are loaded immediately.
Basket Assembly
The buyer navigates and selects products as usual — the shop behaves like a standard B2B shop but remains within the punchout context.
Basket Transfer Back
Via OCI hook or cXML PunchOutOrderMessage, the basket is returned to the procurement system in a structured format — no manual input, no data loss.
Approval Process in Customer System
The basket goes through the internal approval workflow (SAP Ariba, Coupa, etc.) and is returned to the shop as a purchase order.
Applies equally to OCI and cXML protocols; customer-side acceptance testing closes each phase.
Success Factors in Punchout Integration
Not all quality attributes of a punchout connection carry equal weight. This ranking shows what truly matters in practice — and what fails first during go-live if it is missing.
- Seamless SSO transitionBuyers abandon the flow as soon as an extra login screen appears
- Smooth basket transferData loss on return makes the integration unusable
- Customer-specific protocol variantsOCI/cXML implementations vary between procurement systems
- Customer prices & termsIndividual framework agreements must be visible in the punchout context
- Shop performance & load timeSlow pages lead to abandonment and rejection of the integration
Relative Weighting
Relative weighting based on failure frequency and acceptance-testing relevance in typical enterprise projects.
What matters for Punchout & Procurement
Punchout is often the entry ticket, not the extra. Many large companies and public buyers purchase exclusively through their own procurement systems, and a supplier not connected there is simply not considered active. The connection therefore decides not on comfort but on whether you appear in their processes at all.
The OCI or cXML flow has to feel seamless, otherwise it gets avoided. A setup that works technically but is clunky to operate puts buyers off. Single sign-on without an extra login, fast page loading and a smooth basket transfer back into the approval system are the minimum requirements, not the finishing touch of an accepted integration.
Every procurement system implements the standards slightly differently, and that is exactly what many underestimate. OCI and cXML are framework specifications, not exact ones, which is why a setup that works with one customer can stumble with the next. Without customer-side testing and a shared acceptance process, the risk of incompatibilities in production is high.
Solid punchout work is designed from the customer's buying process, not from your own shop. The buyer wants to switch into your shop seamlessly, assemble their basket and hand it back into their system without a break. Only when that transfer works cleanly in both directions does a technical connection become a genuine sales channel.
Punchout opens enterprise purchasing processes
Many large companies and public sector buyers purchase exclusively through their own procurement systems. A punchout connection is often the prerequisite for being considered an active supplier in their processes at all.
OCI flow must be seamless
A punchout setup that technically works but is clunky to use will be avoided by buyers. Single sign-on without extra login, fast page loads in the shop, and a smooth basket transfer are the minimum requirements for an accepted punchout integration.
Each customer has individual requirements
Punchout standards are framework specifications, not exact specifications. Each procurement system implements OCI or cXML slightly differently. Without customer-side testing and a shared acceptance process, the risk of incompatibilities in production is high.
Right inside procurement
With us you're always at the cutting edge of technology and benefit directly from our developer expertise. Together we analyze your shop, identify key areas and develop tailor-made solutions. Your goals and expectations are at the center of our work.
Developers, not resellers
Your shop is built by developers who really understand the code. We pass nothing to subcontractors.
Shopware down to the detail
Architecture, API integration and performance from hundreds of project hours.
One team, every discipline
Development, design and marketing come from one team that works without friction at the handoffs.
Built for growth
We build measurably for conversion, load time and revenue.
Partner, not vendor
We stay on after launch and keep developing your shop continuously.
Ready for your successful online shop?
Related articles from our blog
Angular vs React vs Vue: Which frontend framework suits your shop?
Angular, React or Vue for your shop? A practical comparison for e-commerce and headless shopware with a clear recommendation based on team, SEO and setup.
Shopware Community Day 2026: Die agentische Ära beginnt mit Infrastruktur, nicht mit Chatbots
Vier Launches in Köln, aber die eigentliche Nachricht liegt tiefer: Der Shopware-Core ist jetzt vollständig MCP-abgedeckt und UCP-ready. Was das für deinen Shop bedeutet und welche drei Hausaufgaben jetzt anstehen.
Shop-Migration ohne SEO-Verlust: So überlebt dein Ranking den Plattformwechsel
Der SEO-Verlust bei einer Migration passiert nicht am Launch-Tag, sondern Wochen vorher im Redirect-Mapping. Die handwerklichen Fehler, die Rankings wirklich kosten, und wie du sie vermeidest.
Frequently asked questions