Shopware B2B Features for eCommerce Success 2026

The Shopware B2B Suite is being retired. With Shopware 6.8 it loses support entirely, and most teams running on it haven’t yet thought through what that means for their roadmap.

The replacement — B2B Components — is already shipping new features the Suite will never receive: Individual Pricing, Order Approvals, Organisation Units, AI-driven catalog work via Shopware Copilot, native CAD-to-3D conversion, and a new integration layer called Shopware Nexus. Each of these has landed in the last 12 months, and together they’ve changed what a serious B2B Shopware build looks like.

This guide walks through that change. What’s new, what it does, when each piece earns its keep, and where Shopware genuinely isn’t the right tool. The goal is to be useful regardless of whether you ever talk to us — Atwix is a Shopware Platinum Partner, but this article is written for whoever’s actually evaluating the platform, not as a brochure.

What’s in this guide:

Let’s get into it.

The Architectural Shift: B2B Components vs B2B Suite

This is the single most important update from the last 12 months. If you take nothing else from this guide, take this:

Shopware B2B Suite — the legacy all-in-one B2B plugin — is in maintenance mode. It still receives security patches, but no new features are being added. Support ends with Shopware 6.8.

Shopware B2B Components — the modular replacement built directly into the Shopware 6 core — is where all new development is happening. Every feature in this guide that’s been added since 2024 is part of B2B Components, not Suite.

What this means in practice:

• Starting a new B2B project in 2026? Build on B2B Components from day one.
• Already running B2B Suite? Plan a phased migration to Components before you upgrade to Shopware 6.8. The data migration is non-trivial and the longer you wait, the closer you get to a forced cutover. We outline a typical phased path further down.
• Plan tier matters. B2B Components is included in Shopware Evolve and Shopware Beyond. The Shopware Rise plan does not include Components, which makes it the wrong fit for any serious B2B build.

The Components approach — modular, API-first, with each capability activated per customer or customer group — also fits much better with the way modern B2B systems actually work: headless storefronts, deep ERP integration, and procurement workflows that need to mirror your customers’ real org structures.

The 8 Core B2B Components (with Real Use Cases)

Shopware’s B2B Components are a “choose what you need” toolkit. Every component below can be turned on or off per customer, per customer group, or per employee role. Here’s how each one earns its place.

1. Quick Order — Faster Ordering for Buyers Who Already Know What They Need

B2B buyers don’t browse. They reorder. Quick Order is built around that reality.

• Upload a CSV or XLS file with SKUs and quantities
• Enter SKUs in bulk, adding everything to the cart in seconds
• Save reusable order lists for recurring purchases
• Convert any past order into a new cart with one click

When to enable it: For any customer placing 10+ line items per order, or buying on a recurring schedule. This is usually the first component your buyers will actually thank you for.

Why it matters: Across our implementations, digital self-service consistently cuts order cycle time by more than half compared to phone or email-based PO submission.

2. Employee Management — Multi-User Accounts for Your Customers’ Teams

A single B2B customer often has 5–50 people who need to interact with your store: buyers, approvers, AP teams, branch managers. Employee Management lets that customer onboard their own employees, assign them roles, and manage permissions — all from the storefront, without touching your support team.

Each employee acts on behalf of the company. Orders, addresses, and payment methods are managed at the company level, while individual permissions are scoped per employee.

When to enable it: For any customer with more than one buyer. Especially valuable for franchise operations, multi-branch distributors, and corporate accounts with delegated purchasing.

3. Order Approval — Built-In Procurement Workflows

In B2B, a single purchase often passes through 3–5 hands. Order Approval encodes that into the platform.

• Define which roles can approve which orders
• Set thresholds based on order value, product type, or customer group
• Build multi-step approval chains with the Rule Builder
• Approval requests, decisions, and audit trails all live inside the customer account

A construction supply company can let junior buyers add items freely, but anything over $10,000 routes to a budget holder for approval before submission. The whole flow happens inside the portal — no phone calls, no rogue email threads, no lost POs.

When to enable it: For customers with formal procurement compliance requirements, or anywhere you’ve seen orders get held up in email approval chains today.

4. Quote Management — Negotiation, Inside the Platform

Pricing is often the start of a B2B conversation, not the end. Quote Management moves that negotiation into the cart.

