Headless Commerce with Shopware: Frontend Freedom for B2B

In the traditional e-commerce model, the backend not only handles business logic but also delivers fully rendered HTML pages to the browser. This is easy to operate but inflexible: the backend's template system dictates how the shop looks and behaves. Headless commerce separates these layers entirely. The backend — in our case Shopware CE — handles data storage, pricing, order processing and all B2B business logic. The frontend is an independent application that communicates with the backend via the Shopware Store API and renders the interface completely on its own terms.

This decoupling creates freedoms that are not achievable with the classical Shopware Storefront approach. The frontend team can work with modern frameworks such as Vue.js, React, SvelteKit or Next.js without needing knowledge of the PHP backend stack. Frontend iterations, A/B tests and performance optimizations can be performed entirely independently of backend deployments. At the same time, design specifications can be realized at any level of detail that a theme system could never accommodate. For B2B projects with complex user interfaces, customer-specific dashboards and multi-step ordering processes, this is a decisive advantage.

The Shopware Store API is a complete REST API that makes all Shopware frontend functions accessible programmatically. Product catalogs, category structures, search, cart, checkout, customer accounts and B2B-specific features such as company hierarchies, approval workflows and individual price lists — everything is available via cleanly documented endpoints. The API follows the OpenAPI standard and is fully typed, so frontends can use auto-generated client code.

Headless commerce is not the optimal choice for every project. A classic Shopware Storefront shop is faster to build and sufficient for many B2B projects. The decoupled architecture delivers its value when specific requirements arise that a classic storefront approach cannot fulfill economically. In our projects, we recommend headless commerce for the following scenarios.

In B2B commerce, purchasing rarely happens through a single channel. Buyers order via the web shop, field sales staff via an app on a tablet, large accounts via punchout connections from their ERP, and certain products are assembled through a specialized configuration portal. The headless architecture makes exactly this scenario possible: all channels communicate through the same Shopware Store API, and the business logic — customer-specific prices, order approvals, inventory levels and ERP connectivity via our integration platform — lives in a single place in the backend.

In practice this means: when a pricing rule changes in the ERP, the change takes effect immediately across all channels without any frontend updates. New product data, categories or promotional prices are maintained once and automatically available in the web shop, app and punchout portal. PIM integration delivers structured product data into the Shopware backend, from where the API distributes it to all frontends. This central data model is the true value of a well-built headless system: it eliminates data silos not only between shop and ERP but also between your various sales channels.

A headless commerce project with Shopware CE covers much more than frontend development alone. We handle the full spectrum from architecture design through API extensions to production-ready deployment. The following describes the key service components included in a typical headless B2B project.

The decision between headless commerce and a classic storefront approach is one of the most important architectural choices we make together with our clients. Both approaches have their place, and we deliberately set no default that applies to every project. What matters are your specific requirements, your internal technology environment and your long-term digital strategy.

Headless commerce in a B2B context presents different demands than in the consumer space. Complex company hierarchies, multi-level approval workflows and customer-specific catalog views must work just as reliably through the Store API as in the classic storefront approach. In our projects, we have built headless frontends for exactly these scenarios and have proven patterns for mapping complex B2B logic in a decoupled frontend.

We pay particular attention to pricing strategy in the headless context. In B2B, correctly displaying customer-specific prices, tiered rates and framework contract conditions is business-critical. We implement a carefully designed caching strategy that ensures pricing pages are never served with incorrect data: price requests are cached server-side with short TTLs and are never stored in public CDN caches at the customer level. The result is fast price display without the risk of showing one customer another customer's price.

For B2B portals with a strong self-service character — such as the B2B customer portal — the headless approach is particularly well suited. Order histories, invoice archives, delivery status and individual dashboards can be designed far more conveniently and responsively with a modern JavaScript framework than with classical Twig templates. At the same time, the customer portal benefits from the central Shopware backend logic for permissions, company hierarchies and pricing.