Run every brand, region, and market on one platform
Run B2B and B2C, multiple brands, legal entities, regions, markets, and customer groups from one platform, while sharing the data and integrations that should stay shared.
One operating pattern behind every brand, unit, and market
Each of these runs on one platform, one Vendure Dashboard, and one shared catalogue, with only what differs configured per entity.
Several brand storefronts share one catalogue, each with its own pricing, language, and look. One team operates every brand, and each brand team sees only its own.
Give each division, subsidiary, or operating company its own storefront and rules, while the catalogue, customers and orders stay on one system. Each legal entity is modelled as a seller.
Different currency, language, tax, and fulfilment per region, without a parallel stack per country. Add a market by configuring it, not by rebuilding.
Wholesale, retail, key accounts, and partner tiers each get their own price lists (contract pricing, from Scale). Separate catalogues run as separate channels.
Sell to businesses and to consumers from one platform. Company accounts, quotes, and approvals for buyers, a clean consumer storefront for shoppers, and one order and customer record behind both. See how the B2B buying flows work.
One catalogue, one order flow, one team
Running more brands, regions, and segments should not mean running more systems. On Vendure, everything that is shared stays shared, and only what actually differs is set per entity.
One catalogue to maintain
Products live once, in a shared catalogue. Each brand or market selects what it sells and overrides only its price, translation, or availability. Change the product once, and every storefront that carries it updates.
Local price, currency, and tax
Set pricing, currency, and tax per market. The European storefront sells in EUR, the US one in USD, each with its own tax rules, on one deployment.
Local language, one source
Product and content translations per market, from one canonical record. A Swedish storefront and an English export storefront read the same product, each in its own language.
The right access for each team
Scope Dashboard users to the brands or regions they run. A brand team sees only its brand, a regional manager only their region, a central team keeps the full view. One Dashboard, the right view for each person.
Regional stock and fulfilment
Attach warehouses and fulfilment rules per market, so the same product ships from a UK warehouse for UK orders and a German one for German orders.
One customer and order record
Every brand and market reports into one order and customer model, so a buyer who moves between your storefronts is one record, and your numbers add up across the business.
A storefront your customers actually use
Every one of these storefronts is a real, buyer-ready application, not a template you fight with. Company accounts, quotes, approvals, quick order, and multi-step checkout: the flows B2B buyers expect, wired to a surface your team owns and can change. The Vendure B2B Storefront is included from Scale.
Launch a new brand or market on a storefront that already works, on a codebase your team controls. No proprietary frontend runtime between you and the experience your customers see.
One codebase, every business model
The storefront ships reference scenarios on one codebase, configured rather than forked. Hybrid businesses run B2B and B2C from the same code, scoped by the authenticated buyer.
A polished consumer storefront: browse, search, checkout, accounts, and order history. Use it for B2C channels alongside the B2B buying experience.
The same shell configured for a buyer at a customer company: company accounts, quote-to-order, approvals, quick order, and contract pricing.
Configurator-driven ordering (configurator on Enterprise) and vertical-specific catalogue presentation, on the same components and the same checkout.
Teams building complex commerce with Vendure
Under the hood: one deployment, or a tenant per deployment
Most programmes run every brand, region, and segment on one deployment, sharing one Vendure Dashboard and one catalogue. When a business unit needs hard data isolation, Vendure can also run as one codebase with a separate instance and database per tenant, on the same upgrade path. Each production database needs its own Project and plan subscription.
The two patterns compose. A multi-tenant deployment can still run multiple brands inside each tenant, so you match the isolation to the requirement rather than the other way round.
What teams ask about running multiple brands and markets
Common questions from operations and ecommerce teams sizing a multi-brand, multi-region, or hybrid rollout on Vendure.
Yes. Multiple brand storefronts share one catalogue, one Vendure Dashboard, and one order flow, with their own pricing, language, and theming. One team operates every brand, and each brand team can be scoped to see only its own.
Yes. Business buyers get company accounts, quotes, and approvals, consumers get a B2C storefront, and both run on one catalogue with one order and customer record behind them. The B2B buying page covers the procurement side.
Each market has its own currency, language, tax rules, and fulfilment, configured on the same platform. Products and content are translated from one canonical record, so you maintain the product once and each market reads it in its own language and price.
Yes. Dashboard access is scoped per brand or region. A brand team sees only its catalogue, orders, and customers, a regional manager sees only their region, and a central team keeps the full view.
One. Products, collections, and assets are shared canonical records. Each brand or market selects what it sells and overrides only its price, translation, or availability. A change to the shared product flows through every storefront that carries it.
Run everything on one deployment when brands, regions, and segments share a feature set. Move to a separate instance and database per tenant when a tenant needs a different feature set, hard data isolation for residency or compliance, or independent spin-up and teardown. Each production database needs its own Project and plan subscription. The patterns compose, and solutions engineering will scope the right shape with you on a discovery call.
Model your brands, regions, and markets
Set up your brands, legal entities, regions, and customer groups in a 14-day trial, or compare the plans to see which one fits.
