Shopware for B2B: B2B Suite or B2B Components?

ECOMMERCE · SHOPWARE B2B

You’re thinking about moving your B2B sales onto Shopware — and you immediately hit the question: is standard Shopware enough, or do you need the B2B Suite? Let’s be honest up front: the software is rarely the problem. B2B commerce doesn’t fail because of the shop — it fails on pricing logic, approvals and product data. Shopware’s B2B features are good, but they only hold up when a PIM feeds them clean data. That’s exactly what this article is about: not a feature firework, but the one question that matters — when the effort actually pays off for you.

And one important note right at the start, so you’re not building on outdated information: the classic “B2B Suite” as a monolithic plugin is being phased out. Shopware now focuses on the modular B2B Components. What that means for your decision we’ll clear up below — because this is exactly where many people are currently taking the wrong turn.

What makes B2B commerce different

B2C is simple at its core: one person, one cart, one price, one credit card. In B2B, every one of those givens breaks down:

• Customer ≠ person. A customer is an organisation with several buyers, departments and locations. The apprentice fills the cart, the head of purchasing approves, and accounting wants to see the right cost centre.
• Price ≠ price. Every customer — sometimes every framework contract — has its own terms: tiered prices, special discounts, customer-specific price lists, negotiated quotes. The “RRP” is of little interest to anyone in B2B.
• Catalogue ≠ catalogue. Customer A may see 4,000 items, customer B only the 200 from their framework contract. Visibility is part of the negotiation.
• Order ≠ purchase. Between “wants to order” and “is allowed to order” sit budgets, approval limits and sign-off processes.

That’s why a standard shop hits a wall fast in B2B: it’s built for the anonymous individual buyer, not for the purchasing organisation. And this is exactly where the trap is. Most projects don’t fail because Shopware couldn’t handle these cases — they fail because the data underneath isn’t clean: price lists live in Excel, technical attributes are missing, variants are named inconsistently, translations are incomplete. The nicest B2B login is worthless if the customer sees half a product description on the very first item.

Remember: the B2B Suite (or the B2B Components) solves the process side — roles, approvals, pricing logic. It does not solve the data side. For that you need a PIM. More on that later.

What the Shopware B2B Suite can do

First the context, because it decides buy or no-buy: Shopware has rebuilt its B2B functionality over the past few years. The classic B2B Suite was one large, bundled plugin — all or nothing. It’s being phased out; the active focus is on the B2B Components, a modular, commercial toolkit (Evolve plan and up) from which you activate only what you need.

In practice that means: if you’re starting fresh today, you plan on B2B Components, not the old Suite. The search term “B2B Suite” has stuck around, but the product behind it has changed. And to be clear: the B2B Components are commercial (Evolve plan and up) — they are not part of the free core.

The B2B Components consist of individually activatable modules. The most important ones:

• Employee Management: One company account with multiple employee logins. Each employee gets a role, and roles carry permissions — e.g. “may order without approval”, “may order up to amount X”, “may manage employees”.
• Organisation Units: These let you map the customer’s structure — multiple locations, departments, hierarchies.
• Budget Management: Its own module (since Shopware 6.7.4.0). A budget defines how much a unit may spend within a period; if the limit is exceeded, the order goes into approval.
• Order Approval: The classic four-eyes process. The buyer assembles the order, an approver grants or rejects it.
• Quote Management: Create, send, accept or reject quotes right in the shop — the digital replacement for the PDF ping-pong over email.
• Quick Order: Ordering by item number and quantity via an input form or by file import (CSV). For regular customers who know what they want, this is worth its weight in gold.
• Shopping Lists: Shared, recurring lists of approved items — handy for reorders.

This is deliberately not an exhaustive list — there are further modules (among others Individual Pricing, Advanced Product Catalogues, Sales Agent). You activate only what you actually need.

And on top of that, customer-specific pricing logic: different price lists per customer group/organisation, tiered and special prices that apply directly in the storefront for the logged-in customer.

What is not readily included in the standard and often forgotten: an OCI/Punchout connection to your key accounts’ procurement systems (e-procurement). This runs via established extensions and belongs in the project budget from the start.

Feature comparison: B2B Components vs. standard Shopware

For context: industry observers now see self-service, approval workflows and personalised terms as a baseline expectation of professional buyers — not a nice-to-have.

When it pays off — and when it doesn’t

Now for the decision you came here for. The B2B Components cost money and project effort — they’re tied to the higher Shopware plans (Evolve plan and up; per the official price list from €2,400/month, excl. VAT and plan-dependent; “Beyond” for large setups on request/custom). So it’s worth asking the question honestly in both directions.

The B2B Suite / B2B Components pay off when …

