Launch a New Country Without Forking Your Codebase — Market-Driven Commerce
How Commercefull's market model turns international expansion from an engineering project into a configuration exercise — with a 12-dimension readiness gate before you go live.
October 27, 2026
Ask a team that’s expanded internationally what it cost, and they’ll rarely say “translation.” They’ll say the checkout forked for Germany, the tax module hardcoded for the US, the address form that assumes everyone has a ZIP code. Six months later you’re maintaining three country branches and a spreadsheet of which checkout handles yen.
Commercefull takes a different position: a new country is configuration, not code. The Market aggregate is the boundary — and a readiness gate tells you what’s missing before customers find out.
What a market actually is
A Market binds everything that defines “selling in these countries, under these rules” into one versioned object:
- Selling countries — not one country per market; a market can cover a region
- Currencies and locales — default plus supported sets
- Capabilities —
MarketCapabilitiesdeclares what’s available (returns, BOPIS, etc.) - Commercial bindings — catalog assortment, default price list, contracting entity
- Payment and fulfillment methods — what’s offered in this market
- Hostnames — how the market resolves on the storefront
Stores and channels remain the where and how you sell; markets become the which countries, under what rules. They’re complementary — a store can serve multiple markets, and a market resolves through the channels of its bound store.
The 12-dimension readiness gate
This is the part that turns “we think we’re ready for Belgium” into “we know.”
GET /business/markets/:marketId/readiness audits every dimension — locale, currency, catalog, pricing, tax, payments, shipping, returns, legal, compliance, support, and fraud — and reports each as ready, warning, or missing, with an issues list per gap.
Every gap is data, not code:
- Missing currency? Add exchange rates and store currency support.
- No payment coverage? Add a PSP route covering the country.
- No shipping? Extend a shipping zone’s locations and bind a rate.
- Compliance gap? Author policy rules — GDPR/CCPA/LGPD/APPI jurisdiction derives automatically from country groups.
POST /business/markets/:marketId/launch gates on the report — a blocking missing dimension rejects the launch with the failing list instead of letting you discover the gap in production. On success the market goes ready → active and its version is snapshotted onto every order for historical replay.
When code IS genuinely required
Honesty check: not everything is configuration. A market that needs a PSP rail you’ve never integrated, or a domestic carrier API with no adapter, still requires an implementation. But it lands behind the existing ports — a payment gateway adapter, a carrier adapter, a TaxEnginePort implementation — not as a fork in the checkout. The country logic doesn’t leak into the platform.
The payoff over three expansions
The first market takes real configuration work: zones, rates, routes, rules. The second is faster — you reuse shipping lanes, PSP routes, and policy groups. By the third, market launch is an afternoon of admin work and a readiness report review, not a release train.
That’s the point of the architecture. Not “launch 190 countries day one” — but the hundredth launch should look like the fifth, because nothing accumulates as country branches.
Read more
- From One Store to Global Markets — the staged expansion model
- Market Launch Guide — the full draft → readiness → launch procedure
- Stores & Markets module docs
Ready to own your store?
Commercefull is free, open-source, and Apache-2.0 licensed. Every module, every line, every row of data — yours.