What your business customersactually get fromShopware B2B

Basics

Is Shopware a good B2B shop system?

As a B2B shop system, Shopware works well when your business customers need more than a consumer does: several people ordering on one account, prices of their own, and orders that someone in their company has to sign off. Shopware has built dedicated modules for exactly these processes, and part of what you need comes without any extra plan.

It helps to think in two layers. The first layer ships with every Shopware 6 installation: customer groups, net price display, a registration flow in which you check dealers before you let them in, and the Rule Builder for prices, shipping and payment methods based on conditions. Plenty of smaller wholesalers get a long way with that alone.

The second layer is B2B Components. They mirror what really happens in a company's purchasing: one person fills the cart, another approves it, and for larger volumes the buyer would rather ask for a quote than pay list price. These modules are tied to a specific plan, and you want to know that early, because it changes the numbers.

Core features

What does Shopware 6 B2B offer without an extra plan?

Shopware 6 B2B without an extra plan comes down to customer groups, net prices, dealer approval and rule-based pricing through the Rule Builder. According to the Shopware documentation, you decide per customer group whether prices are shown net or gross, so trade customers see the figures they actually calculate with while consumers keep seeing gross prices.

You can also switch on a separate registration form for each customer group. Anyone who signs up through it is not added to the dealer group automatically. You review the request in the administration, accept or reject it, and the customer receives an email about the decision, which keeps your trade terms visible only to businesses you have checked.

The Rule Builder links conditions such as customer group or cart total to outcomes in the shop. The documentation lists product prices, shipping methods, payment methods, promotions and Flow Builder flows as places where rules apply. A common setup: in a product's advanced prices you store a separate price for the rule “customer group is dealer”, and only members of that group may pay by invoice.

Features

What do Shopware B2B Components do in day to day purchasing?

Shopware B2B Components are separate modules you switch on as needed, rather than one package you take as a whole. Shopware documents them module by module, and at their core they cover five processes that come up again and again when you sell to businesses.

With Employee Management a company customer creates its own employees and gives them roles. Order Approval builds on that: certain roles approve or reject orders placed by other roles before those orders reach you. Quote Management lets customers request a quote for the contents of their cart, which you then review and adjust in the backend. Quick Order adds items to the cart by item number or from a CSV file, something anyone who has ever searched for a hundred line items by hand will appreciate. And Shopping Lists let customers save lists for later orders, to which you can add your own suggestions.

On top of that come modules for larger structures. Organisation units map a customer's departments or sites as a hierarchy, and budgets per unit, product catalogues per unit and Individual Pricing build on them. For these newer modules in particular, the documentation names a minimum Shopware version per module, so check the version your shop runs before you plan around them.

1. Step 1Employee ManagementCompany account with employees and roles, the basis for approvals and organisation units.
2. Step 2Order ApprovalOrders only reach you once an authorised role has signed them off.
3. Step 3Quote ManagementCustomers request a quote for their cart, you review and adjust it.
4. Step 4Quick OrderItems go straight into the cart by item number or CSV file.
5. Step 5Shopping ListsSaved lists for recurring orders, optionally with your suggestions.

Plans

Which Shopware plan includes the Shopware B2B features?

Shopware's pricing page places the Shopware B2B features from the Components in the Evolve and Beyond plans, not in Rise and not in the Community Edition (as of October 2026). Among the items listed there are roles and permissions, quote management, quick order, shopping lists, customer specific prices, organisation units and budget management.

On organisation units the sources disagree. Shopware's own documentation and pricing page list them from Evolve, while a specialist article from March 2026 assigns them to Beyond only. What counts for your planning is what Shopware confirms in your quote, so ask that question there, in writing.

Plan prices change over time. Don't plan with a figure from a blog post; work with a current quote and set it against what it would cost to build the missing features yourself. For a broader look at how the editions differ, see our article on Shopware pricing and editions.

Legacy

Shopware B2B Suite or Components: which one applies now?

The Shopware B2B Suite is the older B2B package, and according to the developer documentation it is no longer supported from Shopware 6.8. Shopware has announced 6.8 for 2027, so if you run the Suite today you still have time, but you should not push the switch into the year the new version lands.

The difference is architectural. The Suite is a closed package with a fixed feature set, whereas Shopware describes the Components as more modular and flexible, so you only activate what your customers actually use. New features such as budgets and Individual Pricing are now being built for the Components.

Shopware documents a dedicated migration path that moves data from the Suite to the Components. Before you start, check which customisations in your shop depend on the Suite, because your own code that talks to it will not move across by itself. How to prepare a major update in general is covered in our Shopware update guide.

Integration

Where does a Shopware B2B shop get its prices and stock from?

A Shopware B2B shop usually takes prices, stock levels and customer data from the ERP, because that is where terms and inventory are maintained anyway. Shopware provides the Admin API for this, which the documentation describes as meant for integrations, automation and data synchronisation, with read and write access to every entity.

For B2B that means: before you start maintaining dealer prices in the shop by hand, decide which system leads for which value. If the customer price lives in the ERP, it belongs in the shop through the interface, not in an extra rule that nobody can find a year later. The options and the pitfalls are covered in our article on Shopware ERP integration.

If the standard falls short, for instance because your approval process depends on rules held in the ERP, you are left with a custom extension or an API integration. Through Shopware development at Scalableloops we build integrations and customisations of this kind for Shopware 6.6 and 6.7, tested on both versions.

Planning

How do you plan a Shopware B2B shop without building things twice?

You plan a Shopware B2B shop best from your customers' purchasing process, and only then from the feature list. Write down who places orders at your customers, who approves them, how prices come about and which orders repeat.

Then hold those sentences against the table above. Whatever the core covers costs you no extra plan. Whatever only the Components can do decides between Evolve and Beyond. And whatever neither covers is a case for a custom solution, though it is worth checking first whether an existing extension already does the job. Our guide Shopware plugin: buy or build? helps you weigh that up.

Next steps

How to scope your Shopware B2B needs before you invest

1. 01Write down the buying processWho orders at your customers, who approves, how prices come about, which orders repeat. A few sentences are enough.
2. 02Compare core and ComponentsMark what the core covers and what only the B2B Components can do. That answers the plan question.
3. 03Get plan and version confirmedAsk Shopware to confirm in writing which modules your plan includes, and check the minimum version for each module.
4. 04Settle the ERP interfaceDecide which system leads for prices, stock and customer data before anyone maintains them in the shop.