Item master
An item master (called the material master in SAP) is the core ERP record for a SKU: the internal item number, unit of measure, standard cost, GL account coding, and operational flags — buy vs. make, lot- or serial-tracked, active or discontinued — that purchasing, warehouse, and finance systems key off of. It's built for internal operations, not for what a buyer sees. A PIM holds the customer-facing counterpart: marketing copy, images, spec attributes, and taxonomy meant for syndication. The two records share the same item number but serve different audiences and are usually owned by different teams.
What lives in an item master
A typical item master record carries the fields operations and finance depend on: an internal item number, a short description (often truncated and abbreviated for screen and report space), unit of measure, standard or average cost, GL account and cost-center coding, plant or warehouse assignment, lead time, and status flags like buy-vs-make, lot- or serial-tracked, and active-vs-discontinued. None of that is written for a shopper. It's written for a buyer creating a PO, a warehouse system picking an order, and an ERP closing the books — all of which need one unambiguous, stable record per item, not a compelling description of it.
Item master vs. PIM vs. golden record vs. MDM
These sit in the same conversation because they all touch "the truth about a product," but each does a different job.
| System | What it holds | Audience |
|---|---|---|
| Item master | Operational fields: cost, UOM, GL code, status | ERP, purchasing, warehouse, finance |
| PIM | Marketing content: descriptions, images, spec attributes, taxonomy | Website, marketplaces, distributor portals |
| Golden record | The single trusted value per field, reconciled across every system that has an opinion | Whichever system consumes the reconciled data |
| MDM | The governance process — policies and survivorship rules — that produces the golden record | Data stewards, cross-functional governance |
The item master is one input into a golden record, not a replacement for one. If the item master and the PIM disagree on a spec, MDM's job is deciding which value survives.
Where the item master creates downstream problems
Two failure modes show up repeatedly. First, the item master's internal description is often too terse or code-like to reuse anywhere customer-facing — "HCS 3/8-16 G8 YZ" tells a buyer nothing a shopper needs. Second, an item number renumbered or reused in the ERP without updating every downstream system breaks integrations that depend on it staying stable: a PunchOut cart's SupplierPartID, an EDI 832 catalog line, a website URL slug all silently point at the wrong record until someone traces the mismatch back to the ERP change.
Keeping item master and PIM in sync
The item number is the join key: the PIM's customer-facing record and the ERP's item master should reference the same identifier even though the fields around it differ. New-item setup is where this most often breaks — a SKU exists in the ERP with a cost and a GL code weeks before its attributes, images, and description are ready in the PIM, leaving a gap where the item can be ordered internally but can't be sold anywhere that requires real content.
Frequently asked questions
Is an item master the same as a material master?
They're the same concept under different vendor names. SAP calls it the material master, managed through the Materials Management module; Oracle, NetSuite, and most other ERPs call the equivalent object the item master. Both serve as the core operational record for a SKU inside the ERP.
Does the item master feed the website?
Not directly. The item master's fields — cost, GL code, warehouse assignment — aren't customer-facing content. A PIM typically pulls the item number, and sometimes a small set of operational fields like UOM, from the ERP's item master, then adds the descriptions, images, and attributes that actually populate a product page.
What breaks when the item master and PIM disagree?
Usually a unit-of-measure or status mismatch: the item master shows a SKU as active while the PIM still has it staged as not-yet-published, or the two systems disagree on whether a unit is sold each or by case, which then shows up as a price or availability error somewhere downstream.
Who owns the item master, the ERP team or the PIM team?
Typically the ERP or finance/operations team owns the item master, since its fields serve purchasing, costing, and warehouse processes. The PIM team owns the customer-facing record. New-item setup usually requires both teams to create their respective records against the same item number before a SKU is sellable.