Localize Your Feed for Another Market

Language is set per catalog, so a market in another language gets its own catalog. Set its Locale, then localize your copy with an AI prompt and translate fixed terms with a mapping table.

Updated November 6, 2026

Language is set per catalog, so a German market and a French market each get their own catalog, with their own Locale, feed and copy. Create the catalog, set its Locale, localize your copy with an AI prompt, and use a mapping table for terms that must always translate the same way. Then check what the destination asks for in that market.

Set up the market's catalog#

Create a new catalog and point it at your store's feed for that market. If your store has only one feed, use that one and translate in Renable.

The Locale is set when you create the catalog, and you can change it later. For a new market, it matters most for:

  • The language prompts write in. A French catalog gets French copy without you restating the language every time.
  • The date order Renable reads in your feed. A market that writes dates day-first is read correctly.

Fallback languages are covered in Languages and localization.

Reading prices#

Renable reads most numbers by their own shape, whatever the Locale. A value like 4.490 could be four thousand or four and a bit, so if your market uses a dot as the thousands separator, set the price column's Decimal separator to Comma. You'll find it on the column's type badge on the Mapping tab.

Showing prices#

A number is written exactly as it is unless a Format number step says otherwise. Add that step to the price and leave its separators on their first option, and it writes the catalog language's: 4 490,50 in Sweden, 4,490.50 in the US. See Number format.

Localize your product copy with AI#

The catalog's Locale sets the default language, so a well-scoped prompt writes titles, descriptions and headlines in the market's language.

  1. Open the project the market's catalog belongs to and go to its Creative tab.
  2. In the Prompts section, create or open the prompt that writes the copy you want localized. A prompt belongs to the project and writes separate copy for each catalog in it, so it picks up each market's Locale.
  3. In the instructions, add a line telling it to write in the product's native language. This holds even if you brief the prompt in English.
  4. Under Use as, set the language (and the country, if it matters) so the copy is tagged for this market.
  5. Preview it on one product with Generate. Then turn on Activate prompt and Publish the prompt. Publishing an active prompt spends credits on every product in its scope.

Model choice, scoping and the credit estimate are in Working with prompts.

Translate known terms with a mapping table#

Some values need the same translation every time: category names, size and color labels, material or care terms. Use a mapping table for these. You set the term once and every matching product gets it.

  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.
  4. Publish the catalog to apply it.

The details are in Mapping tables, Joining another feed and Fixing your feed data with rules.

Check what the destination requires#

Destinations generally expect a feed's language and currency to fit the country you target, and can reject products that don't.

  • Confirm the target country, feed language and currency the destination expects for this market. In Google Merchant Center, a product data source's language and countries are set under Data sources when you add or edit it, and each targeted country's own policies apply.
  • Check whether one feed can serve several countries. Google lets one data source target additional countries and converts prices into the shopper's currency; when a new market also speaks a different language, Google says to create a separate data source with the product data translated (Show products in multiple target countries). Meta's localized catalogs let one catalog carry country- and language-specific prices, currencies, translated names and descriptions, and product links.

You set the target country and language in the destination's own dashboard, where you register your channel's feed URL (where to find it), not on the channel in Renable. The channel sends your feed's own text plus any AI-written copy, which follows the catalog's Locale.

Currency#

Renable doesn't convert one currency into another. The amount is whatever your feed carries, and the Currency symbol and ISO currency code placeholders only label it with the currency of the catalog's Locale. A market that prices in a different currency needs those prices in its feed, unless the destination converts them, as Google can.

Or ask Aimée#

Tell Aimée the market you're expanding into, for example "set this catalog up for the German market". She can create the catalog, set its Locale, adjust the prompt and build a translation mapping table with its lookup, then publish once you approve. She turns a prompt on and publishes it only with your go-ahead, since that spends credits on every product in its scope.

FAQ#

Which languages actually work?

That depends on the feature. Prompt-written copy works in essentially any language, while ad-copy extraction and review quotes cover European and North American languages. See Languages and localization.

Related articles#