• your customers have multiple buyers who order separately and need to approve internally.
• you work with customer-specific prices, framework contracts or tiers that differ per account.
• approval processes and budgets are part of purchasing (typical with larger customers and the public sector).
• regular customers with high order frequency need reorders, quick order and shopping lists.
• large customers expect an OCI/Punchout connection to their procurement system.

They don’t pay off (yet) when …

• you essentially sell B2C-style — fixed prices, individual buyers, no approval process. Then customer groups and the Rule Builder in the standard are enough.
• you serve a few key accounts manually and sales run personally anyway. A self-service portal then solves a problem you don’t actually have.
• your product data isn’t ready yet. This is the most important point — and the one most often overlooked. A B2B portal on top of messy data only makes the data gaps more visible, and faster. Data first, portal second.

In short: buy the B2B features for your processes, not for the feature list. If your buyers don’t need roles, approvals and individual prices, you’re paying for an engine you’ll never connect to the accelerator.

Why PIM is the prerequisite

Here the circle closes back to the thesis from the beginning. The B2B Components organise who is allowed to buy what, at which price and with which approval. They don’t concern themselves with what is being sold — that is, the product content itself: technical attributes, data sheets, dimensions, standards, variants, images, translations.

That’s exactly what’s mission-critical in B2B, because B2B buyers buy on facts: they filter on technical attributes, compare data sheets, need ETIM classes and BMEcat conformity for the dealer’s shelf. If an attribute is missing here, the purchase decision breaks — no approval workflow saves that.

Shopware is an excellent output channel, but not an editorial system for product data. If you maintain attributes, prices and variants directly in the shop, you have them exactly there — and nowhere else. As soon as the second channel comes along (marketplace, PDF catalogue, dealer portal, flipaio flip catalogue), you’re maintaining everything two and three times over.

That’s why the apollon approach is: one PIM as the single source of truth delivers the clean, complete, multilingual product data — and Shopware plus B2B Components play it out and handle the sales process. You maintain once, publish everywhere, and the B2B Suite finally holds up, because there’s a reliable data foundation beneath it.

How that connection runs cleanly on a technical level — architecture, field mapping, the limits of Shopware’s built-in tools — we go into in the series article Shopware 6 & PIM: connecting product data cleanly (series article, goes live 30.09.2026). Why manufacturers have different requirements here than dealers is covered in PIM system: manufacturer vs. dealer and in Differences of PIM in B2B and B2C. Specifically for manufacturers with ETIM/BMEcat obligations, PIM for manufacturers (series article, goes live 09.12.2026) follows.

Want to know whether the B2B Suite pays off in your case — and what the data foundation for it needs to look like? The apollon Shopware Agency assesses your processes, plans and product data with you and tells you honestly what you need and what you don’t. Or see in a demo how PIM and Shopware work together.

FAQ

What’s the difference between the Shopware B2B Suite and the B2B Components?

The B2B Suite was a bundled plugin (everything in one package). The B2B Components are the modular successor, offered as commercial B2B Components (Evolve plan and up): you activate individually what you need — among others Employee Management, Organisation Units, Budget Management, Order Approval, Quote Management, Quick Order, Shopping Lists. For new projects you plan on the B2B Components.

From which Shopware plan are the B2B features available?

The B2B Components are tied to the higher commercial plans — Evolve plan and up (per the official price list from €2,400/month, excl. VAT and plan-dependent), with “Beyond” for large setups on request/custom. The community/standard scope doesn’t include them.

Can’t standard Shopware do B2B too?

For simple cases, yes: customer groups, tiered prices via the Rule Builder and one login per account work in the standard. As soon as multiple buyers, roles, approvals, budgets or customer-specific price lists come into play, you need the B2B Components.

Does Shopware support OCI/Punchout for my customers’ procurement systems?

An OCI/Punchout connection isn’t fully covered in the core and is realised via established extensions. Budget for it from the start if your key accounts order through their e-procurement.

Why do I also need a PIM?

The B2B Components govern the sales process (who, which price, which approval), but not the product content. Technical attributes, data sheets, variants, translations and classifications (ETIM/BMEcat) come from the PIM. Without a clean data foundation, a B2B portal only makes your data gaps visible faster.

Is the investment worth it for small B2B dealers?

If you serve a few key accounts personally and sell without approval processes, often not right away. Decide based on your processes: if your customers need roles, budgets, approvals and individual prices, it’s worth it. If not, the standard is enough — and you’re better off investing the money in clean product data first.

Does the B2B Suite pay off in your case?

The apollon Shopware Agency assesses your processes, plans and product data with you — and tells you honestly what you need and what you don’t. In a short demo we’ll also show you how PIM and Shopware work together in B2B.