AI catalogue translation: consistent multilingual eCommerce

Catalogue translation is more than changing language. Products, units and promises must remain accurate while each market receives clear and natural copy.

Separate translatable text from fixed data. Descriptions and category names may be translated, while SKUs, EANs, model references and trademarks follow explicit protection rules. Numbers and units remain unchanged unless an approved conversion is requested. Language alone does not determine currency, tax treatment or delivery eligibility: these remain separate commerce rules. The importer must preserve the link to the original item instead of generating a new commercial identity.

Before bulk generation, agree key terms with the store team. A technical term needs the same translation across categories, filters and descriptions. The glossary includes exceptions, tone and preferred terminology. This avoids multiple translations for the same attribute or confusing filters. A small reviewed sample is a better starting point than immediately translating every product. Suppliers’ trademarked terms may need to remain unchanged even when the surrounding explanation is localized.

Maintain a relationship between every source field and its translation. Changing one product description should not trigger translation of the entire catalogue. Mark the languages requiring refresh and protect human-edited translations. Withdrawn products and changing variations follow the appropriate process across languages, without orphaned pages. A version record lets the team identify which source copy a translation represents and whether later updates have been reviewed.

Each language version needs consistent addresses, links and metadata. Hreflang mappings identify the relationship between versions but cannot replace the actual content. Translate useful information and review titles and descriptions as separate fields. Avoid multiplying near-identical pages for keyword variations. Do not announce service in a country that checkout cannot support. Market-specific commercial information, such as available delivery methods, needs separate verification instead of simple translation.

For a spare-parts catalogue, choose products containing model numbers, decimal values and complex technical terms. Verify codes and compatibility and check that translation introduces no new claims. Test a source-text update, temporary provider failure and restoration of a previous version. Then expand through controlled batches with cost reporting and outstanding approvals. Existing published language versions remain available during processing, and failed records are retried without recreating successful translations.