Part numbers and measurements that disagree across systems
By Jason MurphyPublished 4 min read
By Jason MurphyPublished 4 min read
The short answer
Part numbers and measurements disagree across systems because one item carries several identifiers and several valid ways to state a size. A manufacturer part number, a distributor SKU, a GTIN and an ERP code can all be correct and still not match, and a nominal dimension is not an actual one. A checked record states which is which.
A single product usually has more than one legitimate name, each assigned by a different party for a different job.
Most mismatches are not errors in a single place. They are transformations between places.
A dimension is not a number. It is a number, a unit and a basis, and the same product can truthfully carry different values on different bases.
The record below is invented to show structure. It is not data about any product or company.
item: Casement window unit, series ABC
manufacturer_part_number: ABC-3040-R2 (source: data sheet, rev 2, confirmed 2026-04-02 by engineering)
distributor_sku: D-ABC30R2 (source: distributor catalog export, 2026-09-18)
gtin: not assigned (sold as a configured unit)
unit_width: 36 in, basis: frame, tolerance: +/- 1/8 in
rough_opening_width: 36 1/2 in, basis: opening (source: installation guide, rev 2)
supersedes: ABC-3040-R1 (source: engineering change notice)
status: activeA person reading a catalog infers which number is meant from context. A purchasing agent or an assistant comparing three suppliers has to decide whether two values are the same quantity. If one source gives the frame width and another the opening, the comparison treats a real difference as an error, or an error as a difference. Either way a buyer receives a wrong answer with the confidence of a precise one.
The remedy is not to force one number everywhere. It is to record each identifier and each measurement with its kind, its basis, its source and its date, and to state the mapping between them: which SKU points to which part number, which dimension is on which basis, which part supersedes which. The manufacturer owns the engineering values and the part number. The distributor owns its SKU and the cross-reference to it. The record states that order, and a comparison against every copy shows where a system has drifted. See dealer network data governance.
Different parties assign different identifiers to one item, and a dimension can be stated on different bases, such as nominal or actual and unit or opening.
A part number identifies the part as designed. A GTIN identifies a specific packaged unit, so one part can have several.
As a value with a unit, a basis and a tolerance where one applies, with the source and date. A bare number is ambiguous.
The party that assigns the identifier owns its side of the mapping. The distributor owns its SKU and the pointer to the manufacturer part number.
Labs · Field notes
Labs · Field notes
Business Truth
A spec is copied six times before anyone reads it. Each copy is a chance to change it.
Product data3 min read
The record of what a company sells, with a source and a confirmation date on every fact.
Product data3 min read
Assistants do well with specs stated in text, and badly with values that depend on the configuration, lapsed approvals and series names only your reps know.
Product data3 min read
A dealer network disagrees with itself by design. The fix is deciding, per fact, who wins.
Dealer and channel data3 min read
Markup tells software what a value is. A source and a date tell it whether to believe it. The vocabulary has room for both.
Product data3 min read
AI can read a public PDF. It is slower to trust an undated one two clicks from the page. Put the key facts in text and keep the PDF as proof.
Product data3 min read
One email a week: what we asked the AI, what it got wrong, and how we checked.
Our research reaches 17,000+ followers across our channels. Upstream is the weekly version.
Weekly. Unsubscribe anytime. Privacy