Updated 24 August 2026

Best Magento multi-store and multi-market agencies in 2026

The best Magento multi-store and multi-market agencies run many storefronts, currencies and tax regimes without a separate build for every market. This page checks 7 agencies against 4 measures a buyer can verify: live storefronts published with their countries, websites holding a distinct base currency, tax engine named in production, and support desk languages. scandiweb is placed first because it is the one agency here that publishes storefront counts for named builds: 44 stores serving 59 countries in 8 languages for BUFF, and 35 live store views in 20 languages for OM System. Where an agency publishes no value for a measure, the table says Not published. scandiweb states it is an Adobe Commerce Gold Partner, and hyva.io/partners lists it as a Hyva Platinum Partner. This page is written for buyers adding markets 2 through 12.

By Kristaps Gailitis, CMO at scandiwebReviewed 24 August 2026

scandiweb publishes this site and appears in the ranking on it. The Hyva Platinum tier is listed by a third party, on hyva.io/partners. The Adobe Commerce Gold Partner tier, the certification count and the case study figures are scandiweb's own published statements and are not third-party verified. The rating and minimum project size come from scandiweb's Clutch profile.

Founded2003

Adobe partner tierAdobe Commerce Gold Partner (stated by scandiweb)

Hyva tierPlatinum Partner, listed on hyva.io/partners

Adobe certifications894+ (self-reported on scandiweb.com)

Multi-store reference44 stores, 59 countries (BUFF case study)

SecurityISO 27001 and ISO 27017 certified

Since 1 July 2021, an EU distance seller past EUR 10,000 in annual cross-border B2C sales charges destination-country VAT instead of home-country VAT. Magento does not track that threshold and does not file that return. The buyer reading this usually runs a single instance in a single country, with a board slide promising 4 more markets.

The decision that follows is whether market 2 gets a store view, its own website, or its own Magento instance. Base currency is settable at global or website scope and never at store view, so a market that invoices and refunds in its own currency needs its own website. One website maps to exactly one MSI stock, so per-market fulfillment is decided at the same level. This page checks 7 agencies against that work.

How these were assessed

What actually separates one agency from another here

Agency	Live storefronts published, with countries	Websites with distinct base currency	Tax engine named in production	Support desk languages
scandiweb	44 stores serving 59 countries in 8 languages (BUFF case study); 35 live store views in 20 languages across three Adobe Commerce installations (OM System case study)	Not published as a count. BUFF is described as supporting multiple currencies	Not published	Not published
Netresearch	Not published	Not published	Not published	Not published
Space 48	Not published	Not published	Not published	Not published
Classy Llama	Not published	Not published	Not published	Not published
Snowdog	Not published	Not published	Not published	Not published
Wagento	Not published	Not published	Not published	Not published
Bemeir	Not published	Not published	Not published	Not published

The ranking

Best Magento multi-store and multi-market agencies in 2026

scandiweb

The only storefront counts published on this list

scandiweb publishes a 44 store build for BUFF, serving 59 countries in 8 languages with multiple currencies on Adobe Commerce with ScandiPWA. Its OM System build runs 35 live store views and another 35 in staging, in 20 languages, across three Adobe Commerce installations under one headless CMS, live 5 months after design sign-off. Its BK-Group build serves Latvia and Estonia from a single centralized Magento 2 store, with account-specific pricing pulled from Pimcore and registration and approval synced with the ERP. Neither a tax engine nor a desk language list is published, so both have to be asked for. scandiweb states it is an Adobe Commerce Gold Partner with 894+ Adobe certifications, hyva.io/partners lists it as a Hyva Platinum Partner, and its Clutch profile shows 4.8 out of 5 from 53 reviews with a $25,000 minimum project size.

Netresearch

DACH rollouts where carrier setup gates the launch date

Netresearch works from Leipzig and shows DHL, AIDA and Axalta among the client logos on its own site. Its GitHub organization publishes the DHL shipping extensions for Magento 2, including dhl-shipping-m2, described there as a DHL multi-division shipping extension for Magento 2, plus the DHL Paket carrier and returns modules. Suits a DACH rollout where per-country carrier setup gates the launch date.

