Run several brands, countries, languages or B2B and B2C channels from one Magento installation. We design the website, store and store view structure, set up domains, currencies, tax and inventory, and make sure search engines understand every version of your store.
Magento organises a multi-store installation in three levels. A website holds customers (by default), payment and shipping settings, currencies and prices. A store holds a root category, so different stores can show different catalogues. A store view is usually a language or locale, with its own translations, product names and descriptions.
Getting this structure right at the start matters more than any other decision. It controls whether customers and carts are shared between brands, how prices and currencies work, which catalogue each audience sees and how much content your team has to maintain.
We have built multi-store Magento for brand portfolios, wholesale and retail on one platform, and Nordic, UK and European storefronts with separate domains and languages. We bring that experience to your structure, tax, inventory and SEO design.
From initial architecture to adding a new country to an existing installation.
Design the website, store and store view hierarchy around your brands, markets, customers and team.
Separate domains, subdomains or subfolders per store, with web server, Varnish and SSL configuration.
Locale store views, translated products, categories, CMS and emails, and translation workflows with your team or PIM.
Base and display currencies, tax rules per country, VAT display and market-specific payment and shipping methods.
Multi-source inventory with warehouse sources and stock assignments per website.
hreflang, canonical tags, localised metadata and sitemaps per store, avoiding duplicate content across markets.
Each website or store view is reached through its own base URL. On Nginx or Apache, the incoming domain is mapped to a run code and run type — MAGE_RUN_CODE and MAGE_RUN_TYPE — which tell Magento which website or store view to load. With subfolders, the store code can be added to URLs instead.
Varnish caches each store separately because the store context is part of the cache key. SSL certificates must cover every domain, and cookies are configured per domain so sessions do not leak between brands.
We keep store configuration in app/etc/config.php and environment-specific values in env.php, or set them with bin/magento config:set in deployment scripts. That way a new environment can be created with every store correctly configured, rather than clicking through the admin by hand.
Multi-store mistakes are expensive to undo. We plan structure, data and SEO together.
We document scope decisions before configuration, so finance, operations and marketing agree on how it will work.
Store settings are managed through config.php, env.php and data patches, so environments stay consistent.
Separate Hyvä or Luma child themes per brand, sharing components where it makes sense.
hreflang and canonical rules are tested so each market ranks with its own version of the page.
Adding a new store view to an existing installation can take days; a new multi-country platform takes longer.
Brands, markets, languages, customers, pricing, tax, inventory and content workflows.
Scope hierarchy, domains, catalogue structure and data ownership documented and agreed.
Stores, settings, themes, translations and integrations implemented as code.
Products, categories and CMS content imported and translated per store view.
Markets launched one at a time with SEO checks, tracking and monitoring.
Tell us which brands, countries and languages you plan to run. We will propose a structure and the work involved.
Within one business day, Mon–Fri
No obligation. We reply within one business day.