Part Number Cross-Reference: How to Find OEM and IAM Equivalents

Pick any common spare part — an oil filter, a brake disc, a wheel bearing — and count how many different part numbers exist for it. For a Nissan Juke front brake disc, there are at least five: the OEM number from Nissan, and equivalents from Brembo, Bosch, ATE, and TRW. Same part. Same dimensions. Same fitment. Five completely independent numbering systems that never agreed to talk to each other.

A part number cross-reference is the bridge between them. It answers the question: "I have this number — what else refers to the same thing?" Whether you are a mechanic sourcing a replacement, a distributor filling a purchase order, or a catalog manager building a searchable inventory, cross-reference is the lookup that makes any part number useful regardless of which system it came from.

Why the same part has so many numbers

There is no universal part numbering standard in the automotive industry. Each vehicle manufacturer assigns its own part numbers in its own format — Nissan uses formats like 402061KA3B, BMW uses 34116792224, Toyota uses 04465-42160. These numbers are anchors in the OEM catalog, linked to specific vehicles, models, and production years.

Every IAM manufacturer — Bosch, Brembo, NGK, Mann, TRW, Febi, ATE, and hundreds of others — builds their own catalog in their own format, with their own part numbers assigned by their own engineering teams. Bosch numbers look different from Brembo numbers. TRW numbers look different from ATE numbers. None of them map to OEM numbers automatically.

Then there is the historical layer. OEM part numbers get superseded. A brake disc for a 2010 Nissan Juke might have been produced under one number, then superseded to a second number when a running design change was introduced. Both numbers refer to the same part fitment, but only the active number appears in the current dealer catalog. The superseded number still appears on old boxes, old orders, and old workshop records — and buyers searching it still need to be able to find the active replacement.

A real example: one part, many numbers

The front brake disc for a Nissan Juke 2010–2019 (1.6L, non-ST, front axle) illustrates how this multiplies in practice:

Six numbers. One part. If you search any one of those numbers in a well-built spare parts catalog with complete cross-reference data, you should find the same product — or at least be able to see that an equivalent is available under a brand you carry.

How to look up a part number cross-reference

Step 1: Start with the number you have

It does not matter whether you have an OEM number, an IAM number, or a number from a box with no obvious brand attribution. A cross-reference lookup works bidirectionally — OEM to IAM, IAM to OEM, IAM brand A to IAM brand B. Enter the number you have.

Step 2: Clean the number before searching

Part numbers are formatted inconsistently across systems. The same number may appear as 0986479A28, 0 986 479 A28, or 0-986-479-A28 depending on the source. Before concluding a number yields no results, strip all spaces, dashes, and dots and search the raw string. Most cross-reference databases normalize on the backend, but not all do.

Step 3: Validate the match against vehicle fitment

A cross-reference result shows you equivalent part numbers. Before using or selling a cross-referenced part, verify the fitment — make, model, year range, engine variant, and fitting position — matches your vehicle. A false cross-reference (two different parts incorrectly linked) is rare in quality databases but does occur, especially for parts that went through a design change at some point in their production history.

Step 4: When no cross-reference exists

Not every part has a published cross-reference. For very new parts, niche OEM components, or parts where IAM manufacturers have not yet tooled up to produce an equivalent, the cross-reference database may return nothing. In these cases, the vehicle application data is your fallback: look for parts that share the same make, model, year, position, and technical specification — that is the same logic cross-reference databases use to build their mappings in the first place.

OEM to IAM: the most common lookup direction

The most frequent cross-reference lookup is OEM → IAM: you have the manufacturer's part number from a workshop manual or a dealer quote, and you want to find a less expensive aftermarket equivalent.

This direction is well-supported by most IAM manufacturers, who publish their own cross-reference tables linking their part numbers to OEM originals. Bosch, for example, maintains extensive tables mapping their part numbers to BMW, Mercedes, Toyota, Ford, and most other OEM numbers. These tables are the primary data source for cross-reference databases.

