Item Master Data
Item master data is the central, permanently stored collection of all of a company's product data – such as item number, description, units, prices, tax rates, suppliers and stock information. It serves as the authoritative reference for every process in the ERP system.
Item master data is the central collection of all permanent data on a company's products. For each item it holds a unique item number, description, units, prices, tax rates, weights and dimensions, supplier and stock information, along with many further attributes. This makes the item master the authoritative reference that every process in the ERP system draws on – from purchasing through inventory management to sales, shipping and accounting.
As part of master data, the item master does not describe individual business transactions but the stable properties of a product that stay the same across many transactions. When an item is ordered, stored or sold, the system accesses this single record instead of re-entering details such as price or weight each time. A well-maintained item master is therefore a prerequisite for correct documents, reliable stock levels and processes that can be automated.
At a glance
- Central record per product: item number, description, prices, units, stock and supplier data
- Part of master data – long-lived and referential, unlike transaction data
- Maintained once, used in every process: purchasing, warehouse, sales, accounting
- Unique item number as the key; often supplemented by GTIN/EAN
- Data quality determines automation, stock accuracy and document quality
What belongs in the item master?
An item master record bundles all the details that describe a product throughout its entire use within the company. The fields can be organised into a few groups: identification and description, commercial data, logistics data, and tax and accounting details. Depending on the industry and system, attributes such as variants, bills of materials, customs tariff numbers or sustainability information are added.
The scope of an item master grows with requirements. A simple retail item often needs only a few dozen fields, whereas a technical product with variants, batch tracking and customs relevance can carry hundreds of attributes. What matters is not the number of fields but that the details actually used are consistent, unambiguous and up to date.
Typical data fields
Commercial fields include sales and purchase prices, discount groups, minimum order quantities and the assigned tax rate. Logistics fields cover the unit of measure, packaging unit, weight, dimensions, storage location, minimum and reorder stock levels, and delivery times. Relevant for accounting are revenue and expense accounts, tax codes and, where applicable, cost centres.
The item number as the key
Every item master record is identified by a unique, unchangeable item number. It is the key through which all documents, postings and stock levels refer to the item. It is often supplemented by a GTIN or EAN for unambiguous identification in trade, as well as by supplier and manufacturer numbers for purchasing.
How the item master works in the ERP system
In the ERP system, the item master is the single source of truth for all product-related details. Once an item has been created, every downstream transaction references this record instead of duplicating data. A sales order takes price, tax rate and unit from the master; goods receipt posts the incoming quantity to the same item; the invoice derives the revenue account from the master.
This makes the item master the link between the modules: purchasing, inventory management, sales, shipping and financial accounting all access the same base data. A price change only has to be maintained in one place and takes effect immediately in all future documents. Conversely, an error in the master record – such as an incorrect tax rate – propagates unchecked through every process. This central role makes data quality in the item master a critical factor.
Via interfaces, the item master is often synchronised with upstream systems. A PIM (Product Information Management) supplies marketing-oriented descriptions and media, while the ERP item master holds the commercial and logistics core data. In e-commerce scenarios, item data is distributed to shop systems and marketplaces via an API so that assortment, prices and availability appear consistently everywhere.
Why a well-maintained item master matters
The value of a good item master shows in nearly every process. Because prices, units and tax rates are stored centrally, documents are generated automatically and error-free; manual re-entry is eliminated. Inventory management stays accurate because every posting is clearly assigned to a specific item. Analyses of revenue, margin or stock turnover become reliable because they rest on a uniform data basis.
Conversely, poor master data is one of the most common causes of friction in day-to-day operations: duplicated items, inconsistent descriptions, outdated prices or incorrectly assigned tax rates lead to wrong deliveries, incorrect invoices and unusable reports. The effort of cleaning up such errors after the fact usually far exceeds the maintenance effort of clean initial entry. Data quality in the item master is therefore not an end in itself but has a direct impact on efficiency and costs.
Distinction: item master, material master and transaction data
The item master belongs to master data and sits alongside other master data objects such as the customer master and the supplier master. What they have in common is that they describe stable reference objects that business transactions point to. To be distinguished from these are transaction data – orders, deliveries, invoices and postings – which record individual, point-in-time events and use the item master but do not change it.
Item master vs. material master
The terms item master and material master essentially mean the same thing: the central record of a product. The difference is mostly linguistic and industry-dependent. In trade and e-commerce, people speak of the item master when it comes to saleable goods. In industry and production-oriented systems – such as the SAP environment – the term material master is used, which, in addition to merchandise, also maps raw materials, semi-finished goods and finished products and is supplemented by production-relevant views.
Maintaining the item master: data quality and DACH specifics
For an item master to deliver its value, clear rules for creation and maintenance are needed. These include a well-thought-out numbering system, binding naming conventions for descriptions, mandatory fields per item type, and an approval process that checks new items before they enter productive use. Regular clean-ups remove duplicates and retire phased-out items instead of deleting them.
In the DACH region, tax and legal requirements must also be observed. The correctly stored VAT rate per item is the basis for a proper invoice. Because item master data feeds into tax-relevant documents, it is indirectly subject to the GoBD requirements for traceability and immutability: changes to price- or tax-relevant fields should be logged, and documents should be reproducible with the state that was valid at the time. For cross-border trade, customs tariff numbers and countries of origin are often maintained in the master.
When switching systems, the item master is regularly the most demanding migration object. Fields have to be mapped between the old and new system, units and tax codes have to be harmonised, and duplicates have to be cleaned up before the transfer. Good data quality in the old system shortens any migration considerably.
Example
Example: retailer harmonises 8,000 items before switching ERP
A mid-sized retail business maintained its items for years in an inventory management system without fixed rules. Descriptions were inconsistent, several items existed as duplicates, and for some entries the tax rate was stored incorrectly. In practice this led to faulty invoices and to reports that nobody quite trusted.
Before introducing a new ERP system, the team cleaned up the item master: it defined a uniform numbering scheme, mandatory fields and naming conventions, added missing GTINs and corrected the tax rates. Duplicates were merged and phased-out items retired. Only the cleaned-up master moved into the new system. The result: automatically correct documents, stock synchronised across channels, and analyses that controlling can rely on.
Frequently asked questions
Related services
Questions about Item Master Data in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.