• Customer requests a quote directly from their cart instead of checking out
• Sales team reviews, approves, or counter-offers inside the admin
• Once accepted, the quote converts to an order with one click
• Full history of every quote, comment, and revision lives on the customer record

Combined with Digital Sales Rooms — Shopware’s virtual consultation feature — sales reps can hold live sessions with customers, share screens, walk through product configurations, and respond with a custom quote inside the same platform.

When to enable it: Any time pricing is negotiated rather than published. Especially valuable for custom orders, project-based purchases, and anything where the cart-to-close flow today involves a back-and-forth email chain.

5. Shopping Lists — Shared, Approved Procurement Lists

A small feature that punches above its weight. Shopping Lists let teams maintain shared, persistent lists of approved items.

• A product manager builds the approved list once
• The procurement team orders from it repeatedly
• Lists can be updated centrally, so everyone is buying from the same negotiated set
• Buyers stop guessing which SKU is the “right” one

When to enable it: Any customer where multiple people order from the same approved catalog — facilities teams, restaurant chains, healthcare procurement, anything with standardized inputs.

6. Organisation Units — Mapping Real Org Structures

Large customers don’t have one address and one budget. They have departments, regions, cost centers, and subsidiaries. Organisation Units lets you mirror that structure inside the customer account.

• Create departments with their own shipping addresses, payment methods, and approval rules
• Assign employees to the right department
• Apply rules and permissions at the department level, not just per user

For a franchise business where every location places its own orders but corporate oversees compliance, this maps cleanly onto the actual org chart.

When to enable it: For customers with multiple physical locations, regional buying authority, or anything more complex than a single office.

7. Budget Control — Spending Limits with Real Teeth

Budget Control gives your customers (and their finance teams) granular control over spending inside your store.

• Set spending limits per department, sub-account, or individual user
• Show remaining budget directly in the storefront so buyers see it before checkout
• Trigger automatic email notifications when budgets hit a threshold (e.g., 80% used) — sent to designated approvers or organisation units
• Let buyers submit orders for approval when their budget is fully used
• Restrict which categories or products a user can order

When to enable it: For enterprise customers with formal budget governance, or any customer that’s asked you “can we limit what this user can spend?”

8. Individual Pricing (Released March 2026)

The newest B2B Component, added in Shopware 6.7.8.0. Individual Pricing translates the contract pricing logic that used to live in spreadsheets and ERP exports directly into the Shopware catalog.

• Customer-specific prices that load instantly when a buyer logs in
• Volume tiers applied automatically — no manual cart adjustments
• Customer group pricing for whole industries, regions, or contract tiers
• Catalog-wide discount rules (percentage, fixed amount, or fixed price) per customer or organisation unit

This isn’t a replacement for the Rule Builder — it works alongside it. We cover the full pricing engine in the next section.

The Shopware Pricing Engine for B2B

B2B pricing is where most platforms either give up or quietly require custom development. Shopware’s combination of Advanced Prices, Rule Builder, and Individual Pricing handles real-world B2B pricing without writing code.

Advanced Prices is the foundation. You can define multiple price points per SKU based on quantity thresholds and customer group. Tiered pricing, volume breaks, and contract pricing are all native.

Rule Builder adds conditional logic on top. Rules can apply based on cart total, customer attributes, order frequency, region, time period, or any combination. A typical B2B store might have 30–50 active rules covering everything from “10% off orders over 100 units” to region-specific contract pricing.

Individual Pricing (new in 2026) extends this with catalog-wide discount logic — percentage, fixed amount, or fixed price — assignable to individual customers or organisation units.

Together, these three systems support every B2B pricing pattern we’ve encountered in practice: tiered volume pricing, customer-group pricing, named-account contract pricing, multi-tier dealer pricing, and rebate-style structures. Without custom development, in nearly every case.

The piece that does still take work is getting the right pricing data into Shopware in the first place — usually from your ERP. That’s an integration problem, not a Shopware problem, and we cover it below.

What’s New for Shopware B2B in 2026

A lot has shipped in the last 12 months. These features aren’t part of the original B2B Components set — they’re 2026 additions worth knowing about.

Shopware Nexus — Integration Orchestration

