Why Multi-Market Feeds Are Different from Single-Market Feeds

Selling internationally through Shopify Markets means your products need to appear in local Google Shopping results across multiple countries. Each country has its own Google Merchant Center account (or sub-account in a multi-client setup), its own language requirements, its own currency, and its own product data specifications. A single English-language feed with USD pricing won't work for your German, French, or Japanese customers.

The complexity isn't just translation — it's a fundamentally different data pipeline for each market. Product titles need to be in the local language. Prices must be in the local currency with correct tax handling. Landing page URLs must point to the localized version of your store. Shipping information must reflect local delivery options and costs. And regulatory requirements (energy labels, warranty information, product safety certifications) vary by market.

Shopify Markets and the Translations API

Shopify Markets provides the foundation for multi-country selling. Each market can have its own language, currency, and domain or subfolder structure. The Translations API (or Shopify Translate & Adapt app) stores localized versions of product titles, descriptions, and other content alongside the primary (default) language.

How Translations Work in Shopify

When you create a translation for a product, Shopify stores it as a resource translation linked to the original product. The translation includes the locale code (e.g., de for German, fr for French, ja for Japanese) and the translated content for each field. Your feed generation pipeline needs to query these translations and use the correct localized content for each market's feed.

Use the translatable resources GraphQL query to retrieve translations for products, variants, and collections. For each market feed, resolve the product title and description in the target language. If a translation doesn't exist for a specific product, fall back to the default language — but flag these gaps so your localization team can prioritize them.

Currency and Price Localization

Shopify Markets handles currency conversion automatically based on your pricing strategy. You can use automatic exchange rates (Shopify converts from your store currency in real-time), manual exchange rates (you set fixed rates per currency), or market-specific prices (you set explicit prices for each market, independent of exchange rates).

For product feeds, you need to pull the market-resolved price — the price your customer actually sees on the localized storefront. Use the contextualPricing GraphQL query with the target market's context to get the correct local price. Never calculate the price yourself using exchange rates, because Shopify may apply rounding rules, price adjustments, or market-specific overrides that change the final number.

Feed Architecture: One Feed Per Market

The cleanest architecture is one feed per market, each configured for the target country's Merchant Center account. Each feed contains the same products but with localized attributes.

Per-Market Feed Configuration

For each market feed, configure: Language: The primary language of the target market (de for Germany, fr for France). Currency: The market's local currency (EUR, GBP, JPY). Landing page URLs: Must point to the localized version of your store. If you use subfolders (store.com/de/), append the locale prefix to all product URLs. If you use country-specific domains (store.de), use the market's domain. Shipping: Local shipping rates and delivery estimates for the target country. Tax handling: Some markets require tax-inclusive pricing in feeds (most of Europe), while others use tax-exclusive (US, Canada).

URL Structure and Hreflang

Google needs to crawl the landing page that matches your feed's language and currency. If your feed says the product costs 49.99 EUR and the title is in German, the landing page URL must show 49.99 EUR with German content. Mismatches between feed data and landing page content cause disapprovals.

Ensure your Shopify Markets configuration includes proper hreflang tags on your product pages. These tags tell Google which language and country each URL version serves. Shopify generates these automatically when Markets is configured correctly, but verify them — missing or incorrect hreflang tags cause Google to index the wrong version of your pages, undermining your localized feed efforts.

Managing Google Merchant Center for Multiple Markets

Google offers two approaches for multi-country feeds: a Multi-Client Center (MCC) account with separate sub-accounts per country, or a single Merchant Center account with multi-country feeds.

Multi-Client Center Approach

An MCC gives each country its own Merchant Center sub-account. This provides clean separation — each country has its own feed, its own diagnostics, and its own performance data. It's easier to troubleshoot issues because disapprovals in one country don't affect others. The downside is management overhead: you're maintaining multiple accounts, each with its own settings.

Single Account with Feed Rules

Google also supports submitting multiple feeds to a single Merchant Center account, each targeting a different country and language. You specify the target country and language when creating the feed. This is simpler to manage but makes diagnostics harder — when products are disapproved, you need to determine which country's requirements are failing.

Common Multi-Market Feed Errors

Price and Currency Mismatches

The most common error: your feed shows EUR prices but the landing page displays USD (or vice versa). This happens when the feed pulls prices from the wrong market context, or when the landing page URL doesn't include the locale parameter that triggers Shopify's currency switching. Always verify that the feed price, feed currency, and landing page displayed price all match exactly.

Language Mismatches

Google checks that the feed language matches the landing page language. If your feed contains German titles but the landing page defaults to English because the URL doesn't trigger the German locale, the product gets disapproved. Test each market's URLs in an incognito browser to verify the correct language renders.

Missing Translations

If you submit a German feed but 30% of your products don't have German translations, those products show English titles in a German feed — which Google will disapprove. Implement a translation coverage check in your feed pipeline: before including a product in a market feed, verify that translations exist for all required fields. Products without translations should either be excluded from that market's feed or flagged for urgent localization.

Shipping Configuration by Country

Each market feed needs accurate local shipping information. Your US shipping rates don't apply to your UK feed. Configure shipping either in each Merchant Center sub-account (recommended) or include country-specific shipping attributes in each feed. Don't forget to account for duties and import taxes for markets where customers expect landed-cost pricing.

Scaling Feed Management Across Markets

Managing 2-3 market feeds is feasible manually. Managing 10+ markets requires automation. Key principles for scalable multi-market feed management include treating your default language feed as the template (all other feeds are generated by applying translations and market-specific pricing to this base), automating translation coverage reporting so you know which products are missing translations per market, building market-specific rules for attributes that vary by country (tax handling, shipping data, regulatory attributes), and monitoring disapproval rates per market to catch country-specific issues quickly.

How Galantis Connect Handles Multi-Market Feeds

Galantis Connect generates market-specific feeds automatically from your Shopify Markets configuration. The platform queries the Translations API for localized product data and the contextual pricing API for market-resolved prices, assembling complete localized feeds without manual configuration per market.

The visual field mapping interface includes market-aware selectors — map the German title to the feed title for your DE feed, the French title for your FR feed, and so on. Market-specific rules handle the differences between countries: "if market = DE, set tax_handling to 'gross'" or "if market = UK, append '/en-gb/' to all product URLs."

Translation coverage dashboards show you which products are missing translations per market, so you can prioritize localization work. Products below your coverage threshold are automatically excluded from market feeds to prevent language mismatch disapprovals. And channel-specific overrides let you customize feed attributes per market without duplicating your entire feed configuration.

Getting Started with Multi-Market Feeds

Start with your highest-revenue international market. Configure a single localized feed, verify it passes Merchant Center validation, and monitor performance for 2-4 weeks before adding additional markets. Focus on translation coverage first — a feed with 90%+ translated products in the correct currency will outperform a feed covering more markets with spotty translations.

Ready to generate localized feeds for every Shopify Market automatically? Galantis Connect pulls translations, market pricing, and localized URLs to build per-country feeds with zero manual duplication. See how it works at galantis.io.