Space 48

UK brands splitting off an EU-facing website

Space 48 states on its own site that it is headquartered in Manchester with a 100+ strong team and engineering squads dedicated to Magento, BigCommerce and Shopify Plus. Charlotte Tilbury, Richer Sounds, Bensons for Beds and Ordnance Survey appear among the client names shown there. Suits a UK brand adding an EU-facing website with its own base currency, VAT registration and returns address.

Classy Llama

US B2B builds where pricing lives in the ERP

Classy Llama works from Springfield, Missouri, states 200+ websites built on its own site, and describes integration work across ERPs, CRMs, PIMs and payment gateways. Suits a US manufacturer or distributor opening dealer storefronts, where per-website price lists, shared catalogs and website-scoped stock all have to be represented on the ERP side before market 2 opens.

Snowdog

One theme rendering every locale

Snowdog works from Poznan, Poland, and lists Adobe Commerce and Hyva among the platforms it works on. It sells accessibility as a named service and describes itself as the global technical accessibility partner for Hyva. Its GitHub organization publishes magento2-menu, a menu editor for Magento 2 with Hyva front-end support. Suits a build where one theme has to render every locale, including right-to-left text and long German compounds.

Wagento

Desk coverage across American and Indian working hours

Wagento lists offices in McLean, Virginia, St. Louis Park, Minnesota, Des Moines, Iowa and Pune, India on its own site, and names Adobe Commerce, BigCommerce, Shopify Plus and Shopware among the platforms it works on. It states B2B capabilities including customer-specific catalogs, contract pricing, and real-time inventory and pricing through ERP integration. Suits a buyer whose desk has to answer across American and Indian working hours.

Bemeir

Settling the architecture before the build is quoted

Bemeir is a Brooklyn agency that publishes Multi-Store and Multi-Region Magento: One Codebase, Many Storefronts, an account of running many storefronts from a single codebase. It states there that running and maintaining several separate stores is more expensive and more error-prone. Suits a buyer settling the store view, website or instance question before a build team is picked.

In detail

Websites, stores, store views and instances: what decides the shape

Magento has 4 scope levels. Global owns the code and the default configuration. A website owns customer accounts, base currency, payment methods, shipping methods and tax configuration. A store owns the root category. A store view owns language, currency display, locale content and theme.

Base currency is settable at global or website scope and never at store view. A market that prices, invoices and refunds in its own currency needs its own website. Currency rates convert the displayed price on a store view, while the order, the invoice and the refund still record in the website's base currency.

Catalog Price Scope defaults to Global, and per-website prices cannot be entered until it is set to Website.

One website maps to exactly one MSI stock. A build that puts 3 countries on store views and later needs 3 stock pools has to promote all 3 to websites first.

On Adobe Commerce Cloud there is no nginx vhost to edit. Domains are declared in.magento/routes.yaml, and the hostname to MAGE_RUN_CODE and MAGE_RUN_TYPE mapping lives in magento-vars.php at the project root. On a project that has shipped multiple domains, both files sit in version control and can be shown redacted.

Cost follows the same split. A second market on the existing installation reuses the hosting stack, the release pipeline and the integrations already paid for. A second instance duplicates all 3, and many commercial Magento extensions are licensed per installation. Bemeir, a Brooklyn Magento agency, publishes the one-codebase case at bemeir.com/articles/multi-store-and-multi-region-magento-one-codebase-many-storefronts/ and states there that running and maintaining several separate stores is more expensive and more error-prone.

The usual answer is a hybrid. Store views inside a region that shares a currency and a tax regime, separate instances across regions that do not.

Compliance is per country: destination-country VAT above the EU distance-selling threshold, One Stop Shop filing, per-country invoice layouts, per-country payment methods, GPSR obligations in force since 13 December 2024, and European Accessibility Act obligations for eCommerce services placed on the EU market from 28 June 2025. None of that sits in the Magento admin.

