When a product title or description changes in the source language, it is easy for the translated storefront to fall out of sync. I use this small review loop to catch the common problems before they become customer-facing.
1. Keep a source snapshot
Before a catalog update, export the relevant product content or save a dated copy. Keep stable identifiers (product ID, handle, or another durable key) beside the source text. A row number is not a reliable identifier: exports can be sorted differently next time.
2. Compare by key, not by position
After the update, compare the old and new source values using the stable key plus the field name. Mark rows as added, changed, removed, or unchanged. This makes a small title edit visible even if the rest of the product record is identical. Treat a removed item separately; do not silently erase its translation history until you know whether the product was intentionally retired.
3. Send only changed text for translation review
For each changed field, keep the source text, target locale, existing translation, and a status such as needs review. Preserve placeholders, product codes, URLs, and Liquid or HTML snippets exactly. A short note about context helps too: “button label,” “material name,” or “fits on mobile” can prevent a literal translation that sounds wrong.
4. Check more than whether a translation exists
A useful review can ask:
- Is the target-language value present and non-empty?
- Does it still describe the current source text and product details?
- Were placeholders and markup preserved?
- Did punctuation, units, variant names, or availability language change?
- Does the phrase fit the place it appears, especially buttons and navigation?
A non-empty field is not proof that the content is current. Compare its source version or last-reviewed status as well.
5. Review the storefront in context
Preview a few representative product pages in each affected locale. Look for untranslated fragments, awkward line breaks, clipped buttons, mixed-language titles, and stale variant labels. Check mobile as well as desktop. Keep a short list of the exact page and field for any issue so a teammate can reproduce it.
6. Keep a reversible record
Store the source snapshot, reviewed translations, and a small change log together. Before applying a bulk update, test a handful of products and retain the previous values so a bad import can be rolled back. Record who reviewed each change and when; that makes the next edit easier to triage.
A simple spreadsheet can run this process: one row per stable product/field/locale key, with columns for the previous source, current source, current translation, status, and reviewer. The important part is repeatability, not a particular tool.
Disclosure: I’m Ava at LocaleDelta, where we’re exploring a CSV-based way for small Shopify teams to spot changed and missing storefront translations. LocaleDelta is not a Shopify App Store listing. I’d be glad to hear what you use to keep your own translation reviews from getting lost between catalog updates.
Top comments (0)