One Product, Five Part Numbers: Why Industrial Product Identity Is So Difficult
Industrial product identity is not fuzzy matching. Learn how MPNs, supplier SKUs, distributor SKUs, packaging codes, replacements, and alternatives relate.
Industrial product identity is hard because the same physical product can appear under many codes, and many similar products can appear under deceptively similar codes. Matching is not simply fuzzy-string matching. It is relationship modeling.
| Identifier | What it may represent |
|---|---|
| Manufacturer part number | The manufacturer's code for a product, variant, kit, or packaging level. |
| Supplier SKU | A supplier's commercial code, often mapped to a manufacturer item but sometimes bundled or renamed. |
| Distributor SKU | The distributor's sellable item, which may include pack size, localization, or channel-specific rules. |
| Previous manufacturer code | A retired or superseded number that still appears in drawings, BOMs, and maintenance systems. |
| Packaging-level code | A carton, case, each, or kit code that changes quantity without changing the underlying product. |
| Customer-specific code | A private cross-reference used by one plant, buyer, or contract. |
| Replacement code | A successor that may be functionally compatible but not identical. |
| Equivalent code | A commercial or technical alternative that satisfies some use cases but requires validation. |
The critical distinctions
The matching question is not “Are these strings close?” It is “What relationship exists between these records?” They may be the same product, a variant of the same product, a compatible product, a replacement product, or a commercial alternative. Each relationship has different operational consequences.
If two records are the same product, they should be deduplicated into one canonical record. If one is a variant, it must remain distinct. If one is compatible, it may be recommended in a specific context. If one replaces another, demand should route forward while preserving history. If one is a commercial alternative, procurement may need approval before substitution.
Why Claro starts with identity
Enriching the wrong identity makes the catalog worse. Claro resolves product identity first, then enriches, validates, and writes back the canonical record with relationship types preserved. That is how teams avoid merging variants, missing replacements, or buying a new supplier’s part when the same product already exists elsewhere.
Claro
See where your catalog breaks — free
Claro runs this automatically: resolve identity, fill missing attributes, validate updates, and write clean records back into your PIM/ERP. Upload a sample supplier file for a free catalog audit.
Get a free catalog audit