Multi-market

Part 1 — For business and content users

A market in Laioutr is a regional slice of your storefront: a named region (e.g. Switzerland, Germany) with its own domains, languages, and currency. You configure markets in Cockpit → Markets.

Each market has one or more domains. A domain maps a host and optional path prefix to a language:

One domain per market is the default (the root URL without path prefix). You can also limit pages to specific markets in Studio; other markets won't show that route.

The combination of market and language is the context a customer browses in. When someone visits www.shop.ch/fr, Laioutr resolves the market (Switzerland) and the language (French). Everything downstream (currency, measurement system, content translations, available pages) follows from this context.

Languages are defined once in Cockpit → Translations and assigned to markets via domains. See Multi-language support.

Part 2 — For developers

Configuration

Markets and their domains come from RC (laioutrrc.markets). Each RcMarket has:

• id, slug, name
• currency (ISO 4217, e.g. CHF)
• regionCodes (e.g. ["CH"])
• defaultDomainId
• domains: dictionary of RcMarketDomain, each with id, host, optional path, and languageId

At build time, Frontend Core transforms this into a RenderI18nConfig (via buildI18nConfig()) with resolved types (RenderMarket, RenderMarketDomain, RenderLanguage) and lookup maps (marketById, marketBySlug, hostToMarket). You access this derived config through composables, never the raw RC.

Composables

const market = useMarket()          // ComputedRef<RenderMarket>
const language = useLanguage()      // ComputedRef<RenderLanguage>
const domain = useMarketDomain()    // ComputedRef<RenderMarketDomain>
const currency = useCurrency()      // ComputedRef<string>, shorthand for market.currency
const config = useI18nConfig()      // RenderI18nConfig (static, not reactive)

These are always defined. Resolution falls back to the default market when the host is unknown.

Use useI18nConfig() when you need the full list of markets and languages, for example to build a market picker.

Currency: use useCurrency() for formatting (via the UI Kit's $money formatter) or passing to APIs.

Region / measurement: use useLanguage().value.measurementSystem (metric/imperial) or useMarket().value.regionCodes for region-specific behaviour.

Page-level market scope

RcPage.marketIds (optional): if set, the page only exists in routes for those markets. A "CH only" landing page won't generate routes in the Germany market.

Validation

validateI18nConfig(languages, markets) runs at build time and checks: valid BCP 47 codes, existing defaultDomainId and languageId references, no duplicate (host, path) pairs. Issues are logged as warnings.

Dev hosts

toDevHost(host) maps production hosts to local development hosts (e.g. www.shop.ch → shop-ch.local.laioutr.tech). A *.local.laioutr.tech wildcard DNS record points to 127.0.0.1, so you can test multi-domain setups locally. The first market is also aliased to localhost as an offline fallback.

Fallback behaviour

Market and language are never null at runtime. Resolution always produces a result: