Shopware B2B Components: the complete guide to every module, dependency, and configuration

If you run a Shopware store serving business customers, you have probably noticed that the platform's B2B capabilities have changed fundamentally. The old B2B Suite, a single large plugin that handled everything from roles to budgets to ordering workflows, is being retired. In its place: a set of modular components built directly into the Shopware core. For the full picture of Shopware's B2B ecosystem, see our Shopware B2B Guide.

This guide covers every B2B Component available today, how they interact, which Shopware edition you need, and where the gaps still are. Whether you are migrating from the B2B Suite or building a B2B storefront from scratch, this is the reference page the official docs do not give you.

What are Shopware B2B Components?

Shopware B2B Components are modular building blocks integrated directly into the Shopware 6 core. Unlike the legacy B2B Suite, which was a standalone plugin bundling all B2B functionality into one package, B2B Components follow a composable architecture. You activate only what your business actually needs.

The shift matters because it changes how B2B features are maintained and extended. Components receive updates through the regular Shopware release cycle, not through a separate plugin update path. They use the same APIs, the same admin interface, and the same data model as the rest of your store. For a broader look at the B2B Suite Overview [URL PENDING], that article covers the suite-level perspective.

The Shopware B2B Components Product Page lists six core components as of early 2026: Employee Management, Quick Orders, Order Approval, Quote Management, Shopping Lists, and Organization Units. Each component can be activated independently, though some have dependencies on others.

All B2B Components at a glance

No single page in the official documentation lists every component with its purpose, edition requirement, and dependencies in one place. The information is scattered across multiple docs pages, release notes, and marketing materials. Here is the consolidated reference.

The Official B2B Suite Documentation still covers the legacy suite. For the new components, refer to the Features section of the Shopware 6 docs. The table above reflects the current state, but Shopware continues to add components with each release cycle.

One pattern worth noting: Employee Management is the foundation. Order Approval, Quote Management, and Organization Units all depend on it. If you are planning a phased rollout, start there.

Roles, permissions, and budgets

A B2B store without role management is just a B2C store with bigger order volumes. Employee Management is where the B2B architecture actually begins. You create employee accounts under a company umbrella, assign roles, and define what each role can see, order, and approve.

The permission system is granular. You can restrict access to specific product categories, set order value limits, or require approval for orders above a threshold. A procurement manager might have unrestricted ordering up to EUR 5,000, while a department employee needs approval for anything above EUR 500. These rules are defined in the admin and enforced in the storefront automatically.

Budget management ties directly into the approval workflow. Each department or employee can have a monthly or quarterly budget. When an order would exceed the remaining budget, the approval process kicks in. This is the kind of control that procurement teams in mid-sized companies actually ask for.

For companies with complex organizational structures, the B2B Customer Portal extends these capabilities with self-service account management, order history across all employees, and centralized invoice access.

Ordering processes: quick order, lists, and approvals

B2B buyers do not browse. They know exactly what they need, they have a parts list or a reorder from last quarter, and they want it in the cart in under 60 seconds. According to multiple industry surveys (2025), 83% of B2B purchasers prefer self-service ordering through digital platforms. The ordering components are built for exactly this workflow.

Quick Order is the most straightforward component. Buyers enter product numbers and quantities directly, or upload a CSV/XLS file with their entire order. No browsing, no product pages, no clicking through categories. For a warehouse manager reordering 200 SKUs every two weeks, this cuts ordering time from 45 minutes to under 5.

Shopping Lists add persistence. Teams can maintain shared lists for recurring purchases, seasonal orders, or project-specific materials. Unlike a cart, lists survive sessions and can be collaborated on across multiple employees.

For a deeper look at the full B2B Ordering Process, including integration with ERP systems and AI-assisted product consultation, that guide covers the end-to-end workflow.

Pricing logic and quote management

In B2B, there is no such thing as a single price. Every customer has negotiated rates, volume discounts, contract-specific pricing, and sometimes project-based quotes that override everything else. Shopware handles this through its Advanced Pricing rules engine, which the B2B Components extend with quote workflows.

