30-day money-back guaranteeStripe checkout

Guide · Catalog data

Part number cross-reference guide for technical distributors: build, clean and reuse mappings

Every experienced industrial distributor relies on cross-reference tables: customer material numbers on one side, manufacturer codes in the middle, and your own stocked item numbers on the right. When those mappings live in individual reps’ spreadsheets, quotes slow down and errors repeat. This guide gives you a clean column layout, shows the formatting traps that break lookups, and explains when a mapping is safe to trust.

Updated 21 November 2026

How Quotrail turns RFQs into quote drafts · Quotrail plans and pricing

Minimum columns for a reliable cross-reference table

Whether you maintain cross-references in your ERP or import them via Excel or CSV, every mapping row needs clear ownership and traceability. The example below uses invented numbers.

Recommended cross-reference columns (invented example data)
ColumnExample valueWhy it is required
Customer numberC-10420Scopes the mapping strictly to one customer so identical codes never bleed across accounts
Customer part no.AB-4711/32The exact string printed on the buyer’s RFQ or ERP export
Our article no.NF-31-000320Your active catalog SKU that carries pricing, stock and pack size
Manufacturer part no.4WE6D6X/EG24N9K4Optional second anchor to verify manufacturer consistency
Status / successorActive (or Discontinued → NF-31-000399)Prevents quoting obsolete items automatically
Confirmed by / dateM. Keller · 2026-10-14Creates an audit trail when a buyer questions a substitution

Six formatting traps that break exact lookups

  • ERP zero-padding: Exporting `000000000000221599` from an ERP fails a plain lookup against `221599` unless leading zero-fill is normalized.
  • Separators and casing: `AB-4711/32`, `ab 4711 32` and `AB471132` refer to the same item when punctuation and spaces vary between buyer templates.
  • Copied webshop prefixes: Buyers often copy `Art.-Nr.` or a supplier shop prefix alongside the part number.
  • One customer code mapped to two SKUs: Duplicate rows in a spreadsheet let the first match win silently unless imports reject collisions.
  • Dimensions misread as part numbers: Strings like `25x47x7` describe a seal geometry and belong in technical attributes, not part-number matching.
  • Outdated mappings after discontinuation: A previously confirmed cross-reference must never auto-approve an item marked discontinued.

You can test how leading zeros, prefixes and technical attributes are parsed in our live RFQ unit and part number checker.

How Quotrail manages customer cross-references

You can import existing cross-reference lists as Excel or CSV files with a trial check first — if a row collides with an existing mapping, it is rejected for review instead of silently overwritten. During daily quoting, whenever a reviewer resolves an unfamiliar customer number, Quotrail stores the mapping on that customer’s profile with who confirmed it and when. Read the detailed mechanics in our guide on customer part number matching.

Frequently asked questions

Should customer part numbers be stored globally across all buyers?
No. Two customers can assign the same internal material code to completely different items. Every customer part number mapping must be scoped to one customer account.
How can we import existing Excel cross-reference sheets into Quotrail?
Export your customer number, customer part number and article number as Excel or CSV. Quotrail validates the file in a trial run before writing anything and flags duplicate or conflicting mappings.
What happens if a mapped article is discontinued later?
Quotrail never marks a discontinued item as clear, even if the customer mapping was confirmed multiple times; it surfaces the successor for a human reviewer to confirm.

Quotrail Support

Product support

Hello! How can I help you?

Find a suitable plan