Multi-region commerce without multiplying your codebase
One catalog, region-scoped pricing. The pattern behind a recent build.
Every new market should not mean a new codebase. Yet that is exactly what happens when teams treat each region as a separate project - a forked theme, a duplicated CMS, a pricing spreadsheet that lives in someone's inbox. We recently shipped a multi-region commerce build on a single Medusa backend, and the pattern is worth writing down because it is simpler than most proposals make it sound.
One catalog. Region-scoped pricing, tax, and fulfillment rules. One admin the ops team actually learns. When the client opened their fourth market, the work was measured in days - not the six-week rebuild their previous agency quoted.
The anti-pattern we see constantly
Teams multiply stores instead of multiplying regions. Each country gets its own Shopify instance, its own Webflow site, its own set of apps that never quite agree on product data. Launching market five means hiring someone whose job is reconciliation. That person becomes the most expensive line item in the P&L, and nobody planned for it.
Multi-region is a data problem dressed up as a frontend problem. Solve the data layer first.
We design regions as first-class citizens in the backend - not as afterthought filters on a single global price. Currency, tax, shipping zones, and localized content all hang off a region ID. The storefront reads region context at the edge and renders accordingly. No duplicate deployments.
What this looks like in practice
Product data lives once. Marketing pages pull localized copy from a CMS keyed by region. Checkout adapts payment methods per market without forking the flow. When the client asks for a fifth country next quarter, we add a region config and translate - we do not clone the repo. That is how you scale commerce without multiplying your codebase.
When should you break a CMS collection into multiple?
When two kinds of content genuinely have different fields and different places they get used — not just because one has slightly more variety.
How do you handle nested references in Webflow?
Keep references to one hop wherever possible. If you find yourself needing two hops to render a single field, flatten the second collection into the first.
Do CMS items count toward site plan limits?
Yes — every collection item counts toward your CMS item limit regardless of whether it renders a page.
Enjoyed this? We build the systems we write about.
Fixed monthly retainers on Webflow and Medusa JS — by the same people who wrote this.