Glossary
Data completeness describes whether the records and values required for a particular purpose are present. In a product catalogue, it asks whether each applicable product has the information needed for its category, market and stage of use. A populated field contributes to completeness only within the defined assessment; its presence does not establish that the value is correct.
A completeness check starts with a scope: the products being assessed, the applicable attributes and the use being supported. A technical buying guide may need different information from a warehouse receiving process. Optional fields and attributes that do not apply should not silently inflate the number of missing values.
Keep missing, unknown and not applicable distinct. A placeholder such as "TBC" might occupy a field while leaving the actual information unavailable. Decide how those cases are counted before comparing results.
Suppose a distributor requires voltage, power, mounting type and dimensions for each motor in a new range. A record with three of these four values is incomplete for that agreed check, even if its marketing description is long. A separate record might contain all four fields but lack a document required for another purpose.
The check should identify the missing attribute and responsible team, rather than report only a single catalogue percentage. Report the population and requirements alongside any score so changes in scope remain visible.
A fully populated record can contain the wrong voltage or an obsolete drawing. Accuracy, validity and timeliness therefore need their own checks. Completeness also differs from final channel readiness, which can include image requirements, approval status and other destination rules.
Explore practical support for organising, improving and maintaining product information.