Audit Catalog Data Quality for Spare Parts
A structured audit playbook for spare-parts catalog data: supersession completeness, applicability coverage, description quality, attribute fill rates, and a scoring method to prioritize fixes.
A spare-parts data audit measures where your catalog stands on the things that cause wrong-part orders, missed sales and customer frustration: supersession gaps, missing applicability data, inconsistent descriptions, empty attributes and unverified cross-references. This playbook gives you the dimensions, the checks, and a scoring method.
The audit is not a one-time project. It is a repeatable process that produces a score, a prioritized fix list, and a before-and-after comparison for the next cycle. Run it quarterly, or whenever a major supplier feed is onboarded.
Audit dimensions
| Dimension | What it measures | Why it matters |
|---|---|---|
| Supersession completeness | % of discontinued parts with at least one REPLACED_BY link | A discontinued part without a successor link = a customer search that returns nothing |
| Chain integrity | % of supersession chains that resolve to an active terminal part | A chain that ends at another discontinued part = a broken lookup |
| Applicability coverage | % of parts with at least one structured fitment record (machine, model, serial range) | A part without fitment data cannot appear in a will-fit lookup |
| Description quality | % of descriptions that follow a consistent structure (type + key attribute + size/specification) | Inconsistent descriptions break search, filtering and deduplication |
| Attribute fill rate | % of key specification fields populated (dimensions, ratings, material, weight) | Empty attributes break filtering and comparison; 'blank' may mean not applicable or just missing |
| Cross-reference accuracy | % of cross-referenced pairs verified against specifications | An unverified cross-reference is a wrong-part risk |
The audit process
- Define the scope
Decide which product groups to audit. A full-catalog audit is ideal but may not be practical in the first cycle. Start with the product groups that generate the most orders, the most returns, or the most customer complaints about wrong parts.
- Export the data
Pull the relevant records: part number, status, description, key attributes, supersession links, applicability records, cross-references. Normalize part numbers and descriptions so comparisons are consistent.
- Run the supersession checks
For every part with status “discontinued” or equivalent:
- Does it have at least one outgoing REPLACED_BY link?
- Does the chain resolve to a part with status “active”?
- Does the chain contain any cycles?
- Are quantity ratios recorded on every link?
- Is the source recorded on every link?
- Run the applicability checks
For every part in the scope:
- Does it have at least one fitment record?
- Are the fitment records structured (make, model, serial range) or free text?
- Are there overlapping serial ranges for the same part and model?
- Are open-ended ranges flagged for review?
- Run the description checks
Sample descriptions across the scope:
- Do they follow a consistent pattern (type + key attribute + spec)?
- Are abbreviations consistent (e.g., always “mm” not sometimes “MM” or “millimeter”)?
- Are there duplicates with different descriptions pointing to the same product?
- Are descriptions machine-readable or free-text narratives?
- Run the attribute checks
For each key specification field:
- What is the fill rate (% of records with a non-empty value)?
- Of the filled values, what is the format consistency (same unit, same precision)?
- Are blanks genuinely “not applicable” for that product type, or are they missing data?
- Run the cross-reference checks
For every cross-referenced pair:
- Do the key specifications match (dimensions, ratings)?
- Is the relationship type recorded (SAME_AS, EQUIVALENT_TO, SUPPLIED_BY)?
- Is the source of the cross-reference recorded?
- Has the pair been verified (auto-matched, human-reviewed, manufacturer-confirmed)?
- Score and prioritize
Score each dimension as a percentage. Prioritize fixes by business impact:
- Order accuracy — supersession gaps, wrong cross-references (highest priority)
- Findability — missing applicability, poor descriptions (medium priority)
- Data maturity — attribute fill rates, format consistency (ongoing improvement)
Scoring template
| Dimension | Metric | Your score | Target |
|---|---|---|---|
| Supersession completeness | % discontinued parts with successor link | — | ≥ 90% |
| Chain integrity | % chains resolving to active part | — | ≥ 95% |
| Applicability coverage | % parts with structured fitment record | — | ≥ 80% |
| Description quality | % descriptions following consistent pattern | — | ≥ 85% |
| Attribute fill rate (critical fields) | % key specs populated | — | ≥ 75% |
| Cross-reference accuracy | % pairs verified against specs | — | ≥ 70% |
The targets are starting points. Adjust them based on your industry, catalog size and the cost of wrong-part orders. A heavy-equipment distributor where a wrong part means a machine down for a week should aim higher than a general MRO supplier.
Common findings
Where Claro fits
Claro runs these checks continuously against the product identity layer. Supersession gaps, broken chains, unverified cross-references and missing applicability records surface as exception queues for the catalog team. The scoring is computed automatically and tracked over time, so each audit cycle shows measurable improvement.
Related
Glossary
Spare Parts Data Glossary
All spare-parts data terms in one table.
Guide
Model supersession chains
Data model, chain resolution, splits, merges.
Guide
Spare parts applicability data
Machine, model and serial range fitment.
Playbook
Build a supersession table from price-list changes
Turn price-list diffs into candidate pairs.
FAQ
What should a spare-parts data audit cover?
At minimum: supersession completeness (do discontinued parts have successor links?), applicability coverage (do parts have machine/model/serial-range fitment records?), description quality (are descriptions structured and consistent?), attribute fill rates (are key specifications populated?), and cross-reference accuracy (do cross-referenced parts actually match on specifications?).
How do you prioritize which data problems to fix first?
Score each problem by business impact: does it affect order accuracy (wrong part shipped), search findability (customer cannot find the part), or pricing (wrong price shown)? Fix order-accuracy problems first, then findability, then pricing. Within each tier, prioritize by volume — the parts ordered most often get fixed first.
Claro
See how Claro handles this in production
This concept is one piece of keeping a catalog trusted. See how Claro resolves identity, enriches missing attributes, and validates every update before it reaches your PIM or ERP.
Learn more