MPN reference

Manufacturer part numbers: the field distributors get wrong most often.

An MPN is the manufacturer's own code for a product. It is not unique across manufacturers, it is not yours to tidy up, and a single stripped hyphen is enough to break matching against a supplier feed or a marketplace listing.

Govern part numbers in Nexodo Compare product identifiers

Manufacturer owned

The brand defines the string, not the distributor.

Not globally unique

Two brands can legitimately use the same part number.

Match with brand

Brand plus MPN is the pair channels accept.

Definition in practice

Three fields that look alike and behave completely differently.

The MPN is issued by the manufacturer and printed in its own catalog and on its own packaging. The SKU is issued by whoever holds the stock. The GTIN is issued from a GS1 licensed company prefix and is unique worldwide. A distributor catalog holds all three, and confusion between them causes duplicate products, failed channel validations and mismatched supplier files.

The rule that resolves most of it: an MPN is only meaningful in combination with a brand. On its own, a part number such as 1234-A tells you nothing, because several manufacturers may use it. Any matching, deduplication or channel submission built on the MPN alone will eventually match the wrong product.

Field	Who sets it	Uniqueness
MPN	The manufacturer	Within that manufacturer's own catalog
SKU	The company holding the stock	Within that company's own systems
GTIN	GS1, from a licensed company prefix	Worldwide across all trade items

Formatting

Store the manufacturer's string exactly, and normalize in a second field.

Manufacturer part numbers contain hyphens, slashes, spaces, letter case and leading zeros that carry meaning. A part number that reads 0-3 is not the same as 03. A suffix after a slash often denotes a variant such as a voltage or a finish. Cleaning these characters out to make a column tidy destroys information that the manufacturer relies on.

The workable pattern is two fields. One holds the manufacturer's published string verbatim and is what you publish. A second holds a normalized form, usually upper-cased with separators removed, used only for internal matching and duplicate detection. Never publish the normalized form and never let an import overwrite the verbatim one.

Publish the verbatim manufacturer string, always
Keep a separate normalized form for matching only
Preserve leading zeros by storing part numbers as text
Treat a suffix change as a different part until the manufacturer says otherwise

Distributor reality

The same part arrives from three suppliers written three ways.

A distributor buying the same manufacturer's product through several channels receives that product's part number formatted differently by each of them. One supplier upper-cases, another inserts spaces, a third appends its own suffix. Loading these into one column without evidence produces either duplicates or a silent overwrite of the correct value.

This is exactly the case Nexodo is built around. Each supplier file keeps its own source observation of the part number, the normalized form drives the match, and a reviewer sees the competing values side by side before deciding which string is canonical. When a manufacturer later corrects a part number, the history shows what was published and when.

One source observation per supplier, retained after import
Matching on the normalized form, decision on the verbatim form
Conflicts surfaced for review rather than resolved by last write
History that shows which part number was published to a channel

Channels

MPN is the fallback identifier, so it has to be right.

Shopping feeds and marketplaces ask for a GTIN first. When a product genuinely has none, they accept a brand and manufacturer part number pair instead, and some require an explicit declaration that no identifier exists. A wrong or reformatted MPN in that position causes matching failures that look like ranking problems rather than data problems.

Before a channel submission, check three things: the brand value matches the manufacturer's registered brand name rather than a supplier abbreviation, the MPN is the verbatim string, and the declaration about identifier existence is consistent with the GTIN field actually being empty.

Brand value written as the manufacturer writes it
Verbatim MPN in the channel field, not the normalized form
Identifier-existence declaration consistent with the GTIN field
No SKU substituted into an MPN field to satisfy a validator

Frequently asked questions

Clear answers before you evaluate a PIM.

Is an MPN the same as a part number?

Yes in normal usage. MPN is the field name that shopping feeds and marketplaces use for the manufacturer's own part number. Engineering teams often call the same value the part number or the catalog number.

Can two products share an MPN?

Across different manufacturers, yes, and that is normal. Within one manufacturer's catalog it should not happen. This is why every system that matches on MPN has to match on brand and MPN together.

Should I clean up part numbers on import?

Not in the published field. Normalize into a second field for matching and leave the manufacturer's string untouched. A cleaned part number is unusable for ordering, and ordering is what the field exists for.

What if a supplier adds its own prefix to the part number?

Treat the prefixed value as the supplier's reference, not as the MPN. Keep it as a supplier-specific field so you can reconcile against that supplier's invoices, and keep the manufacturer's own string in the MPN field.

Continue your product data research

Product identifier reference

Test Nexodo with a supplier file your team already uses.

Tell us how your supplier files arrive and what your channels reject, and we will tell you whether this workflow fits.

Talk to us See what Nexodo does

A person replies, normally within one business day
Use a representative product sample
We will say plainly if Nexodo is the wrong fit

Manufacturer part numbers: the field distributors get wrong most often.

Three fields that look alike and behave completely differently.

Store the manufacturer's string exactly, and normalize in a second field.

The same part arrives from three suppliers written three ways.

MPN is the fallback identifier, so it has to be right.

Clear answers before you evaluate a PIM.

Continue your product data research

Every product identifier your catalog carries, and what each one is actually unique across.

How to design a SKU numbering system you will not have to replace in two years.

Turn many supplier catalogs into one trustworthy product catalog.

Onboard supplier product data without surrendering control.

Test Nexodo with a supplier file your team already uses.