In this article
  1. Introduction
  2. 1. Confirm which catalog is assigned
  3. 2. Review product availability from the market’s point of view
  4. 3. Verify how each price is calculated
  5. 4. Test the real storefront context
  6. 5. Record exceptions before launch
  7. Saveable preflight checklist
  8. A market launch is a storefront result

Before launching a Shopify market, confirm its assigned catalog, test product availability and final regional prices, preview the storefront on mobile and desktop, and record every intentional exception and owner.

Key takeaways

  • Confirm the market and its assigned catalog.
  • Test included, excluded, variant, sale, and newly added products.
  • Review calculated prices and the customer-visible storefront.
  • Record exceptions, ownership, and the final verification date.

Turning on a new country in Shopify Markets does not guarantee that every customer will see the assortment and prices you expect.

The catalog assigned to a market controls which products are available there and can also control their prices. That makes the catalog the practical bridge between a market configuration and the storefront a customer actually experiences.

Before announcing a new region, run this five-step preflight.

1. Confirm which catalog is assigned

Start in Shopify admin and identify the catalog connected to the target market. Do not assume the default catalog is doing the work.

Write down the market you are launching, the catalog assigned to it, and any submarkets that inherit configuration from a parent market. Inherited settings can make a setup look complete while hiding a regional exception.

2. Review product availability from the market’s point of view

Shopify’s product list includes a View as option for checking a specific market. Use it to see which items are included in the assigned catalog and which are unavailable.

Check more than best sellers. Include one standard product, one product with several variants, one sale item, one newly added product, and one product that should be excluded. This sample catches common assortment mistakes without requiring a full manual review of every item.

3. Verify how each price is calculated

A market price can reflect fixed catalog pricing, percentage adjustments, currency conversion, and other configuration. Inspect the calculated price for your sample products instead of checking only the base price in the product record.

Look for unexpected conversion or rounding, a fixed price that overrides a general adjustment, an incorrect compare-at price, a margin problem after regional pricing, and inconsistent prices across variants.

The operational question is not “Did we configure a price?” It is “Does the customer see the intended offer?”

4. Test the real storefront context

Admin checks are necessary, but they do not replace a storefront review. Preview the target market and inspect the experience as a customer would.

Verify the correct currency and price format, product and variant availability, collection membership and navigation, search and filtering behavior, sale labels and compare-at prices, and shipping or policy messages that mention a region.

Test on both mobile and desktop. A correct catalog can still be presented poorly by theme logic, custom code, or app blocks.

5. Record exceptions before launch

Do not leave exclusions and overrides in someone’s memory. Create a short launch record containing products intentionally unavailable in the market, products with fixed regional prices, known variant exceptions, the person responsible for future catalog updates, and the date of the final storefront check.

This becomes useful when the catalog changes or a new product is added after launch.

Saveable preflight checklist

  • Confirm the market and assigned catalog.

  • Review included and excluded products with View as.

  • Test standard, variant, sale, new, and intentionally excluded products.

  • Inspect final calculated prices and compare-at prices.

  • Preview currency, collections, search, filters, and regional messaging.

  • Check mobile and desktop.

  • Record exceptions, ownership, and the verification date.

A market launch is a storefront result

Shopify Markets gives merchants a flexible way to control regional availability and pricing. The safest launch process checks the outcome of those controls, not just the configuration.

If Appexa is helping with your storefront, we can review how the catalog, theme, filters, and regional messaging come together before customers see the new market.

Frequently asked questions

What should I check before launching a new Shopify market?

Confirm the assigned catalog, test product and variant availability, review final regional prices, preview the customer-facing storefront on mobile and desktop, and document intentional exceptions before launch.

How does a catalog affect a Shopify market?

The catalog assigned to a market determines which products are available there and can also control market-specific pricing. The assigned catalog therefore directly affects what customers can see and buy.

How can I check product availability for a specific Shopify market?

Use Shopify’s market-specific product view to review which products are included or excluded. Test a representative sample that includes a standard product, variants, a sale item, a new item, and an intentionally excluded product.

Why should I preview the storefront after checking Shopify Markets settings?

Admin settings do not show the entire customer experience. A storefront preview helps verify currency formatting, product and variant availability, collections, search, filters, regional messages, and any theme or app behavior.

What catalog exceptions should be documented before launch?

Record intentionally excluded products, fixed regional prices, variant exceptions, the person responsible for future updates, and the date of the final storefront review.

Sources

  1. Creating catalogs for markets
  2. Overview of markets features and concepts
  3. Managing and editing markets
  4. Pricing your products