Skip to content
Magento Multi-Store Specialist

Magento multi-store without the maintenance hell

Most multi-store Magento setups work, but they are painful to run. I do Magento multi-store development with the long run in mind: a shared catalog, per-store overrides, one deploy for every storefront, and regional compliance set up from the start.

  • Hreflang done right: server-rendered, validated on every deploy
  • Per-store payment + shipping (iDEAL, Klarna, BACS, Razorpay)
  • GDPR / CCPA / LGPD scoped per store-view, not site-wide
Fixed written quote 12+ multi-store deployments shipped
  • 12+ Multi-store deployments

    From 2-store EU and UK setups to 30-store global rollouts. One Magento backend, several branded storefronts.

  • 8 Currencies handled

    Live FX feeds, segment pricing and regional payment gateways, like iDEAL for the Netherlands and BACS for the UK.

  • 6 Languages supported

    A translation pipeline, hreflang and locale-specific structured data, set up so search engines index each storefront correctly.

  • GDPR+ compliance per region

    Cookie consent, data residency and right-to-be-forgotten, configured per store view instead of site-wide.

What you get

Six things every multi-store Magento should ship with

The number of storefronts matters less than these six. They decide whether your team can run the setup day to day without calling a developer.

  • Store / website hierarchy done right

    Website, store and store view configuration that still makes sense at store number ten. Shared admin, separate carts where needed, and catalog and config inheritance you can predict.

  • Multi-currency without manual price entry

    Live FX rates from ECB or OpenExchangeRates, rounding rules per currency, customer-group price overrides. Nobody uploads price CSVs.

  • Multi-language with proper hreflang

    A translation memory pipeline, locale-aware structured data, and hreflang checked automatically. I’ve cleaned up the same hreflang mistakes 100×, so the setup blocks them from day one.

  • Per-store payment + shipping

    iDEAL for NL, Klarna for DE, BACS for UK, Sofort for AT, Razorpay for IN. Each storefront shows only the methods that work in its region.

  • Compliance per region

    GDPR for the EU and UK, CCPA for the US, LGPD for Brazil, PIPEDA for Canada. Cookie consent and data residency are set per store view, not site-wide.

  • Shared catalog with per-store overrides

    One product master with per-store name, description, price and category placement. Edit once and it applies everywhere, with overrides only where a store needs them.

How it works

Five steps from architecture to live

You can review on staging daily from week two. I launch one storefront at a time so each region gets my full attention.

  1. 01

    Brief & quote

    You send a short brief on WhatsApp: your stores, regions, languages and currencies, or the setup you plan to launch. I reply with a fixed written quote: scope, price and timeline. Once you approve it, I book the slot.

    Step 1
  2. 02

    Architecture audit & plan

    Inside the approved engagement I review your current multi-store setup, or plan a new one if you haven’t launched. I map websites, stores and views, find settings leaking between them, and check payment and shipping per region. You get a written report, a diagram of the target setup and, for a live multi-store, the migration plan.

    Days 1-6
  3. 03

    Build & configure

    Store hierarchy, currencies, languages, hreflang, payment and shipping per region, and compliance per store view. You can review progress on staging every day.

    Weeks 2-8
  4. 04

    Localise

    Translations through Crowdin, Phrase or manual files. Locale-aware structured data and an SEO check per region. A crawl before and after confirms hreflang is correct.

    Weeks 6-10
  5. 05

    Launch & stabilise

    Rollout one store at a time if you want it. The cutover time and the rollback plan are agreed with you in writing before launch. 30 days of post-launch cover, and an optional retainer for ongoing localisation.

    Weeks 10-12

Your quote

Get a fixed quote for your project

Send your store URL and describe what you want to change. We can review the requirements and agree a written scope, quote and timeline before work starts.

  • Written scope, price and timeline
  • You approve every change
Book your slot

Reserve your multi-store project slot

Send me a short WhatsApp message. I reply with a fixed written quote: scope, price and timeline.

Message me on WhatsApp

