Translating a listing
You already have the listing in one language: the second one is translated from the first, not written again.
Video transcript
In this video, you'll translate a product record you've already published.
First, add the language to your output languages.
Save, and your catalog now works in both.
On the record, the selector at the top shows your languages.
The English record is already published: you don't generate it again, you translate it. The button shows the cost.
Done: the translation says the same thing as the original, it's not a second draft.
And what translating would break, like the URL or the structured data, is copied as is.
Each language is edited separately, without touching the others.
If you change the original, the translation tells you it came from an earlier version…
…and offers to translate it again. It doesn't update on its own: it's your call.
In the next video, you'll organize your product images.
What it is
When a product already has a published listing in one language, you can translate it into another instead of generating it from scratch. It is cheaper and, above all, the result says the same thing: it is not a second write-up that may come out different.
- It translates from the PUBLISHED listing in your organization’s primary language. If the primary has none, there is nothing to translate from.
- The translation enters the product history as one more version, with its source recorded.
- Each language can be edited by hand separately, without touching the others.
How to do it
On the product page, the language selector at the top shows your organization's languages. Pick the missing one and use «Translate to …». The button states how many credits it costs before you press it.
What gets translated and what is copied as is
Text gets translated: name, descriptions, bullets, claims, SEO metadata. Copied byte for byte are the things that mean the same in any language and that translating would spoil: codes, the INCI ingredient list, the JSON-LD, the URL slug, the hex colour and proper names such as the sub-brand or the colour name. This is not the model's decision: those fields are never even sent to it.
If you change the original afterwards
If you edit the source-language listing after translating, the translation warns you that it came from an earlier version and offers to translate again. It does not update by itself: redoing it costs credits and that decision is yours.
What it costs
Translating costs less than generating again, because translating an already written text is reading and rewriting, not reasoning from the product data. The exact price is on the button before you press it, and you are only charged if the translation succeeds.