Spare Parts Applicability Data: Machine, Model and Serial Range
Applicability data says which machines, models and serial-number ranges a part fits. This guide covers the data model, the common problems (open-ended ranges, mid-serial changes, overlapping fitment), and what a clean applicability record needs.
Applicability data records which machines, models and serial-number ranges a part fits. It answers “does this part work in my equipment?” — the question behind every will-fit lookup, fitment selector and service BOM filter. Getting it wrong means a customer receives a part that does not fit their machine, and getting it right requires more than a model name.
A customer calls and says, “I need the hydraulic pump for my XR-700.” The XR-700 was produced from 2015 to 2023. In 2019, the manufacturer switched to a different pump at serial number XR700-42000. The customer’s machine is serial XR700-38500 — so they need the old pump, not the new one. If the catalog only stores “fits XR-700” without the serial range, the customer gets a 50/50 chance of receiving the right part.
What applicability data carries
A complete applicability record connects a part to the equipment it fits, at a level of detail that resolves mid-production changes:
| Field | Purpose | Example |
|---|---|---|
| Part identity | Which part this record is about | HY-3200 (hydraulic pump) |
| Equipment make | The manufacturer of the machine | Illustrative Equipment Co. |
| Equipment model | The model line | XR-700 |
| Model variant | Sub-variant or option package, if applicable | XR-700T (turbocharged) |
| Serial range start | First serial number where this part applies | XR700-10001 |
| Serial range end | Last serial number (or 'open' for no upper bound) | XR700-41999 |
| Year range | Production years, if serial range is unavailable | 2015–2019 |
| Effective date | When this fitment record was established or last confirmed | 2024-01-15 |
| Source | Where the fitment data came from | OEM parts book rev. 3, page 47 |
| Verified | Whether the record has been checked against the manufacturer's documentation | Yes |
The common problems
Open-ended serial ranges
Many fitment records say “from serial 42000 onwards” without an upper bound. That works until the manufacturer makes another mid-serial change at serial 58000. Open-ended ranges must be revisited whenever a new engineering change is announced — or they silently become wrong.
Serial-number format inconsistencies
Manufacturers do not follow a universal serial-number format. Some use pure numbers (42000), some use prefixed alphanumeric codes (XR700-42000), some include year codes or plant codes. Comparing serial ranges across records requires normalization — and the normalization rules are manufacturer-specific.
Mid-serial engineering changes
The hardest case: a manufacturer changes a component mid-production without changing the model name. The boundary is a serial number, not a model year. If the catalog’s applicability model only supports model-level fitment, there is no way to represent the break point. The customer’s serial number falls on one side or the other, and the catalog cannot tell which.
Overlapping fitment
Two parts may both list “fits XR-700” with overlapping serial ranges. This can be legitimate (a running change where both parts were used during a transition period) or a data error (duplicate records with inconsistent ranges). Without overlap-detection logic, the catalog returns both parts and the customer guesses.
Missing fitment data
Some parts — fasteners, seals, standard bearings — fit many machines but have no formal fitment table. The catalog either omits them from will-fit lookups (making them unfindable by equipment) or assigns them a broad “universal” applicability that dilutes search results.
The applicability data model
Applicability is a many-to-many relationship between parts and equipment configurations. A part fits multiple machines; a machine uses multiple parts. The relationship carries attributes (serial range, source, verification status) that belong to the link, not to either end.
| Entity | Key attributes |
|---|---|
| Part | Part ID, description, status, supersession chain |
| Equipment | Make, model, variant, serial-number series, production years |
| Fitment (the link) | Part ID, equipment ID, serial range start, serial range end, source, effective date, verified flag |
The fitment link is where the serial-range data lives. Putting it on the part record or the equipment record forces a flat structure that cannot represent mid-serial changes or overlapping ranges cleanly.
Before and after
| Before | After |
|---|---|
| Fitment stored as a free-text note: 'fits XR-700' | Fitment stored as a typed record with make, model, serial range, source and verification status |
| No way to represent mid-serial changes | Serial range start and end on every fitment link, with open-ended ranges flagged for review |
| Overlapping records not detected | Overlap detection surfaces conflicting fitment records for review |
| Source of fitment data unknown | Every fitment record carries a source: OEM parts book, supplier feed, field-service report |
Where Claro fits
Claro connects applicability data to the product identity layer. When a fitment record references a part number, Claro resolves it to the canonical product identity — including supersession, so a discontinued part’s fitment record can surface the current successor. When a manufacturer issues an engineering change that shifts the serial boundary, the update propagates through every affected fitment record.
Related
Glossary
Spare Parts Data Glossary
All spare-parts data terms in one table.
Guide
Parts book data model
How to structure the data behind a parts book so it stays current.
Playbook
Audit catalog data quality for spare parts
A structured audit covering supersession, applicability, descriptions and completeness.
Glossary
What is supersession?
When a manufacturer replaces one part number with another.
FAQ
What is applicability data in a spare-parts catalog?
Applicability data records which machines, models, and serial-number ranges a part fits. It answers the question “does this part work in my equipment?” and is the basis for will-fit lookups, online fitment selectors, and bill-of-material filtering.
Why are serial ranges so hard to get right?
Because manufacturers introduce engineering changes mid-production run, so the boundary between “old part” and “new part” falls at a serial number, not a model year. Open-ended ranges, format inconsistencies, and mid-serial changes create ambiguity that a flat spreadsheet cannot resolve cleanly.
What does a clean applicability record need?
At minimum: the part identity, the machine or equipment identity, the model or variant, the serial-range start and end (or “open” if no upper bound), the effective date, the source of the fitment data, and a flag for whether the record has been verified against the manufacturer’s documentation.
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