Can a configurator change language without changing the product?

A language switch should change the explanation of a product, not its underlying identity. Stable option references, quantities and selected values should survive translation. Decide separately whether a market change also affects availability, price lists or commercial documents.

Separate language from market

A French-speaking dealer and a German-speaking dealer may sell in the same country. Two English-speaking markets may use different price lists or measurement conventions. Do not make every language switch an undocumented commercial change.

Define the relationship between interface language, account, selling market, currency and product catalogue. The user should understand when a switch changes only labels and when a different commercial scope must be selected.

Test a saved product across two languages

Configure a door with a specific opening direction and hardware set. Save it, switch language and inspect the selection, preview, price and exported specification. Translate the opening label carefully: a confusing description can lead to a different customer decision even when the identifier remains stable.

Use a reviewer who understands the product terminology in each language. A structurally complete dictionary does not establish that a technical label means the same thing to the intended buyer.

Include errors, documents and follow-up

Customers encounter more than navigation labels. Translate unavailable-option explanations, measurement instructions, validation messages, saved-project communications and the relevant quotation text. Keep technical codes unchanged where they are operational identifiers.

If a document must be issued in a particular language, define who chooses it and which version the customer accepts. The language of a salesperson's browser should not accidentally determine a contractual document's content.

Specify localization as part of Configurix delivery

A multilingual Configurix project can share controlled product definitions while presenting localized journeys. Provide terminology, market requirements and test configurations. Ask for both language review and functional evidence that switching does not change the selected product unexpectedly.

Should every translated label have a new option ID?

No. Use one identity when the underlying choice is the same. Create a different option when the product meaning or specification is actually different.

Can one language serve several regional domains?

Yes, where the content and commercial scope are appropriate. Define regional differences explicitly rather than duplicating the entire catalogue for every website.