What should be translated in a multilingual product catalogue?

Separate product identity from the description

Keep a master record for the model code, manufacturer-defined range and identifiers customers use when ordering. Translate the category, purpose and descriptive features into language the buyer understands. Keeping a brand name unchanged is a starting decision; record a different market name separately if the brand has approved one.

In our example, the model field remains MX-240 in both languages. A product specialist might confirm “in-line duct fan” as the English generic name. Do not ask a translator to classify the product from a photograph alone. Similar-looking components can have different applications, so the context belongs in the translation brief.

Record decisions, not just word pairs

A small catalogue can start with one shared table. Include the source term, approved translation, protected code, product context, person approving it and review date. Note a retired translation as well, so the next editor does not accidentally bring it back.

• Record the term the sales team hears from buyers.
• Ask a technical owner to confirm the meaning and product class.
• Read the translation inside the actual title and short description.
• Compare the term across navigation, filters and download names.

The glossary is not a list of keywords to repeat. Its purpose is to make it clear that the two language versions describe the same product.

Protect only the fields that need protection

W3C explains that the HTML translate attribute indicates whether an element’s content should be translated by translation tools; it does not change its appearance. Ask the developer to consider translate=no narrowly for protected model or brand fields. Applying it to the whole description may also exclude information the customer needs translated. W3C guidance.

The attribute does not guarantee identical behaviour in every translation tool. Your published professional translation still needs a glossary, human review and consistently structured fields.

Follow one product from page to PDF to enquiry

Find an item in the Turkish catalogue, change the language and open its technical file. Compare the model code in all three places. Then check which product reference reaches the quote request. Opening a different product after switching languages is a navigation problem; changing the identity of the correct product is a content-mapping problem.

Include more than newly created records in the test. Choose an item with a retired name, a brand containing unfamiliar characters and two closely named variants. Search by model code and approved generic name. Record the outcome before deciding whether the old terminology needs search synonyms.

Make acceptance more specific than “translation finished”

Before approving the first language package, require the sample product group to pass identity, download, category and enquiry-reference checks together. Assign responsibility for maintaining the glossary when a new product arrives. Avoid adding unrelated free-text fields that quietly undermine the agreed terminology.

Our Gerhman project page is a relevant catalogue reference. It is not evidence that the glossary procedure in this guide was implemented there or produced measured results. For your catalogue, our website design service can help plan the content fields and publication checks together.