docs/user/manage-products/translations.mdx
The Translations page gives you a single place to see how well your product catalog is translated across every language your store supports. Rather than hunting through individual product pages, you can see at a glance which products have been translated and which still need attention — and use bulk import/export to handle translations in volume.
To access Translations, navigate to Products → Translations in the admin dashboard.
<Note>The languages shown on this page are determined by your Markets configuration. If you don't see any locales listed, you'll need to set up additional markets first. See <u>Settings → Markets</u> for more details.</Note>
At the top of the page, you'll see a coverage summary table with one row per locale your store supports (excluding your default language). Each row shows:
fr, de, es)This gives you a quick health check on your localization progress without needing to export any data.
Below the coverage table, you'll see a paginated list of all your products. Each product has a column for every configured locale, showing either a checkmark (✓) if a translation exists or a dash (—) if it's missing.
To edit a product's translations, click on the product name. This will open the translation drawer where you can add or update translated content for that product.
If you prefer to manage translations in a spreadsheet, you can export your entire translation dataset as a CSV file.
Click Export in the top-right corner of the page.
Click Export to confirm, and a download link will be sent to the email address associated with your admin account.
Once you've updated your translations in the exported file (or built a new file from scratch), you can import them back in bulk.
Click Import in the top-right corner of the page. This opens the import side panel.
Once submitted, you'll be redirected to a processing screen where you can monitor the import progress. Any rows with errors will be flagged with a message so you can fix and re-import them.
<Note>The translation import uses the same importer infrastructure as the product importer. If you're familiar with importing products, the process will feel very similar.</Note>