The result of an OEM → IAM lookup should show you: the OEM anchor number, the vehicle applications it fits, and every IAM equivalent available in the database with brand name, IAM part number, and where applicable, an availability or price indicator. From there, you choose based on brand preference, price, and stock availability.

IAM to OEM: the reverse lookup

The reverse direction — IAM → OEM — is useful when you have a part number from an existing component (the number on the box or the part itself) and need to know what OEM number it corresponds to, or what other IAM brands make the same part.

This is common in three situations: a mechanic replacing a part already installed by a previous workshop (which used a specific IAM brand), a distributor reordering a part and wanting to check if cheaper alternatives are available, and a buyer verifying that an IAM number they found online actually corresponds to the right part for their vehicle.

Quality cross-reference databases handle both directions equally. The underlying data is a network of linked numbers — it does not inherently have a direction. OEM and IAM numbers are nodes in the same graph; a lookup from any node returns all connected nodes.

Where cross-reference data comes from

Cross-reference databases are built from several overlapping sources, each with different strengths and different gaps.

Manufacturer tables. IAM brands publish their own cross-reference tables — their numbers mapped to OEM equivalents. These are authoritative for the brand that published them but do not cover competitors. Bosch's table tells you Bosch equivalents for OEM numbers; it does not tell you what Brembo or TRW make for the same number.

Fitment-based matching. Parts that share identical vehicle fitment records — same make, model, year, engine, and position — are likely equivalent. Fitment-based matching fills gaps where no manufacturer table exists and validates matches where one does.

Technical attributes. Dimensions, material, thread pitch, bore diameter, and other technical specifications provide another layer of equivalence confirmation. Two brake discs with identical dimensions and fitment but from different brands are almost certainly cross-references, even if no published table says so.

Multi-source validation. A quality cross-reference confirms every match against at least two independent sources before publishing it. A cross-reference that appears in only one place — one manufacturer's table, with no fitment corroboration — carries meaningful uncertainty and should be treated with caution.

Common mistakes when using cross-reference data

Ignoring the application data

A number match without a fitment check is not confirmation of equivalence. Parts with the same number format from different production years can be physically different. A brake disc redesigned mid-production may have a superseded OEM number and a new cross-reference set that does not include the old IAM equivalents — but both OEM numbers may still appear in cross-reference databases. Always verify against the vehicle's make, model, year, and engine.

Treating superseded numbers as active

OEM part numbers are superseded when a running change is introduced. The superseded number is still valid as a lookup key — it tells you what the part was — but the active part number for ordering is different. When a cross-reference returns a superseded OEM number, follow the supersession chain to the current active number before sourcing the part.

Assuming all IAM equivalents have equal quality

A cross-reference database tells you which numbers refer to the same part. It does not rank brands by quality. A Brembo cross-reference and a no-name generic cross-reference for the same OEM number are not the same purchasing decision. The number equivalence is real; the quality of the specific manufacturer behind each IAM number varies widely outside the major established brands.

Cross-reference for parts sellers and catalog managers

If you are building or managing a spare parts catalog, cross-reference data is not just a lookup tool — it is an organic search multiplier. Every additional part number linked to a product page is an additional keyword that page can rank for. A brake disc with six cross-referenced part numbers can appear in searches for all six numbers, not just the primary one you assigned at import.

At catalog scale, this matters enormously. A catalog of 30,000 SKUs where each part averages four cross-references has 120,000 additional part number searches it could be ranking for — searches it currently cannot capture if those equivalent numbers are not on the page. Most spare parts catalogs are missing the majority of their potential organic reach not because they lack the products, but because they lack the cross-reference data that makes those products findable by buyers searching equivalent numbers.

AI search makes this even more acute. When a buyer asks an AI assistant "what is equivalent to Brembo 09.C294.11?", the answer comes from pages that explicitly publish cross-reference data in a structured, readable format. A product page that lists OEM number, vehicle fitment, and all IAM equivalents is exactly what those queries retrieve. A page with only a primary SKU and a description is invisible to them.

Frequently asked questions