Managing a multilingual product catalog

A multilingual catalog needs a dependable relationship between the original record and every language version. That relationship must survive renamed products, supplier imports and corrections made by editors.

Before choosing a translation tool, define which fields are shared, which need translation and which can differ by market. Those rules determine how the catalog should be stored and updated.

Keep identity separate from presentation

Use a stable internal reference to connect language versions. Product titles and visible URL slugs can change; they are poor identifiers for synchronisation.

Model numbers and dimensions may be shared. Descriptions and usage guidance usually need separate language values. Prices, availability, documents and units require a deliberate decision because a language and a sales market are different things.

For example, an English and a German description may refer to the same physical product and stock record. A regional offer for that product could still have different availability. The data model should express both relationships without duplicating the whole product unnecessarily.

Make translation status visible

Automatic translation can provide a draft, but the team needs to know what has been reviewed and what has changed since that review.

Useful record fields include:

• Source record ID and source revision.
• Language and translation revision.
• Draft, awaiting review, approved or outdated status.
• Last reviewer and review date.
• Editorial overrides that must survive the next import.

A changed description should flag its translations for review. A stock update should not force the description through translation again. Keeping those changes separate avoids unnecessary work.

Maintain a glossary for specialist terminology, product families and terms that stay untranslated. Review the glossary alongside real catalog examples rather than a list of isolated words.

Define import ownership

Decide what a supplier feed can overwrite. A corrected translation should not disappear because the next import includes the original machine-generated text.

One approach is to store imported values separately from approved editorial overrides. Another is to require approval when an import conflicts with a reviewed field. The choice depends on the publishing tools, but the conflict must be visible.

Also define how to treat records missing from a feed. An incomplete import should not immediately delete every missing product and its translations. Validate the import before applying removals, then archive or unpublish according to the agreed rule.

Check language URLs and navigation

Google recommends different URLs for language versions. If using hreflang, each page should identify itself and the corresponding alternatives; Google’s localised-page guidelines explain the supported methods.

Test that a language switch opens the equivalent product, rather than always returning to the homepage. Decide what the visitor sees when a translation is unavailable.

Rehearse one complete update

Choose a small group of products with different attributes and content lengths. Import them, translate them, approve corrections and then change the source data again.

Confirm that editorial changes survive, outdated translations are flagged and shared specifications remain consistent. Finally, test search, filters, forms and confirmation messages in each language, including longer text on a phone.