Shopware Nexus is a new integration layer that orchestrates business logic — pricing, availability, approvals, variant rules — directly inside the Shopware ecosystem, reducing dependency on external middleware.

This matters because 52% of total project effort in B2B Shopware implementations is spent on integrations, according to Shopware’s B2B Ecommerce Compass 2026 partner ecosystem survey. Anything that compresses that share of effort frees up budget for actual customer-facing improvements.

Nexus is in beta as of mid-2026. For projects starting now, it’s worth scoping with both Nexus and an external middleware option in mind, and choosing based on your specific integration topology.

Shopware AI Copilot

The Shopware Copilot is a chat-based AI assistant built into the Shopware Administration. It started in 2025 as a Q&A tool for Shopware features and configuration, and has since added a Skills framework — extensible capabilities that go beyond answering questions:

• Text generation — product descriptions, category texts, meta descriptions, generated from product attributes and translated automatically into multiple languages
• Image keyword assistant — auto-generated alt tags and SEO keywords for uploaded images
• AI image editor — background removal, scene generation, product placement
• Data Insights Skill — analyze sales and customer data through natural-language questions (“How are my sales doing this week?”, “Which products are trending in Germany?”)
• Chat history — added in Shopware 6.7.9.0, making Copilot more useful for ongoing admin work

For B2B operators with thousands of products and customer-specific pricing rules, the time savings on catalog content alone are significant.

Agentic Commerce Sales Channel

Released in Shopware 6.7.10.0 (May 2026) — note: this was originally planned for the April 6.7.9.0 release but slipped one cycle. The new Agentic Commerce sales channel generates a structured product feed (JSONL format) that AI platforms like ChatGPT can consume natively. You configure seller metadata, get a shareable feed URL, submit it to the AI platform, and track orders through Shopware’s existing affiliate infrastructure.

The OpenAI feed ships as a preconfigured template. Other platforms will follow as the market develops.

For B2B specifically, this is forward-looking — AI-driven procurement is still in early days, but the merchants who have structured feeds and referral tracking in place now will have a meaningful advantage when that traffic grows.

Product Bundles

Released in 6.7.9.0 (April 2026), available from the Evolve plan. Currently shipping as a “blueprint” — core bundle functionality, with variants and quantity selection coming in later iterations. If product bundling is part of your merchandising strategy, it’s worth testing now while the feature is still being shaped.

JSON-LD Structured Data

Shopware now supports JSON-LD structured data — the format Google and other search engines prefer for product, breadcrumb, and FAQ markup. Currently behind a feature flag. For B2B sites where SEO competes with deep distributor catalogs, this is a meaningful upgrade for visibility.

Spatial Commerce for B2B — Where 3D and AR Earn Their Keep

The CAD-to-3D conversion isn’t strictly a B2B feature — it sits inside Shopware’s broader Spatial Commerce stack — but it’s one of the most useful additions for B2B operators in years. Especially if you sell anything more complex than a single SKU.

CAD-to-3D Conversion (Stable as of April 2026)

Upload a CAD file, get a web-ready .glb 3D model back. The model works in product media, AR viewers, and immersive Shopping Experience layouts.

• Commercial plan customers get unlimited conversions
• Community Edition users get one free conversion per month, with additional capacity through the Intelligence+ subscription

Why this matters for B2B: previously, putting a 3D model on a product page required either a 3D artist on staff or a separate conversion service. For manufacturers and industrial distributors with hundreds or thousands of CAD-modeled products, that cost killed adoption. With CAD-to-3D in Shopware, the workflow lives inside the platform you’re already paying for.

Explosion Graphics Block (Released April 2026, €49/month add-on)

Build interactive exploded views of complex products with annotations and direct links to component spare parts. Drop the block into any product detail page or Shopping Experience.

This is the strongest fit for:

• Machinery and industrial equipment — let buyers navigate the assembly to identify parts before ordering
• Spare parts catalogs — link each annotated component to its purchasable spare part
• Anything complex enough that buyers normally call sales to figure out what they need

For an industrial supplier, an exploded view can replace a 12-page parts manual and a phone call with a single product page interaction.

3D Product Visualization and AR

Shopware natively supports:

• 3D product images embedded in product detail pages
• AR viewing on mobile (project the product into the buyer’s real environment via smartphone camera)
• QR code triggers on desktop product pages — scan with phone, view in AR
• 3D renderings inside Shopware Shopping Experiences with the Scene Editor

