Skip to content

Systems and records

Industrial parts cross reference data: suggested match or verified fit?

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

Treat each cross-reference as a claim with a source, an authority and an application, and label it by the strongest evidence behind it: suggested, attribute equivalent, declared interchange, authority approved, verified in service or rejected. A suggestion only says two parts look alike. Verified compatibility needs an approval from the right authority or a recorded installation that performed, and customer substitution terms can still require sign-off.

Checklist

Industrial parts cross

This page covers industrial parts cross reference data: suggested match or verified fit.Illustrative

Key takeaways

  • A cross-reference says two parts are listed as equivalents; it does not say who confirmed fit or for which installation.
  • Label every match with the strongest evidence behind it, from suggested to verified in service, and let a fit return demote it.
  • The authority that can declare fit depends on the application, and in regulated settings such as aviation it is set by rule.
  • Customer substitution terms can require approval even for a well-evidenced match, so grade the agent's action as well as its label.
  • Returns coded wrong part, substitution approvals and quote notes are the records that make cross-reference history valuable as data.

How should a service task tell a compatibility suggestion from verified compatibility?

Treat every cross-reference as a claim with a source, an authority and an application, and label it with the strongest level of evidence that actually supports it. A suggestion from a lookup table or a matching model says two parts look alike. Verified compatibility says someone with the authority to decide confirmed that the candidate works in this specific application, or that it was installed and performed. The two are different facts, and a record, a model or an agent should never upgrade one into the other.

That distinction is what makes industrial parts cross reference data useful for AI. A distributor's archive of cross-references, substitutions, quotes and returns can train a model to propose candidates, but it can only teach the model to say compatible when the records carry the evidence behind each match. This page sets out an evidence ladder, an authority map and a field-level evaluation set that a distributor or service business can build from its own records.

It is written for owners and operations leads at distributors, repair shops and maintenance providers who hold this history and want to know what it is worth as data, and what has to be in it first.

Why is a matching table not a fitment record?

Cross-reference tables say which part numbers are offered as equivalents; they do not say who confirmed the equivalence or for which installation. Attribute matching makes the gap easy to miss, because two parts can share every cataloged attribute and still differ in a tolerance, a material, a seal type or a revision that matters in service.

Classification standards make attribute comparison possible but do not settle fit. ETIM International describes its model as product classes, each with its own set of features that describe technical characteristics, recorded as alphanumeric, logical, numeric or range values. Two parts in the same class with the same feature values are a strong candidate pair, and that is all.

The automotive aftermarket separates the two explicitly. The Auto Care Association describes ACES as the industry standard for managing and communicating product fitment data, and its FAQ says the standard is not a source of application data: a company has to research or obtain its own fitment data. A standard file format moves a claim between trading partners; it does not create the evidence behind the claim.

Identity also drifts. GS1's GTIN Management Standard requires a new GTIN for certain product changes, including a change of more than 20% to a physical dimension or to gross weight. Smaller changes can keep the same identifier, so a cross-reference recorded years ago may point to a part number whose physical item has since been revised.

Which authority can declare two parts compatible?

The authority depends on the application, and in regulated settings it is defined by rule. In U.S. aviation, 14 CFR 21.9 restricts producing a replacement or modification article that is reasonably likely to be installed on a type-certificated product unless it falls under a listed basis, such as a production approval or a standard part made to an established specification, and bars a producer from representing other parts as suitable for installation. FAA Advisory Circular 20-62E says the installer must determine that an article is eligible for installation before returning the product to service.

Government supply catalogs record their own judgment. The Defense Logistics Agency describes the interchangeability and substitutability portion of its PUB LOG data as a reference source for determining whether items of supply are interchangeable or substitutable. That is an authority's recorded decision, not a distributor's inference.

Most industrial cases sit outside these regimes, and the authority is the equipment manufacturer, the part manufacturer's published interchange, the customer's engineer or the person who signs off the repair. Record which of these spoke for each match. A distributor's own sales experience is real evidence too, but it is evidence of performance in past applications, not a declaration of fit for a new one.

Which authority can declare two parts compatible?
AuthorityWhat it can establishTypical recordWhat it cannot establish
Equipment manufacturerApproved parts for its own equipmentParts manual, service bulletin, superseded part listFit of parts it never evaluated
Part manufacturerIts own published interchange with other numbersInterchange sheet, catalog noteFit in a specific installation
Regulator or approval holderEligibility for installation in a regulated productProduction approval marking, approval tag, eligibility recordAnything outside the approved scope
Customer engineer or approverAcceptance for that customer's applicationSigned substitution approval, engineering changeFit for other customers
Government catalogRecorded interchangeability or substitutability between itemsI&S relationship on a stock numberCommercial items outside the catalog
Distributor experienceThat a substitute was sold and not returned for fitOrder, delivery and return historyThat it is approved or will fit elsewhere

Which evidence level does each match earn, from suggestion to verified fit?