Customer-specific pricing is configured through price rules in the admin. You assign price groups to customer groups or individual companies, set tiered pricing based on quantity breaks, and define validity periods. The system supports net pricing with per-customer tax rules, which is standard in European B2B but surprisingly absent from many competing platforms.

Quote Management adds negotiation to the mix. A buyer requests a quote from the cart, the merchant reviews and adjusts pricing in the admin, sends the quote back, and the buyer accepts or requests revision. The entire exchange is tracked in the system, replacing email chains with an auditable workflow. For details on B2B Pricing and Editions, see the dedicated pricing guide.

Payment terms are another layer. B2B transactions rarely use credit cards. The B2B Invoice Payment component supports purchase on account, net payment terms (net 30, net 60), and integration with ERP invoicing systems.

Sales representative component

Not every B2B order happens through a self-service portal. Trade shows, customer visits, phone calls: sales reps still place orders on behalf of customers. The Field Sales Feature handles this with a dedicated login mode.

A sales representative logs into the storefront, selects a customer account, and effectively impersonates that customer. They see the customer's specific pricing, budget limits, and order history. Orders placed this way are attributed to the customer but flagged as rep-initiated, which matters for commission tracking and audit trails.

The use cases are practical. A field rep at a trade show can build an order on a tablet using the customer's negotiated pricing. A phone support agent can place a reorder while the customer describes what they need. An account manager can create a quote for a customer who prefers not to use the portal directly.

Component architecture: dependencies and interactions

Modular does not mean independent. B2B Components have dependencies, and activating them in the wrong order leads to configuration issues. Here is the dependency map that the official docs do not provide in one place.

A minimal B2B configuration uses Employee Management plus Quick Orders. This covers the most common use case: a company with multiple buyers who need fast reordering with basic role separation. The full configuration, with all six components active, is appropriate for enterprises with departmental budgets, approval hierarchies, and active sales teams.

Performance impact is minimal. Each component adds its own database tables and storefront logic, but the overhead is negligible for stores under 10,000 products. For larger catalogues with complex pricing rules, the quote management and approval workflow queries can add latency. The Shopware Developer Docs cover caching and indexing strategies for high-volume B2B stores.

B2B Components vs. B2Bsellers Suite vs. custom plugins

Shopware's native B2B Components are not the only option. The B2Bsellers Suite, a third-party plugin, offers a broader feature set out of the box. And custom development is always possible. The right choice depends on your edition, budget, and how specialized your B2B workflows are.

The honest assessment: if you are already on Shopware Evolve or Beyond, B2B Components are the natural choice. They are maintained by Shopware, receive updates automatically, and are the clear strategic direction. If you are on Community or Rise and need B2B functionality without upgrading, B2Bsellers Suite fills the gap effectively. Custom development only makes sense for workflows so specialized that neither solution covers them.

One friction point worth acknowledging: the B2B Components feature set is still catching up to what the old B2B Suite offered. Features like contingents, advanced cost center management, and some edge cases in approval workflows are either missing or less mature than in the legacy system. Shopware is closing these gaps with each release, but as of early 2026, the transition is not seamless for every use case.

AI integration with B2B Components

B2B product catalogues are often complex. Industrial supplies with thousands of specifications, chemical products with compatibility requirements, technical components where the wrong part means a production line stops. This is where AI employees add a layer that B2B Components alone cannot provide.

An AI employee integrated with Shopware's B2B setup reads the buyer's role, their company's pricing tier, and their order history. When a procurement manager searches for a replacement part, the AI does not just return search results. It recommends the correct specification, flags compatibility issues, and applies the customer's negotiated pricing automatically. Qualimero's clients in the home and garden sector see a 35% increase in average cart value from this kind of guided selling.

The combination works because B2B Components handle the structural logic (who can order what, at what price, with whose approval) while the AI handles the consultation logic (what should they order, and why). Neither replaces the other. Together, they turn a self-service portal into something that feels like having a product expert available around the clock.

Frequently asked questions

Shopware's B2B Components represent a clear architectural improvement over the legacy B2B Suite. The modular approach, core integration, and API-first design make them the right foundation for B2B stores on Evolve and Beyond. The feature set is not yet as comprehensive as the old suite or third-party alternatives, but the gap is closing with every release. For the broader strategic context, return to the Shopware B2B Guide.