Knowledge hub · definition

How Spare Parts Compatibility Data Should Be Structured

Spare parts compatibility data describes the relationship between a part and the machines, models, assemblies or configurations in which that part can be used.

It is not simply another product attribute: it is relational data connecting one product record to one or more application contexts. For ecommerce, this data helps a buyer move from “I have this machine” to “show me parts that fit it.”

For enrichment, it creates a high-risk area where unsupported assumptions should never be published as fact.

Relational, not attributive HIGH RISK
Part record → Application context
{{ r.name }} {{ r.note }}
A wrong relationship leads directly to a wrong purchase decision. 10 sections
Machine and model relationships

Identify the machine clearly enough to distinguish similar families

Depending on the catalog, that may involve manufacturer, machine type, model, generation or another approved identifier.

The relationship should be stored separately from marketing text so the same verified compatibility can support product pages, filters and downstream exports.

Machine-side identity layers ONE VERIFIED SOURCE
{{ r.num }}
{{ r.name }} {{ r.note }}
One relationship serves three consumers
{{ c.label }}
{{ st.label }}

{{ c.title }}

{{ c.text }} {{ c.tag }}
Target schema follows the customer catalog: part → machine family/model relation → evidence/source → validation state
Identifiers

Identifiers anchor both sides of the relationship

Part-side references can include MPN or OEM number; machine-side references can include model names or internal machine identifiers used by the catalog.

Compatibility should not be created only because two pages contain similar product names.

Part side · machine side NO TEXT MATCHING
Part-side reference Machine-side reference
{{ r.left }} {{ r.right }}
Similar product names are not evidence of fitment.
Model, year and version issues

The same model family name can cover incompatible configurations

Technical products change during a model lifecycle. A part that fits one version may not fit every year or configuration carrying the same model family name.

If the source does not provide enough detail to resolve those differences, the relationship should remain incomplete or require review rather than be generalized across the entire model range.

One model family · four production ranges NEVER GENERALIZED
{{ r.model }} {{ r.range }} {{ r.status }}
Two ranges verified, one unresolved, one excluded — not one blanket claim for the family.
Entity · example field · purpose REFERENCE DATA MODEL
Entity Example field Purpose
{{ r.key }} {{ r.val }} {{ r.use }}

{{ c.title }}

{{ c.text }}
Compatibility is published only when the part identity and machine relation are supported by evidence; ambiguous relations are held for review Product data validation
Ecommerce filters

Machine-based filters without parsing free text at query time

Once compatibility is structured, ecommerce can expose machine-based filters or guided selection.

The filter hierarchy should mirror the actual data model and avoid creating selectable combinations that have not been verified.

Guided selection · mirrors the data model VERIFIED ONLY
{{ r.step }} {{ r.label }} {{ r.field }}
Unverified combinations are never selectable.
Agriculture example

One component across several models, and near-identical parts that differ

Agricultural spare parts are a strong use case because one component may be marketed across several tractor or harvester models while apparently similar parts can differ by dimensions or machine generation.

AC820825 shows the pattern: one part record, verified Optima / Optima HD relations and source evidence kept alongside the fitment claim.

Part → verified models → evidence AC820825 FITMENT EXAMPLE
{{ r.step }}
{{ r.name }} {{ r.val }}
Every model in the list needs its own source evidence.
{{ r.a }} {{ r.tag }}
Keep reading

Related guides on identifiers, fitment and validation

See How It Works

Talk to ENRIVAQ

Request a catalog assessment

Tell us enough to make the next step useful for your catalog.