MPN (Manufacturer Part Number)

An MPN is the manufacturer's own name for a thing it makes. 3M calls a respirator 8210. Ideal Industries calls a 600V wire connector 30-076. Grainger did not assign those numbers, and neither did GS1. The manufacturer did, using whatever internal convention it prefers.

That convention is the source of most of the pain:

• No format standard. MPNs run from 8210 to HD-3/8-16X2-G8-ZN. Length, character set, and case are all up to the manufacturer.
• No central registry. Nobody issues MPNs. Two manufacturers can legitimately use the same string.
• No uniqueness across brands. Short numeric MPNs like 1234 recur across unrelated brands.
• They change. Manufacturers supersede part numbers on revisions, and the old number lingers in customer POs for years.

The practical consequence: an MPN is only an identifier when it is paired with a brand. 30-076 means nothing on its own. Ideal Industries 30-076 means one specific wire connector.

These four get used interchangeably in meetings and they should not be. Each is assigned by a different party for a different purpose.

Identifier	Assigned by	Scope of uniqueness	Example format	Common on industrial SKUs?
MPN	The manufacturer	Within that manufacturer's catalog	8210	Almost always
SKU	The seller (distributor/retailer)	Within that seller's system	WC-30076-BX	Always, it's your own number
GTIN	GS1, via the brand owner's prefix	Globally, across all trade	14 digits	Often not
UPC	GS1 (a 12-digit GTIN form)	Globally	12 digits	Retail-facing goods mostly

The distinctions that matter in practice:

• A SKU is yours. It reflects how you sell the item: your pack size, your branch, your ERP. Two distributors selling the same 3M 8210 will have two different SKUs and the same MPN.
• A GTIN is global but optional. Nothing forces a manufacturer to barcode a specialty flange or a made-to-order cable assembly. If it never crosses a retail scanner, it may never get one.
• An MPN is what the buyer types. A contractor searching your site types 8210, not your internal SKU and not a 14-digit number.

So the three answer three different questions: what is it (GTIN), what does the maker call it (MPN), how do I sell it (SKU).

In electrical, industrial, MRO, and fastener catalogs, GTIN coverage is thin. Bulk hardware sold by the pound, cut-to-length wire, and configured assemblies frequently carry no barcode at all. Build your matching strategy on GTIN and you match a slice of your lines and go blind on the rest.

Brand + MPN is the fallback that actually covers the catalog:

• It appears on the manufacturer's spec sheet, the packaging, and the purchase order.
• It is what the supplier sends in their price file.
• It is what a buyer pastes into your search bar.
• It is what a competitor's PDP shows, which makes it the join key for cross-reference work.

The cost of that coverage is ambiguity. 301 from one brand and 301 from another are different products, and a naive match on the bare number merges them.

Normalization matters too. A supplier file may carry HD-3/8-16X2-G8-ZN while your ERP holds hd3816x2g8zn, hyphens and case stripped by some import job years ago. Same bolt, no exact match.

MPNs are not stable over time. When a manufacturer revises a product, tightens a tolerance, changes a housing material, or drops a variant, it often issues a new part number and marks the old one superseded. The old number does not disappear. It stays in customer purchase orders, in maintenance records, and in the spec binders on a plant floor for years after the change.

That leaves two problems in the catalog:

• Dead numbers still get searched. A buyer types the number printed on the part in their hand, not the current one. If your site only knows the new number, the search returns nothing and the order goes to whoever does know it.
• Supersession is not one-to-one. An old number can map to one replacement, to several, or to nothing at all. A discontinued connector may be replaced by two parts split across different wire ranges, and picking one of them silently is worse than saying so.

The fix is to store the supersession chain instead of overwriting it. Keep the old MPN on the record as a searchable alias, flag it as superseded, and point it at the current part. A buyer searching a twenty-year-old number should land on the product that replaces it, with the substitution stated plainly on the page.

Anglera's job starts after the identifier exists. Your PIM stores the record, whether that is Akeneo, Salsify, Syndigo, inriver, or Pimberly. Anglera does the work of filling it in, and brand + MPN is the anchor it works from.

A typical pass looks like this:

Step	What happens
Normalize	Strip formatting noise from the MPN, reconcile brand aliases (3M vs 3M Company)
Match	Resolve brand + normalized MPN against manufacturer sources and spec documents
Extract	Pull attributes from the matched source: thread pitch, voltage rating, UL listing, material
Verify	Confirm each value traces to a source tied to that exact MPN
Write back	Push completed attributes into the PIM against your SKU

Two rules hold throughout. Anglera does not match on a bare MPN without a brand. That is how a Grade 8 hex bolt ends up with a Grade 5 spec sheet. And every enriched value stays traceable to the source it came from, so a reviewer can check the claim against the manufacturer's own document instead of trusting the output.