Client project approval

Shopify Store Consolidation Acknowledgement

Step 1 of 6

Recommended safest route

Use AUS as the main store, then stage UK and US into Markets

The AUS store is the recommended survivor store. Shopify Markets and multicurrency support should be prepared first, then UK data should be migrated while the UK store remains live. UK launches only after QA, and US follows after UK has stabilized.

1

Prepare AUS

Configure Shopify Markets, currency, domains, tax, shipping, locations, and fulfillment routing.

2

Migrate UK

Move UK data into AUS while the current UK store stays live for orders, references, and fallback.

3

Launch UK

Switch UK only after QA confirms checkout, redirects, tax, shipping, payments, and fulfillment.

4

Repeat for US

Use the same proven process for US after UK launch monitoring is complete.

Why not a new store? A new Shopify store would require migrating all three regions, including AUS. If AUS is clean, that adds cost, risk, and disruption without a clear operational benefit.

Important findings

What can be migrated and what cannot be perfectly merged

Shopify data can be consolidated, but Shopify does not provide a true native merge of multiple stores. The points below need to be understood before any live work starts.

Usually migratable

  • Products, variants, images, SKUs, tags, collections, SEO fields, and metafields
  • Customers and customer details
  • Pages, blogs, menus, redirects, and theme content
  • Historical orders through a migration app or API process
  • Some app data, depending on each app vendor

Not perfectly mergeable

  • Customer passwords cannot be transferred
  • UK/US Shopify analytics and traffic history will not merge into AUS analytics
  • Saved reports, admin history, and some app settings cannot be transferred
  • Discounts, gift cards, loyalty, subscriptions, and saved payments need separate review
  • Historical orders cannot be imported through normal Shopify admin CSV import

Project risks that need approval

  • SEO/domain changes can create temporary ranking and indexing volatility.
  • Tax, VAT, GST, duties, and import-tax settings need accountant or tax advisor confirmation.
  • Local currency checkout depends on the AUS store payment provider setup.
  • 3PL routing must be tested by market, stock status, and fallback behavior.
  • Customer communications must explain account reset and regional cutover timing clearly.

Client input

Project answers required before kickoff

These answers define how the consolidation will be planned, estimated, and staged.

Do you approve using AUS as the main survivor store unless discovery finds a blocker?
Do you approve the staged rollout: UK first, monitor, then US?
How should historical UK/US orders be handled?
Preferred domain strategy
Preferred market pricing model
If local stock is unavailable, should orders be allowed to ship from another region?
Are there active liabilities or special datasets that must be preserved?

Readiness checklist

Access and data availability

Confirm what can be provided before kickoff. Any unavailable item becomes a project dependency.

Acknowledgement

Confirm understanding before kickoff

This acknowledgement is an operational project approval record. It is not standalone legal advice and it is not a formal e-signature contract.

Final review

Review and submit acknowledgement

Check the summary below, type your full name exactly as entered, and submit the record.

On submission, the page records the submitted answers, acknowledgement selections, timestamp, browser user agent, country metadata where available, and the IP address available to Cloudflare on the server request.