Build the test matrix first
Build a small test matrix before you begin. Include the countries that matter most, at least one real postal code per destination, a high-volume product, a restricted or unusual product, an in-stock and low-stock variant, and cart values around any free-shipping threshold. Record expected currency, language, catalog, tax display and delivery behavior beside the observed result.
Outcomes can vary by destination address, product, variant, cart value, market, payment and shipping configuration, and customer session. Record all of these with each result.
Step-by-step checklist
Confirm the visitor enters the intended market
Start in a private browser window and use the destination selector or market-specific URL. Check the country, currency and language shown. Repeat without an existing customer session because cookies, prior selections and geolocation can change the experience.
Test representative product availability
Open direct product URLs, collection links and search results. Confirm that products meant for the market are visible and purchasable, and that excluded products fail gracefully instead of appearing available until checkout.
Verify currency and price continuity
Compare product, collection, cart and checkout currency. Check discounts, compare-at prices and rounding. A correct product-page symbol does not prove that checkout will preserve the same currency or price.
Exercise real variants and inventory states
Choose common and edge-case variants. Add them to cart, change quantity and confirm that the selected variant remains sellable for the destination. Product-level availability can hide variant-level restrictions.
Enter a complete destination address
Reach checkout without placing an order. Use a deliverable street, city, region and postal code. Confirm that appropriate shipping options appear, their prices are plausible, and the delivery wording is understandable.
Review tax, duty and total presentation
Note what the storefront says about taxes and duties and what checkout actually itemizes. Treat this as a presentation check, not a legal determination. Test several cart values because thresholds and product classifications can change the result.
Repeat, document and assign failures
Retest on mobile and desktop, then capture the URL, destination, product, variant, cart value, session state and observed evidence for every issue. Retest after each configuration change before opening paid traffic.
Common failure modes
The market is active but the catalog is incomplete
A destination can be selectable while individual products or variants remain unavailable because catalog and publication rules differ.
Currency changes between page and checkout
Market detection, payment configuration, app behavior or a stale session can cause a fallback to the store currency.
Shipping appears only for some carts
Profiles, package assumptions, weight, inventory location, product restrictions, thresholds and the exact postal code can all affect rate eligibility.
A successful test is treated as universal
One product, address and browser session proves only that path. Outcomes can vary by destination address, product, variant, cart value, market, payment or shipping configuration, and customer session.
What the public storefront can—and cannot—prove
Can be observed on a tested public path
- Whether a public product URL loads for the selected market
- Displayed currency and the presence of a sellable variant
- Whether a temporary cart can be created
- Whether a public shipping-rate request returns an option for the tested path
Needs manual, Admin or operational verification
- Shopify Admin market, catalog and payment configuration
- All product and variant combinations
- Final payment authorization or fraud checks
- Every checkout extension, customer account state or post-purchase email
The free scanner is intentionally narrow: it does not claim automatic duties, localization or catalog-wide scanning, and it does not prove every customer journey.
Frequently asked questions
Can I test Shopify Markets without placing an order?
Yes. You can verify much of the public buying path and stop before payment. A real low-value order may still be appropriate for payment, fulfillment, refund and notification QA when your team authorizes it.
How many destinations should I test?
Test every launch market at least once, then give deeper coverage to important countries, risky products and address types. Do not assume two countries inside one multi-country market behave identically.
Does the free scanner prove a market is fully launch-ready?
No. It checks a limited public-storefront path for the selected product and destinations. Use its evidence as one part of the broader manual checklist above.
Related guides
Sources and further reading
This guide paraphrases platform concepts and adds an independent QA workflow. Consult current official documentation and qualified advisers for your configuration.