Foundation · 2 min
What you need to know
How should ecommerce translations be managed?
Use a translation management workflow with a source owner, stable content identifiers, locale status, glossary, reviewer, publication state and history.
What happens when the original content changes?
Mark linked translations for review when meaningful source text changes. Do not overwrite an approved localized adaptation automatically without showing the change.
How do I know which translations are outdated?
Compare each locale’s recorded source version with the current source and report changed, missing or unreviewed segments. Give urgent customer and compliance content higher priority.
Should product translations share the same product record?
Usually, yes. A shared product identity keeps inventory, core facts and analytics connected while localized fields and market overrides hold appropriate differences.
How should untranslated content be handled?
Choose an explicit policy: withhold the incomplete page, show a clearly identified fallback, or publish reviewed partial content only where the journey remains understandable.
Should fallback languages be used?
Fallbacks can preserve access, but customers should know the language changed, and essential checkout or policy text must not silently fall back to a language they cannot understand.
A quick store check
Edit one source paragraph and confirm every linked locale becomes visibly outdated until it is reviewed.
Foundation · 2 min
Frequently asked questions
Can translators edit product facts freely?
No. Local style may change, but governed facts require source-owner control.
Should fallback content be indexed as a localized page?
Not when the page lacks meaningful localized value and would mislead searchers.