Multi-Store vs Multi-Channel vs Multi-Market — Pick the Right Expansion Axis
Three different expansion questions, three different Commercefull concepts. A practical guide to stores, sales channels, and markets — and when you need which.
October 29, 2026
“Go international” is actually three different questions wearing one hat:
- Where do you operate — one store, or several regional ones?
- How do customers reach you — web, POS, marketplace, AI agents?
- Which countries do you serve — and under what commercial rules?
Commercefull models them as three distinct concepts — Store, SalesChannel, Market — and you add them at different stages. Getting the mapping right early saves an expensive re-platform later.
Store: where you operate
A Store is an operating unit under your Organization: its own catalog assortment, price lists, currencies, locales, warehouses, fulfillment modality (physical/digital/hybrid), tax display mode, and theme.
You need multiple stores when regions genuinely operate differently — a US store (USD, tax-exclusive, US warehouses) and a UK store (GBP, tax-inclusive, UK warehouses) with separate inventories and merchandising teams. One store is enough until that’s true.
SalesChannel: how customers reach you
A SalesChannel is a route to the customer: web, pos, marketplace, social, agentic, api. Channels are organization-owned and assigned many-to-many to stores — one store sells through all its channels simultaneously.
Every basket, order, and event records storeId + channelId, so channel-scoped merchandising works: assortments, collections, promotions, pricing rules, content, and themes can all target a channel. Agentic checkout is just a channel of type agentic — same order pipeline as your web storefront.
You need channels when the same store sells through several surfaces — which is earlier than most teams think (web + a marketplace listing is already two).
Market: which countries you serve
A Market binds selling countries, currencies, locales, capabilities, a catalog assortment, a default price list, payment/fulfillment methods, a contracting entity, and hostnames — one versioned object for “we serve these countries under these rules.”
You need markets when expansion is driven by country rules rather than store count: distinct tax display modes, VAT regimes, payment-method preferences, legal entities, or language requirements per country. Markets are created as drafts and must pass a 12-dimension readiness audit before launch — see the market launch guide.
The decision table
| Your situation | What you operate |
|---|---|
| One country, one storefront | One store + web channel |
| Same store, selling on web + marketplace + AI agents | One store + multiple channels |
| Regional catalogs, warehouses, or teams | Multiple stores |
| Countries with distinct tax/payment/legal/language rules | Markets (bound to stores) |
| All of the above | Stores + channels + markets — they’re complementary, not exclusive |
The key property: each stage builds on the last. You don’t fork the platform to add a channel or a market — a market resolves through the channels of its bound store, and everything stays in one codebase, one data model.
Read more
Ready to own your store?
Commercefull is free, open-source, and Apache-2.0 licensed. Every module, every line, every row of data — yours.