Skip to content
Browse documentation 146 guides

Configuration

Brands, storefronts, legal sellers and country routing

Configure multi-brand ownership, local policies, currencies, gateways and verified sign-in destinations.

About 2 min read

On this page

Brand defaults

Open System → Brands & storefronts with settings.manage (some release copy calls this Multi Country/Multi Brand). A brand defines identity, logo, colours, storefront/customer themes, legal seller, address, tax, terms/privacy, invoice footer/format, product allowlist, support departments, gateway connections and SMTP routes. A global storefront leaves country blank; a regional storefront supplies its legal country and allowed/default currency.

Choose account sharing explicitly. Shared customer identity does not transfer orders, invoices, services, domains, tickets or payments to another seller. Those records retain issuing brand/storefront. Invoice seller snapshots and queued email envelopes retain their original identity.

Local overrides

A storefront may inherit or override permitted seller/contact, logo, support, nameserver, gateway and mail choices. An explicit empty gateway list disables online methods. An explicit empty mail map cannot borrow another brand's sender. The legacy default can retain its installation-default behavior where null is meaningful. Configure actual prices and compatible payment methods for each offered currency.

Pinned TLDs control homepage/domain-search choices. Missing retail prices produce quote flows rather than invented amounts. Currency locks also apply to customer registration/profile, cart and checkout.

Country routing

Enable guest and/or customer country routing on the source storefront. Guest region preference and trusted-proxy country signals are different inputs; browser locale is not proof of physical location. Customer routing uses the owning account's billing country and stays within its brand. Choose Off, Redirect or Restrict and a valid fallback. A cross-brand guest redirect does not transfer sign-in.

Customer cross-host sign-in uses a short-lived single-use destination-bound handoff, with MFA and session checks repeated. Cookies are not widened across every brand. Pending or failed ownership/routing/HTTPS readiness blocks automatic authenticated destination routing.

Safe activation

Save storefronts inactive. Use the DNS/hosting/HTTPS readiness procedure, then activate only after current checks pass. Review both customer checkout and an old issued invoice after changing brand settings: the storefront may change while that issued document must remain stable.

Need a hand?

Tell us your product version, the step you are following and what happened. Our support desk keeps your conversation together.

Contact support →