No form to fill. Send me a quick message. I reply during 10 AM to 7 PM IST, Monday to Saturday.

Helpful to mention

  • Company
  • Current state
  • Planned storefronts
  • Target regions
  • Currencies needed
  • Languages needed

These are already in the message for you. Just add your answers.

Message me on WhatsApp

Or save my number: +91 84012 70422

What clients say

Multi-store builds I’ve already shipped

Client reviews are public on my Top Rated Plus Upwork profile.

What Our Customers Say

Fantastic person, very knowledgeable, honest and reliable.

“Fantastic person, very knowledgeable, honest and reliable. Sorted out my issue within an hour! I cannot wait for the next project to work with Kishan

SZ

S. Z.

Kishan- I appreciate your expertise.

“Kishan- I appreciate your expertise. Your work was timely and complete. When I have this task again, I will definitely hire you. Thank you so

JB

J. B.

I had the pleasure of working with Kishan Savaliya on our Magento 2 project, and I was thoroughly impressed with his work.

“I had the pleasure of working with Kishan Savaliya on our Magento 2 project, and I was thoroughly impressed with his work. Kishan is not just a Magento developer, he is a true professional who sets a high standard with his top-notch technical skills. His task was to install a...

MM

M. M.

Kishan was very helpful in helping set up my magento site, theme, installing my extensions, and fix any errors.

“Kishan was very helpful in helping set up my magento site, theme, installing my extensions, and fix any errors. He is very trustworthy and I highly recommend hiring

SE

S. E.

Great from start to finish, Kishan has went above and beyond, helping at all hours of the day.

“Great from start to finish, Kishan has went above and beyond, helping at all hours of the day. I would highly recommend him, and will always consider him for future

YA

Y. A.

CEO

I am very grateful to have found Kishan.

“I am very grateful to have found Kishan. He has helped me tremendously through the process of creating my ecommerce site. I was completely lost and ignorant. He guided me and completely helped me set up magento 2. He was patient with me and is very trustworthy. If and when the...

SE

S. E.

Trusted by stores in

  • United States
  • United Kingdom
  • Canada
  • Australia
  • Germany
  • France
  • Netherlands
  • India
FAQ

Honest answers to the multi-store questions everyone asks

When should I use Magento multi-store vs separate Magento installs?

Use multi-store when your storefronts share most of the catalog, customer base, or admin operations, you get one upgrade, one extension stack, one hosting bill, and surgical per-store overrides where needed. Use separate installs when storefronts are run by different teams, have totally distinct catalogs, or need fundamentally different stacks (e.g. one Hyvä, one Luma headless). 90% of cases we see are multi-store wins, the maintenance and SEO consolidation alone usually justify it.

What's the difference between websites, stores, and store views in Magento?

Magento has three scopes:

  • Website, isolation boundary for customers, carts, orders and (by default) prices. Use one website per legal entity / region with separate carts.
  • Store, root-category boundary. Use multiple stores per website when you need different catalog trees (e.g. brand A vs brand B sharing a checkout).
  • Store view, locale boundary. Use one per language inside the same store (e.g. EN, FR, DE views of the EU store).

Wrong-scope configuration is the #1 source of multi-store pain. We map the hierarchy in the audit before any code is written.

How does multi-currency work in Magento?

Magento supports multiple currencies natively. We typically wire it up like this: (1) Allowed currencies set per website. (2) Live FX feed (ECB, OpenExchangeRates, fixer.io) with cron import every hour. (3) Per-currency rounding rules and price-display formatting per locale. (4) Optional fixed prices in customer-group + website scope to avoid FX drift on premium SKUs. Customers see only the currency for their region; admins see all currencies side-by-side in reports.

How do I do hreflang for a multi-store Magento setup?

Three rules: (1) Every URL must reference every other locale variant of itself, including a self-reference. (2) Each variant must point back, bidirectional. (3) Always include x-default. We generate hreflang server-side per URL (not via JS), validate it on every deploy with Screaming Frog, and emit it on canonical URLs only. Common foot-guns we prevent: hreflang on non-canonical URLs, region-only tags without language, and hreflang loops between cross-linked storefronts.

