Many growing e-commerce businesses face the same challenge: multiple brands, different target audiences, or international markets - but all managed from one central hub. 67% of mid-sized retailers already operate more than one online shop (DigitalCommerce360). Shopware 6 offers a powerful solution for exactly this scenario with its Sales Channel concept. In this guide, you will learn how to efficiently manage multiple shops with a single Shopware installation, which architecture fits your business model, and where the typical pitfalls lie.
What Is a Multistore in Shopware 6?
Shopware 6 does not require a separate "multistore plugin" - the ability to run multiple shops is natively built into the architecture. The core element is called the Sales Channel. Over 100,000 active Shopware installations (Shopware AG) use this concept worldwide. Each Sales Channel represents an independent storefront with its own domain, design, languages, and individual settings - but it is based on the same product catalog, the same customer database, and the same backend processes.
The result: 73% of multi-shop operators cite centralized data maintenance as their most important efficiency factor (IFH Köln). You maintain your product data, orders, and customer records in one central place, while each Sales Channel has its own storefront with individual appearance and customized rules. Businesses typically save up to 40% in administrative overhead compared to running separate shop installations (Shopware Community Survey).
A separate Shopware installation per shop means multiple maintenance cycles, separate updates, and isolated databases. Sales Channels share the technical infrastructure and enable centralized data management - a decisive advantage for efficiency and data consistency.
Typical Use Cases for Multistore
Shopware 6's Sales Channel architecture suits a wide variety of business models. Here are the most common scenarios we implement in practice:
International Shops
Separate storefronts per country with own language, currency, tax rates, and shipping options. Cross-border e-commerce grows 17% annually (Statista) - one product catalog, many markets
Multi-Brand Strategy
Different brands with unique design, assortment, and positioning under one central administration
B2B + B2C in Parallel
A B2B portal with tiered pricing and net display alongside the B2C consumer shop. B2B e-commerce in Germany reaches €468 billion in revenue (IFH Köln) - same products, different rules
Outlet and Brand Shop
Main shop with full prices and a separate outlet channel with reduced prices from the same inventory
Marketplace Integration
Besides your own storefront, also Amazon, eBay, and other marketplaces as Sales Channels
Multiple Domains
Separate domains for different product lines, regions, or target audiences - centrally managed and analyzed
Architecture: How Multistore Works Technically
The heart of the multistore capability is Shopware 6's database architecture. At its core, shared entities (products, categories, media, customers) are held in the central database, while channel-specific configurations (prices, visibilities, domains, themes) are stored per Sales Channel.
Each Sales Channel has its own configuration layer that individually controls the following aspects:
| Area | Central (shared) | Per Sales Channel (individual) |
|---|---|---|
| Products | Master data, descriptions, media | Visibility, prices, availability |
| Customers | Customer base, addresses, history | Customer groups, registration |
| Orders | Central overview and fulfillment | Order number sequences, workflows |
| Design | Base theme and assets | Theme configuration, layouts, CMS |
| Languages | Translations in the system | Active languages per channel |
| Payments | Payment provider configuration | Active payment methods per channel |
Setting Up Sales Channels: Step by Step
Setting up a multistore requires careful planning. Here is the proven workflow we follow in XICTRON projects:
- Define strategy: Which Sales Channels are needed? Which data is shared, which is channel-specific? Which domains and languages are planned?
- Create Sales Channel: In the administration under Sales Channels, create a new storefront channel and configure base data (name, languages, currencies, countries)
- Assign domain: Assign a custom domain or subdomain to the Sales Channel and configure DNS settings
- Control product visibility: Use dynamic product assignment to define which products are visible in which channel - via categories, tags, or manual assignment
- Differentiate pricing: Map channel-specific prices through pricing rules and customer groups - especially relevant for B2B scenarios
- Customize theme: Assign a custom theme or theme configuration per Sales Channel for individual appearance
- Configure payment and shipping: Define which payment and shipping providers are active per channel
- Testing and go-live: Comprehensive testing of all channels, verify cross-channel orders, and go live incrementally
Always test multistore configurations in a staging environment before going live. Changes to shared entities (products, categories) affect all Sales Channels simultaneously. Our hosting provides dedicated staging environments for exactly this purpose.
Internationalization with Sales Channels
One of the most common multistore use cases is internationalization. 76% of online shoppers prefer products in their native language, and 40% will not buy in a foreign language at all (Common Sense Advisory). European cross-border e-commerce reaches €237 billion (Cross-Border Commerce Europe). Shopware 6 offers two strategies for this:
Strategy 1: One Sales Channel with multiple languages - Ideal for European markets with the same currency and similar shipping conditions. You configure one Sales Channel with multiple language domains (e.g., shop.de, shop.at, shop.ch) and manage translations centrally.
Strategy 2: One Sales Channel per country - Recommended when currencies, tax rates, payment methods, or assortments differ by market. Each country shop has its own rules, but all share the product catalog and administration.
For internationalization, connecting a PIM system is particularly valuable: product texts, descriptions, and media can be translated centrally and synchronized to all Sales Channels via the Shopware API.
B2B and B2C from One Installation
Combining B2B and B2C sales in one Shopware installation is a scenario we implement regularly at XICTRON. 83% of B2B buyers now expect the same user experience as in B2C (Salesforce). The Sales Channel architecture enables clean separation while maintaining a shared data foundation:
- Price differentiation: Net prices in the B2B channel, gross prices in the B2C channel - based on customer groups and tax rules
- Tiered pricing: Volume discounts and individual price lists active only in the B2B channel, controlled via custom development
- Customer registration: B2B with company validation and approval process, B2C with instant registration
- Payment methods: Invoice and SEPA direct debit in B2B, PayPal and credit card in B2C
- Content and design: Technical product data and CAD downloads in B2B, emotional product images and lifestyle content in B2C
- Self-service portal: B2B customers with extended features such as reordering, budget management, and quote requests
Key Benefits of Multistore Architecture
The multistore architecture offers significant advantages over separate shop installations that directly impact efficiency and costs. Businesses with centralized e-commerce infrastructure achieve 28% lower operational costs (Forrester):
Central Product Management
Create products once, available in all channels. Changes to master data take effect everywhere immediately.
Unified Order Management
All orders from all channels in one overview - for efficient fulfillment and reporting.
Consistent Customer Data
One customer base across all channels - enabling cross-channel analysis and personalization.
Reduced IT Costs
One server, one update cycle, one maintenance - instead of separate infrastructure per shop. This reduces maintenance costs by an average of 35% (Gartner).
Faster Market Entry
New markets or brands can be set up as a new Sales Channel in days instead of weeks. Businesses with multi-channel strategies generate 190% more revenue than single-channel retailers (Omnisend).
Scalability
The architecture grows with you - whether 2 or 20 Sales Channels, central management stays manageable.
Challenges and Solutions
A multistore setup also brings challenges that should be addressed during planning. Here are the most common pitfalls and proven solutions:
| Challenge | Solution |
|---|---|
| Performance with many Sales Channels | Dedicated hosting with sufficient resources, caching strategies, and CDN deployment through professional infrastructure |
| Plugin compatibility | Check before deployment whether plugins support all Sales Channels - not every plugin is multistore-capable |
| Complex pricing structures | Implement rule-based pricing with advanced pricing rules and channel-specific customer groups |
| SEO for multiple domains | Configure correct canonical tags, hreflang attributes, and individual meta data per Sales Channel |
| Theme management | Use theme inheritance: create a base theme and define only the variations per channel |
| Team permissions | Assign granular admin rights per Sales Channel so teams can only edit their own channels |
Each Sales Channel increases database queries and memory requirements. From three to four active channels, we recommend dedicated hosting with SSD storage and Elasticsearch for product search. Our cloud solutions provide the necessary scalability. We also recommend migrating to PHP 8.5 for maximum performance with multiple channels.
Headless Multistore: API-First Approach
The headless commerce market grows annually by 22.1% (Grand View Research). For maximum flexibility, Shopware 6 offers the headless approach: The Store API delivers data per Sales Channel while the frontend is completely decoupled. Each Sales Channel can use its own frontend - whether classic storefront, React app, mobile app, or IoT application.
The Store API authenticates via the Sales Channel Access Key, uniquely assigned to each channel. This way, frontends receive only the data, products, and configurations of their respective channel. For complex multi-frontend scenarios, API integration is the key to success.
ERP and PIM Integration in Multistore
As the number of Sales Channels grows, manual data maintenance quickly becomes impractical. This is where integrations play a central role - 65% of e-commerce businesses with more than three sales channels use a PIM system (Ventana Research): A PIM system supplies all channels with consistent product data and translations, while the ERP system (SAP Business One, Microsoft Dynamics, or JTL-Wawi) synchronizes inventory, prices, and orders.
The typical integration architecture looks like this: The PIM delivers product data via the Admin API to all Sales Channels, the ERP synchronizes inventory and prices on a channel-specific basis, and orders flow from all channels back to the ERP for central processing. For individual consulting on the right integration architecture, we are here to help.
Planning Your Multistore Strategy
The success of a multistore setup depends entirely on planning. Before the first Sales Channel is created, the following questions should be answered:
- Which channels (B2B, B2C, international, brands) are needed in the short and medium term?
- Which data is shared across channels, and which is exclusive per channel?
- Are the planned plugins and extensions multistore-compatible?
- Is the existing server infrastructure sufficient for multiple active channels?
- What is the SEO strategy for multiple domains or subdomains?
- Which ERP/PIM integrations are needed for automated data management?
- How will team permissions be distributed across Sales Channels?
- Which KPIs will be tracked per channel and across channels?
Businesses that strategically plan their multistore architecture typically achieve 60% shorter time-to-market for new channels (McKinsey) and lower ongoing operational costs. A thorough consultation before starting pays off in the long run.
We analyze your business model, define the optimal Sales Channel architecture, and create a roadmap for implementation. From strategy through technical implementation to hosting - everything from one source.
This is what your multi-brand shop could look like:
Industrieteile-Portal
Fashion & Lifestyle Shop
Bio-Hofladen mit Abo-Modell
There is no fixed upper limit. In practice, many businesses operate 3-10 Sales Channels in one installation. From 5-6 active channels, however, we recommend high-performance hosting with dedicated resources, as each channel generates additional database queries.
Yes, all Sales Channels use the same product database. Through visibility rules, you control which products are displayed in which channel. Prices, descriptions, and media can be individually overridden per channel, while master data remains centralized.
Yes, this is a typical multistore use case. Through customer groups and channel-specific rules, you cleanly separate B2B and B2C logic. B2B customers see net prices and volume discounts, B2C customers see gross prices - all in one Shopware installation.
Not necessarily. Shopware 6 supports theme inheritance: you create a base theme and define only the variations per Sales Channel such as colors, logo, and fonts. For standalone brand identities, however, we recommend dedicated themes with custom design.
Each Sales Channel has its own domains with individual meta data, canonical tags, and hreflang attributes. Shopware 6 generates channel-specific sitemaps. For international setups, correct hreflang configuration is crucial to avoid duplicate content issues.
Via the Admin API, all common ERP systems can be connected, including SAP Business One, Microsoft Dynamics, and JTL-Wawi. The integration synchronizes inventory, prices, and orders across channels. Contact us for a customized integration consultation.
This article is based on data from DigitalCommerce360, Common Sense Advisory, Shopware AG, Shopware Community Survey, IFH Köln, Statista, Harvard Business Review, Salesforce, Forrester, Gartner, Omnisend, Grand View Research, Ventana Research, and McKinsey. The cited figures may vary depending on the survey period and methodology.
Multistore architecture for your business?
We design and implement your Shopware multistore solution - from Sales Channel strategy through technical implementation to ongoing operations.
Request multistore consultation