What Is a Crosswalk (Part Number Cross-Reference Table)?

A crosswalk is a mapping between two identifier systems — supplier code to internal SKU, OEM to aftermarket, old part number to new. This entry covers the common kinds, why spreadsheet crosswalks fail, and what a trustworthy crosswalk row carries.

A crosswalk (also called a cross-reference table or mapping table) connects identifiers from one system to identifiers in another — a supplier’s part number to your internal SKU, an OEM number to its aftermarket equivalents, or an old part number to its current replacement. In practice the three terms are used interchangeably.

A sales rep gets a phone call: “I need part XY-2040.” That is the customer’s internal number. Somewhere in a shared drive is a spreadsheet that maps XY-2040 to your SKU INT-8832, which maps to the manufacturer’s MPN MFR-4401. The spreadsheet was last updated by someone who left the company. Nobody is sure which rows are current. That spreadsheet is your crosswalk, and it is the single point of failure for every quote that involves a part number the customer calls something different from what your ERP calls it.

The common kinds of crosswalk

Crosswalk type	Maps from	Maps to	Typical source
Supplier to internal	Supplier's part number	Your internal SKU	Supplier price lists, onboarding feeds
OEM to aftermarket	OEM part number	Aftermarket equivalent(s)	Aftermarket cross-reference databases, will-fit lists
Old to new	Discontinued part number	Current successor	Manufacturer supersession bulletins, price-list diffs
Customer to internal	Customer's internal code	Your SKU or MPN	Customer-specific mapping files, EDI setup
Standard to standard	One classification code	Another classification code	ETIM-to-ECLASS mapping tables, UNSPSC crosswalks

Why spreadsheet crosswalks fail

The spreadsheet is where crosswalks start, and where they stay too long. The problems are structural, not a matter of discipline.

No direction. A row that says XY-2040 = INT-8832 does not say whether the mapping goes both ways, or whether XY-2040 is the customer’s number and INT-8832 is yours. In a graph, that is two different edges: SAME_AS (bidirectional, same product) versus a supplier-to-internal mapping (directional, one system’s code pointing at another’s).

No evidence. Who added this row? When? Based on what — a supplier’s price list, a customer email, a product specialist’s memory? Without a source field, nobody can verify a mapping they did not create.

No date. Part numbers change. A mapping that was correct in 2023 may point at a discontinued part in 2026. Without an effective date, there is no way to tell current rows from stale ones short of checking each one manually.

No many-to-many. One OEM part may map to three aftermarket equivalents, and one aftermarket part may fit four OEM applications. A two-column spreadsheet handles this by duplicating rows, which creates ambiguity about which mapping is primary and which is a secondary alternative.

No owner. When a mapping is wrong, who fixes it? When a new part number appears, who adds the row? Spreadsheet crosswalks have contributors but no stewardship.

What a trustworthy crosswalk row carries

Field	Purpose
Source identifier	The starting point of the mapping
Target identifier	Where the mapping points
Direction	One-way or bidirectional
Relationship type	SAME_AS, REPLACED_BY, EQUIVALENT_TO, SUPPLIED_BY — the kind of link
Effective date	When the mapping became valid
Evidence / source	The document, feed or process that justifies the link
Confidence	How certain the mapping is (auto-matched, human-reviewed, manufacturer-confirmed)
Created by	Person or process that added the row

This is not a bigger spreadsheet. It is a different data model — one where every mapping is a typed, sourced, dated edge in a product identity graph rather than a bare cell pairing.

Where Claro fits

Claro replaces the spreadsheet crosswalk with resolved, evidenced relationships. When a supplier feed, a customer code or a legacy part number arrives, Claro matches it against the existing identity graph — using the same entity resolution and relationship types that handle deduplication and supersession. The result is a mapping with direction, source, confidence and a review trail, not a row someone pasted into a shared file.

Glossary

Spare Parts Data Glossary

All spare-parts data terms in one table.

Glossary

What is supersession?

When the mapping is old-to-new within one manufacturer's lineage.

Playbook

Build a supersession table from price-list changes

Workflow for turning disappeared and appeared codes into candidate pairs.

Playbook

Resolve a legacy part number to a current SKU

Step-by-step: normalize, look up, follow the chain, confirm.

FAQ

What is a part number crosswalk?

A crosswalk is a mapping table that connects identifiers from one system to identifiers in another — for example, a supplier’s part number to your internal SKU, or an OEM number to its aftermarket equivalents. The terms crosswalk, cross-reference and mapping table are used interchangeably in practice.

Why do spreadsheet crosswalks break?

Spreadsheet crosswalks typically lack direction, evidence, dates and ownership. They cannot represent many-to-many relationships cleanly, they drift as part numbers change, and there is no audit trail for who added a row or why. The result is a file that the team does not fully trust but cannot stop using.

What should a trustworthy crosswalk row contain?

At minimum: the source identifier, the target identifier, the direction of the mapping, the type of relationship, an effective date, the evidence or source that justifies the link, a confidence level, and the person or process that created the row.