Translations
Product Studio shows which product texts are missing or outdated in each language, and helps you fill them in the sheet or through a translation agency.
What is checked
The plugin configuration sets what is checked:
| Setting | Default | Meaning |
|---|---|---|
| Source language | The system language | The language translations are made from. |
| Languages to check | The languages of your sales channels, without the source language | The languages that are checked for missing and outdated texts. |
| Texts to check | Name, description, meta title and meta description | Keywords, pack unit and pack unit plural can be added. |
| Custom fields to check | None | Text and HTML custom fields of products, checked like the texts above. Other custom field types are ignored. |
With "Only check languages of the product's sales channels", a language only counts for products that are visible in a sales channel with that language.
When you change one of these settings, all products are checked again in the background (this needs the queue worker, see Getting started).
A text is missing when the language has no own value. Variants count as translated when their main product is translated, as in the storefront.
A text is outdated when the source text changed after the translation was saved. Product Studio records the source text every time a translation is saved, from the moment the plugin is installed. Translations that already existed before the installation are only recognised as outdated after they are saved once, or after you mark them as up to date (see below).
Languages tab
A table with one row per language and one column per text, showing the share of main products that have a translation and the number of missing and outdated texts. "Filled" per language is the share of all checked texts (every text of every main product) that have a translation. Below it, "Fully translated" counts the main products without any missing or outdated text in that language, which are the products that are ready to sell in it. Click a number, or "Edit missing texts" in the row menu (…), to open those products in the sheet in translation mode, with the source text next to the target language.
"Export for translators" in the row menu exports these products with the source and target columns.
"Mark translations as up to date" accepts the current translations of the selection (or all products) without changing them, for example after a typo fix in the source text. More than 500 products are handled in the background. A source text that changes before that is done stays outdated, because you didn't see it. Marking all products needs the "Bulk actions" permission; selected products in the sheet need the editor permission.
Translator round trip
- On the Languages tab, click "Export for translators" for a language. The CSV has the products with missing or
outdated texts in that language: the product number and, per text, a column in the source language and one in the
target language, for example
Name (en-GB) [name@en-GB]andName (fr-FR) [name@fr-FR]. Missing translations are empty. - The translator fills in the target columns and keeps the header row as it is.
- Import the file (Import tab). The columns are mapped automatically from their headers. Use "Only fill empty fields" to add missing translations, or "When the cell has a value" to also replace outdated ones. Set the source language columns to "Don't import".
- Check the review, apply. The imported translations are recorded as up to date.
Product Studio doesn't translate texts itself; there is no machine translation.
Bulk help
- "Copy from another language" in bulk actions copies texts that don't need translating, such as model names, optionally only where the target is empty.
- Rules with a language scope (Data quality rules) give products a lower score when a language is incomplete, for example "description at least 300 characters in German".