Shopware B2B webshop: from B2B Suite to B2B Components
The buyer who orders components for your production line on Monday morning spent the weekend shopping on consumer webshops. That is the benchmark now. They want to see their own agreed prices, check stock themselves and place a repeat order at eleven at night without phoning anyone.
A Shopware B2B webshop approaches this differently. Much of what wholesalers and manufacturers need sits in the platform itself or in the B2B module, rather than in separate plugins that collide at the next update. This page covers what Shopware offers as standard, what the move from B2B Suite to B2B Components means, and why the ERP connection ultimately decides whether any of it works.
.png)
Where existing ordering portals fall short
Companies looking for B2B webshop development usually come from a portal that was fine once. The pain is rarely in the design. It is that the portal knows only one version of reality, while B2B is made of exceptions.
This customer has a contract price, that one has a volume tier from 250 units, a third may only order up to a budget ceiling and needs sign-off from the purchasing manager above it. When your platform cannot hold that logic, it moves into spreadsheets and into the heads of your internal sales team.
That is exactly why orders keep arriving by phone, and why the digital investment never shows up as less manual work. Gartner research cited by BlueSnap found that 75% of B2B buyers prefer a purchasing experience without a sales rep in the middle.
Every exception you solve in custom code becomes next year's biggest brake on progress. Shopware therefore treats business selling not as an extension of consumer selling, but as its own model with its own data structure.
What Shopware offers for B2B
The functionality you would expect in a serious wholesale ordering portal largely sits in the platform itself. These are the seven parts that in practice take the most manual work away from your internal sales team.
Customer-specific prices
Every logged-in buyer sees their own contract price, set per customer, per customer group or per contract.
Volume tiers
Discounts that follow the number of units, so volume agreements no longer need confirming by email.
Quote management
A request from the webshop, a response from your internal sales team and a quote the customer converts into an order.
Budgets and thresholds
Order thresholds and budgets per user, with an approval step as soon as an order exceeds the agreed ceiling.
Users and roles
Multiple users under one customer account, with permissions for who may view, who may order and who approves.
Fast ordering
Ordering by article number or through an uploaded order list, for buyers who know exactly what they need.
Repeat orders
Recurring orders your customer places again straight from the order history, without walking through the catalogue.
From B2B Suite to B2B Components
For years the B2B Suite was the standard for business functionality in Shopware. That suite is being phased out and succeeded by B2B Components. The difference is not cosmetic: where the suite was one coherent block, B2B Components is modular. You switch on what you need and leave the rest, which keeps both maintenance effort and installation complexity down.
For existing shops that means planning a decision rather than waiting for one. If you run the B2B Suite today, the question is not whether you move but when, and which of your current custom extensions become redundant in the new model. In many cases custom work disappears, because the standard has caught up.
Release 6.7.13.0 of 5 August 2026 took two steps here:
- Quote management: product comments, version control and line-level discounts
- Organization units: a head office with branches under one contract
That finally mirrors how quoting actually works in practice: back and forth over a handful of lines, a discount on one article, and a new version for the customer. With organization units you model complex customer hierarchies, where every branch has its own users, budgets and delivery addresses.
Which B2B functionality you can actually switch on is determined by Shopware, not by your agency. B2B Components is tied to your licence, so the plan you need follows from what you want to be able to do. We put that question on the table early in the project, because the answer affects your annual costs. What it means for your budget is covered on the costs page.
.png)
B2B and B2C in one shop or in separate sales channels
If you sell both to businesses and to consumers, the question is not whether Shopware can handle it but how you set it up. A single shop with different customer groups works well when the assortment largely overlaps and the difference sits in pricing and payment terms. You then manage one catalogue and one content environment.
Separate sales channels make more sense as soon as branding, assortment or navigation genuinely diverge, or when B2B needs its own domain and its own SEO. Shopware supports multiple sales channels on a single installation, so you never need to run a second shop for it.
The decision is about management and positioning, not technology. The Shopware hub explains how that choice ripples through the rest of your landscape. Underneath both variants sits the same engine: the Rule Builder, which lets you define conditions without code, and the Flow Builder, which routes an order above a certain value to an account manager.
The ERP connection is the heart of your B2B webshop
All the B2B functionality in the world is useless if the price on screen is wrong. In B2B the webshop is rarely the source of truth: pricing agreements, credit limits, stock and order status live in your ERP. The webshop has to display and return that data, reliably and quickly enough to make promises on.
That is why Memo builds the integration layer as its own component, with Alumio as the iPaaS between Shopware and the ERP. Shopware stays on-premise, giving you control over hosting and performance, while the connections live in a managed environment where you can monitor and repair them. What that layer looks like is set out on the page about connecting Shopware to your ERP, PIM and marketplaces.
Which ERP sits behind it differs per client. We have built integrations with Exact Online, Microsoft Dynamics and AFAS among others, and the approach is always the same: the ERP remains the source for prices, credit limits and stock, the webshop displays them, and Alumio watches the traffic in between.
Boomlab, a laboratory wholesaler serving the Benelux, runs exactly that setup: a Shopware B2B environment with Alumio as the integration layer. Memo has been a Shopware Bronze Partner since 2018 and is also a Shopware Extension Partner, with seven valid Shopware 6 certifications in the team and six extensions in the official Shopware Store. See the Boomlab case for the details.
Want to know which of your current B2B processes Shopware already solves as standard, and where you genuinely need custom work? Send us your process description or let us look inside your current portal. In half an hour we will map what is standard, what B2B Components adds and which integrations you need.
Frequently asked questions
What is the difference between the Shopware B2B Suite and B2B Components?
The B2B Suite was a single coherent module of business functionality and is being phased out. B2B Components is its successor and is modular: you activate only the parts you need, which makes updates and maintenance simpler. If you run the B2B Suite today, plan the move deliberately rather than waiting until support ends.
Can I show ERP-driven customer-specific prices in the webshop?
Yes, and that is the normal setup. The ERP remains the source for contract prices, volume tiers and credit limits, and the webshop shows them to the logged-in customer. An integration layer such as Alumio keeps that flow manageable and visible, instead of a direct link that breaks whenever either side changes.
Can several people from the same customer place orders?
Yes. One customer account can hold multiple users with their own roles and permissions: view, order or approve. Budgets and order thresholds determine when an order needs an approver's sign-off. Organization units extend this to head offices with branches under the same contract.
Should B2B and B2C live in separate webshops?
Not necessarily. If the assortment largely overlaps and the difference sits in prices and terms, one shop with customer groups is enough. If brand, assortment or navigation diverge sharply, a separate sales channel on the same Shopware installation is more comfortable. You then run two experiences without paying for a second platform.
What does a Shopware B2B webshop cost?
That depends on your assortment, the number of integrations and how much of your current logic has to come along. The largest cost item is almost never the shop itself but the integration with ERP and PIM. The costs page sets out indicative ranges and what actually drives the price.