Every hardware team eventually asks the same question: should we track parts by manufacturer part number (MPN), or invent our own internal numbering scheme? The honest answer is it depends on how many hands touch your BOM.
Manufacturer part numbers (MPNs)
MPNs are unambiguous and directly linked to a specific, sourceable part. They're great for solo builders and small teams because there's no translation layer — what's in your inventory is exactly what you'd order from a distributor.
The downside: MPNs are long, inconsistent in format across manufacturers, and don't communicate anything about function (a resistor's MPN tells you nothing about its value at a glance).
Internal part numbers
Larger teams often introduce an internal numbering scheme (e.g. R-0603-10K-1%) that encodes category, package, and value directly in the identifier. This makes BOMs easier to scan and lets you swap an approved alternate manufacturer part without renumbering anything downstream.
The tradeoff is overhead: someone has to own the numbering scheme, and every new part needs to be assigned a number before it can be used.
A hybrid approach works for most teams
Track the MPN as the source of truth for sourcing and compliance, but let a lightweight internal category/value naming convention drive how parts are searched and displayed. You get unambiguous procurement and a numbering scheme that reads naturally, without maintaining a second full identity for every part.
In PartSense, we handle this hybrid workflow natively using "Meta-Parts." You can create a generic requirement (like RES-10K-0603) and link multiple acceptable MPNs directly to it. You get the clean internal naming scheme, and the unambiguous sourcing data, all in one place.
Whatever you choose, consistency matters more than the specific format — pick a convention early and stick with it as your BOM grows.