Shopware B2B Components vs the Shopware B2B Suite: what is the difference?

No, and the confusion is everywhere, including on pages we have written ourselves. They are two separate Shopware products with separate documentation trees, and a proposal that uses the names interchangeably has not been checked. Both cover the same territory: company accountA company account is a customer record that holds several people, each with their own login and their own permissions. One buyer might place orders, another might only approve them, a third might only look up past invoices. structures, approvals and quoting.

B2B Components is the newer of the two. Shopware’s documentation describes nine components, Quick Orders, Employee Management, Quote Management, Organisation Units, Order Approvals, Shopping Lists, Advanced Product Catalogues, Budget and Individual Pricing, each with its own minimum Shopware version, and states that "the B2B Components are available to you as of the Shopware Evolve plan via the Shopware Commercial extension".

The B2B Suite is the older product. It has its own developer documentation section, separate from the commercial-features tree where B2B Components live, it is documented for Shopware 6 with separate documentation still published for Shopware 5, and its administration and customer-account documentation sit under extensions rather than under commercial features.

One practical tell if you are reading a proposal or a job advert: if it names individual components with version numbers, it means Components. If it talks about the suite as a single thing you switch on, it probably means the Suite, or it means the writer has not checked.

Shopware addressed this directly in its own announcement of B2B Components, an article first published in August 2023 and last updated 10 March 2025. Three statements from it are worth quoting because they settle questions people keep guessing at.

On whether the Suite is dead: "the introduction of Shopware B2B Components does not signal the end of the Shopware B2B Suite". So anyone telling you the Suite is discontinued is going beyond what Shopware has said.

On migration: "we are dedicatedly working towards providing a smooth migration pathway from the B2B Suite to Shopware B2B Components". That is a stated intention, not a shipped tool, and the wording has stood since March 2025. Treat a Suite-to-Components migration as a project to scope rather than a button to press.

On the future: "at some juncture in the future, the two offerings will diverge, even in their fundamental functionalities". That is the sentence that should decide a new build. Divergence with new features landing on Components is a different proposition from two products moving in parallel forever.

One caution about the date. That article was last updated in March 2025 and we read it on 20 August 2026. Shopware ships monthly, so confirm the current position with Shopware directly before you commit a roadmap to it.

One claim per cell, read from Shopware documentation and from Shopware’s own announcement on 20 August 2026. Where we could not establish something from public documentation, the cell says so rather than guessing.

The row that matters most for a new build is the last one.

Because the older name is still the one in circulation. Agency pages, job adverts, comparison articles and vendor decks written between 2019 and 2023 all say B2B Suite, and that language has been copied forward for years without being re-checked. Search results reward the older phrase because more pages carry it.

We are not exempt. Acro Commerce’s own Acumatica and Shopware connector page currently says that multi-division hierarchies, department budgets and approval workflows "come from Shopware’s B2B Suite". Those capabilities are Organisation Units, Budget and Order Approvals, which are B2B Components. That wording is stale and we are correcting it, and we are saying so here rather than quietly editing it, because a page that tells you to check vendor claims should be checkable itself.

The practical cost of the confusion is not embarrassment, it is scoping. The two products have different documentation, different version gates and, as far as we can establish, different licensing. A requirements document that names the wrong one produces an estimate for the wrong work.

Five questions. Ask them in writing and keep the answers, because the public documentation does not settle all of them and the person selling to you may be using the older vocabulary out of habit.

The fourth question is the one that catches existing Shopware customers.