Every cross-reference in the dataset gets one label from this ladder, chosen by the strongest evidence attached to it. The labels are cumulative only where the evidence is: a verified-in-service match without an authority record stays at that level, and an authority declaration with a later fit return drops to rejected for that application.

When evidence conflicts, the most specific record wins for its own application. A manufacturer interchange sheet that lists two numbers as equivalent is level 2 in general, but a documented fit return from a particular machine makes the pair rejected for that machine while leaving the general label alone. Keep both facts in the case rather than averaging them into a confidence score, because the next customer's application is what decides which one applies.

Evidence also ages. Set a review date on every label at level 2 or above, and attach the part revision the evidence refers to. When a manufacturer issues a new revision or the item gets a new identifier, the label falls back to the level supported by evidence for the new revision, which is often level 1 until someone checks.

Which evidence level does each match earn, from suggestion to verified fit?
LevelLabelMinimum evidenceWhat a model or agent may say
0SuggestedLookup table, text similarity or model output onlyPossible candidate; needs checking
1Attribute equivalentKey class features match on recorded valuesMatches on listed attributes; fit not confirmed
2Declared interchangeManufacturer or catalog interchange naming both numbersListed as interchangeable by the named source
3Authority approvedApproval record from the authority for this applicationApproved for this application by the named authority
4Verified in serviceInstalled in the stated application with no fit return or failure in a defined windowHas worked in this application
RRejectedFit return, failed inspection or approver refusalDoes not fit this application; reason recorded

What should the compatibility evidence and authority evaluation set include?

Each case in the evaluation set is a request for a substitute, the candidate offered, the evidence linked to it and the outcome. The fields below are enough to grade both a matching model and an agent that answers customers, and they map onto records most distributors already hold in an ERP such as Epicor Prophet 21, Infor or NetSuite, a quoting tool and a returns system.

At a glance

What should the compatibility evidence and authority evaluation set include

Build the set to include hard cases on purpose: candidates that match every listed attribute but were returned, superseded part numbers, and requests in regulated applications where only an authority record should move the label above level 2.

Draw cases from real requests rather than from the cross-reference table alone. Quotes where a substitute was offered, orders where it shipped and returns where it came back give each case a request, a candidate and an outcome; a table entry by itself gives none of those. Split the set by date so the newest requests are held out, which tests whether a model generalizes to parts and applications it has not seen rather than memorizing old pairs.

Have two people label a sample of cases independently against the ladder, and resolve disagreements by tightening the minimum evidence rule for that level rather than by vote. Disagreement usually means a level is defined loosely, for example what counts as a defined window for verified in service, and the fix belongs in the ladder, not in the individual case.

What should the compatibility evidence and authority evaluation set include?
FieldContentWhy it matters
Case boundaryOne request, one source part, one candidate, one applicationPrevents mixing evidence across installations
Application contextEquipment, model, operating conditions, regulated or notFit is defined per application
SpecificationClass, feature values and revision for both partsSupports level 1 and exposes revision drift
Claim source and authorityWho asserted the match, with document linkSeparates suggestion from declaration
Service termsCustomer approval rules or contract substitution clausesSome customers forbid substitution without sign-off
ApprovalsApprover name or role, date, scopeRequired for level 3
DatesRequest, quote, delivery, install, return datesMeasures evidence maturity
OutcomeKept, returned for fit, returned for other reason, failedGrounds level 4 and R
Gold labelLadder level and the evidence that justifies itWhat the model is graded against

When do a customer's substitution terms override a strong match?

The deciding link is usually the customer's substitution terms, not the part data. Some supply agreements and purchase orders require written approval before a substitute ships, and some customers prohibit substitution entirely on named parts. In that case a level 2 interchange is not enough to ship, and the correct agent action is to request approval, whatever the match quality.

Grade the agent on the action as well as the label. A correct answer states the level, names the source and, where terms require it, routes the request to the approver. An answer that says compatible on level 0 or 1 evidence is wrong even when the candidate later turns out to fit, because it claimed an authority it did not have.

Score separately for over-claiming and under-claiming. Over-claiming, stating a higher level than the evidence supports, is the costly error in service work, since it can put an unsuitable part into a machine. Under-claiming, such as hiding a level 4 match behind vague wording, costs sales and time but not safety. A model that is tuned on a single accuracy number will trade one for the other without anyone noticing.

How are three illustrative bearing substitutes labeled when one has a different seal?

This example is illustrative; the counts and durations are invented to show the method. A maintenance customer asks a distributor for a substitute for a discontinued sealed ball bearing on a food-plant conveyor. The cross-reference table returns three candidates with identical bore, outside diameter and width.

The evaluation set records each candidate separately. Candidate one is listed in the original manufacturer's interchange sheet and was sold to the same plant twice in the past year without a return, so it is level 4 for this application. Candidate two matches every dimension but uses a different seal material; one past sale to another plant was returned within 10 days with the reason code wrong part, so for that application it is rejected and here it stays level 1. Candidate three is level 0, a text match with no attributes recorded for its seal or clearance.