When this earns its keep in B2B: Configurable products (machinery, custom equipment, modular furniture), high-AOV purchases where confidence reduces returns, and anything where buyers historically need a sales rep to visualize the product. Industrial equipment, automotive parts, and custom industrial furniture are the strongest fits we’ve seen.

When it doesn’t: Commodity products, low-AOV reorders, anything where the buyer already knows exactly what they’re getting. Don’t 3D-model your fasteners catalog. Pick the products where buyer hesitation is actually slowing the sale.

The honest take: spatial commerce is most valuable in B2B when you’re selling something complex enough that the buyer would normally need a sales conversation to be sure. If your sales team spends time answering “will this fit?” or “what does this actually look like?” — 3D and AR can deflect a meaningful share of that effort.

ERP Integration: The Make-or-Break Layer for B2B

You can have every B2B Component perfectly configured and still ship a B2B store that doesn’t work — if the ERP integration is wrong.

In B2B, your ERP is the system of record for almost everything that matters: customer-specific pricing, real-time inventory, customer accounts, order history, credit terms, ship-to logic, and tax. Shopware needs to read most of that in real time, and write orders back accurately. Get this layer right and the rest of the platform works. Get it wrong and you’re firefighting daily.

This is also where most B2B Shopware projects burn time and budget. Shopware’s own partner ecosystem survey found that 52% of total project effort goes into integrations — not frontend or UX work.

What Shopware Integrates With Natively

Shopware connects to most major ERPs — SAP Business One, Microsoft Dynamics 365, NetSuite, Infor CloudSuite, WeClapp, Xentral — through native connectors and middleware platforms like Alumio and Celigo. For pure-play DACH stacks running on those systems, this is often enough.

Where It Gets Harder — Distribution ERPs

The trickier integrations are with distribution-specific ERPs: Infor CloudSuite Distribution, Epicor Prophet 21, Kodaris, Expertek. These systems carry the deep B2B logic that distributors actually run their businesses on — multi-warehouse inventory, customer-specific contract pricing, complex Ship-To structures, regional pricing exceptions — and they’re notoriously hard to wire to a modern eCommerce platform without custom work.

If you’re on Prophet 21 or Infor today, you have basically three options:

A generic iPaaS like Boomi, Celigo, or Workato — cheap to start, expensive to maintain because they don’t speak distribution-ERP natively. You end up writing the distribution logic anyway, just inside someone else’s tool. Per-transaction pricing also gets ugly fast at distributor order volumes.

Custom point-to-point integration — the most flexible, the most expensive over a 5-year horizon. Every ERP version upgrade and every Shopware major release becomes a regression project. Works fine if you have a strong in-house engineering team that’s already comfortable maintaining commerce middleware. Most distributors don’t.

A purpose-built platform with pre-built distribution-ERP connectors — fastest to live, predictable maintenance cost, but you’re trusting the vendor’s roadmap. We built Sirius for this third path because we kept watching the first two fail in the same predictable ways: iPaaS deployments where pricing logic kept bleeding into custom code, and custom integrations that worked beautifully at launch and turned into maintenance nightmares 18 months in. Sirius ships pre-built connectors for Prophet 21, Infor, Kodaris, and Expertek, with bidirectional real-time sync and a unified GraphQL endpoint.

The right choice depends on your stack, your engineering capacity, and what your 3-year roadmap looks like. We’re happy to walk through the trade-offs for your specific situation — including the cases where one of the first two options is the better answer.

A Real Shopware B2B Project: Halron Lubricants

Theory is one thing. Here’s how a real B2B Shopware project plays out.

Halron Lubricants is a Midwest distributor that’s been serving industrial and commercial clients for nearly a century. Halron came to Atwix locked into a closed legacy eCommerce platform — every change required a vendor ticket, integrations were rigid, and the platform couldn’t keep pace with the business.

“We were spending too much time managing technology instead of using it to move forward.” — Keith Van Pay, IT Manager, Halron Lubricants

The goal was clear: an open platform, deeply integrated with Halron’s Infor CloudSuite Distribution ERP, that gave the team direct control over content, customers, and catalog management.

