Glossary
Data uniqueness describes whether an entity is represented without unintended duplicate records within a defined scope. For product data, the scope might be a sellable item, manufacturer part or supplier offer. Defining that unit first is essential: two records can legitimately share a name or describe related products without being duplicates of the same entity.
A uniqueness assessment needs an identity rule. A manufacturer part, a distributor stock item and a supplier offer can have different identifiers and purposes. Treating them as the same record type can make legitimate commercial relationships look like duplicates.
Choose the fields or matching logic used to identify repeated entities. A single attribute may be insufficient when several brands reuse similar codes or the same physical item is sold in different packaging.
A distributor buys the same branded component from two approved suppliers. Its catalogue may contain one product record linked to two supplier offers. Those offers are legitimate records. Creating two independent customer-facing product records by accident could create a uniqueness problem at the catalogue level.
A box of ten components is also different from a single component when the sellable unit differs. The record model must make that distinction explicit before a duplicate-detection rule is applied.
Common values such as colour or material are expected to repeat. Uniqueness therefore does not require every cell in a dataset to be different. Product matching identifies possible shared identities; deduplication resolves confirmed duplicates. Ambiguous matches should be reviewed before records or their relationships are removed.
Explore practical support for organising, improving and maintaining product information.