Use case: taking your catalog to another country and another language

By Manuel Mattar3 min read

In short

In this example, the brand adds English as an output language, translates from the published Spanish product record instead of writing from scratch, approves each language separately and sets up an English channel with the values its new store expects. Prices, currencies and the country's legal requirements stay on its side.

This is an example scenario, not a customer. The catalog size and the steps describe a hypothetical situation.

The situation

A Mexican kitchenware brand has 800 products with Spanish product records already published in its store. It is about to open a store in the United States and needs the catalog in English: names, descriptions, bullets and SEO metadata.

The first idea was to ask an agency to translate an Excel file. The problem is a familiar one: the file freezes the day it is sent, the Spanish records keep changing and, three months later, nobody knows which English version matches which Spanish version.

What the team does in Bruxel, step by step

1. Add the language without changing the primary one

In Content → Brand voice, the team adds English to the output languages. Spanish stays as the primary language: adding a language does not change it. From the primary language's record, you translate into the others.

On the same screen it reviews the voice: form of address, tone, brand context and forbidden words. The voice is one for the whole catalog, so the team writes the context with both markets in mind.

2. Translate, do not rewrite

On each product page, the language selector shows the organization's languages. The team picks English and uses “Translate to…”. The button says how much it costs before you click it, and it is only charged if the translation comes out right. If the result comes back practically identical to the original —a sign it did not translate—, it is not published and not charged.

The text is translated: name, descriptions, bullets and SEO metadata. Codes, the friendly URL, structured data and proper names are copied as they are. The translation enters as one more version in the history, with its origin noted, and each language can be edited by hand separately.

For new products that do not have a record yet, the team generates directly: with two output languages, the cost doubles, and Bruxel checks the balance covers the total before starting.

3. Approve each language separately

With the “Editorial workflow” turned on, nothing new is published without an administrator's approval. Everything goes by product and language: the person reviewing English approves in Content → To publish without touching what is published in Spanish.

4. A channel for the new store

In Channels → Channels & templates, the team creates the US store channel with English as its language. Two tools handle the market differences:

  • Channel values: a list option can come out with another value in that file. “Rojo” comes out as “Red” without changing the option in Bruxel.
  • Value per channel: if a text attribute needs different wording for that channel, it is marked that way in Attributes and the product page gains a tab to write it.

Then “Measure” says how many products would come out complete in that channel. A product without a published English record does not go out in the file, and the product page says so.

5. Keep both languages aligned

When someone edits the Spanish record, the English version warns that it came from an earlier version and offers to translate again. It does not update on its own: the team decides when the new translation is worth paying for.

What gets solved

  • English comes from the published Spanish, so both records say the same thing.
  • Each language has its own history and approval, without overwriting the other.
  • The new store receives a file in its language, with its values, from the same catalog.
  • Misalignments are visible: the translation warns when its original changed.

What does not get solved

  • The language is not a regional variant. Bruxel works with Spanish, English, French and Portuguese; each country's differences are handled in the voice and in review.
  • Translating is per product, from the product page. In a large catalog that is shared-out work, not one click.
  • Prices, currencies and inventory are not handled by this flow.
  • The new country's legal requirements are the brand's responsibility. The rule against health or efficacy claims helps, but it does not replace a review by someone who knows that market.

To go deeper, read the guides on translating a product record, brand voice and generating descriptions, or the AI content, Channels and Review and quality pages.

Frequently asked questions

Is translating the same as generating again in the other language?

No. Translating starts from the published record in the primary language and says the same thing; generating again is a second draft that may come out different. Translating also costs less, and the button shows how many credits before you click it.

What is not translated?

Codes, the INCI ingredient list, the JSON-LD, the friendly URL, the hex color and proper names such as the sub-brand or the color name are copied as they are. Those fields are not even sent to the model.

If I change the Spanish record, does the English one update on its own?

No. The translation warns that it came from an earlier version and offers to translate again. Redoing it costs credits, so the decision is yours.

Sources

  1. Internationalization and localization (Wikipedia)
  2. Product information management (Wikipedia)

About the author

Manuel Mattar

Founder of Bruxel.AI

In 2014 he founded Wolf Sellers, an e-commerce agency in Mexico City, and later Bruxel.AI, the AI-powered PIM.

See all posts by Manuel Mattar

Try it with your catalog

Create your free account and try Bruxel with your own products using the welcome credits.

Keep reading

Use case: taking your catalog to another country and another language