The Atwix and Halron teams started with a discovery phase that mapped every workflow — Ship-To accounts, billing nuances, customer-specific product restrictions, regional pricing — against how CloudSuite handled the same data. The output: a clear definition of what data lives in the ERP versus what’s managed in Shopware, and how the two systems sync in real time.

What changed after launch:

• Halron’s team manages the storefront directly. No more vendor tickets for content, catalog, or customer changes.
• The ERP integration is real-time and accurate. Pricing, inventory, and customer data flow in both directions, with guardrails ensuring every product, order, and Ship-To pairing syncs correctly.
• The storefront is fast. Page loads, navigation, and checkout are noticeably better for long-term customers.
• The platform is built to scale. Phase two will add expanded customer access and shipping integrations for larger industrial orders, including UPS and LTL.

“This project changed how we think about eCommerce. It’s not just an online catalog anymore. It’s how we do business.” — Keith Van Pay, IT Manager, Halron Lubricants

Read the full Halron case study for more detail on the implementation.

When Shopware Isn’t the Right Fit

Useful platform content has to name the cases where the platform isn’t the answer. A few situations where we’d send you elsewhere:

You’re a small B2B operation with a single buyer per customer, no contract pricing, and no approval workflows. BigCommerce B2B Edition or Shopify Plus will get you live faster and cheaper, and you won’t outgrow them for a while. Shopware Evolve is overkill for your stage.

You’re a heavily customized Adobe Commerce shop with deep B2B muscle and a working ERP integration. The replatforming cost rarely pencils out. Stay where you are, optimize what’s already working, and revisit Shopware in 3–5 years if Adobe’s roadmap drifts.

Your business runs on highly customized SAP S/4HANA with bespoke pricing, contracts, and B2B logic that lives entirely in the ERP. A platform like SAP Commerce Cloud (Hybris) or commercetools is closer to your gravity well. Shopware can do it, but the integration spend will dwarf the platform spend, and you’ll spend three years rebuilding logic that already works in SAP.

You sell almost entirely through EDI and have no real eCommerce ambition. No platform will help. Fix EDI first. Adding a Shopware storefront on top of broken EDI just adds a second broken channel.

You need a fully headless, custom-built buyer experience and have no interest in Shopware’s storefront. It’s possible — Shopware’s API-first architecture supports it — but at that point you’re paying for a platform whose storefront you’re not using. commercetools or a build-your-own-stack approach may serve you better.

For most mid-market B2B distributors, manufacturers, and wholesalers — especially those with multi-user accounts, negotiated pricing, and ERP dependencies — Shopware fits well. For everyone else, here’s where to look instead.

What a B2B Shopware Build Actually Costs

Most articles dodge this question. Here’s a real range.

Shopware platform licensing:

• Rise — entry tier, no B2B Components. Wrong fit for serious B2B; mentioned only for completeness.
• Evolve — typical mid-market B2B fit. Includes B2B Components. Annual licensing typically falls in the low five-figure range, scaling with GMV.
• Beyond — enterprise tier with the full feature set, advanced support, and capacity. Annual licensing typically runs into the six figures, scaling with GMV.

Shopware doesn’t publish list prices, and actual numbers vary based on GMV, regions, and term length. Talk to Shopware sales (or your partner) for an actual quote.

Implementation, year one (mid-market B2B with ERP integration):

• Light scope — Evolve plan, B2B Components, single ERP integration via existing connector, modest design customization, no migration: typically $80K–$150K.
• Standard scope — Evolve plan, deeper ERP integration, custom storefront design, data migration from a legacy platform, 2–3 sales channels: typically $150K–$350K.
• Complex scope — Beyond plan, multi-ERP environment, custom B2B workflows, advanced PIM/CRM/WMS integration, multi-region rollout: $350K–$800K+.

Ongoing costs (year 2+):

• Shopware licensing renewal
• Hosting and infrastructure (Shopware Cloud or self-hosted; budget 5–15% of platform cost)
• Ongoing development and support (typically 15–25% of year-one implementation cost annually for active maintenance and incremental feature work)
• Integration maintenance — varies hugely by approach (custom integration is the most expensive over time; pre-built connectors are the cheapest)