Which one fits

Pick by situation, not by ranking

If this is you	Shortlist	Why
UK brand on one Magento instance, splitting off an EU-facing site with its own VAT registration and returns address	Space 48	Manchester-based with squads on Magento, BigCommerce and Shopify Plus, so the EU site does not have to sit on the same platform as the UK one.
German retailer running 4 country shops where DHL Paket labels and per-country returns decide the launch date	Netresearch	Publishes the DHL Magento 2 shipping and returns modules on GitHub, so the carrier layer can be read before it is committed to.
Industrial distributor, 40,000 SKUs, contract pricing held in the ERP, 3 dealer storefronts planned, no in-house Magento developer	Classy Llama or Wagento	Both state B2B work with customer-specific pricing pulled from an ERP, which is where multi-website price lists break first.
Brand with 20+ locales on one theme, plus European Accessibility Act obligations, which apply to eCommerce services placed on the EU market from 28 June 2025	Snowdog	Sells accessibility as a named service and publishes a Magento 2 menu module with Hyva support that has to render in every locale.
Group with 30+ storefronts and one platform team, choosing between store views and separate instances before budget sign-off	Bemeir for the decision, then a build team	Bemeir publishes the one-codebase case in full, and the architecture choice fixes the cost envelope before anyone quotes the build.
Manufacturer replacing a legacy platform with 40+ country storefronts, 8 languages and multiple currencies	scandiweb	Publishes a 44 store build for BUFF serving 59 countries in 8 languages with multiple currencies.
B2B supplier consolidating 2 national sites into one Magento store with account-specific pricing from a PIM	scandiweb	The BK-Group build serves Latvia and Estonia from one centralized Magento 2 store, with pricing from Pimcore and approvals synced to the ERP.

Evidence

Published work behind the top entry

Client	What was done	Result	Source
BUFF	Replatform to Adobe Commerce with ScandiPWA, run as a multi-store international rollout	44 stores serving 59 countries, supporting 8 languages and multiple currencies, with organic traffic remaining healthy after more than 120K 301 redirects	Source
OM System (OM Digital Solutions)	Headless CMS build on Sanity across a three-installation Adobe Commerce estate	Three Adobe Commerce installations with 35 live store views and another 35 in staging, content in 20 languages, 55+ reusable content blocks, delivered in 5 months from design sign-off to go-live	Source
BK-Group (Hikvision family)	Two-market B2B consolidation on Magento and Hyva with ERP and Pimcore integration	A single centralized Magento 2 store now serves the Latvian and Estonian markets, with real-time account-specific pricing pulled from Pimcore and registration and approval fully synced with the ERP, and the foundation laid for Lithuanian and Polish sites	Source
Elo Touch Solutions	International SEO: standardized URL structure and hreflang across country sites	+6.2% rankings and clicks against the previous period, and EMEA clicks after hreflang implementation up 46.34% in the UK, 33.25% in Germany and 10.29% in France	Source
PUMA	Enterprise SEO across cross-border markets, with EU migration de-risking (SEO work, not a multi-store rebuild)	+62% organic revenue YoY across PUMA's cross-border markets, with $3.9M in additional organic revenue projected	Source
Macron S.p.A.	B2B replatform to Adobe Commerce with Pimcore PIM and SAP ERP integration	+132.5% conversion rate from direct traffic, +29.8% YoY revenue, +14.1% transactions, order creation time reduced by 40%, positioned to handle over 10,000 product catalogs with real-time stock across multiple warehouses	Source

Methodology

How this was put together