Can I share customers across stores or keep them separate?

Both. Magento has a customer account scope setting (Stores > Configuration > Customers > Account Sharing Options): set to Global for one account across all websites, or Per Website to isolate. Most multi-region setups want per-website isolation (so a UK customer can’t accidentally order at US prices), while same-language sibling stores often share globally. Switching this setting after launch is painful, we always decide it upfront in the audit.

Will multi-store make my Magento slower?

Done right, no. The Magento application is shared in memory; each store view just changes what gets rendered. Done wrong, with bloated core_config_data, runaway URL rewrites per store, or unscoped extension queries, multi-store can be measurably slower. We size Redis + Varnish for the storefront count, scope every config to the right level, and load-test each store view separately before launch. We commit Lighthouse 90+ on every storefront, regardless of count.

How do I handle different payment methods per region?

Payment method config is scoped per website. We typically enable: iDEAL + Bancontact for NL/BE, Klarna + Sofort for DE/AT, BACS + Worldpay for UK, Stripe + Apple Pay + Google Pay for US/CA, Razorpay + UPI for IN, plus PayPal as a global fallback. Each website only exposes payment methods that work for its region, customers never see options that will fail at gateway.

Can I have different prices per country / currency?

Yes, three layers of control: (1) Catalog price scope set to Website, so each website can have its own price list. (2) Customer-group pricing for tier-based discounts (B2B, VIP, etc.). (3) Cart price rules per website for region-specific promotions. We can also import region-specific price CSVs nightly from your ERP if you have a master pricing system. Tax-inclusive (EU/UK) vs tax-exclusive (US) display is handled at the same scope.

How does GDPR / CCPA / LGPD compliance work per region?

Each regulation has different requirements, we configure them per store-view, not site-wide. GDPR (EU + UK): explicit cookie consent before any tracking, right-to-be-forgotten endpoint, data-export request flow. CCPA (California): “Do Not Sell My Personal Information” link, opt-out by default. LGPD (Brazil): explicit consent + DPO contact in footer. PIPEDA (Canada): less invasive, but still requires consent for marketing. We use scoped cookie-consent extensions that auto-detect the visitor region, and integrate with your CRM for unified data-subject-access requests.

Can different storefronts have totally different designs?

Yes. Theme assignment is scoped per store-view, so each storefront can have its own theme, logo, colour palette, fonts, header, footer, even checkout layout. Most clients use one parent theme with per-storefront skins (cheaper to maintain, faster to build, easier to upgrade). For radically different brands, e.g. a luxury sub-brand vs a discount sub-brand on the same backend, we deploy fully separate themes with shared core blocks. Hyvä supports this pattern natively.

Can I do B2B differently per region?

Yes, Adobe Commerce B2B (companies, quote workflow, requisition lists, customer-specific pricing, Net-30 / Net-60 payment terms) is scoped per website. So you can run B2C in the US, B2B in DE, and a hybrid B2B+B2C in the UK off the same backend. Each region can have its own sales reps, quote approval flow, payment terms and ERP integration. Salesforce / HubSpot / NetSuite integrations can also route per region. (Note: B2B requires Adobe Commerce, not Open Source.)

What's the maintenance burden of a multi-store Magento?

Lower than running N separate Magentos, that’s the point. (1) One upgrade applies to all storefronts. (2) One extension stack to license & maintain. (3) One hosting bill (provided you sized it for the storefront count). (4) One admin login for your ops team. The catch: set up wrong, multi-store can become an n-by-n compatibility matrix every time you change something. That’s why we audit + diagram + scope-test before any code goes live, and bake regression tests for each storefront into the deploy pipeline. 30 days post-launch + retainer covers ongoing localisation.

Kishan Savaliya Online 10 AM to 7 PM IST Chat on WhatsApp