nextlevels logo
DEEN

Shopware B2B Components

Last updated on

In short

Shopware B2B Components is the modular B2B extension of Shopware 6 and the official successor to the older B2B Suite. Instead of a single, bundled plugin, it consists of several individually activatable modules, each covering a clearly defined B2B function: employee management, quotes, order approvals, quick order, shopping lists and organization units.

You only switch on the building blocks your business actually needs instead of carrying the complete feature package. The Components are deeply integrated into the Shopware 6 core, follow an API-first architecture and, for new installations from the Evolve plan upwards, are the standard way of providing B2B functionality.

The term therefore sums up a strategic decision by Shopware: away from the monolithic B2B module and toward a modular, extensible system that fits better into headless and composable architectures. For merchants who are planning a B2B platform today or replacing an existing B2B Suite installation, the B2B Components are the central point of reference.

Why the B2B Components exist

In 2023, Shopware added the modular B2B Components to the original B2B Suite and has invested consistently in this direction ever since. The Suite, a single large plugin attached to a standard shop, has since been maintained in maintenance mode only and no longer receives new features. For new projects, Shopware recommends the Components; support for the old Suite ends with the release of Shopware 6.8. That deadline has moved: Shopware has postponed 6.8 to 2027 (originally planned for 2026) and extended the extended support for 6.6 until 6.8 becomes available. The time buffer for a migration is therefore larger than first assumed, but the end date remains tied to 6.8.

The reason for the cut is architectural. A monolithic plugin is hard to extend in a targeted way: anyone who wanted to adapt a single function often had to intervene in the whole system. The modular Components, by contrast, can be activated individually and extended via clearly defined interfaces. This matches the API-first approach of Shopware 6 and makes it possible to start a B2B setup lean and expand it step by step, instead of carrying the full feature set from day one.

The core modules at a glance

The B2B Components bundle the typical requirements of digital business-customer trade into individually activatable building blocks that build on each other. The following six form the core:

The six core modules of the Shopware B2B Components and their purpose
ModuleFunction
Employee ManagementMaps a business customer’s purchasing organization: a main account creates employees and assigns roles and permissions. The foundation of most other modules.
Quote ManagementQuote business in the shop: customers request a basket as a quote, sales negotiates, and the final quote becomes the order.
Order ApprovalApproval workflow: orders above a defined value or under certain rules must be approved before they are placed.
Quick OrderFast ordering for repeat buyers: items go into the basket in seconds by item number or list, without the detour through categories and search.
Shopping ListsShareable order lists that several people in a company work on together. Ideal for recurring procurement.
Organization UnitsDifferentiated access rights along locations, departments or subsidiaries. Maps group and branch structures cleanly.

The modular cut is the real core of the concept: a merchant with a simple repeat-order business might only activate Employee Management and Quick Order, while a supplier to corporate groups also needs Order Approval and Organization Units. This freedom of choice is exactly what distinguishes the Components from the “all or nothing” logic of the old Suite.

What the Components do not cover

An important distinction: the B2B Components are the B2B sales logic on the Shopware platform, not a replacement for an ERP, a PIM or a CRM. OCI and punchout connections to the procurement systems of large purchasing organizations are not included ready-made in the core either, neither in the Suite nor in the Components; in practice they are implemented with established extensions such as PunchCommerce or B2Bsellers. Anyone advertising them as “included natively” is oversimplifying. The Components handle the self-service and ordering processes in the shop, not the master data or logistics architecture behind them.

B2B Components versus the B2B Suite

The difference is less a question of feature scope than of architecture and life cycle: the B2B Suite is the monolithic all-in-one plugin that is being phased out, while the B2B Components are the modular system Shopware is actively investing in. For new projects, the recommendation in almost all cases is therefore to start with the Components; existing Suite shops plan the migration in the medium term. As a Shopware B2B agency, we support both new builds and migrations. You will find the full comparison, including costs and the end-of-life roadmap, in our guide to migrating from the Shopware B2B Suite to the B2B Components.

Availability and licensing

The B2B Components are not an extension you buy separately but part of the commercial Shopware plans. They are included from the Evolve plan upwards (as of May 2026 from around €2,400 per month); the Rise plan below it does not include B2B functionality. Larger setups with several shops, high order volumes or special support requirements typically sit in the Beyond plan. As plan structures and terms are adjusted regularly, the exact figures should be checked against Shopware’s official information before signing any contract.

A note on customer-specific prices: Since Shopware 6.7.8.0, the Evolve plan includes the separate module “Individual pricing”. It lets you create rule-based discounts and special prices for companies, organization units or customer tags in the Administration, including volume pricing and a validity period. This is distinct from “Customer-specific pricing”: individual prices per customer that arrive via the API, for example from an ERP. That feature remains reserved for the Beyond plan. Shopware describes the details in its feature focus on Individual Pricing.

A concrete real-world example

