How to organize a multi-country product feed without mixing currencies, language or stock
A beginner-friendly guide to separating markets, localizing prices and publishing cleaner feeds when you sell across countries.
Julia Villegas

A multi-country product feed helps you sell across markets without mixing language, currency, price, stock or product links. If you run catalog ads, Google Shopping or dynamic product campaigns, separating each market properly reduces feed errors, rejected items and ads that send shoppers to the wrong local page.
What a multi-country product feed is
A product catalog is the structured data behind your products: ID, title, description, image, price, availability, brand, category and landing page, among other fields. When you send that catalog to an advertising or commerce platform, it is usually called a product feed.
A multi-country product feed organizes that data by market. The same physical product can exist in several countries, but the data you send to each channel should not always be identical.
For example, a footwear store selling in the United Kingdom, Germany and France may carry the same running shoe model in all three countries. Still, the feed needs to reflect local buying conditions:
- The title may need to be in English, German or French.
- The price may use GBP in the UK and EUR in Germany or France.
- The landing page should point to the correct local product page.
- Stock may differ by warehouse, delivery area or shipping rule.
- Some channels, attributes or formats may be available in one market but not another.
The core principle is simple: the feed must describe the real product and match the page where the user lands. Google’s product data specification explains that required and optional attributes can vary depending on the product, destination and market. Meta’s documentation for getting started with catalogs describes catalogs as the foundation for showing products across its commerce and advertising experiences.
For beginners, the practical takeaway is this: do not think of international expansion as “one huge file for everything”. Think of it as one well-organized product source with specific outputs for every market and channel.
Why it matters for catalog ads and shopping campaigns
When a catalog grows, small errors scale quickly. A badly formatted price, a landing page from the wrong country or an outdated availability value can affect hundreds or thousands of products at once.
A market-based feed structure matters because it helps you:
- Avoid currency mismatches. A shopper in the UK should not see an ad creative with a euro price if the local store sells in pounds.
- Keep the ad and landing page consistent. The product, price, language and availability shown in the ad should match the destination page.
- Reduce preventable feed issues. Each channel has its own requirements for attributes, formatting and availability.
- Run campaigns by country. You can activate, pause or adjust products for one market without breaking another.
- Make reviews easier for teams and agencies. Ecommerce, marketing and agency teams can audit specific market feeds instead of chasing errors in a mixed global file.
This is especially important for dynamic product ads and other catalog-based campaigns. In those formats, the ad creative is built from product data. If the data is wrong, the ad inherits the mistake.
Multi-country product feed: fields you should separate
Before exporting a file or feed URL, decide which fields are global and which must change by country. Use this table as a starter structure:
| Field | Global or market-specific? | What to check |
|---|---|---|
| Product ID | Usually global if it is the same product | Keep it stable across exports |
| Title | Market or language-specific | Make it readable and locally useful |
| Description | Market or language-specific | Include relevant buying information |
| Price | Market-specific | Amount, currency, tax and promotions |
| Availability | Market-specific | Local stock, delivery rules and restrictions |
| URL | Market-specific | Domain, subfolder, language and correct product |
| Image | Global or local | Make sure it represents the product sold in that market |
| Category | May need adaptation | Channel taxonomy and local shopping habits |
| Destination channel | Market-specific | Availability and requirements for Meta, Google or other channels |
A common mistake is keeping a single price field or a single product URL for all countries. That may feel faster at the start, but it becomes fragile as soon as you add promotions, local stock, country-level campaigns or channel-specific rules.
Example: a home decor store
Imagine a fictional online home decor store that sells in the UK, France and Italy. It has a table lamp called “Oslo table lamp”. The physical product is the same, but the catalog data should be treated differently in each market:
- UK: English title, GBP price, URL such as
/uk/oslo-table-lamp, availability based on the UK warehouse. - France: French title, EUR price, URL such as
/fr/lampe-table-oslo, limited stock because of logistics. - Italy: Italian title, EUR price, URL such as
/it/lampada-tavolo-oslo, temporarily out of stock.
If the store sends the UK URL and one global availability value to every market, campaigns may advertise products that cannot be bought locally or send users to a page in the wrong language. The product exists, but the buying experience is still broken.
How to prepare one feed per market, step by step
You do not need to build a custom software integration just to get started. If your destination channel supports feed uploads by URL, the practical work is to prepare accepted attributes, publish a feed URL and let the platform download it according to its own schedule.
Define real markets, not only languages. A language is not always a market. The United States and the United Kingdom share English, but they do not share currency, tax rules, shipping conditions, product availability or pricing. Start with a clear list: country, language, currency, domain or URL structure, active channels and internal owner.
Choose a stable product ID strategy. The ID should allow the same product to be recognized over time. Avoid IDs that change by campaign, export date or file name. If the same product is sold in several markets, you can keep a base ID and separate local values in dedicated fields or outputs.
Separate amount and currency. Do not store “£29.99” or “29,99€” as free text if you later need to validate or transform the value. Work with price amount and currency consistently. In the final feed, follow the format required by each platform.
Create local landing pages you can verify. Every product should point to the right local page. Check that the page loads, the product exists, the language is correct and the price does not contradict the feed.
Segment stock and availability. If stock is managed by warehouse, country or delivery zone, do not export a global availability value. A product available in Germany may not be available in Spain. For catalog ads, this reduces the risk of promoting items that shoppers cannot actually buy in that market.
Map attributes by channel. Meta, Google, TikTok, Pinterest and other channels do not always require the same attributes or use the same field names. Review the destination’s specification before exporting. In Google, required attributes can vary by product type and country, so not every catalog needs exactly the same structure.
Create one output per market and channel. Instead of sending
global_catalog.csveverywhere, create outputs such asgoogle_uk,google_fr,meta_ukormeta_it. This makes it easier to review errors, launch campaigns and update one market without disrupting another.
How to do it with AdMotion
In AdMotion, this workflow starts in the Feed Manager. It connects your store or product file, maps fields, normalizes data with rules, filters product sets and publishes feeds through URLs generated on download.
A basic setup could look like this:
Connect the product source. Start from a supported store, product file or existing feed. The important part is to import a base structure with the fields you need: ID, title, price, stock, image, URL, country or any other value that helps separate markets.
Map the fields. Review which column corresponds to each catalog value. For example:
title_uk,title_fr,price_uk,price_fr,url_ukoravailability_it. If the source has unclear column names, mapping helps you clean up the structure before exporting.Normalize data with rules. You can create rules to clean titles, complete fields, separate products by country or exclude items without a valid local URL. AdMotion supports rules, including rules written in natural language, and the result is reviewed in the editor before it is applied.
Create product sets by market. A set is a selection of products that matches certain conditions. For example: “products available for the UK”, “products with a valid French URL” or “home decor products with EUR prices for Italy”. These sets help you control what enters each feed.
Create the output feed. For every market and channel, prepare an output in the required format. If you use several destinations, Export Channels helps you work with feeds for Meta, Google Shopping, TikTok, Pinterest and other supported channels, with an analyzer that checks each feed against the channel specification.
Review the feed and copy the URL into the channel. Once the feed is ready, copy its URL into the platform that will read it. The channel then imports the feed according to its own schedule.
There is one important limitation to keep in mind: the import frequency of your source and the download frequency of the destination channel are different things. A clean feed URL does not mean Google, Meta or any other platform will reflect every change instantly. Plan download schedules and check diagnostics inside each destination platform.
If you are moving away from manual spreadsheets, the most useful next step is to test whether your market rules, product sets and output feeds can be centralized in the Feed Manager with your own catalog.
Common mistakes when scaling to more countries
The concept is simple, but these issues show up often when ecommerce teams expand internationally:
- Translating the title but not the URL. The ad looks local, but the landing page is still from another market.
- Using one global availability value. Products are advertised in countries where they cannot be shipped or purchased.
- Reusing the same feed for every channel. A feed that works for one destination may need changes for another.
- Changing IDs during a restructure. This makes historical tracking harder and may break associations in ad platforms.
- Not checking the landing page. The feed says one thing, while the store shows another.
- Mixing local promotions. A discount intended for one country appears in campaigns for another.
- Assuming feed URL equals instant update. The feed may be refreshed, but the channel still imports it on its own schedule.
The answer is not to duplicate work endlessly. The answer is to keep one organized source and create specific, validated outputs. That way, you can scale markets while keeping traceability.
Final pre-launch checklist
Before you upload or schedule an international product feed, review this list:
- Each market has its own language, currency and landing page logic.
- Product IDs are stable and recognizable.
- Feed prices match the destination pages.
- Availability reflects local stock and delivery rules.
- Images represent the actual product sold in that market.
- Products without a valid local URL are excluded.
- Required channel attributes are completed.
- The final feed has been reviewed before the URL is copied into the channel.
- The destination platform has a defined download schedule.
- Someone owns price, stock and promotion validation for every market.
If you manage several countries or clients, document the rules you use. For agencies, reusable rules and clear project structures reduce repeated manual work. AdMotion’s solution for performance agencies supports one access point for multiple projects, person-level permissions and rules that can be copied between feeds.
What to do this week
Choose one pilot market. Do not try to fix every country at once. Start with the market that has the most active campaigns or the most visible feed issues.
Audit 20 representative products. Pick products from different categories, price ranges, stock situations and promotions. Compare the feed, ad destination and product page manually.
Build a market field matrix. List which fields are global and which must exist per country: title, description, price, currency, URL, stock and availability.
Create one channel-specific output. Prepare at least one dedicated output for Google or Meta instead of reusing a generic file. Use the official destination documentation to validate required attributes.
Centralize feed cleanup. If your team still relies on manual spreadsheet edits, organize rules, sets and feed outputs in a feed management workflow. With the platform, you can start from your own catalog and check whether the market-based structure fits your operation.
An international catalog is not just a translated product list. It is a control system for keeping product data, ads and store pages aligned. When language, currency, price, stock and URLs are separated by market, scaling campaigns becomes easier to manage and less vulnerable to avoidable feed mistakes.
Frequently asked questions
Do I need a separate feed for every country?
Not always. You can keep one well-structured master source, but you should create clear outputs by market and channel. This lets you adapt language, currency, price, stock and URLs without mixing local data. A shared source can feed several final outputs if your fields and rules are organized properly.
Can I use the same product ID across markets?
Yes, if it represents the same product and remains stable over time. The key is not to use the ID to mix local information. You can keep a base product ID while separating variable values, such as price, URL, availability and language, into market-specific fields or outputs.
Will my feed update instantly in Google or Meta?
Not necessarily. A feed management tool can generate an updated feed URL when the file is downloaded, but the destination platform imports that URL according to its own schedule. You should separate source updates, feed generation and the channel’s download frequency when planning changes.
Sources
- Feed Manager de AdMotion — AdMotion
- Primeros pasos con catálogos de Meta — Meta
- Especificación de datos de producto de Google — Google
Related posts

Product feed format: CSV, XML or Google Sheets?
Choosing between CSV, XML and Google Sheets is not just a technical preference. It depends on catalog size, update frequency, team workflow and the ad channels you need to feed.

Feed rules: how to clean titles, prices and descriptions without editing products one by one
Feed rules help you fix repetitive catalog data issues without editing every product manually. Learn how to remove HTML, normalize prices and improve titles with a safe, reviewable workflow.

Product titles: how to clarify variants without stuffing your feed
Product titles help Google Shopping, Meta and other channels understand what each catalog item is. Learn a simple brand/type/attribute pattern to describe variants clearly without artificial keyword stuffing.