What are Shopware B2B Components and how do they differ from the old B2B Suite?

Shopware B2B Components are the newer, modular replacement for the old Shopware B2B Suite. Instead of installing one large monolithic package with tightly coupled features, you now enable smaller business-focused components inside Shopware 6 that handle specific B2B needs like company accounts, employee permissions, approval rules, quote management, and buyer-specific pricing. The goal is flexibility. You only install and maintain the parts your store actually needs.

The old B2B Suite came from the Shopware 5 era and was heavily tied to legacy architecture. It worked well for classic wholesale stores, but customising it was painful once workflows became more complex. B2B Components are built for Shopware 6’s API-first structure and Flow Builder ecosystem, so integrations and custom logic are much cleaner to extend.

For most merchants moving from Shopware 5 to Shopware 6, this is one of the biggest architectural changes. You’re no longer buying a single “B2B mode” for the store. You’re assembling B2B capabilities feature by feature depending on how your sales process works.

How it works

In the old B2B Suite, features were bundled together as a large plugin layer sitting on top of Shopware. That meant shared dependencies, coupled permission logic, and harder upgrade paths. Even small changes often required overriding core workflows.

B2B Components in Shopware 6 work more like composable modules. They integrate with native entities, APIs, Rule Builder, Flow Builder, and custom apps. So instead of hacking wholesale logic into the storefront, you extend existing Shopware services in a cleaner way. That’s a big deal for long-term maintenance.

It also changes how projects are scoped. With the old suite, many stores paid for functionality they never used. With components, you can build lighter B2B setups without dragging in procurement workflows or approval chains you don’t need.

Biggest differences at a glance

• The old B2B Suite was plugin-centric. B2B Components are platform-centric and tie into native Shopware services.
• Shopware 5 customisations often required deep overrides. Shopware 6 B2B projects rely more on APIs, apps, events, and Flow Builder automation.
• The old suite assumed a traditional wholesale storefront. B2B Components support headless and composable commerce setups much better.
• Upgrades are usually cleaner because components are less tightly coupled.
• Licensing and project scoping are more modular. That lowers complexity for mid-market stores that only need selected B2B features.