A part number cross reference links your part to every other number a buyer might search for it by: the OE number, the original manufacturer's number and equivalent parts from other brands. Mechanics and parts buyers search by those numbers, not by your SKU. SKULaunch can enrich parts with OE references and cross-reference numbers, normalised for search, so customers find the right part whichever number they have.
The problem
A customer has the original equipment number from the old part, or a competitor's part number from a quote. If your catalogue only holds your own codes, search returns nothing and the sale goes elsewhere. Cross-reference data exists in supplier files, catalogues and manufacturer sites, but rarely in the product record.
Where references are held, they are often unusable: pasted into the description, crammed into one comma-separated field, or typed in whatever format the supplier used. Site search cannot match them reliably, and nobody can tell which numbers are genuine equivalents and which are approximations.
Before and after
An illustrative example from an aftermarket filters catalogue. Brand names and numbers are placeholders.
Before: what you hold
Your SKU, the supplier part number and a short description: "Oil filter, fits various Peugeot and Citroen, OE 1109.AH, also replaces BrandB 12-345". No structured references.
After: in SKULaunch
- OE reference 1109.AH held as a typed reference, with a normalised search value of 1109AH
- Equivalent numbers from BrandB and BrandC added as aftermarket cross-references, each with its brand
- The source of each reference recorded, so it can be checked
- Reviewed in the grid before publishing to site search and channels
How it works in SKULaunch
- Add reference attributes. Create fields for OE numbers and cross-references, with the reference type and brand alongside each number.
- Source references. Extract numbers from supplier files, PDF catalogues and manufacturer pages.
- Normalise. Strip spaces and punctuation variants so searches match, while keeping the display format.
- Review and publish. Approve references in bulk or one by one, then send them to your site search and channels.
Types of cross reference
"Cross reference" covers several different relationships, and mixing them causes problems. Hold the type with every number.
- OE number. The vehicle maker's own number for the part, as printed in its parts catalogue. This is what a dealer or a customer with the old part usually has.
- OEM number. The number used by the company that made the part for the vehicle maker. Many people use OE and OEM interchangeably, so agree a definition and stick to it.
- Aftermarket equivalent. A part from another brand that does the same job. This is what buyers mean when they search a competitor's number.
- Supersession. One number replaced by another. The old number should still find the part, but the relationship runs one way.
- Interchange. Parts that can be swapped, sometimes only under conditions, such as with an adaptor or for certain applications.
How to structure part number cross reference data
Treat references as a repeating set on the part, not a single text field. Each reference needs four things: the type, the brand or manufacturer, the number as displayed and a normalised number for matching. Add the source if you want to audit it later.
The same OE number appears as "1109.AH", "1109AH" and "1109 AH". Store a normalised version for search alongside the display format, so customers find the part however they type it. That one detail often recovers more searches than adding new references. Sensible normalisation rules are:
- Convert to upper case.
- Remove spaces, full stops, hyphens and slashes.
- Keep leading zeros unless you know the brand's numbering ignores them.
- Never overwrite the display value. Buyers want to see the number as the manufacturer prints it.
Why cross references drive search
A buyer typing a part number is close to purchase. They know what they need and are checking who has it. If your search returns no results for a valid OE or competitor number, you lose a buyer who was ready to order. Indexing the normalised references in site search, and including them in feeds where channels accept them, turns those dead searches into results.
Manual versus at scale
For a few hundred parts, a parts specialist can look up references by hand from catalogues. Across tens of thousands of SKUs and several suppliers, that becomes a permanent backlog. Extracting references from the files and catalogues you already receive, normalising them in bulk and reviewing by exception is the only approach that keeps up with new ranges.
Common mistakes
- Storing references in the description, where search and filters cannot use them.
- Treating a supersession as a two-way equivalent.
- Losing the brand, so a number cannot be told apart from an identical number from another maker.
- Publishing approximate matches as exact equivalents. A wrong cross reference costs more than a missing one.
What changes
Customers find parts by the numbers they actually have, and fewer searches end with no results.
Common questions
What is a part number cross reference?
It is a record that links one part number to other numbers for the same or an equivalent part, such as the OE number or a competitor's part number.
What is the difference between OE and OEM numbers?
OE usually means the vehicle maker's number. OEM usually means the number of the company that manufactured the part for the vehicle maker. Usage varies, so define both in your data model.
Where do the numbers come from?
Supplier data, catalogues and manufacturer sources. Availability depends on your range and set-up, so confirm sources for your catalogue with us.
Can we show competitor numbers?
Yes, as cross-references, following your own policy on brand names.
How should superseded numbers be handled?
Hold them as a supersession reference so the old number still finds the current part.
Does this help on marketplaces?
Yes, where channels accept reference numbers.
More on parts data: enriching from a part number, search keywords and synonyms, vehicle applications, fitment data and automotive parts.

.avif)