Glossary
Product localisation adapts product information for the language, conventions and requirements of a particular market. It can include translation, units, terminology, imagery and market-specific content. Localisation should preserve the underlying product facts while making the information appropriate for its intended audience and destination.
Two markets can use the same language but require different terminology, measurements or channel formats. A locale commonly combines a language and country context. The data model should distinguish shared facts from content that legitimately varies by locale, market or channel.
For example, the same technical product could need an English description for the UK and Australia, with different commercial availability or supporting documents. The product's verified material does not change because the destination changes, but its surrounding presentation may.
Translation alone does not establish that a technical term, unit conversion or claim is appropriate. Review important category terminology and keep the relationship between the original value and its local representation. Do not create a regional specification by guessing what a market would normally expect.
Assign owners for translation and approval, and define what happens when a shared source value changes. A translated field can become outdated even when it remains populated. Keeping source, locale and review status distinct helps teams identify which market versions need attention.
Explore practical support for organising, improving and maintaining product information.