Ask what the number means before commissioning a conversion feature
“Add inch measurements to the catalogue” sounds like a small, well-defined website request. It becomes a different project if the field being converted is a commercial size designation rather than a measurement. The first conversation should establish what the data means before estimating how quickly it can be transformed.
This fictional example concerns a Norway-connected technical supplier. It shows how two representative product records can change the scope from a blanket conversion rule to a more useful content structure.
Bring the source behind one familiar label
The supplier's product P-51 belongs to its proprietary Size 50 class. An approved drawing separately gives its outside width as 52.4 mm. The class name is used in sales conversations and item references. It is not a declaration that the outside width is 50 millimetres.
The proposed feature would read the existing size field, extract 50 and display its inch equivalent. The arithmetic could be performed accurately while producing a false description of the product. The error would begin before the conversion: a label would have been treated as a measured quantity.
During discovery, the product owner places the catalogue record beside the approved drawing. The team asks which value the buyer needs, where it comes from and what the existing designation represents. That question reveals a data requirement the feature request did not mention.
Write the two meanings separately
The agreed first scope retains the commercial designation as Size 50. It adds an outside-width field whose approved source is the 52.4 mm value on the drawing. The model records the measurement and its unit separately from the label.
NIST identifies an inch as exactly 25.4 millimetres. Dividing the approved 52.4 mm by that conversion factor gives about 2.062992 inches. For this fictional catalogue, the product owner chooses a supplementary display of approximately 2.063 in, alongside the original 52.4 mm value and its drawing reference.
The precision choice is a presentation decision for the example. It does not add measurement accuracy, define a tolerance or establish fitness for a particular use. The authoritative drawing and the organisation's technical review continue to govern those matters.
The designer does not rename Size 50 to an inch-based class. The customer can recognise the supplier's established designation while seeing the separate dimension relevant to the question.
Use an incomplete product to test the scope
The supplier also brings P-52, another item in the Size 50 class. Its public record does not yet have an approved outside-width measurement. A convenient implementation might copy 52.4 mm from P-51 or convert the shared class label. Both would invent a product claim.
Instead, the agreed first version retains P-52's designation and shows that the outside width requires clarification. Its enquiry identifies P-52 so the receiving colleague can investigate the actual item. The missing value is not treated as zero or borrowed from the neighbouring product.
That second record changes the delivery estimate too. The work includes a way for the editor to identify missing approved measurements and publish them later. It is not merely a formula added to every row in an existing export.
Review the buyer and editor journeys
| Record or action | Result the reviewer should observe |
|---|---|
| P-51 public page | Size 50 remains the designation; width is separately labelled 52.4 mm and approximately 2.063 in |
| P-51 enquiry | The receiving record identifies P-51 and does not substitute a converted class name |
| P-52 public page | Its designation remains; an unapproved width is not supplied |
| Editor corrects P-51's measurement from a newly approved source | The supplementary conversion follows that measurement, with the source change reviewed |
| Editor changes a descriptive family label | Neither product's measured width changes as an accidental consequence |
In the completed fictional walkthrough, the reviewer can explain why P-51 has a supplementary inch value and P-52 does not. Sales receives the correct item reference from both pages. The editor can see the missing source requirement instead of treating it as a failed calculation.
If the catalogue has multiple languages, each version needs the same distinction between designation and dimension. Suitable reviewers approve the labels and explanations. A translated field name does not change what the underlying quantity represents.
Turn the investigation into a useful brief
The brief now identifies two fields, their source owners, the display convention, the missing-value treatment and the receiving enquiry. It also records what remains outside scope: engineering suitability, new measurement work and automatic conversion of every number appearing in a document.
Bring a similar pair to your own first conversation: one record that appears straightforward and one whose source is incomplete or different. Ask what the person needs to decide, which values are actually measurements and who can approve the meaning. That often provides a firmer basis for a project than a long feature list.
The product information service can develop that structure. Use the short brief to describe the confusing designation or field before committing to a conversion feature.