Multi-country and multi-language feeds
How target countries, languages, currency and feed labels combine in Merchant Center, when one feed covers many markets and when you genuinely need separate feeds.
Selling into several countries or languages means telling Merchant Center which market each product is for, in which language, and which currency. Often a single feed with the right country and language targeting covers everything. You only need separate feeds when the actual product data differs by market, translated titles, local prices, or country-specific availability.
The three things a market needs
To serve a product into a given market, Merchant Center has to know three things:
- Target country: where the product is sold and shipped. It governs which policies, shipping and tax settings apply, and which currencies are valid.
- Content language: the language of the product's titles, descriptions and other text. It must be a language supported for the target country.
- Currency: carried on the
priceattribute (andsale_price), and it must be a currency valid for the target country.
A single data source can carry a target country and language, and can target more than one country. The question is never "do I need separate feeds" in the abstract: it's whether the product data itself differs across the markets you're targeting.
When one feed is enough
One feed covers multiple markets cleanly when the data is effectively the same:
- Same language across countries: one English feed targeting the UK, Ireland and Australia, for example, where titles and descriptions read the same.
- A currency those countries share or accept: or prices that are valid across the targeted set.
- No market-specific attributes: availability, shipping and identifiers don't diverge by country.
Here you set the feed's target country/language, optionally add more target countries, and let shipping and tax settings handle the per-country specifics.
When you genuinely need separate feeds
Split when the data differs, not just the market:
| Difference | Why one feed can't hold it |
|---|---|
| Translated titles/descriptions | The same id can't carry two languages of the same text field |
| Market-specific prices in different currencies | price carries one currency; different local prices need different rows |
| Country-specific availability or exclusions | A product in stock in one market and not another needs distinct data |
| Different product ranges per country | Products that only exist in some markets |
The rule of thumb: language and price are the usual triggers. If a product needs a German title and a euro price for Germany and an English title and pound price for the UK, that's two content languages and two prices: two feeds (or a primary plus a supplemental that overrides the market-specific attributes).
Deep dive Labels, IDs, and the localisation matrix
Once you're past a single market, three mechanics decide whether the setup stays sane:
- Feed label is your organisational spine. A feed label is a free-text tag on a data source, independent of country, that you use to target campaigns and segment products in Google Ads. Two feeds targeting different markets get different labels so a UK campaign and a DE campaign can each point at the right catalog. Label deliberately from day one: retrofitting labels across live campaigns is painful.
idis shared across languages, distinct across true variants. For the same product sold in two languages, keep the sameidacross the country/language feeds: Google understands them as the same offer localised, which pools signal rather than splitting it. Don't mint a freshidper country for what is genuinely one product; do keepids distinct for products that are actually different SKUs.- Supplemental feeds shine for the delta. When markets share most data and differ only in a few attributes (a translated title here, a local price there) a primary feed plus a supplemental feed that overrides just the market-specific columns by
idis cleaner than duplicating the whole catalog per country. You maintain one base and thin per-market patches. - Currency and country must agree. A
pricecurrency that isn't valid for the target country is a hard rejection, not a warning. When one feed targets several countries, either the currency is accepted across all of them, or you supply per-market prices so each country resolves to a valid currency.
The localisation matrix (countries × languages × currencies) grows fast, and the failure mode is duplication: five near-identical full feeds that drift apart the first time someone edits one and forgets the others. Keep one base of truth, express per-market differences as the smallest possible delta, and let labels and shared ids hold the whole thing together. Where the per-market data is generated rather than hand-maintained, produce it in a layer that outputs each market's feed from a single source: so a title fix propagates to every language instead of being re-done four times.
A quick decision guide
- Same language, compatible currency, same products → one feed, multiple target countries.
- Different language OR different currency → separate feed per language/currency, or a primary plus supplemental overriding the delta.
- Different product ranges per country → separate feeds, labelled per market.
For how each of these feeds actually reaches Merchant Center, see feed delivery methods; for the attributes involved, the product data spec overview.
Frequently asked questions
Do I need a separate feed for every country I sell to?
No. If the product data is identical bar the market, same titles, same currency handling, one feed with multiple target countries covers it. You only split feeds when the data genuinely differs per market, such as translated content or country-specific prices.
What decides which currency a product shows in?
The price attribute carries its own currency code, and it must match a currency valid for the target country. A feed targeting several countries either uses a currency each of those countries accepts, or supplies market-specific prices so each country sees its own.
What's a feed label for?
A feed label is a free-text tag on a data source that lets you target campaigns and organise products by feed, independently of country. It's how you keep, say, a UK feed and an EU feed distinct in Google Ads even when both are live.