A global Shopify setup should follow the commercial and operational differences between countries. Use one store with Markets when catalogue, operations and governance can remain substantially shared; use multiple stores when legal entities, catalogues, pricing, teams, integrations or experiences require real separation. Architecture should precede localisation.
Why this decision matters
The visible product or tactic is only one part of the operating system. The real decision includes people, workflow, data, integrations, governance, failure recovery and measurement. A technically possible route can still be commercially weak if it creates manual reconciliation, review burden, unclear ownership or a poor customer experience.
Start by naming the accountable business owner and the outcome the organisation expects. Record the present baseline and the conditions under which the decision will be revisited. This prevents feature enthusiasm from becoming an unmeasured long-term dependency.
The wrong way to evaluate it
Do not begin with a pricing table, demo or isolated traffic metric. Vendor pages describe capabilities, not the organisation’s implementation. Do not compare options using different data, easier scenarios or unequal expert support. Do not assume more automation, messages, events or features automatically create more value.
The evaluation should expose difficult states: invalid input, incomplete data, refunds, failures, permissions, multiple markets, review exceptions and handoff to another team. The deciding constraint usually appears outside the happy path.
Decision scorecard
Score business fit, user workflow, data and integration, security and privacy, performance, governance, support, portability, commercial model and internal ownership. Weight the criteria. A mandatory regulatory, checkout or data requirement should not be averaged away by several minor conveniences.
Require evidence for every high-weight score. Evidence can be an official capability, controlled test, architecture review or signed operational commitment. Treat unverified assumptions as risks, not as benefits.
Implementation deep dive
Market model
Define which countries are true launch markets, expected demand, entity and settlement requirements and customer promise. Do not activate dozens of markets without operational readiness.
Store architecture
Choose single versus multi-store using shared-data and governance criteria. Document product, customer, order, inventory and content ownership.
Localisation
Implement domains or subfolders, language, currency, pricing, payment methods, duties, tax, shipping, return policy and support. Translation alone is not localisation.
Search and analytics
Use unique accessible URLs, correct canonicals and hreflang where variants exist. Separate market reporting while preserving a reconciled global view.
Launch
Pilot a market with representative orders, refunds, returns and service cases. Monitor margin and operational exceptions before scaling acquisition.
Representative pilot
Use this production-like scenario: map two priority countries across entity, catalogue, currency, pricing, tax and duties, payments, language, domain, inventory, fulfilment, returns, support and data. Freeze the inputs, acceptance criteria and measurement method before testing. Record all manual interventions and expert corrections because they represent future operating cost.
Measure conversion by market, landed-price accuracy, fulfilment performance, return cost, localisation defects, reconciliation effort and operating ownership. Add quality and risk observations next to numerical results. A faster workflow is not a win when it causes more defects, complaints, support work or financial reconciliation.
Architecture and data
Map every system, event, identifier, data owner and transfer. Decide which platform is authoritative for each record. Document how duplicates, delayed events, retries and partial failures are resolved. Avoid storing sensitive or unnecessary data merely because the product makes collection easy.
Where APIs or webhooks are involved, use authentication, signature verification, idempotency, event replay and observable state transitions. Where content or campaigns are involved, preserve version, source, approval and attribution records.
Governance
Define administrators, editors, reviewers, service owners and escalation paths. Apply least privilege, separate production and test access, protect secrets and document material configuration. Review the exact plan, region and setup; generic provider assurances do not replace deployment-specific assessment.
Create change control for pricing, tax, policy, platform, market or model updates that could invalidate the decision. Assign a recurring review owner instead of relying on the original implementer’s memory.
Commercial model
Model one-time implementation, migration, configuration, training and QA separately from recurring subscription, processing, app, infrastructure, support and staff effort. Include the cost of errors, abandoned processes and exit. Use current official commercial terms at the decision date and the organisation’s actual usage assumptions.
Do not publish a universal cheapest option. Commercial suitability changes with order mix, customer geography, transaction pattern, team capability and support needs.
Project Supply can translate this decision into an implementation and measurement plan. Explore Ecommerce Development: Project Supply service overview or discuss the project at Contact Project Supply.
90-day execution plan
Days 1–15: document requirements, baseline, owner, data boundaries and failure cases.
Days 16–30: run the representative pilot and close high-risk unknowns.
Days 31–60: implement integrations, content or code, permissions, QA, training and rollback.
Days 61–90: measure production outcomes, remove avoidable complexity and decide whether to scale.
Measurement
Build a balanced scorecard across outcome, quality, cycle time, variable cost, rework, adoption, policy exceptions and customer impact. Establish a baseline before rollout and document attribution limitations.
Review leading signals weekly during rollout and commercial outcomes after a meaningful operating window. Stop or redesign when observed results contradict the business case.
What not to do
Do not automate an unclear process, launch to every user at once, suppress negative evidence, or preserve an unsuccessful setup because migration has already consumed effort. Sunk cost is history. A professional decision remains reversible and evidence-led.
Do not let a tool define policy, customer promise or data ownership. Technology should enforce an intentional operating model, not quietly become one.
Project Supply can translate this decision into an implementation and measurement plan. Explore Ecommerce Development: Project Supply service overview or discuss the project at Contact Project Supply.
Multi-country commerce architecture
Choose the market operating model
Decide which countries share catalogue, inventory, legal entity, fulfilment, support and merchandising. Shopify Markets can coordinate international experiences, but it does not remove operational differences. Define who owns prices, translations, duties, returns and local campaigns. Split stores only when governance, catalogue or system boundaries justify the added duplication.
Design URLs and localisation
Use a consistent country or language URL structure and ensure every version is crawlable and self-consistent. Implement canonical and hreflang signals carefully, provide visible market switching and avoid automatic redirects that block users or crawlers from alternatives. Translate intent and commercial context, not only interface strings; local search demand and product terminology may differ.
Model price, tax and duty experience
Define how base prices, currency conversion, rounding, local price lists, taxes, duties, shipping and returns are presented. Verify current platform and partner capabilities for each market. Test the amount customers see from product page through checkout and refund. Unexpected landed cost damages conversion and support even when the checkout is technically valid.
Integrate fulfilment and inventory
Map locations, sellable inventory, routing, delivery promises, carrier services, cancellations and reverse logistics. Use representative cross-border and local orders during testing. Confirm how the ERP, warehouse, customer service and analytics interpret market and currency. A global storefront fails when downstream systems cannot fulfil or reconcile the promise shown online.
Launch market by market
Begin with one representative market, a controlled catalogue and measurable demand. Validate localisation, search indexing, checkout, payment, fulfilment, customer communications, analytics and support before expansion. Track contribution margin, conversion, delivery reliability, returns and service contacts by market. Use evidence to decide whether the next market should reuse or change the operating model.
Decision workshop and acceptance gate
Representative production scenario
Use a merchant launching one new country with local currency, translated content, cross-border fulfilment and market-specific returns. Write the starting state, expected outcome, user roles, data involved, dependencies and time boundary. Preserve failed attempts and manual interventions, because they reveal the operating effort that a polished demonstration hides. The scenario must be difficult enough to exercise the deciding constraint but small enough to repeat after configuration or implementation changes.
Cross-functional review
Include commerce, finance, tax advisers, fulfilment, customer service, SEO and engineering. Ask each participant to score immediate usability, long-term ownership, risk and measurable value. Differences in scoring are evidence, not noise: they show where one team receives the benefit while another inherits administration, review or failure recovery. Resolve material disagreements in the decision memo rather than allowing them to surface after launch.
Acceptance evidence
Require market configuration, crawl and hreflang checks, end-to-end orders, landed-cost review, inventory routing, refunds and market-level margin reporting. Define pass, conditional pass and fail before testing. Name who adjudicates ambiguous results and prevent the team from moving the success threshold after seeing which option performs better. Keep evidence with the implementation record so future owners can understand the original assumptions and repeat the test when conditions change.
Failure and recovery
Explicitly simulate incorrect localisation, unexpected duties, overselling, broken redirects, unfulfilled delivery promises or fragmented data across systems. For each failure, define detection, customer impact, escalation owner, containment, recovery and communication. A route is not production-ready merely because the happy path works. Recovery must be possible with the people, access and documentation available during real operating hours, not only with the original implementation specialist present.
Ninety-day governance
During the first 30 days, validate configuration and resolve high-severity defects. During days 31–60, compare real outcomes with the baseline and remove unnecessary manual work. During days 61–90, decide whether to scale, redesign or exit. Record the owner, measurement cadence, next review date and triggers that require an earlier review.
Executive decision memo
Conclude the multi-country Shopify architecture work with a short decision record that states the chosen route, rejected alternatives, evidence, assumptions, unresolved risks, accountable owner, implementation boundary, success measures, review date and exit trigger. Include the source versions or access dates behind time-sensitive claims. The memo should distinguish verified facts from internal estimates and recommendations. It should also describe what would change the decision—for example, a material vendor capability change, a different customer mix, new policy requirements, unacceptable operating effort or results outside the agreed tolerance. This record prevents the organisation from repeating the same discovery and gives future teams a defensible basis for scaling, redesigning or replacing the implementation.