The exception is the one that teaches most. The plant's supply agreement requires its maintenance engineer to approve any substitute on food-contact lines. Even candidate one cannot ship without that approval, so the gold action for the agent is to propose candidate one with its evidence and request sign-off.

How are three illustrative bearing substitutes labeled when one has a different seal?
Candidate (illustrative)Evidence linkedGold labelGold agent action
Candidate oneManufacturer interchange; 2 prior sales to this plant, 0 returns in 90 daysLevel 4 for this applicationPropose with evidence; request engineer approval
Candidate twoDimensions match; different seal; 1 fit return elsewhere in 10 daysLevel 1Mention only as unverified; do not recommend
Candidate threeText match onlyLevel 0Do not present as an option
Any candidateNo engineer approval on fileNot shippableRoute to approver before quoting as a substitute

Which substitute requests belong with a specialist rather than the ladder?

Stop and escalate whenever the application is regulated, safety-related or covered by a customer approval requirement, and the evidence is below level 3. Aviation parts, pressure equipment, lifting gear, electrical protection and medical or food-contact equipment all carry rules or customer terms that decide who may approve a substitute. The dataset can record those decisions; it cannot make them.

There is a useful exception at the other end. Commodity items made to a published dimensional or material standard, such as many fasteners, fittings and standard bearings, can reasonably sit at attribute equivalent with a standard reference attached, and that is often all the application needs. Even U.S. aviation rules list standard parts made to an established industry or government specification among the permitted bases. Record the standard and its edition with the case, so the label shows why attribute evidence was enough.

Narrow the claim when evidence is old or the part has been revised. A level 4 label earned on a revision that has since changed should drop back until it is re-verified. The limits of this design are real: return data undercounts fit problems that customers fix on site without returning anything, and a missing return is weaker evidence than a recorded inspection. A specialist service operator should review the ladder thresholds for each product family, and a rights reviewer should confirm which manufacturer content can be included.

Which substitution records make cross-reference history licensable?

The records that make this evaluation set valuable are the ones distributors often discard as noise: substitution approvals, quote notes explaining why a candidate was rejected, returns coded wrong part, and links between a request and the equipment it was for. Kept together and dated, they turn a cross-reference table into evidence a model can learn the difference from. Manufacturer interchange content and syndicated catalog data usually come with their own license terms, so they are separated from the distributor's own records before anything is offered.

Distributors that license their own substitution and return history through SourceX hand over the qualification, rights review, contract, preparation, delivery and payment steps, while the scope stays theirs: no record ships until the distributor has approved the scope and terms and signed. A short company assessment, with no part data uploaded, shows whether the business qualifies in the first place.

Frequently asked questions

Is a cross-reference the same as an interchangeable part?

No. A cross-reference says a source lists two part numbers as equivalents or candidates. Interchangeability is a judgment that one part can replace another in a given use, made by someone with authority for that use. Record which one you have and who said it.

What counts as verified compatibility in distributor records?

Either an approval from the authority for that application, such as the equipment maker or the customer's engineer, or evidence the part was installed in that application and performed without a fit return or failure over a defined window. Both should be linked to the case with dates.

Can attribute matching on ETIM or similar classes prove fit?

It shows that two parts share the recorded feature values for their class, which makes them strong candidates. It cannot cover tolerances, materials or revisions that the class does not record, or the conditions of a specific installation. Label it attribute equivalent, not compatible.

Do aviation parts follow different rules?

Yes. In the U.S., 14 CFR 21.9 limits who may produce replacement articles for type-certificated products and how they may be represented, and FAA guidance in AC 20-62E puts the eligibility determination on the installer. Data about such parts should record the approval basis, and a qualified person makes the call.

What distributor records make cross reference data worth licensing?

Cross-references linked to the request, the application, the approval and the outcome. Returns with reason codes, substitution approvals and quote notes are often the scarce part. Records whose content belongs to a manufacturer or catalog provider need a rights check first.

Sources

  • The Auto Care Association describes ACES as the aftermarket industry standard for managing and communicating product fitment data. Source
  • The Auto Care Association FAQ says ACES is not intended as a source of application data, so companies must research or obtain their own fitment data. Source
  • ETIM International's model assigns each product class its own features describing technical characteristics, typed as alphanumeric, logic, numeric or range. Source
  • GS1's GTIN Management Standard requires a new GTIN when a physical dimension or gross weight changes by more than 20%. Source
  • 14 CFR 21.9 restricts production of replacement articles reasonably likely to be installed on type-certificated products to listed bases and limits representing other parts as suitable for installation. Source
  • FAA Advisory Circular 20-62E says the installer must determine that an article is eligible for installation before returning the product to service. Source
  • DLA describes the interchangeability and substitutability portion of PUB LOG as a reference source for determining interchangeability or substitutability of items of supply. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies