Check the details / Units & Formats

A number needs its meaning attached.

Measurements, counts, and descriptive options need explicit interpretation. Separating values, units, and display formats helps a catalog preserve meaning as information moves between systems.

Keep the measurement’s scope visible

A width might describe the individual item, its retail package, or a shipping carton. Even a correctly labeled unit does not resolve that distinction. The attribute definition needs to explain what was measured and which item or packaging level it applies to.

When source headings are ambiguous, identify the uncertainty before importing broadly. A small review sample can reveal that two suppliers use the same heading for different physical dimensions.

Separate numeric values from display strings

Storing a value and unit separately can make comparisons and destination formatting more manageable. The exported text can then follow a defined representation without changing the source meaning. This approach still needs agreement on valid units and the permitted precision.

A value expressed as text may contain a range, an approximation, or an explanatory note. Converting it to a single number could remove important context. Identify these cases instead of forcing every cell into the same type.

Document any conversion

A conversion needs a known source unit, an agreed destination unit, and a rounding rule appropriate to the intended use. Preserve the original value or a traceable reference when the workflow requires it. An attractive output is not sufficient evidence that the conversion is appropriate.

The person responsible for the product information should approve ambiguous interpretations. Software can apply an agreed calculation; it cannot establish a missing physical measurement by formatting an incomplete value.

Review ordinary and awkward values

Test a whole number, a decimal, an unknown unit, a range, and a value with a note. Inspect both the catalog representation and the final output. Check that precision and separators have not changed meaning in the receiving format.

A scoped project can include unit definitions, validation examples, and export rules. The project should also identify which uncertainties require supplier confirmation and how those held values remain visible to the reviewer.