Product-data field notes · Fictional worked examples

When the source files disagree, keep the conflict visible.

A newer-looking file is not automatically a better source. Match the exact product and measurement basis, preserve the conflicting evidence, and resolve the fact before using it in a repair.

One item, two different measurements.

The following records are fictional. Both files mention SKU NOV-24. One states the product’s overall width; the other lists a carton width. Treating the figures as competing product specifications creates a conflict that did not need to exist.

RecordExact statementMeasurement basis
Product sheet ANOV-24 overall width: 610 mmProduct
Shipping sheet BNOV-24 carton width: 680 mmPackaging

Identity and context come before confidence.

A repair needs an evidence chain: the item identifier, the source location, the quoted fact and the field being changed. A model’s confidence score cannot substitute for one of those pieces.

If two exact-item sources really disagree about the same measurement, keep both passages and require a decision. Do not average the values, choose the larger number, infer an undocumented revision, or quietly copy a sibling model.

  • Use the exact item or variant identifier, including meaningful suffixes.
  • Distinguish the product from its packaging and required installation space.
  • Preserve units and the original source wording in the evidence ledger.
  • Record the reason and authority for a customer decision.

A supplied source is evidence to review, not an authenticated fact.

Specstead can verify that a proposed passage is present in the submitted source and associated with the supplied item. That does not establish that the document is genuine, current, complete or approved by the manufacturer.

Only submit source material you are entitled to use. Resolve uncertain product facts with the responsible supplier before accepting a change. The review remains self-service, and unresolved facts stay out of the accepted repair.

Inspect an example, then check your own family.

Download the fictional catalogs, exact-item records and expected reviews. The preliminary fit checker helps separate a supported repair from a task that needs another workflow.

The free preflight checks whether your CSV fits Specstead’s supported scope. It does not change your file or store. Source-backed proposals and customer decisions follow in a private workspace.

Start with the free check See input requirements

Sources and method.

Examples on this page are invented to explain review decisions. They are not customer results or measured platform tests. Guidance checked 2026-10-11; Specstead’s implemented scope is described in the file guide.

All product-data guides · File and evidence requirements