If you're still planning a Shopware project based around the B2B Suite in 2026, buy an end-of-life module. That sounds exaggerated, but it is the official line from Schöppingen: Shopware only maintains the suite in maintenance mode and clearly positions the more recent Shopware B2B Components as the successor path. Anyone who releases budget now and does not know this is building tech debt into the investment proposal.
This does not invalidate the question "is the B2B Suite worth it?". Thousands of shops are running productively with it, the module is anchored in the market and a large part of the B2B logic that SMEs need is still functionally located there. But the question will take a different form in 2026 than in 2023. It's less about whether the suite is worth its price and more about whether you should invest in it today or jump straight to the next level.
What the Shopware B2B Suite is and what its 2026 state really looks like
The Shopware B2B Suite is the older, classic B2B module for Shopware 6. It attaches itself to a standard shop and provides the functions that distinguish a nice order catalogue from a serious B2B self-service platform: Sub-accounts with roles and rights, approval processes, quotation requests with their own object type, order lists and quick ordering via SKU or CSV, customer-specific assortments and prices, OCI and punchout integration to procurement systems as well as a salesperson view in which the office staff can order on behalf of a customer.
Functionally, this is a complete package. Strategically, it is a module with an expiry date. Shopware introduced B2B Components as a modular successor in 2023, has maintained the suite in maintenance mode since then and openly communicates that it is scheduled to be phased out with Shopware 6.8. Anyone making a purchase decision should have this status in the first slide of the argumentation, not as a footnote at the end.
What the suite is not was the same answer in 2023 as it is today: no ERP replacement, no PIM, no CRM. It is the B2B sales logic on the Shopware platform, not the answer to every requirement that starts with "B2B". If your real pain point is master data maintenance or the complaints process, no B2B module in the world will help. Then the leverage lies in the PIM and ERP, and Shopware is only the front end of this architecture.
Suite or B2B Components: The real decision 2026
This is the decision that many teams underestimate. Both modules offer B2B functionality on Shopware 6, but today they are aimed at completely different time horizons.
The Suite is the ready-made package from the past. If you want a classic, process-driven B2B shop and are building on existing Suite setups, this is the quickest way to achieve results. For existing customers with a current Suite installation, there is no good reason to switch in the middle of the season. Maintenance continues, security updates come, the system remains operational until the planned EOL.
The B2B Components are a bet on the future. Instead of a ready-made package, you get individual components that you can combine in a targeted manner. Employee management, offers, quick ordering, customised product ranges as separate modules, closer to the API-first spirit of Shopware 6, better suited for headless and composable frontends. The range of functions is not yet fully congruent with the Suite, but is consistently approaching it and is recognisably the product investment in which Shopware flows.
For new projects in 2026, the recommendation in most cases is: B2B Components, not Suite. Exception: your requirements profile depends on precisely one function that is still only fully mapped in the Suite today and that you will need productively in the next twelve months. Even then, a migration strategy to Components belongs in the initial project plan, not the next one.
In short: you are not deciding between two equivalent modules. You are deciding between a system with a clear phase-out date and a system in which Shopware is actively investing.
Functional scope: what the suite can do and where components can already keep up today
The following five functional blocks are what determine the B2B suitability of a shop system for SMEs. I'll go through them and tell you what the status is at Components, because that's the question you'll actually have to answer in 2026.
Organisational structures instead of individual customers: A B2B customer is rarely one person. It is a buyer, a technical contact, an accounting department and sometimes a corporate centre that has to approve. The suite maps this hierarchy: Main customer with sub-accounts, each with their own rights, cost centres and budget limits. Components cover this in their employee management component and are largely on a par here.
Approval processes with budget limits are the second block. Orders over 5,000 euros? Only go out if the line manager approves. Sounds trivial, but it is precisely the reason why classic B2C shops fall behind with large SMEs and corporate customers. Without an approval workflow, phone calls and emails continue in the background; the shop is then just a catalogue, not a sales channel. Approval workflows are more deeply developed in the suite than in the components today, but the components are getting closer.
Offers as a separate process are the third block. In B2B, a purchase often begins with an enquiry, not with a click on "Add to basket". The suite recognises quote requests as a separate object type, with negotiation, expiry dates and conversion to an order. Components now provide their own quote module for this. Anyone who has to replicate this in the standard system will quickly have a four- to five-figure custom development project on their hands.
Order lists and quick orders are the fourth block. Recurring orders with twenty to three hundred items are commonplace in B2B, not a special case. Order lists, CSV uploads and quick SKU searches save buyers a measurable amount of time and are often the real reason why a B2B shop is accepted in the first place. Both Suite and Components cover this. This is where the playing field is level.
OCI/Punchout for corporate customers is the fifth and, in practice, the trickiest block. Large purchasing organisations dock their SAP or Coupa systems to your shop, fill the shopping basket there and transfer it to their own ordering system. Important clarification: OCI/Punchout is neither included in the suite nor in Components ready in the core. In practice, this is done via established extensions such as PunchCommerce, B2Bsellers or Agiqon, depending on the requirements profile. Anyone who advertises with "natively included" has either done the demo superficially or is embellishing it. Plan the extension into the budget right from the start.
What a B2B shop system with Shopware really costs
The official prices have been publicly available on shopware.com since the beginning of 2026, in a clarity that did not previously exist in the Shopware world. Important first: The plan structure and conditions change regularly. Verify the figures before each contract on a daily basis, especially the prices at the end of the funnel of a financial year.
As of May 2026, Shopware 6 is available in three plans. Rise starts at around 600 euros per month, but does not include B2B functionality. Evolve starts at around €2,400 per month and is the level from which the B2B components are included. Beyond is negotiated individually, is often in the five-digit range per month according to publicly available estimates and is aimed at setups with a high GMV, several shops or special support requirements. Those who wanted the classic B2B suite in the past historically ran Enterprise contracts, which today typically merge into Beyond tariffs.
Implementation is the bigger item, not the licence. According to our estimates for new medium-sized projects, the one-off budget is between 80,000 and 300,000 euros, depending on the depth of the product range, interface complexity and front-end requirements. Anyone who thinks this is a lot should consider two figures. Experience has shown that an independent custom B2B portal on a greenfield site costs many times more and comes with a significantly higher maintenance risk. And around half of the implementation budget is spent on items that have nothing to do with the choice of suite or components: ERP interface, PIM connection, authentication, hosting, theme.
Ongoing operation comes on top of this. Cloud hosting, support SLA, performance optimisation, continuous development. In our experience, for a medium-sized B2B shop with a noticeable load, a figure of 3,000 to 10,000 euros per month is realistic, across platform, partner retainer and hosting combined. For very large setups with their own traffic peaks and several language shops, the range is higher.
What you should not do at this point is confuse the pure licence with the total cost of ownership. Platform costs are never the most expensive item in a serious B2B project. They only seem expensive if you look at them in isolation.
When Shopware pays off as B2B shop software
Three profiles in which the investment typically pays off:
The manufacturer with a mix of retailers and direct customers who wants to digitalise its wholesale business. Customer-specific product ranges and prices pay off here. Retailer A sees different products and conditions than retailer B, both order via the same shop, both have sub-accounts for their own employees. Without this separation, you would have to recreate this in custom logic. This works for two retailers, but is no more than twenty.
The technical wholesaler whose buyers work with order lists and quick orders. Here, the leverage lies not in glossy product detail pages, but in the speed of reordering. If a service technician orders three hundred items for the following week on Thursday afternoon, the CSV upload function decides whether the shop is used or bypassed.
The machine or component manufacturer with corporate customers whose bulk buyers procure via SAP or Coupa. Here, OCI/Punchout is not a "nice to have", but a prerequisite for the shop to be accepted by the customer's purchasing department. The right extension delivers this, everything else would be in-house development with a permanent maintenance promise.
What these three profiles have in common: The B2B processes are the core of the business model, not an accessory. The shop is not "also B2B", but an essential sales channel. For all three profiles, the right answer in 2026 is Components rather than Suite, provided that no existing Suite investment delays the migration.
When Shopware is the wrong B2B shop system
Honest rebuttal, because otherwise no practical contribution. There are constellations in which the entire model is oversized and the decision in favour of it creates more problems than it solves.
If your B2B sales essentially consist of ten key customers that you know personally, the real lever is not a self-service portal with an approval workflow. A streamlined, well-integrated shop for routine orders plus a sensible CRM for the sales force is more likely to be a winner here.
If your product range depth is low and you essentially make B2C-related sales with company accounts, the Rise tariff with an "employee account" extension from the store is often sufficient. It's difficult to justify the Components licence for thirty orders per day.
If your real pain point is master data quality, ERP integration or logistics processes, no B2B module in the world will help. Then Shopware is only one building block of the architecture anyway, and the expensive question is how cleanly your PIM and order management are docked. In this architecture discussion, a Shopware agency with B2B experience brings significantly more than a licence upsell.
How to evaluate correctly (including demo)
A serious evaluation rarely goes beyond a standard 60-minute demo. What actually provides insight:
Firstly, keep your three toughest user stories to the module. Not "can the sub-accounts", because of course it can. But rather "my customer X with fourteen employees and three cost centres, two of them with approval from 2,500 euros, what does the actual flow look like, from login to approved order?" If the demo partner doesn't show this in twenty minutes, that's a signal.
Secondly: run through OCI or Punchout in a real case, if relevant. With one of your corporate customers, against their real procurement system, including extension. This is the component that is most often glossed over in demonstrations.
Thirdly, negotiate TCO without a licence price. Don't ask "what does the B2B Suite cost" or "what does Evolve cost". Ask "what does a ready-to-use B2B shop cost for our profile over three years", i.e. platform, implementation, hosting, maintenance, migration. That's the figure you write in the investment proposal.
Fourthly: migration path on the table. If you are still using the suite in 2026, you should not move the components switch to nowhere. Take a look at at least an initial migration path draft before you sign. A Shopware B2B demo without this question is half a conversation in 2026.
Conclusion: Module decision belongs before the project, not in the project
Back to the initial thesis. The Shopware B2B projects that go wrong almost always have a module decision that was made too late, too generalised or too cost-oriented. In 2026, the situation is clear: the B2B Suite is a reliable module with an expiry date. The B2B Components are the path that Shopware is investing in and are the more honest answer for almost every new project. A standard shop plus employee accounts is sufficient for B2C-related sales; a separate architecture is only sufficient where B2B processes become the core of the business model.
If the components fit, they are worthwhile. If the suite fits, it's worth it until EOL. What is not worthwhile is setting up a new suite investment today without pricing in the EOL curve. This decision should be made before kickoff. Not in sprint two.
If you can't properly categorise your own status here, you're better off with an hour of architecture discussions than with five demos. A well-founded e-commerce consultation typically provides more clarity in this discussion than any functional guidance from Shopware itself.
Status: May 2026. Plan structure, prices and roadmap statements for the Shopware B2B Suite and B2B Components are regularly updated. Verify licence details and the current EOL communication on shopware.com or via your implementation partner on a daily basis before they are included in a budget or contract.