A technical wholesaler supplies industrial customers who order through their own purchasing departments. With the B2B Components, it maps this as follows: via Employee Management, each customer creates its own buyers and assigns roles. Via Order Approval, orders of €5,000 or more must first be approved by the relevant head of department. The customer’s service technicians use Quick Order to place recurring orders with three hundred line items by item number in minutes instead of clicking through categories. And via Organization Units, each branch only sees its own range and its own terms.

This setup shows the principle: the merchant activates exactly the four modules its business model relies on and leaves Quote Management and Shopping Lists inactive for now. If quote business were added later, Quote Management could be switched on without rebuilding the existing setup. This step-by-step extensibility is the economic core of the Components.

B2B Components and migration from the Suite

For existing Suite shops, the Components are the migration target. Data such as customer hierarchies, roles and price lists can generally be carried over, and the functional configuration can be recreated because the concepts are the same. What needs to be checked individually are the custom adaptations that have grown over the years: they determine whether a migration is a manageable conversion or a larger project. For the technical transfer, Shopware provides its own migration path including CLI tools, which is being extended continuously.

The recommended process for such a migration has five phases: a thorough inventory of the functions actually in use, mapping each Suite function to its Component counterpart, building in a staging environment alongside live operation, a test phase with real customer accounts and finally the go-live. Because this build takes place next to the running shop, there is usually no downtime. The duration depends almost entirely on the depth of the existing customizations: an installation close to the standard can be switched over in a few weeks, while a heavily customized installation with an OCI connection is better planned in months. What matters is to plan the migration early rather than postponing it until shortly before the Suite’s end of support.

Detailed technical information on the architecture and the individual modules can be found in the official Shopware documentation on the B2B Components.

B2B Components in headless and composable setups

A central reason for the modular cut is the API-first orientation of Shopware 6. Unlike the old Suite, whose logic was closely tied to the bundled storefront, the B2B Components provide their functions via the Store API. This makes them usable in headless and composable architectures in which the front end is not the classic Shopware storefront but a separate application, for example one based on a modern JavaScript framework or a customer portal.

In practice, this means that a company can map order approvals, employee management or quick ordering in a custom-built front end or even in an existing portal while using Shopware as the commerce back end. This decoupling of function and presentation was hard to achieve with the monolithic structure of the Suite. For merchants with individual requirements for the interface, performance or integration into an existing system landscape, it is one of the strongest strategic advantages of the Components.

At the same time, a headless setup is not an end in itself. For many mid-sized companies, the bundled storefront with the Components activated is entirely sufficient, and the extra effort of a custom front end only pays off when requirements clearly differ. The Components allow both routes without locking you in with the first decision, and this openness is part of their concept.

Frequently asked questions about the Shopware B2B Components

Are the B2B Components the same as the B2B Suite? No. The B2B Suite is the older, monolithic B2B plugin that now only runs in maintenance mode. The B2B Components are the modular successor that Shopware is actively investing in and that is the standard for new projects.

How many modules do the B2B Components consist of? The core consists of six modules: Employee Management, Quote Management, Order Approval, Quick Order, Shopping Lists and Organization Units. Shopware has since extended the range: the developer documentation also lists Individual Pricing and Digital Sales Composables (and combines Quick Order and Shopping List into one module), and the product page additionally markets Advanced Product Catalogs and Budget Management. Each module can be activated individually. Which of them are included in your plan varies: customer-specific prices from an ERP or API (customer-specific pricing), for example, remain reserved for the Beyond plan.

From which Shopware plan are the B2B Components included? From the Evolve plan (as of May 2026 from around €2,400 per month). The Rise plan does not include B2B functionality. Terms change regularly and should be checked before signing a contract.

Can I migrate from the B2B Suite to the B2B Components? Yes. Data and standard configuration can largely be carried over; individual custom adaptations must be checked for compatibility one by one and translated to the modular architecture. Planning the migration early is advisable, as support for the Suite ends with Shopware 6.8.

Which of the B2B Components do I need to activate? Only those your business needs. Employee Management is the foundation on which most other modules build; Quote Management, Order Approval, Quick Order, Shopping Lists and Organization Units can be added independently and supplemented later without rebuilding the existing setup.

Do the B2B Components cover OCI/punchout? Not in the core. OCI and punchout connections to procurement systems are implemented via established extensions and should be included in the project budget from the start.

Changelog

  1. · Content reviewed (6.8 timing 2027, Evolve plan); English version brought in line with the German one · Slawa Ditzel
  2. · Note added: “Individual pricing” in the Evolve plan since Shopware 6.7.8.0, “Customer-specific pricing” remains Beyond (source: Shopware feature focus) · Slawa Ditzel
  3. · Created · Slawa Ditzel
Next step

B2B commerce with Shopware

Customer groups, price lists, approval workflows and self-service portals: B2B features from a single source.