How should a configurator handle different supplier material names?

A configurator should not decide that two materials are interchangeable merely because their names look similar. Use stable product and material references, with approved mappings between customer language, supplier descriptions and factory items. Treat substitution as a product decision rather than a text-cleaning exercise.

Identify what each name describes

A customer may see “anthracite,” a supplier may use a finish code and purchasing may maintain an internal item reference. These can describe related aspects of the same selection without being identical fields. Preserve the original supplier reference where your process needs it.

Also separate descriptions from specifications. Two finishes with similar names can have different surface treatment, grade or compatibility requirements. Ask the manufacturer to approve the mapping.

Test a supplier change with the same public label

Suppose a business changes the supplier of a fitting while retaining the customer-facing description. Check whether earlier projects retain their original material mapping and whether new orders use the approved replacement. Inspect related components and documents as well as the visible label.

If the items are not interchangeable, the application needs a different product choice or a review route. Reusing the familiar name should not conceal a change that matters to manufacturing or installation.

Keep unit conversion explicit

A supplier may sell a material by pack while the factory consumes individual pieces. Another may quote a length in metres while the configuration uses millimetres. Store the conversion and pack assumptions in the agreed data model rather than embedding them in a translated description.

Use known purchasing and production examples to check quantities. Correct names do not prevent an incorrect unit from multiplying the requirement.

Make the mapping maintainable in Configurix

A Configurix product-data connection can be scoped around your catalogue and receiving systems. Define who approves mappings, how supplier updates are reviewed and which historical references remain attached to accepted projects.

Can translated names share one product code?

Yes, when they refer to the same approved option. Language alone should not create a different material identity.

Should the supplier name become the customer's option label?

Only if it is useful and appropriate. Customer terminology and operational references serve different users; connect them without forcing one description to do every job.