Shopware B2B Agency

B2B commercethat takes buyers seriously

B2B buyers decide differently from B2C customers: approval matrices, budgets, negotiated prices. As a Shopware B2B agency we build shops that reflect exactly this reality – with the Shopware B2B Suite, the newer B2B Components and custom logic where the standard falls short.

Book a call

Standard shops know one price, one cart, one buyer. In B2B you need customer hierarchies, individual price lists, order approvals and integration with the customer's ERP. Bolt that on afterwards and every edge case becomes a patchwork of plugins.

Every customer has negotiated prices your shop simply cannot represent.

Order approvals still run over email and Excel instead of the shop.

Punch-out from the customer's procurement system stays an empty promise.

For every B2B edge case you stack on yet another plugin.

What matters for Shopware B2B

In B2B the data structure decides everything before the first line of frontend exists. Who is the customer, which hierarchy, which price list, which approval stage – all of that has to be modelled cleanly, or every special rule turns into a workaround later. So we first clarify what the Shopware B2B Suite does out of the box and where your reality needs its own logic. Only then do we talk about templates. That keeps the shop maintainable even when the fiftieth special price arrives.

Prices and approvals in B2B are rarely static: customer-specific lists, tiered prices, budgets per buyer and approval chains all interlock. The source of truth almost always lives in the ERP, not the shop – so we build the pricing and approval logic to stay ERP-driven instead of being maintained twice. Punch-out via OCI or cXML wires your catalogue straight into the customer's procurement system. What matters to us is that error cases become visible rather than failing quietly in the background.

What makes our work in Shopware B2B measurable

Silver Partner: Shopware partner status
OCI · cXML: punch-out standards
4: ERP systems integrated
B2B Suite: plus custom pricing logic

How we deliver B2B

Roles, permissions & hierarchies

Multiple buyers per customer, budgets, cost centres and approval workflows – cleanly modelled with the Shopware B2B Suite and custom extensions.

Individual prices & tiers

Customer-specific price lists, tiered prices and negotiated terms – synced from the ERP in real time or as a robust batch job.

Punch-out & procurement

OCI and cXML punch-out integration with SAP Ariba, Coupa and other procurement platforms, so you're orderable inside your customer's system.

ERP-driven catalogues

Stock, prices and customer-specific assortments come from SAP, Dynamics or proALPHA – bidirectional, with monitoring and retry strategies.

B2B Suite vs. B2B Components – where things stand in 2026

Shopware has moved the B2B Suite, the classic monolithic B2B plugin, into maintenance mode and positioned the modular B2B Components as its successor. New B2B projects on the Evolve plan no longer get the Suite since May 2025, they start directly with the Components. The Suite receives no new features, the Components are actively developed.

The Suite's end of support is tied to Shopware 6.8, and Shopware has officially postponed that major version to 2027. In parallel, extended support for Shopware 6.6 was prolonged until the 6.8 release. So you have room to plan, but the direction is clear: if you still run on the Suite today, you are better off choosing the moment for the switch yourself instead of letting the roadmap dictate it.

Functionally the Components cover the same scope as the Suite: sub-accounts with roles and permissions, approval processes with budget limits, quote requests, quick order, shopping lists and customer-specific assortments. They started as six individually activatable modules (Employee Management, Quote Management, Order Approval, Quick Order, Shopping Lists, Organization Units); as of July 2026 Advanced Product Catalogs, Budget Management and the rule-based pricing engine Individual Pricing have been added, among others. Technically they are API-first and built closer to the Shopware core. For you this means: data and configuration can usually be carried over, custom adaptations to the Suite have to be translated to the new architecture one by one. OCI and punch-out integrations are part of neither the Suite nor the Components core; they run via extensions such as PunchCommerce or B2Bsellers, or via a custom-built interface.

How the switch works in practice is covered in our post Migration step by step: costs, timeline, demo.

Costs & timeline for Shopware B2B

The B2B Components carry no separate license on the Evolve plan, they are included from Evolve upwards (as of May 2026 from around 2,400 euros per month). The Rise plan (from around 600 euros per month) contains no B2B functionality, Beyond is negotiated individually. The costs of a migration from the Suite are therefore almost entirely project costs: analysis, development, data transfer and testing.

As a market-typical orientation, not binding prices: a Suite installation close to standard with few active modules is a migration project in the low five-figure range. An installation customised over years with its own plugins, an adapted checkout and a grown OCI integration can cost a multiple of that, because every special case has to be translated to the new architecture individually. The biggest lever on total costs: combine the migration with a version upgrade, frontend relaunch or new ERP integration that is due anyway, so setup, testing, data migration and go-live happen only once.

The timeline splits into five phases: inventory (which Suite features and custom adaptations you actually use), mapping each used feature to its Component counterpart, build-out in a staging environment alongside live operation, a test phase with real customer accounts and processes, and finally the go-live. A lean, standard-near installation typically takes a few weeks, a complex installation with OCI integration and many active modules is planned in months. Your shop does not stand still meanwhile. Shopware changes plan conditions and prices regularly – verify them on the day before signing a contract.

We don't bolt B2B on afterwards

We know the Shopware B2B Suite, its limits and the points where custom logic is the better answer. With us developers talk architecture, not sales talking packages.

B2B Suite plus custom logic
We use the Shopware B2B Suite where it holds and extend it with clean custom plugins where your pricing and approval models go beyond it.
ERP-driven prices
Customer-specific prices and tiers come from your ERP – SAP, Microsoft Dynamics, Sage or proALPHA – instead of being maintained twice in the shop.
Punch-out that holds
OCI and cXML connections to your customers' procurement systems with clear error paths, so no cart is ever lost in silence.
Live in real B2B operation
This logic runs in production at Bike-Discount and other clients, not just in a demo environment.

Discuss your B2B requirements

Paul Kalisch
Executive Partner

info@next-levels.de +49 (0) 2161 539 71 60

Data & Insights

All posts

Cross-border e-commerce with Shopware 6: setting up a multi-country shop correctly

05/19/2026

Cross-border expansion with Shopware 6 is no push of a button. From twelve real setups: when a new sales channel is enough, when a separate instance is necessary, which tax and payment traps DACH retailers overlook, and how to bring Varnish, hreflang and OSS together cleanly. As of May 2026.