Skip to main content
← All guides

Data quality & completeness

What "complete" means for a product record

The Smart Station team8 min read

Ask three people in the same business whether a product record is complete and you will get three answers. That is not a failure of communication. It is a genuine absence of a definition, and until somebody makes the decision explicit, the question cannot be answered.

Completeness is a decision, not a fact. Making that decision is most of the work.

Why there is no universal standard

A complete record for a t-shirt and a complete record for a variable-speed drive have almost nothing in common. The t-shirt needs a good photograph, a size chart and a fabric composition. The drive needs a power rating, a supply voltage, an enclosure rating, a datasheet, a wiring diagram and a compliance certificate — and the photograph barely matters.

Any vendor offering you a universal completeness standard is offering you somebody else's decision. It will be wrong for at least half your catalogue.

Defining it per category

The workable unit is the category, because within a category buyers ask the same questions. Work through your top categories by revenue and, for each, answer one question: what does a buyer need to know before they will commit?

Ask the people who take the calls. Counter staff and internal sales know exactly which question comes up every time, because they answer it every time. That question is a required field.

CategoryAlways requiredCategory-specific
Cable glandsTitle, image, short and long descriptionThread size, IP rating, cable range, material
Power suppliesTitle, image, short and long description, datasheetOutput voltage, current, mounting, input range
EnclosuresTitle, image, short and long description, drawingExternal dimensions, IP rating, material, door type
ConsumablesTitle, image, short descriptionPack quantity, unit of measure

Note that the consumables row is deliberately shorter. Requiring a datasheet on a box of cable ties makes the rule unenforceable, and an unenforceable rule gets ignored across the whole catalogue rather than just where it does not apply.

The minimum viable product record

Separate from category rules, there is a floor below which a product should not be published at all. For most technical distributors that floor is:

  • A title containing the manufacturer part number
  • One image that shows the actual product
  • A short description that would let somebody identify it
  • A correct category and brand
  • A price, or an explicit enquiry path

Everything else is a category decision. This floor is a publishing gate.

Writing rules people follow

Three properties separate a rule that is followed from one that is quietly ignored.

It must be checkable without judgement. "Has a datasheet" is checkable. "Has a good description" is not, and will be scored differently by every person who looks at it.

It must be visible where the work happens. A standard in a document nobody opens is not a standard. The rule needs to show up as a score on the record itself, naming the specific missing fields.

It must be achievable. If a rule cannot be satisfied for a whole brand because the manufacturer simply does not publish that attribute, the rule is wrong, not the data. Fix the rule.

The test of a completeness standard is not whether it is thorough. It is whether, six months later, anybody is still applying it.

Once the definition exists and is being scored automatically, something useful happens: "our product data is a mess" becomes "Delcon is at 46 percent and 781 products are missing datasheets". The first statement generates anxiety. The second generates a work queue.

Common questions

What makes a product record complete?
Whatever your buyers need in order to commit, decided per category. There is a universal floor — a title containing the manufacturer part number, one image of the actual product, a short description, a correct category and brand, and a price or an explicit enquiry path — and everything above that floor is a category-by-category decision.
Should every product have the same required fields?
No. Requiring a datasheet on a box of cable ties makes the rule unenforceable, and an unenforceable rule gets ignored across the whole catalogue rather than only where it does not apply. Set a low universal floor and define the rest per category.
How do you measure product data completeness?
Score every record automatically against the rules for its category and name the specific missing fields on the record itself. A standard that lives in a document nobody opens is not a standard.

Where to next

Who wrote this

The Smart Station team

Written by the engineering and delivery team at Smart Station (Pty) Ltd, the South African software company that builds GetShopSync. The material here comes from building catalogue systems for distributors — it is what we have measured and what we have got wrong, not a survey of the literature.

See it against your own catalogue.

Thirty minutes. Bring three supplier URLs and we will capture them live, so you are judging the output rather than the pitch.