Supplier Part Number Mapping: How to Match Every Part Number
Supplier part number mapping is the practice of linking the number your supplier uses for an item to your own internal part number (and, ideally, to the manufacturer’s number), so that every quote, order, confirmation and invoice lands on the right item in your ERP. Build the mapping once in your master data, keep it controlled, and automate the point where part numbers enter your system: the inbox. That is where most mismatches start, because suppliers and customers send part numbers in PDFs, Excel files and free-text emails, and someone has to retype them.
We built Ampwise for exactly that handoff. It reads orders, PO confirmations and invoices from Outlook or Gmail, extracts the data without templates, and lets your team approve verified data into the ERP with one click. Below is how the mapping itself works, how to set it up, and where automation takes the repetitive work off your team.
TL;DR
- A supplier part number is the number a supplier uses for your part. Mapping connects it to your internal number and the manufacturer’s number, so a PO can reference all three.
- “Cross-referencing part numbers” is the everyday term for this link. In most ERPs it lives in a cross-reference table, with one internal part pointing to many outside numbers.
- Accuracy comes from matching on the specification, recording who approved each link, and treating mismatches as exceptions to review, not guesses to accept.
- Old, changed and duplicate numbers need a dated mapping table, not overwriting.
- The slowest part is usually the inbox. Automating extraction and validation of emailed documents means fewer retyped numbers and faster approval.
Table of Contents
- What supplier part number mapping means
- How ERPs store part number relationships
- Setting up supplier part number mapping, step by step
- Keeping a mapping accurate
- Where the real time goes: the inbox
- What to tell your team and your suppliers
- Our perspective
- See it on your own emails
- FAQ
- Sources
What supplier part number mapping means
Three numbers usually describe one purchased item:
- Your internal part number, the one your ERP, warehouse and bills of materials use.
- The manufacturer part number, which identifies the item at its maker.
- The supplier part number, the number your supplier or distributor prints on its quote, confirmation and invoice.
The Epicor part-numbering white paper describes the supplier part number as the number your supplier labels your part with, and notes that the supplier may be a manufacturer or a distributor. Mapping it creates a three-way connection between the internal part, the manufacturer part and the supplier part. Once linked, supplier quotes point to a specific supplier part number and manufacturer, and the generated purchase order references all three numbers.
That is the practical payoff. When a confirmation arrives quoting the supplier’s code, your system already knows which of your parts it is.
Mapping versus cross-referencing
The two terms overlap heavily. People searching for “cross-reference part numbers” usually want one of two things: to find which of your parts a vendor’s number belongs to, or to find a substitute from another maker. ERP vendors separate these ideas.
SAP’s master data documentation defines an interchange as an alternate product that can be substituted for a given product, and a cross-reference as an alternate part number used to find the main record, which is not itself a record. Put simply:
- Mapping or cross-reference: same item, different name. The supplier’s number is just another label for your part.
- Interchange or substitute: a different item that can stand in for yours. This needs an engineering decision, not a lookup.
Keeping these apart prevents the costliest error in the field: treating a similar-looking part as the same part.
How ERPs store part number relationships
Most systems use a cross-reference table. The details differ, but the logic is the same.
Many outside numbers, one internal part. The Epicor paper gives the example of an internal bolt, B1001, made by two companies under two different numbers (1234-12 at ABC Metals and ABC-100 at Acme Machining). Both numbers point to B1001 through a cross-reference table. The same paper shows internal shortcuts, such as a short code, mapped to a full 12-digit part number so users can find the main part from any part number field.
Typed relationships. Cetec ERP’s guide describes a “cross” as another name for one of your parts, whether a customer, vendor or manufacturer number. In its cross-reference workflow you open the part’s Crosses table, enter the other number, choose the cross type and the associated customer, vendor or manufacturer, mark a default (only one per type and association), and update. From then on the system treats that name as the same part.
Trading-partner numbers for transactions. Oracle’s JD Edwards documentation defines item cross-references as relationships between your item numbers and your trading partners’ item numbers. Vendor item numbers are used when vendors require their own part numbers on orders or communications, and for EDI each number a partner might transmit should be cross-referenced.
Catalog matching. Some systems suggest matches for you. ServiceTitan’s documentation says its Pricebook Connect “High Match” logic triggers when most field values match, or when the vendor part number matches exactly, and presents potential matches sorted by confidence for a person to map.
The common thread: the system proposes or stores, and a person with authority confirms.
Setting up supplier part number mapping, step by step
1. Decide which identifiers you track
For purchased components, OpenBOM recommends keeping four identifiers explicit: internal part number, manufacturer part number, supplier ordering code and ERP item code. The values may coincide, but each has a different owner, so record the relationships instead of assuming every system uses the same code.
Where it goes wrong: a single “part number” field that holds whatever the last person typed. Within a year it contains a mix of your numbers, vendor numbers and manufacturer numbers, with no way to tell which is which.
2. Always pair manufacturer name with number
BuyPLM’s good-practice guidance notes that different manufacturers may reuse the same number, so both the manufacturer name and the number are required to identify a part uniquely. It also separates model numbers whose capabilities evolve from datasheet numbers that represent a fixed, backwards-compatible specification. Know which kind you are mapping before you assume a number never changes.
3. Build the table from real documents
Start with the numbers that actually appear on your supplier quotes, order confirmations and invoices, not a theoretical catalog. Take your last 12 months of purchase orders and list every supplier number that came back. This gives you the set of aliases your team meets daily, and it is also the set that causes the exceptions.
4. Record the type, the default and the approver
For each link, store the type (supplier, manufacturer, customer), the associated partner, whether it is the default, the date and who approved it. Use one default per type and partner, as the Cetec workflow does, so the system never has to choose between two equally weighted names.
5. Apply the map where documents enter
This is where the table either earns its keep or sits unused. A confirmation that arrives by email with a supplier code only helps if that code is looked up against the table before the line is posted. If someone retypes it into the ERP by hand, every transposed character defeats the mapping.
At this step, we take the retyping off your team’s hands. Ampwise extracts line items from emails, PDFs, Excel files and scanned documents without templates, validates the data, and holds it for one-click approval before it goes into your ERP. For the mechanics of that extraction, see how attachment text extraction works for ERP and how to import an Excel attachment without retyping.
6. Validate before release
A mapped number should still pass checks: does the quantity make sense, does the price match, does the supplier match the PO? Our guides on ERP data validation rules and validating purchase orders before ERP release show which checks to set up, and 3-way match automation shows how they come together for invoices.
Keeping a mapping accurate
A cross-reference is only as good as the decision behind it. A few habits keep it reliable.
Match on specification, not on pattern. Two parts with the same nominal size can still differ in thread, material, finish or certification. When you map a substitute rather than an alias, compare the properties that decide fit and function. For material behavior in particular, this practical guide to engineering material properties helps check that two components behave the same way in the application.
Keep the original value. Whenever a supplier number is approved as a cross-reference, map it through controlled master data and keep both values so you can trace what the supplier actually sent. Connect981’s guidance is to treat part-number and revision mismatches as controlled exceptions: the internal system of record wins unless an approved change process says otherwise, and the affected receipt, ASN, PO line or work order is held or flagged until it is resolved.
Treat “similar” as a question. A cleanup guide from KTSU on duplicate spare-part numbers advises treating a similarity result as a request for review, not permission to merge. Establish the original identity, map every alias, variant, unit and open transaction affected, and get the source-to-target mapping approved before changing a live master. A supersession can be directional and date-effective, so it should not be treated as interchangeable in every application.
Map old numbers to new ones. If you renumber or merge items, load a mapping table from old to new numbers. The IFS Cloud part-numbering blog points out that each old number should appear once with exactly one new number, while several old numbers may point to one new number when duplicates merge. Pre-change invoices, drawings and warranty claims still carry the old number, and suppliers and customers should receive the mapping.
A quick checklist for handling an unmatched number
| Situation | What to do |
|---|---|
| Supplier number found in the table | Post the line, keep the supplier value on the record |
| Number not found | Hold the line, identify the part from the datasheet or the supplier, add the link after approval |
| Number matches several parts | Check manufacturer name and number together, then pick one default |
| Supplier changed or superseded a number | Add the new link with a start date, keep the old one for open orders and history |
| Duplicate internal parts | Map every alias and open transaction before merging |
Where the real time goes: the inbox
A clean table solves the lookup. It does not solve how numbers get into your system. In wholesale and manufacturing, orders, inquiries, PO confirmations and invoices arrive as emails with attachments, and each uses a slightly different part number format. The person at the keyboard reads a supplier code, finds the internal part, retypes the quantity and price, and moves on to the next line.
That routine is where errors creep in and where speed is lost. For purchasing managers, a delayed PO confirmation means delayed visibility of delivery dates. For technical sales, a slow order entry means a slower reply to the customer. For a CEO, it is headcount spent on typing.
Automating the entry step changes the picture. Our own figure is that Ampwise reduces manual data entry by up to 90%, and customers see faster order processing, fewer errors and lower operating costs, with ROI in as little as three months. Because it works directly in Outlook and Gmail, handles free-text emails, PDFs and scans, and integrates with your existing ERP, your team keeps its tools and its ERP workflow. If you handle manufacturer orders this way, automating email orders with human review before posting shows the approval flow in detail, and PDF invoice field mapping covers the field-level side.
What to tell your team and your suppliers
Mapping works best when the people who create the numbers know the rules:
- Buyers add a supplier link as part of creating or changing a vendor item, not afterward.
- Engineering owns approval for anything that is a substitute rather than an alias.
- Receiving flags any delivery whose number does not resolve, instead of guessing.
- Suppliers are asked to quote your part number or the manufacturer number on confirmations when they can, which reduces the number of aliases you have to maintain.
It also helps to record, for each approved equivalent, the link, the date, the approver and the datasheet comparison. The next person who sees the number should not have to repeat the research.
Our perspective
We think part number mapping is a master data problem that is lost or won at the point of entry. Most companies we talk to about email-to-ERP workflows already have a cross-reference table, or at least a spreadsheet that someone trusts. The trouble is that the table sits in the ERP while the numbers arrive in an inbox, in PDFs, Excel sheets and sentences like “same as last time, but the 40 mm one.”
That is why we built Ampwise to work where the work happens: in Outlook and Gmail, with no templates and no changes to how your suppliers write to you. It reads the email and its attachments, extracts the order lines, validates the data, and puts the result in front of your team for one-click approval before it reaches the ERP. Your people stay the decision-makers on the exceptions, and stop being the typists on everything else.
If a day of your team’s week goes into reading part numbers from one place and typing them into another, that is the first thing to automate.
Evert
See it on your own emails
If your orders, confirmations and invoices reach you by email, Ampwise connects that inbox to your ERP, so part numbers are extracted, validated and approved instead of retyped. It supports multiple ERP integrations, adds smart email labeling and status tracking, and extracts metadata from each message. Learn more on the Ampwise AI page, or see how connecting Outlook to your ERP works.
FAQ
What is the difference between a supplier part number and a manufacturer part number?
The manufacturer part number identifies the item at the company that makes it. The supplier part number is what the vendor, who may be a distributor, calls it on quotes and invoices. Mapping both to your internal number lets one purchase order reference all three.
Can one internal part have several supplier part numbers?
Yes. This is the normal case, and ERP cross-reference tables are built for it: several outside numbers can all point to one internal part. Mark one default per type and partner so the system knows which number to print on outgoing documents.
How do I handle a supplier number that is not in my table?
Hold the line instead of guessing. Identify the item from the datasheet or the supplier, decide whether it is an alias of an existing part or a new item, and add the approved link with its date. Keep the supplier’s original value on the record for traceability.
Is a cross-reference the same as a substitute part?
No. A cross-reference is another name for the same part. A substitute is a different part that may be used instead and needs an engineering comparison of fit, form and function before you approve it.
Sources
- Epicor ERP part numbering recommendations (white paper)
- SAP Library: Product-Level Relationships
- Cetec ERP: How to create cross part references
- Oracle JD Edwards: Understanding item cross-reference setup
- ServiceTitan: Map provider catalogs to your pricebook
- OpenBOM: How to implement part number management
- BuyPLM: Defining and using purchased parts
- Connect981: Part number and revision mismatches in supplier data
- KTSU: Duplicate spare-part numbers, a controlled cleanup guide
- IFS Cloud part numbering: decide the scheme before the load
- Engineering material properties: a practical guide
