E-Commerce: Punchout & Procurement
Large purchasing organisations order from their own procurement systems — suppliers not integrated there are simply considered less often. 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.
Punchout & Procurement challenges
Large purchasing organisations order from their own procurement systems, and suppliers not connected there simply slip through the cracks. An OCI punchout connection becomes a prerequisite for supplier onboarding, corporate customers keep ordering by email and phone for lack of integration, and you lose tenders to competitors who offer exactly that connection.
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.
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.
Good to know
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?
Whether it's an improvement or a fresh start: a no-obligation conversation never hurt anyone.
Related articles from our blog
Shopware B2B Suite 2026: Funktionen, Kosten und warum die Suite gerade ausläuft
Shopware B2B Suite 2026: Features, costs, EOL with 6.8 - and the honest decision Suite vs. B2B Components for new projects.
Shopware B2B Suite zu B2B Components migrieren: Kosten, Zeitplan, Demo
Die B2B Suite läuft aus. So migrierst du auf die B2B Components: was es kostet, wie lange es dauert und worauf du in der Migrations-Demo achten musst.
Subscription commerce with Shopware: How recurring revenue supports your shop
Subscription commerce turns one-off purchases into predictable, recurring revenue. How this works with Shopware and how to start a subscription model.
Frequently asked questions