---
title: Understanding B2B Components and the Modular Model | Shopware Community Hub
description: >-
  Understand what Shopware B2B Components are, how they extend a standard store,
  which modules exist, and the Shopware plan and version requirements behind
  them.
canonical_url: >-
  https://hub.shopware.com/learn/unit/understanding-b2b-components-and-the-modular-model
---

<LearningObjectives>

- Understand what **B2B Components** are and how they extend an existing Shopware shop.
- Learn how the modular B2B model works for customers and customer groups.
- Learn which **B2B modules** support common customer buying needs.
- Identify the required **Shopware plan** and module-specific version requirements for B2B modules.
- Understand how B2B Components differ from similar Shopware feature.

</LearningObjectives>

# Understanding B2B Components and the Modular Model

B2B customers usually buy differently from B2C customers. A B2C customer often buys for themselves. A B2B customer buys for a company.

That means the shop may need to support company-specific workflows:

- Several employees order through one company account.
- Some orders need approval before they become binding.
- Prices may be negotiated.
- Recurring orders should be easy to repeat.

Shopware supports these workflows with **B2B Components**. They add B2B functions to an existing shop, such as Employee Management, Roles, Organisation Units, Order Approval, Quote Management, Quick Order, Shopping Lists, Budget Management, and Individual Pricing.

The important point is that B2B Components are modular. You do not enable everything for every customer. You choose the modules that match the customer's purchasing process.

Before you configure the modules, you need a clear mental model of what each module is for. This helps you choose the right modules instead of creating a setup that is more complex than the customer's process requires.

In this learning unit, you learn what the B2B Components are, which problems the modules solve, and how to decide which modules a B2B customer needs.

## What B2B Components Are

B2B Components are modular functions for B2B workflows in an existing Shopware shop. They are part of the **Shopware Commercial** extension and are available from the **Evolve** plan upward.

You do not install a separate B2B shop. Instead, you enable B2B functions inside the same shop for the customers or customer groups that need them.

When the right functions are active, that customer's account can act as the company account. Employees, roles, approval rules, budgets, and other B2B features then belong to this company account context.

This is the key mental model:

> B2B Components are modular additions to an existing shop. They only take effect for the customers or customer groups where you enable them. All other customers continue to use the shop as before.

Because B2B Components are modular, you choose the modules that fit the customer's process.

- A small reseller might only need Quick Order and Shopping Lists.
- A larger enterprise customer might also need Employee Management, Roles, Organisation Units, Order Approval, Quote Management, Budget Management, and Individual Pricing.

<Callout title="Commercial Extension Required" type="info">

B2B Components are not part of the free Community edition. They require the Shopware Commercial extension and a plan that includes B2B Components. If you cannot find the B2B options described here, first check that Shopware Commercial is installed and active.

</Callout>

## Which B2B Modules to Use

Once a customer needs B2B workflows, the next question is which parts of their buying process need support.

Use the customer's process to choose the right modules:

| Customer Need | B2B Module |
|---------------|------------|
| Several people order for the same company. | Employee Management |
| Different employees need different permissions. | Roles |
| Departments or locations need separate control. | Organisation Units |
| Orders need approval before they become binding. | Order Approval |
| Customers negotiate prices before ordering. | Quote Management |
| Customers need to add known products quickly. | Quick Order |
| Customers reorder the same products regularly. | Shopping Lists |
| Spending should be limited per unit or period. | Budget Management |
| Specific customers need negotiated prices or discounts. | Individual Pricing |

Start with the modules that match the customer's current process. Add more modules later when the customer's workflow requires them.

A useful way to group the modules is:

- **Who can buy**: Employee Management, Roles, Organisation Units.
- **How orders are placed and controlled**: Order Approval, Quote Management, Quick Order, Shopping Lists.
- **Pricing and budgets**: Budget Management, Individual Pricing.

This learning path follows the same structure.

## Version Requirements

Not every B2B module was introduced in the same Shopware version. Before you plan or promise a module, check whether the shop version supports it.

Some important version requirements are:

- Employee Management: from Shopware 6.5.6.0.
- Order Approval: from Shopware 6.5.8.0.
- Shopping Lists: from Shopware 6.6.3.0.
- Budget Management: from Shopware 6.7.4.0.
- Individual Pricing: from Shopware 6.7.8.0. It also requires Organisation Units to be active.

To use every module covered in this learning path, the shop must meet the newest requirement in this list.

<Callout title="Check the Version Before You Promise a Feature" type="warning">

If a B2B module is missing in a shop, check the Shopware version before assuming that something is broken. A shop on an older 6.5 or 6.6 version may not include newer modules such as Budget Management or Individual Pricing.

</Callout>

## Example: Choose Modules for a Customer

Imagine a wholesale customer, for example a regional construction supplier. They explain how their company wants to buy:

- Three buyers and one managing director should each have their own login. Use **Employee Management**.
- Buyers may prepare orders, but only the managing director may approve orders above €5,000. Use **Roles** and **Order Approval**.
- They order the same fasteners and tools every month. Use **Shopping Lists** and **Quick Order**.
- They have negotiated a 10 percent discount for their main product category. Use **Individual Pricing**.

You have not configured anything yet, but you already know which modules this customer needs. You also know which modules they do not need.

For example, a smaller customer who only wants faster reordering may not need Order Approval, Budget Management, or Organisation Units.

## How B2B Components Differ From Similar Features

B2B Components can sound similar to other Shopware features. Keep these boundaries clear before you configure them.

- B2B Components are **not** the administration user and permission system. Employees and Roles control what people can do in the **storefront** company account. They do not control what your own team can do in the Administration.
- B2B Components are **not** the same as customer groups. Customer groups can help prepare or assign B2B settings, but they are not B2B modules by themselves.
- Individual Pricing is a B2B module connected to Organisation Units. It is different from standard advanced prices and price rules.

These boundaries help you avoid confusion later, especially when you configure Roles and pricing.

## Common Pitfalls

Before you start configuring B2B Components, keep these common mistakes in mind.

### Pitfall 1: Enabling Too Many Modules at Once

The goal is not to enable every B2B module. Start with the modules that match the customer's current process. If the customer only needs faster reordering, Quick Order and Shopping Lists may be enough. Add Order Approval, Budget Management, or Organisation Units only when the customer's process requires that extra control.

### Pitfall 2: Planning Features Without Checking the Version

Not every B2B module is available in every Shopware version. Before you promise or configure a module, check the shop version and confirm that the feature exists in that environment.

### Pitfall 3: Mixing Up Storefront Roles and Administration Permissions

B2B Roles control what employees can do in their company's storefront account. They do not grant access to the Shopware Administration and do not replace Administration user permissions.

## Summary

In this learning unit, you learned:

- What B2B Components are and how they extend an existing Shopware shop.
- How the modular B2B model works for customers and customer groups.
- Which B2B modules support common customer buying needs.
- Why the required Shopware plan and module-specific version requirements matter.
- How B2B Components differ from similar Shopware features.

With this mental model, you can look at the customer's buying process and identify which B2B modules are likely needed before configuration starts.

Next, you will put this into practice by activating B2B functions for a customer and presetting them through a customer group.
