Headless Commerce is more than a buzzword – it's a fundamental architectural shift in e-commerce. By decoupling frontend and backend, online shops can create shopping experiences on any channel and device without being tied to a rigid system. Shopware 6 was built API-first from the ground up and offers Composable Frontends as a powerful framework for modern headless projects. In this guide, you'll learn everything about architecture, technologies, and when headless makes sense for your shop.
What is Headless Commerce?
In classic shop systems, frontend (what the customer sees) and backend (inventory, order management, etc.) are tightly coupled – a monolith. Headless Commerce consistently separates these layers. The backend delivers data via an API, the frontend is completely independent.
This means: Your frontend can be built with Vue.js, React, Svelte, or any other technology. It can be a website, a mobile app, a voice assistant, a kiosk system, or an IoT device. The backend (Shopware 6) handles product data, orders, payments – everything else is freely selectable.
The name "Headless" comes from the fact that the backend is missing its visible "head" (the frontend). Instead, it communicates exclusively via APIs with any frontends.
Headless vs. Monolith vs. Composable
To choose the right architecture, you need to understand the differences:
| Aspect | Monolith | Headless | Composable |
|---|---|---|---|
| Frontend Freedom | Limited | Complete | Complete |
| Development Speed | Fast (Standard) | Slower (Custom) | Modular |
| Performance | Good | Very Good | Excellent |
| Team Requirements | Fullstack | Frontend + Backend | Specialized |
| Initial Costs | € | €€ | €€€ |
| Long-term Costs | €€ | € | € |
| Omnichannel | Limited | Yes | Yes |
| Vendor Lock-in | High | Medium | Low |
Composable Commerce goes a step further than Headless: Backend functions are also assembled modularly. Instead of a central backend, best-of-breed solutions for payment, search, PIM, CMS, etc. are combined – all connected via APIs.
Shopware 6: API-First from the Start
Shopware 6 was built from the ground up for headless scenarios. The architecture is based on two central APIs:
Store API (Sales Channel API)
Frontend-focused: Products, cart, checkout, customer accounts. For all storefront integrations.
Admin API
Backend-focused: Full access to all Shopware entities. For ERP integration, automation, B2B scenarios.
Both APIs are fully documented, follow REST principles, and support OpenAPI specifications for automatic client generation.
# Fetch products from a sales channel
curl -X POST \
'https://shop.example.com/store-api/product' \
-H 'sw-access-key: YOUR_ACCESS_KEY' \
-H 'Content-Type: application/json' \
-d '{
"limit": 10,
"includes": {
"product": ["id", "name", "price", "cover"]
}
}'Shopware Composable Frontends
Shopware Composable Frontends is Shopware's official framework for headless projects. It offers pre-built components, composables, and a demo store as a starting point – without locking you into a specific technology.
Technology Stack
The default stack is based on modern, proven technologies:
- Vue 3 – Reactive JavaScript framework with Composition API
- Nuxt 3 – Vue framework with Server-Side Rendering (SSR), Static Site Generation (SSG)
- TypeScript – Type-safe development with automatic API client generation
- Tailwind CSS / UnoCSS – Utility-first styling
- Vite – Blazing fast build process and Hot Module Replacement
The API client is an independent TypeScript library, not bound to Vue. You can use it with React, Svelte, Angular, or vanilla JavaScript (Shopware Docs).
Core Components
API Client
TypeScript-based client for Store API. Automatically generated, type-safe, framework-independent.
Composables
Vue 3 Composition Functions: State management, cart, checkout, product data – ready-to-use logic.
CMS Components
Pre-built components for Shopware Shopping Experiences (CMS pages, blocks, elements).
Three Entry Points
Depending on project requirements, Shopware offers different templates:
- Blank Template – Empty Nuxt application with installed dependencies. Maximum freedom, build everything yourself
- Demo Store Template – Complete, functional shop. Ideal for learning and as a base for customizations
- Custom Stack – Use only the API client, your own framework (React/Next.js, Svelte, etc.)
# Create new project with demo template
npx tiged shopware/frontends/templates/vue-demo-store my-shop
cd my-shop
npm install
# Configure environment variables
cp .env.template .env
# Enter SHOPWARE_ENDPOINT and ACCESS_KEY
npm run devPerformance Benefits of Headless
The decoupled architecture brings measurable performance improvements – crucial for Core Web Vitals and conversion rates:
- Server-Side Rendering (SSR) – First content visible immediately, SEO-optimal
- Code Splitting – Only required JavaScript code is loaded
- Lazy Loading – Components are loaded on demand
- CDN Deployment – Static assets distributed globally
- API Caching – Efficient caching at API level
PWAs (Progressive Web Apps) can load instantly through pre-caching and service workers – traditional storefronts take several seconds. The First Contentful Paint (FCP) time is significantly shorter with PWAs.
Shopware Frontends typically achieve LCP under 1 second and CLS near 0 – significantly better than classic monolith storefronts with Twig templates.
When Does Headless Commerce Make Sense?
Headless is not a silver bullet. For many shops, the classic Shopware storefront is the better choice. Headless makes sense for:
Good Candidates for Headless
- Omnichannel Requirements – Website, mobile app, kiosk, IoT, voice commerce
- Extreme Performance Focus – LCP under 1s, perfect Core Web Vitals
- Internationalization – Different frontends for different markets
- Strong Design Requirements – Individual UI/UX without template limits
- Micro-Frontend Architecture – Teams work independently on frontend modules
- Multi-Brand Strategies – Different brands with one backend
Better Choice: Classic Storefront
- Fast Go-Live – Standard shop with theme customizations
- Limited Budget – No dedicated frontend team available
- Plugin Dependency – Many plugins that provide frontend components
- Simple Maintenance – Everything from one source, updates include frontend
Headless increases complexity and requires specialized frontend developers. For a standard B2C shop with 5,000 products, the classic storefront with PageSpeed optimization is usually the more economical solution.
Headless for B2B E-Commerce
In the B2B sector, headless offers special advantages. B2B customers often expect individual interfaces, complex ordering processes, and integration with existing systems.
Customer-Specific Portals
Individual interfaces per customer group with custom prices, assortments, and workflows.
Quick Order
Optimized re-order flows, CSV upload, article number input – without standard UX compromises.
System Integration
Frontend shows real-time data from ERP, PIM, or external catalogs.
Approval Processes
Multi-stage approval workflows with custom UI components without plugin limitations.
Technical Implementation Step by Step
A typical headless project with Shopware Composable Frontends runs in the following phases:
- Conception – Requirements analysis, architecture decision (SSR vs. SSG vs. Hybrid)
- Setup – Configure Shopware 6 backend, create Sales Channel with API key
- Frontend Scaffolding – Choose template, set up project structure
- Component Development – Product lists, detail pages, cart, checkout
- CMS Integration – Connect Shopping Experiences, render content blocks
- Testing – Unit tests, E2E tests, performance audit
- Deployment – CI/CD pipeline, hosting on your own infrastructure
- Monitoring – Analytics integration, error tracking, performance monitoring
// In a Vue component
import { useProduct, useAddToCart } from '@shopware-pwa/composables-next';
const { product, search } = useProduct();
const { addToCart, isLoading } = useAddToCart();
// Load product
await search(productId);
// Add to cart
const handleAddToCart = async () => {
await addToCart({
id: product.value.id,
quantity: 1
});
};Hosting and Deployment
Headless frontends can be hosted independently of the Shopware backend. Popular options:
Managed Hosting
We host your headless frontend on our optimized infrastructure – including CDN, SSL, and monitoring.
Docker Container
Full control on your own infrastructure. Node.js server with SSR in Kubernetes or Docker Swarm.
Static Export
Pre-rendered HTML via nuxt generate. Hosting on any web server possible.
We handle the hosting of your headless frontend – including CDN, automatic deployment, and performance monitoring. One partner for shop and frontend.
Frequently Asked Questions
Backend plugins (e.g., payment providers, ERP integration) work fully. Frontend plugins (e.g., theme extensions) must be rebuilt in the headless frontend since no Twig templating is used.
This depends heavily on the existing shop. A greenfield project with Composable Frontends typically takes 3-6 months. Migrating existing shops requires additional analysis and migration time.
Yes, the Shopware API client is framework-independent. You can use React/Next.js, Svelte/SvelteKit, or any other JavaScript framework. The official composables are Vue-specific, but the API logic can be adapted.
Yes, if SSR (Server-Side Rendering) is implemented. Nuxt 3 with SSR delivers fully rendered HTML pages to search engines. Additionally, Schema.org markup and meta tags can be controlled programmatically.
Initial development costs are higher than with classic storefronts – expect 1.5 to 2 times the effort. In the long term, however, maintenance costs can decrease since frontend updates can be deployed independently of the backend.
Ideally yes. Headless projects benefit from specialized frontend developers (Vue/React) and backend developers (Shopware/PHP). With smaller teams, fullstack developers can cover both areas.
Headless is the Future, But Not for Everyone
Headless Commerce with Shopware 6 and Composable Frontends offers maximum flexibility, excellent performance, and true omnichannel capabilities. For companies with complex requirements, multiple touchpoints, or strong design focus, it's the right choice.
However: Headless is not an end in itself. For standard shops without special requirements, the classic Shopware storefront with an optimized theme remains the more economical solution. The decision should be based on an honest analysis – not on hype.
As a Shopware agency with experience in both worlds, we're happy to advise you on the architecture decision and implement your headless project from conception to go-live.
Headless Commerce Consultation
We analyze your requirements and recommend the optimal architecture – whether headless, hybrid, or classic storefront.
Request Consultation