Collection translations cover the name, slug, description, and SEO fields. The name and description are what shoppers see on localized collection pages, and the slug is used in localized collection URLs.
On the web
- In your store admin, go to Translations.
- Choose the language you want to translate into.
- Select Collections.
- Enter the translated name and, optionally, a translated slug.
You can also translate collections with per-language CSV import and export or AI translation jobs. Changing the original collection name or slug can mark existing translations as outdated.
If a field already has translations in any language, you cannot clear that field on the original collection until those translations are removed. The same backend rule applies to forms, update imports, and any other source edit path.
Translation CSV imports are row-atomic. If any translated field in a row is invalid, references a missing collection ID, duplicates a localized unique value, or tries to translate a field whose original value is blank, that row is rejected and none of that row's translated fields are saved. Other valid rows in the same file can still be imported.