If your B2B shop runs on the Shopware B2B Suite, you have a deadline you may not have noticed yet. Shopware's developer documentation is explicit: the B2B Suite will no longer be supported starting with Shopware 6.8. Everything the Suite does for your customers today, from employee accounts and roles to budgets, quotes and order lists, has to move to its successor, B2B Components.
The good news is that you have time. Shopware has moved 6.8 from 2026 to 2027 and prolonged Extended Support for Shopware 6.6 until 6.8 is available. Nothing breaks this year. But time only helps if you use it.
Below we explain why the Suite is reaching the end of the road, what B2B Components can do today and what not yet, how the two compare honestly, and how to plan a migration you can do calmly instead of under pressure.
Why the B2B Suite is reaching the end of the road
The B2B Suite was Shopware's first full answer for B2B: one comprehensive extension on the Evolve and Beyond plans that added company accounts, roles, budgets, order lists, quotes and sales rep tools on top of the storefront. It worked, and many wholesalers and manufacturers still run on it.
For the future, Shopware chose a different architecture. B2B Components are built into the Shopware 6 core as separate, API-first modules that you switch on per feature and, where needed, per customer. Shopware develops Components independently of the Suite, so new B2B functionality lands there and the Suite receives none of it. For any new B2B project, Components is the only foundation that makes sense.
The end date is no longer a rumour. Shopware's official migration documentation warns that the Suite is not supported from 6.8 onward and advises merchants to plan their migration promptly. Shopware also provides a dedicated B2B Suite Migration extension to move data across. That tells you this is a planned transition with tooling behind it, not a vague intention.
What B2B Components can do today
For most B2B shops, the core is covered. Shopware's own feature overview lists:
- Employee management with roles and permissions per user
- Organisation units for departments or branches, each with its own shipping addresses or payment methods
- Approval rules for orders above a value or for specific roles
- Budget management per unit
- Quote management, from request to negotiated offer
- Quick order by article number or list upload, plus shared shopping lists
- Advanced product catalogues and individual pricing with rule-based discounts per customer or unit
Most of these requirements live at account level, not shop level, which is why one Shopware installation can serve dealers, countries and brands at the same time. It is also why that setup costs less than it sounds, as we worked out in the real cost of multiple brands on one Shopware instance.
Components also get more complete with every minor release. Shopware 6.7.14.0, released in September 2026, lets merchants assign employees from other companies to an organisation with a defined role, add employees to an organisation unit with a role in the same step, and switch selected B2B feature sets on or off by default for newly registered customers. For groups whose buyers work across several legal entities, that closes a gap that used to require custom work.
It is worth being realistic about what is still in motion. Sales representative functionality is the clearest example. The Suite has a dedicated module for reps who order on behalf of customers. On the Components side, Shopware handles this work through quote management and Digital Sales Rooms rather than as a one-to-one copy of that module. If your reps place orders for customers every day, that is the first flow to test. Some features within both B2B products are also reserved for the Beyond plan, so check your plan before assuming a module is available to you.
Suite vs. B2B Components: the honest comparison
Migrating now makes sense when your Suite usage maps onto modules that already exist: roles, budgets, approvals, quotes and order lists. That covers most wholesale and manufacturing portals we see. Moving early also makes sense if you are planning new B2B features, because building them on the Suite today means building them twice.
Waiting a little longer can be reasonable if your sales team relies heavily on the Suite's sales rep tools, or if you depend on a feature that has no Components equivalent yet. Even then, waiting should mean "inventory now, migrate when the gap closes", not "look again in 2027".
The real effort usually sits in customisation. Plugins, theme overrides and integrations written against Suite entities do not carry over on their own, because Components use different data structures. An ERP sync that writes customer contacts as Suite users, a custom approval flow, a storefront template that shows Suite budget data: each needs to be rebuilt against Components. The migration extension moves data. It does not rewrite your code.
Your migration window: why the 6.8 delay is a gift
The riskiest version of this project is the one done at the same time as the 6.8 upgrade. A major release brings its own breaking changes. Shopware has already announced, for example, that XML configuration for services and routes is removed in 6.8 and that plugin developers need to migrate it. Stack a B2B data migration on top of that and you are changing your platform's foundation and your customers' account structure in one go, with your most important customers as the test group.
Migrating on 6.6 or 6.7, well before 6.8 arrives, separates those risks. A practical sequence:
- Inventory your Suite dependencies. Which modules are used, by which customers, and which plugins, templates and integrations touch Suite data?
- Map features to Components. Per module: the equivalent, the gap and the workaround.
- Plan the customisation. Decide what to rebuild, what to drop and what a standard module can replace.
- Migrate on staging first. Back up the database, make sure the message queue worker is running, and run the migration extension. Shopware designed it to add data to Components without removing anything from the Suite, which keeps a way back open.
- Validate with key users. Let a few of your most active B2B customers test their roles, budgets and approval flows before you switch everyone over.
Where Suite data flows into your ERP, review those mappings in the same pass. If your integration layer addresses Suite entities directly, this is the moment to point it at the Components data model.
Frequently asked questions
Learn more about migrating from the B2B Suite
The end of the B2B Suite is not an emergency, but it is a real deadline. Shopware's delay of 6.8 to 2027 gives you something rare in e-commerce: the chance to do a structural change in a quiet window, on your own schedule, before a major upgrade forces your hand. Your B2B customers expect a portal that simply works, as we described in what B2B buyers really expect, and a calm migration is how you keep it that way.
As a Shopware Business Partner and official Alumio partner, Memo builds Shopware B2B webshops and the integrations behind them. Running on the B2B Suite and wondering what migration involves for your shop? Request a B2B Suite quick scan or book an introduction call, and get a concrete migration picture: what moves automatically, what needs rework and when it makes sense to plan it.