How do you preserve measurement meaning in an export catalogue?
The expression 1.250 on a product card can be interpreted differently by different readers. A number alone also does not explain whether it represents millimetres, weight or items in a pack. Translating an export catalogue must not change the technical meaning of its data. This guide separates the source value, unit and displayed format. All dimensions used here are educational examples, not client product specifications or evidence of engineering suitability.
Create one reliable product record first
Let an illustrative panel width have the numeric source value 1234.5 and the separate unit mm. If a Turkish editor types “1.234,5 mm” in one text field and an English editor types “1,234.5 mm” in another, later updates can diverge. Keep the number, unit, measurement name, source document and review date together. Have the owner of the manufacturer data approve the value. A design team improving the layout should not inadvertently invent a new technical specification.
Understand what the formatting tool does
The MDN Intl.NumberFormat documentation describes presentation by locale and formatting options. In our local check, 1234.5 became 1.234,5 for tr-TR and 1,234.5 for en-GB. The underlying value stayed unchanged. Relabelling a unit does not perform a millimetre-to-inch calculation. Treat formatting and conversion as separate operations; where conversion is required, confirm the calculation and rounding rules with the technical owner.
Name the object being measured
Furniture width, required installation clearance and packaged width are different properties. Our teaching card could say “Product width: 1,234.5 mm”, with packaging dimensions elsewhere. Check that a lettered dimension in a drawing has a corresponding name in the table. If the unit appears only in a heading, consider what happens when that heading is no longer visible on a narrow screen. Colour and proximity should not have to explain the entire relationship between the number and its object.
Do not alter precision for visual symmetry
Removing a decimal part to make every card look equally short can change technical meaning. Let the product owner determine the required precision. Clearly label approximations and never guess tolerances. If a product card, detail page and downloadable document use different precision, document why. Address overflow through typography and layout before editing the data. A visually balanced grid is not a justification for presenting a different measurement, especially when visitors use that information to shortlist products.
Carry the same meaning into the enquiry
When a visitor selects a product and enters an enquiry form, copying only a formatted display string is fragile. Preserve the connection to the product identifier and approved values. If visitors can enter custom dimensions, show the expected unit beside the field and explain the accepted decimal format with an example. A comma or full stop must not silently produce a different magnitude. Compare the entered value with the record received by the team, rather than inspecting only the visible interface.
Prepare a small comparison sheet before launch
Select five representative records: an integer, a decimal dimension, a long code, a large number and a product with several dimensions. Compare the card, detail page, document and enquiry record in each language. These are content accuracy checks, not promises about sales or search rankings. Establish this structure early in the website design project so future catalogue updates remain understandable. For selecting the attributes customers should compare, see our separate product comparison table guide.
Frequently asked questions
Must every measurement on an English page use inches?
No. Language and the target market’s measurement needs are separate decisions. Confirm the audience and industry requirement; offer clearly labelled alternatives where appropriate.
Does a number formatter guarantee technical accuracy?
No. It formats the supplied value. Source data, units, precision and any conversion calculation still require their own verification.