These are honest ranges from the projects we’ve delivered, not list prices. Your actual number depends on ERP complexity, scope discipline, and whether you’re migrating from a legacy platform or building fresh. We’re happy to scope a specific project against these ranges in a discovery call.

A Phased Migration Path: Suite to Components

If you’re already on B2B Suite, the migration to Components isn’t a single switch — it’s a sequence. Here’s how we typically phase it.

Phase 1: Audit and gap analysis (2–4 weeks). Map every Suite feature you actually use against the Components equivalent. Suite has features Components doesn’t (and vice versa); this is where you discover what needs custom work versus what’s a clean swap.

Phase 2: Data migration plan (2–3 weeks). Customer hierarchies, employee accounts, role assignments, approval rules, and budget structures all live in different schemas. Map the migration path for each, including edge cases (orphaned employees, deprecated roles, custom permission flags).

Phase 3: Parallel build on Components (8–14 weeks). Build the Components configuration in a staging environment alongside the live Suite shop. Validate pricing, approvals, and ERP sync against real data before any cutover.

Phase 4: Pilot rollout (4–6 weeks). Migrate a handful of friendly customers first. Catch the issues that only show up in production traffic — usually around custom permissions and ERP sync edge cases — before the full cutover.

Phase 5: Full cutover and Suite decommission (2–4 weeks). Migrate remaining customers, decommission the Suite plugin, and run on Components. Keep the Suite environment available for read-only data access for 30–60 days as a safety net.

Total typical timeline: 18–30 weeks from kickoff to full cutover, depending on complexity. The two biggest variables are the depth of your Suite customization and your ERP integration topology.

The 6.8 EOL date isn’t published as a hard deadline yet, but the closer you wait, the more likely you’ll be doing this under time pressure. Plan now even if you start later.

Why Shopware Works for B2B

Pulling this all together — what makes Shopware a strong fit for serious B2B operations in 2026?

A modular feature set that mirrors how B2B actually works. B2B Components let you turn capabilities on per customer or customer group. You’re not paying for or maintaining functionality your customers don’t use.

A pricing engine built for negotiated B2B pricing. Advanced Prices, Rule Builder, and Individual Pricing handle tiered, volume, customer-group, and named-account contract pricing without custom development.

Genuine API-first architecture. Shopware connects cleanly to ERP, CRM, PIM, WMS, and middleware. This is what lets a single deployment scale across multi-ERP, multi-region, multi-brand environments — the actual complexity that mid-market and enterprise B2B operations live with.

Hybrid B2B/B2C and D2C support. One Shopware install can serve B2B distributors, D2C retail, and field sales reps simultaneously, with separate sales channels, customer groups, and catalogs for each audience.

Enterprise-grade security and compliance. SSL, 2FA, role-based access, audit logging, and EU data residency are built in.

Real scale, in the wild. Beijer Ref consolidated 35 Shopware instances across 28 countries (out of its 45-country footprint and 500+ branches) and grew eCommerce from 0.1% to 15% of total revenue in 36 months — not as a channel experiment, but as a fundamental redesign of how the business sells. BlueAlly, a large-scale IT distributor with millions of SKUs and hundreds of branded sub-stores, launched its first sales portal in under six weeks. Eagle Crusher, a manufacturer of configurable industrial equipment, surfaced complex variant logic and aftermarket compatibility rules directly in the digital experience.

Recognized direction of travel. Shopware was again named a Visionary in the 2025 Gartner Magic Quadrant for Digital Commerce, marking its sixth consecutive year of inclusion in the report. For B2B decision-makers, that’s an additional data point that Shopware is a strategic platform rather than a tactical short-term fit.

If you’ve read this far, you’re past the “what is Shopware” stage. The next question is whether the platform fits your specific business and what a real implementation looks like for your stack.

We can help with:

• A Shopware fit assessment — does Shopware actually solve your B2B problems, and which plan and component set you’d need
• A Suite-to-Components migration scope — phased plan, timeline, and budget range for your specific Suite customization
• An ERP integration assessment — for distributors on Prophet 21, Infor, or other distribution ERPs, where the integration risk and cost actually sit
• A platform comparison — Shopware vs Adobe Commerce vs BigCommerce vs commercetools for your situation

No deck, no pitch. A 30-minute conversation about what you’re trying to do and what makes sense.

Book a discovery call →