Keeping multilingual product information in sync
A change to a size or care instruction needs to reach the translated pages too. Make it clear which text still uses an old source version and who reviews it for each market.

The workflow illustrates a possible design and is not a client case study.
- Detect source changes
- Translate and review
- Publish approved versions
When translations lag behind the source
The source may show a new size while a translated page still carries the old specification. Page-by-page translation makes such omissions hard to spot and can introduce changes to model numbers, units or brand names. Use a common product record and separate translation from content that deliberately differs by market. Then a source change can be followed through to the pages it affects.
Check the store’s translation tools
Shopify Translate & Adapt handles translated and market-specific content. For one store, check its supported resource types first. A shared review process may be useful when several websites, an ERP or a large product catalogue must stay in step.
Show which translations a source change affects
Try one product category in two languages, with agreed terminology and fields that must stay unchanged. A source change should mark the affected translations for review; approved text can then be published. Retain the source version behind each translation so staff can tell whether it is still current.
Verify models, units and formatting
Have someone who knows the product and the language check model numbers, sizes and HTML formatting in the actual store. Look at what appears when a translation is missing, then try withdrawn source text and a repeated run. Word counts or automated scores cannot settle whether the content is accurate.
Bring terminology and market differences
Bring the product fields, target languages, terminology and differences between markets. Identify who approves the product details and each translation.