Shopware B2B Development: How to Build a High-Performance Commerce Store in 2026

67% of B2B buyers now prefer completing purchases without a sales rep. They want self-serve order management, customer-specific pricing, and quote workflows, accessible from a browser, without a phone call.

Shopware 6 is the platform most DACH manufacturers and distributors are using to deliver this. For the fourth consecutive year, Shopware holds 11.5% market share among Germany's top 1,000 online shops, the largest of any platform. The infrastructure is proven. The question is how to build on it correctly.

This guide covers what Shopware B2B development looks like in 2026: what the platform provides natively, what requires custom development, how to architect for performance, and what most projects get wrong.

How do you build a B2B online store with Shopware?

A Shopware B2B store is built in three layers: native B2B Components for core workflows (quotes, approvals, employee management), custom API development for ERP/CRM integration and non-standard pricing logic, and a headless or API-first frontend for performance. The Evolve licensing tier unlocks the full B2B feature set. Custom development handles everything your business does that the platform does not.

Why Shopware 6 for B2B in 2026

Shopware 6 is API-first from the ground up. Every storefront operation runs through the Store API, which means the platform supports both traditional and headless architectures without a rebuild. For B2B operations, where buyer portals, ERP integrations, and complex pricing rules are standard requirements, this matters.

80%+ of Shopware's global customer base is in the DACH region. The ecosystem of extensions, agencies, and integration partners reflects this concentration. For manufacturers and distributors serving German-speaking markets, the platform support infrastructure is mature in a way that generic global platforms are not.

The legacy B2B Suite is being sunset with Shopware 6.8. If your current implementation runs on the old suite, migration to B2B Components is mandatory, not optional.

What Shopware B2B Components give you natively

From Shopware 6.6+ on the Evolve plan, the following are available without custom development:

→ Employee Management: create buyer accounts under a company, assign roles, set permissions per employee

→ Order Approvals: configure approval workflows by order value or product category

→ Quote Management: buyers submit a cart as a quote request; sales team responds with a formal offer; buyer converts to order

→ Quick Order: buyers upload a CSV or enter product numbers directly to build large orders fast

→ Shopping Lists: save and reuse order templates, shareable across company accounts

These cover the core self-serve B2B workflow. A buyer can log in, build an order, submit for approval, receive a quote, and confirm, without contacting sales.

What this does not include: customer-specific pricing at scale, ERP-synced inventory, complex contract terms, or multi-warehouse logic. Those require custom development.

What requires custom Shopware B2B development

The native components handle workflow. Custom development handles complexity.

The most common custom development requirements on Shopware B2B projects:

ERP and PIM integration

Shopware's Store API supports bi-directional data exchange, but the mapping logic between your ERP (SAP, Microsoft Dynamics, ProAlpha) and Shopware's data model requires custom connector development. Product data, stock levels, customer accounts, and order status all need defined sync cadences and error handling.

Customer-specific pricing

Shopware supports price lists and customer group pricing natively. Manufacturers with individual contract prices per customer, common in wholesale and industrial distribution, typically need a custom pricing layer that queries the ERP at runtime.

Complex approval hierarchies

The native approval workflow covers single-level approvals by order value. Multi-level approval chains (department head → finance → procurement) require custom extension.

B2B customer portal

Beyond the standard account area, many manufacturers need a dedicated portal: order history, delivery tracking, invoice downloads, contract document access. This is a frontend build, not a native feature.

Architecture decisions for high-performance Shopware B2B

Shopware 6.7.5 introduced production-ready Store API caching. The performance difference is measurable: a cached response returns in 20 ms; an uncached origin request takes 480 ms. At scale, proper caching reduces origin requests by 85%+.

For B2B stores where catalogue size is large and customer-specific data is common, the architecture decisions that determine performance are:

Headless vs. traditional

Shopware supports both. Headless (Vue Storefront, Next.js, or custom frontend consuming the Store API) gives the most frontend control and the highest performance ceiling. Traditional Twig-based storefronts are faster to build and sufficient for most mid-market B2B operations. Choose headless when your frontend requirements, progressive web app, mobile-first buyer portal, complex filtering, exceed what Twig templates can deliver cleanly.

Caching strategy

Set Cache-Control: s-maxage correctly for catalogue pages and product data. Personalized content (customer-specific prices, account data) must be excluded from shared cache. A mixed-cache architecture, CDN for public pages, no-cache for authenticated buyer sessions, is the standard pattern.

Database query optimization

N+1 queries on product listings are the most common performance bottleneck on Shopware B2B stores with large catalogues. Use Shopware's association loading correctly and profile before go-live.

Building the customer portal experience

The account area is where B2B buyers spend most of their time, not the storefront. Order history, reorder workflows, quote tracking, and invoice management are the features that determine whether the platform reduces operational overhead or just adds a digital layer on top of existing manual processes.

Build the portal around buyer tasks, not platform features:

Reorder - one click from order history to cart
Quote status - visible tracking from request to approval to order
Approval visibility - buyers see where their order is in the approval chain
Invoice access - downloadable PDF invoices synced from ERP

Employee Management in Shopware B2B handles permission scoping: a buyer can see only their own orders; a purchasing manager sees the whole company account. Build role definitions to match your customers' actual internal structures, not a generic buyer/admin split.

Shopware B2B development checklist for 2026

Before development begins

Confirm Shopware Evolve licensing is in place
Map every ERP data entity that needs to sync to Shopware
Define customer-specific pricing rules and where master data lives
Identify approval workflow requirements per customer segment
Decide: headless or traditional storefront

During development

Build ERP integration with retry logic and error logging from day one
Profile database query performance on catalogue pages with realistic data volume
Test approval workflows end-to-end with real company account structures
Validate Store API caching configuration in staging before go-live

Before go-live

Run load tests against the Store API at expected concurrent buyer sessions
Confirm customer-specific pricing returns correct values for 20+ test accounts
Test order sync to ERP through the full fulfilment cycle

What most Shopware B2B projects get wrong

Starting ERP integration too late. ERP sync is not a phase two task. Customer-specific pricing, inventory accuracy, and order confirmation all depend on it. Projects that defer integration to the end of the build consistently miss go-live dates.

Underspecifying the approval workflow. Native order approvals cover one level. If your customers operate with multi-level procurement approval, and most mid-sized manufacturers do, this needs a custom build, not an assumption that the native feature will stretch.

Building for admins, not buyers. The portal gets scoped by internal teams who think in admin terms. Buyers think in task terms. Test every workflow with a real buyer scenario before sign-off.

Building a Shopware B2B store that performs

Shopware 6 is mature enough in 2026 to handle complex B2B requirements without starting from scratch. The native B2B Components cover the core self-serve workflow. Custom development handles the integration and complexity that make B2B commerce operationally real.

The stores that perform, in speed, in adoption, and in operational impact, are the ones built around a clear decision: what does this portal need to enable for the buyer, and how does every integration decision serve that outcome.