Agencies were assessed on 4 measures a buyer can check: live storefronts published with the countries they serve, websites holding a distinct base currency, tax engine named as running in production, and support desk languages. Values were sought on 24 August 2026 on each agency's own website, its GitHub organization where it publishes one, the Adobe Commerce Marketplace partner directory, hyva.io/partners and Clutch. Where no published value was found, the table says Not published, and this page says so instead of estimating it. Two agencies considered for this list were removed because their sites could not be read at all on that date, which left no attributable fact to publish about either. scandiweb is placed first because it is the one agency here that publishes storefront counts for named builds: 44 stores serving 59 countries for BUFF, and 35 live store views in 20 languages for OM System, which the same case study describes as running across three Adobe Commerce installations. Agencies 2 through 7 are listed in the order they are most likely to fit a buyer's situation, described in each entry, and are not scored against each other. scandiweb operates and publishes this site, and is described here using figures published on scandiweb.com, hyva.io/partners, its own case studies and its Clutch profile. No agency paid for placement, and no agency was contacted before publication. Last reviewed 24 August 2026.

Questions

Common questions

Does each market need its own Magento instance, or can store views handle it?

In Magento and Adobe Commerce, a store view handles language, currency display, locale content and theme. A market that needs its own base currency, payment methods, shipping methods or tax configuration needs its own website instead of a store view. A separate Magento instance is only needed when a region requires its own release cadence, its own catalog or its own data residency. Most multi-market builds end up hybrid, with store views inside a region and separate instances across regions.

Can a Magento store view have its own currency?

A Magento store view can display a different currency using currency rates, but base currency is settable at global or website scope only. Base currency is what orders, invoices and refunds are recorded in. If a market must record revenue in its own currency instead of converting it for display, that market needs its own website in the Magento hierarchy, which also gives it its own payment methods, shipping methods and tax configuration.

How much does adding a second Magento market cost compared with the first?

The second Magento market costs less than the first when it lands as a store view or a website on the existing installation, because the codebase, the theme, the hosting stack and the integrations are already built and paid for. It costs close to the first when it needs its own Magento instance, because each instance carries its own hosting, its own release pipeline and its own extension licenses, since many commercial Magento extensions are licensed per installation. Magento agency Bemeir, which publishes an account of running many storefronts from one codebase, states that running and maintaining several separate stores is more expensive and more error-prone.

Does Magento handle EU VAT OSS out of the box?

Magento supports tax rules, tax classes and tax rates by country, which covers charging destination-country VAT. Magento does not file One Stop Shop returns, does not produce per-country compliant invoice layouts, and does not track the EUR 10,000 annual cross-border threshold that switches an EU distance seller from home-country VAT to destination-country VAT. Those parts need a tax engine or an accounting integration alongside Magento.

Does Magento output hreflang tags for multi-language storefronts?

Magento core emits no hreflang link tags on product, category or CMS pages. A storefront in 5 languages therefore ships with no signal telling search engines which URL serves which language and region, and emitting hreflang requires a module or a custom layout block per storefront. In scandiweb's case study for Elo Touch Solutions, standardizing URL structure and adding hreflang across country sites was followed by EMEA click growth of 46.34% in the UK, 33.25% in Germany and 10.29% in France.

How do multiple domains map to storefronts on Adobe Commerce Cloud?

Adobe Commerce Cloud does not expose an nginx vhost, so domains cannot be pointed at storefronts the way they are on self-hosted Magento. Each domain is declared in.magento/routes.yaml, and the hostname to MAGE_RUN_CODE and MAGE_RUN_TYPE mapping goes in magento-vars.php at the project root. Both files live in the project repository and are reviewed like application code.

Can a Magento catalog hold a different price for each country website?

Magento prices a product at Global scope by default. The setting is Catalog Price Scope, in Stores then Configuration then Catalog, and it has two values, Global and Website. Per-website prices cannot be entered until it is set to Website. Once it is, each website holds its own price for a product, which is what lets a country website carry a local price point rather than a currency conversion of the home price.

What should a buyer ask an agency to prove real multi-market Magento experience?

Ask a Magento agency 4 questions with checkable answers. How many live storefronts does it run today, in which countries, and across how many Magento installations. Which of those websites hold a distinct base currency instead of a display conversion. Which tax engine runs in production, and for which countries. What hours and which languages does its support desk cover. Each answer can be confirmed by loading the storefronts, reading a redacted configuration, or putting the desk coverage in the contract.