Catalogue ads in several countries: one catalogue or one per market?
How Meta's country and language feeds localise a catalogue, which fields they can change, and why branded images with prices usually need a catalogue per market.
AI Shopping Feeds Updated
Comparison details were checked against their public websites on 28 October 2026. Products change, so check their current pages before deciding. Corrections: support@aishoppingfeeds.com .
Selling in more than one country adds a question to catalogue ads that doesn’t exist at home: how does a shopper in Ireland see a price in euros while one in the UK sees pounds? Meta has a built-in answer, localised catalogues. It works well for plain product data, and less well for images with prices on them. This post explains both, from Meta’s developer documentation, checked on 28 October 2026.
Option 1: one catalogue, localised
Meta’s localised catalogue feature lets one catalogue hold different details for different countries and languages. In Meta’s words, “Localizing the currency, the price, and the translated title or description are common cases.”
It works through two kinds of extra feed.
Country feeds hold overrides per country. Meta’s setup guide shows an example where the same product has 9.00 GBP and a UK link for GB, and 10.49 EUR and an Italian link for IT.
Language feeds hold translations, such as the title and description in French.
Each override feed needs:
- An
idthat matches an item in your main feed. - An
overridecolumn with the ISO country or language code. - Only the fields you want to change.
Meta is strict about which fields go where. Its supported fields page says price, sale_price, unit_price, base_price, status and availability “must only be provided in a country feed” and can’t go in a language feed. Its setup guide recommends title and description in language feeds, and price, sale price, sale dates, availability and link in country feeds. For catalogues over 100,000 items, Meta says you must create one feed per language or country.
How ads use it
For Advantage+ catalog ads, Meta says the language an ad is shown in is chosen “based on the viewer’s interface language and other signals”, and that it uses the catalogue’s language feed to match. Ad text such as the headline can be given per language in the ad template.
The catch: images
Here’s the detail that matters for branded catalogue ads. Meta’s supported fields page says:
To localize an image, you must use the
image[0].url,image[0].tag[0]nested image fields. Theimage_linkfield isn’t supported for localization.
So if your catalogue’s image_link is a designed image with “£29.00” on it, a country feed can change the price Meta shows in the ad text to euros, but it can’t swap that image for a euro version through image_link. A shopper in Ireland could see a euro price under an image saying pounds.
There are three ways round it:
- Keep prices off the image in a shared catalogue. Use a design with your brand, the product and perhaps a badge, and let Meta show the localised price from the country feed.
- Localise images with nested image fields, if your feed tool can produce a separate image per country and send it as
image[0].urlin each country feed. - Use a catalogue per market, each with its own images and prices.
Option 2: one catalogue per market
The alternative is simpler to reason about: a separate catalogue for each country or currency, each fed by its own feed.
| One localised catalogue | One catalogue per market | |
|---|---|---|
| Setup | Main feed plus country and language feeds | One feed and catalogue per market |
| Prices | Overridden per country | Native in each feed |
| Images with prices | Need nested image fields per country | Each catalogue has its own |
| Pixel matching | One set of IDs | Pixel events must reach the right catalogue |
| Reporting | One catalogue | Split across catalogues |
| Best for | Plain photos, many languages | Branded images with prices, few markets |
The cost of separate catalogues is in the plumbing. Each catalogue needs its own pixel or Conversions API events matched to its IDs, and your ad sets need to target the right country with the right catalogue. If your store uses separate domains or subfolders per market, this often lines up naturally.
Getting the data right in any setup
Whichever option you choose:
- Never convert prices yourself. Use the price you actually charge in each market. A converted price that doesn’t match the checkout is a broken promise and a likely rejection.
- Link to the right site. The
linkfor each country should land on that country’s product page, in its currency. - Check availability per market. A product in stock in the UK warehouse may not ship to Germany.
- Translate properly. Machine-translated titles with mistakes read badly in an ad. At least check the best sellers by hand.
How AI Shopping Feeds fits
In AI Shopping Feeds, each feed has a country, and prices on catalogue images are formatted for that country and its currency, never converted. Feeds are the unit of a market: you set up one feed per country, and each can send products, with its own rendered images, to its own Meta catalogue through our catalogue sync.
That makes the one-catalogue-per-market route straightforward. A feed can also be set as the country version of a main feed in the same Meta catalogue. We then send its prices, sale prices and dates, availability and links as country overrides on the main feed’s items, and its titles and descriptions as language overrides when its language differs. We don’t produce nested image[0].url fields, so the main feed’s images show in every country. If you use one localised catalogue, keep prices off its images.
In the DPA Creative Editor, a design belongs to a feed, and you can save it to your brand’s template library to reuse on each market’s feed, so every market’s images share a layout and differ only in their data.
Frequently asked questions
Can one Meta catalogue show different prices in different countries?
Yes. Meta's localised catalogues use a country feed to override fields such as price, sale_price, availability and link for specific countries, matched to your main feed by id. Translations of title and description go in a separate language feed.
Can I localise catalogue images by country?
Only through nested image fields. Meta's list of supported fields for localised catalogues says image_link isn't supported for localisation, and that you must use image[0].url and image[0].tag[0] instead.
Should I use one catalogue or one per country?
One catalogue with country and language feeds keeps everything together and suits plain product photos. If your catalogue images show prices in a currency, a catalogue per market is usually simpler, because each market's images show its own price.