Localize Your Feed for Another Market

Selling into a new country or language usually means a separate catalog for that market — set its locale, then localize your copy with an AI prompt or translate known terms with a mapping table.

Updated July 15, 2026

Selling into another country or language usually means a separate catalog for that market. Set the new catalog's Locale — it sets the language Aimée writes copy in — then localize your product copy with an AI prompt, or use a mapping table for known term translations. Match the target ad network's country and currency rules too.

Why a separate market means a separate catalog#

Language and number formatting aren't account-wide settings in Renable — they're set per catalog, because a different country or language is usually a different storefront with different customers. So a German-market push and a French-market push live in their own catalogs, each with its own Locale, feed, and copy, rather than sharing one.

For an agency, that keeps each client's markets cleanly separated: you localize once per market, and every product that arrives in that market's feed is read and written in the right language automatically on each import.

A second catalog can point at a market-specific feed your store exports for that country, or — where the store only publishes one feed — at the same feed with the market's Locale set and translation applied in Renable. Either way, the market gets its own catalog.

Set the catalog's locale for the new market#

The Locale is the anchor of a localized catalog:

  • It sets the language Aimée writes in. Ad copy, headlines, and other AI-generated text default to the catalog's Locale, so a French catalog produces French copy without you restating the language every time.
  • It sets the date order Renable reads your feed in. A market that writes dates day-first rather than month-first is read correctly, so incoming dates aren't misinterpreted.

Locale is set when the catalog is created and is editable afterward. The exact fields, fallback languages, and which languages each AI feature supports are covered in Languages and localization — that article is the reference; this guide is the job.

How prices and numbers are read from your feed — whether a comma or a dot is the decimal separator — is a separate catalog number-format setting, not something the Locale derives. If your market prices with a comma decimal, set that alongside the Locale so a value like 1.234,56 isn't misread. How a number is later displayed in your ad creative is a different setting again, configured in Studio. See Languages and localization for the split between reading a feed and formatting a value for display.

Localize your product copy with AI#

The fastest way to get market-ready copy is to let a prompt write it. Because the catalog's Locale sets Aimée's default language, a well-scoped prompt writes titles, descriptions, and headlines in the market's language for you.

  1. Open the market's catalog and go to its Prompts list.
  2. Create or open the prompt that writes the copy you want localized.
  3. In the instructions, include an explicit line to write the output in the product's native language — this holds even if you brief the prompt in English.
  4. Scope the prompt to this market under Use as, so its output is tagged for the right catalog, product set, and language.
  5. Preview it against one product, then press Generate to roll it out.

The full prompt mechanics — types, model choice, scoping, and the credit-cost estimate you see before generating — are in Working with prompts. Generating content spends credits, so preview before you commit.

Translate known terms with a mapping table#

AI copy is right for free-form text, but some values need an exact, consistent translation every time — category names, size and color labels, material or care terms. For those, a mapping table beats an AI paraphrase: you decide the target-language term once, and every matching product gets exactly that.

  1. On the catalog's Data sources tab, add a Mapping table and seed its keys from your feed's real source terms.
  2. Fill in the target-language term for each key.
  3. Add a lookup that reads the translated term back, and write it to the field with a Set field rule.

The table and lookup mechanics live in Mapping tables and Joining another feed; the rule that writes the result is in Fixing your feed data with rules. Nothing reprocesses until you Publish the catalog.

Match the market's ad-network requirements#

A localized catalog still has to satisfy the ad network you're feeding. Ad networks generally expect a feed's content language and currency to be valid for the country you're targeting, and reject products that don't line up.

  • Confirm the target country, feed language, and currency the network expects for this market. [VERIFY: exact Google Merchant Center content-language / target-country / currency requirements and where they're set]
  • Check whether the network lets one feed serve several countries or wants a separate feed per country. [VERIFY: whether Meta and Google Merchant support multi-country targeting from a single feed, and the mechanism]

You configure the target country and content language in the ad network's own dashboard — where you register the feed URL you export from Renable — not on the Renable channel itself. The exported feed's language follows the catalog's Locale, and its currency comes straight from your feed: Renable controls how a price is displayed, but the amount and currency are whatever your feed carries. Renable doesn't convert one currency into another, so a market that prices in a different currency needs those prices in its feed.

FAQ#

Do I really need a second catalog, or can one feed cover two languages?

A catalog carries one Locale, which sets the language Aimée writes in — so covering a second language cleanly means a second catalog for that market. Point it at your store's market-specific feed if you have one, or at the same feed with the new Locale and translation applied in Renable.

Does Renable convert my prices into the market's currency?

No. Renable controls how a number is formatted and displayed, but the price amount and its currency come straight from your feed. If the market sells in a different currency, those prices need to be in that market's feed.

AI copy or a mapping table — which should I use to translate?

Use an AI prompt for free-form copy like descriptions and headlines, where fluent, product-aware wording matters. Use a mapping table for fixed vocabulary — categories, sizes, colors, materials — where you want the same exact term every time rather than a paraphrase. Many localized catalogs use both.

Which languages actually work?

That depends on the AI feature. Prompt-written copy works in essentially any language; Renable's own extractive features cover a narrower set. See Languages and localization.

Or ask Aimée#

You don't have to wire a market up by hand. Tell Aimée the market you're expanding into — "set this catalog up for the German market" — and she can create the catalog, set its Locale, adjust the prompt so copy is written in the market's language, and build a translation mapping table with its lookup, then publish once you approve. Generating the localized copy still runs from Generate, since that spends credits.

Related articles#