An item master is the central record an ERP keeps for every article a business buys, stocks or sells. Each record sits under one item number and holds that article's identifiers, units of measure, packaging levels, weights and dimensions, purchasing and sales parameters and status. Purchase orders, goods receipts, picks, invoices and price lists all point to it, so one wrong field travels into every one of those documents.
German teams call it the Artikelstamm and its contents Artikelstammdaten; keeping them correct is Stammdatenpflege. Dutch teams say artikelstam. For a wholesaler, the item master is the operational half of product data. The other half, the content customers read (descriptions, features, images, classifications for webshops and catalog files), often lives in a PIM. The two systems complement each other, and they work best when every field has exactly one owner.
What belongs in the item master and what sits beside it
Microsoft's documentation for Dynamics 365 Supply Chain Management defines a product by its number, name and description plus categories, attributes, images, units of measure with their conversions and translations, and notes that the definition can also be imported from PLM, PDM or PIM systems (Microsoft Learn). The same page calls keeping product data accurate "a critical business process on its own". That is the job most wholesalers underestimate.
Three kinds of data are often mixed up with the item master, but most ERPs keep them in their own records:
- Stock. The item master defines the article. Inventory records hold the quantity per warehouse, location and batch.
- Supplier relations. In SAP, the purchasing info record holds the data on the relationship between a material and a supplier: the supplier's material number, prices and conditions, the planned delivery time and delivery tolerances (SAP Learning). German SAP users know it as the Einkaufsinfosatz. Other ERPs use a vendor item table or a supplier price list for the same job.
- Customer prices. Contract prices, customer group discounts and volume tiers usually live in price lists or condition records, not on the item itself.
The split matters as soon as you design fields. A wholesaler that buys the same cable tie from two suppliers needs two supplier article numbers, two purchase prices and two lead times for one item number. Squeezing them into the item record as "supplier number 1" and "supplier number 2" works until the third supplier arrives, and then the purchase price on the item no longer says which supplier it came from.
Article master fields for a wholesaler, group by group
The table below lists the field groups a technical wholesaler typically maintains. The example is an illustrative black cable tie, 4.8 x 300 mm, sold per bag of 100 and bought per case of 20 bags. The values show the shape of the data, not a standard, and the GTINs use GS1's demonstration number.
Item master fields for one cable tie, by field group
| Identification | Item number | CT-4830-BK | ERP | Every order line and invoice refers to it, so a reused number mixes two articles' history |
|---|---|---|---|---|
| Identification | GTIN of the sales unit | 9506000134352 (bag of 100) | ERP, checked in the PIM | A wrong check digit fails at the scanner and in marketplace listings |
| Manufacturer | Brand and manufacturer part number | Example Fixings, CT4830B | ERP or PIM | Installers search by part number; spelling variants hide duplicates |
| Supplier relation | Supplier article number, purchase price, lead time | A-77120, USD 9.10 per bag, 10 days | ERP purchasing record | One item can have several suppliers, each with its own number |
| Units | Base unit, sales unit, purchase unit, conversions | Piece; bag = 100 pieces; case = 20 bags | ERP | A case price read as a piece price is off by a factor of 2,000 |
| Packaging levels | GTIN, content and dimensions per level | Case: 19506000134359, 20 bags, 40 x 30 x 25 cm | ERP | Slotting, freight quotes and pallet plans use these values |
| Logistics | Gross weight and dimensions with units | Bag: 0.26 kg, 30 x 12 x 3 cm | ERP or PIM | Mixed millimeters and centimeters break freight and feeds |
| Classification | ETIM class and features, internal product group | ETIM class for cable ties; group FIX-CT | PIM | Technical customers filter and compare on these features |
| Trade and compliance | HS code, country of origin, dangerous goods flag | Heading 3926, CN, no | ERP | Customs declarations and carrier bookings read them |
| Prices | List price, purchase price, VAT group | USD 12.40 per bag | ERP | Price lists and margin reports start here |
| Lifecycle | Status and successor item | Active; successor CT-4830-BK2 | ERP, mirrored in the PIM | Discontinued items stay orderable online when the status is not passed on |
Two notes on the example. The HS code shown is the four-digit heading for other articles of plastics (HS 3926); your customs broker confirms the full code for your own article. Classification works the same way at the level above: our ETIM classification walkthrough shows how a supplier catalog gets its ETIM classes and features.
Units and packaging levels: where item master errors start
Most item master errors in wholesale are unit errors. The supplier quotes per case, the webshop sells per bag, the installer counts pieces. The item master therefore holds one base unit, usually the smallest unit you count in stock, and a conversion factor for every other unit used in buying, selling and storing. Our unit of measure guide goes deeper into unit codes and conversions.
Packaging levels bring their own GTINs. GS1's GTIN Management Standard assigns a unique GTIN at every level of the packaging hierarchy above the base unit, and a change in the number of items in a case, or of cases on a predefined pallet, requires a new GTIN (GS1). So when a supplier moves from 20 to 25 bags per case, the case gets a new GTIN, and your item master needs a new packaging level rather than an edited quantity on the old one.
Three unit failures show up again and again in supplier files:
- Case price on the piece unit. The supplier lists USD 182.00 per case of 2,000 pieces. Loaded against the piece, every order line is wrong by a factor of 2,000.
- GTIN on the wrong level. The case GTIN 19506000134359 typed into the field for the bag means the scanner at the trade counter matches nothing, and the bag's own GTIN 9506000134352 is missing from every feed.
- Dimensions without a unit. One supplier sends millimeters, another centimeters, a third inches. A bag of 300 x 120 x 30 read as centimeters becomes three meters long in your freight calculation.
From supplier price file to orderable item in six steps
New items rarely start in the ERP. They start as rows in a supplier's price file or new-products sheet. A repeatable intake keeps the item master clean from day one:
- Match before you create. Look up each row's GTIN and manufacturer part number in the existing item master. A match means a new supplier relation for an existing item, not a new item.
- Fix the units first. Read which unit the supplier's price refers to (piece, bag, case) and which unit its GTIN identifies. Write both down per row before importing anything.
- Create the item from the product group template. Issue the item number, set the base unit and add every sales and purchase unit with its conversion factor.
- Add the packaging levels. One level per GTIN in the file, each with content, gross weight and dimensions in your house units.
- Attach the supplier relation. Supplier article number, purchase price per purchase unit, minimum order quantity and lead time go on the relation, not on the item.
- Release it. Set the status to active only when the required fields for that product group are filled, so the item cannot be ordered or published half-finished.
Steps 1 and 2 catch most problems. A supplier file that mixes piece and case GTINs in one column, or prices some rows per 100, is far cheaper to correct before import than after the first wrong delivery.
ERP item master and PIM: who writes which field
Our PIM vs ERP guide compares the systems. At field level the split is usually simple. The ERP owns what makes a transaction correct: item number, units and conversions, packaging levels, supplier relations, purchase and list prices, stock and status. The PIM owns what makes an article findable and understandable outside the company: marketing name, descriptions, classification features, images, documents, translations and channel-specific content.
A handful of fields sit on the border. GTIN, brand, manufacturer part number, weight and dimensions are entered in the ERP when the item is created, but every channel needs and checks them. Let them flow from the ERP to the PIM, and when the PIM finds an error, correct it at the source instead of fixing it twice. Pick one writer per field and make the other system read-only for it.
Who writes which item data
Write the split down per field, with a named role rather than a department, and say who checks each field after it is entered. A table like this one, agreed once with purchasing, the warehouse and e-business, settles most later arguments about who should have fixed what.
Field ownership in a wholesale item master
| Item number and status | ERP | Master data team | Purchasing and sales |
|---|---|---|---|
| Base unit and conversion factors | ERP | Master data team | Warehouse at goods receipt |
| Packaging levels and their GTINs | ERP | Master data team | Warehouse at goods receipt |
| Supplier article number, purchase price, lead time | ERP supplier relation | Purchasing | Finance through price variances on invoices |
| List price and price lists | ERP | Pricing or sales management | Sales |
| Sales unit GTIN, brand, manufacturer part number | ERP | Master data team | PIM checks before every channel |
| Weight and dimensions | ERP | Master data team, measured by the warehouse | PIM and carrier invoices |
| Descriptions, images, documents, translations | PIM | Product content team | Category manager |
| ETIM class and features | PIM | Product content team | Customers' catalog imports |
| Channel assortment and channel content | PIM | E-business | Channel error reports |
Code lists such as units, countries and product groups are reference data. They change rarely, but when they do, every item that uses them is affected. The reference data guide explains how to keep those lists apart from the items that use them.
Change control for fields that change what an order means
Most fields can change any day: a better description or a new image breaks nothing. A handful change what an order line means: base unit, conversion factors, case quantity, GTIN, purchase unit and status. Edit one of those on a live item and open orders, stock and price lists suddenly describe something else. Changes to them go through a short routine:
- Request with a reason and a date. Item, field, old and new value, and the date it applies, usually the day the supplier's new pack arrives.
- Check what is open. Open purchase and sales orders, stock on hand and price lists in the old unit or pack. A conversion change with stock on hand needs a stock correction on the same day.
- Decide: edit or new record. A typo is an edit. A changed case quantity is a new packaging level with a new GTIN, per the GS1 rule above. A different article is a new item number with a successor link.
- Approve by the field owner. The master data team for units and packaging, purchasing for supplier data.
- Apply on the date and pass it on. ERP first, then the PIM, webshop, feeds and customers' catalog files on their next run.
- Log it. Old value, new value, date and approver. When a customer disputes an invoice three months later, the log is the answer.
A Stammdatenpflege routine for a small master data team
Item masters decay through small edits: a buyer who overwrites a price, a new item copied from an old one with the wrong case quantity, a discontinued article nobody blocks. The routine below suits a team of one to three people who own item creation and maintenance next to their other work.
Item master maintenance checks
Most of these checks fail first in a supplier file, before anything reaches the item master. The supplier onboarding guide covers the data delivery spec and first-file triage for a new supplier. If one supplier's delivery keeps causing them, the free data readiness check has a person go through one of your supplier files with you on a call.
Lifecycle statuses that stop wrong orders
A status field only helps when everyone agrees what each value allows. Many wholesalers work with four: in preparation (visible to purchasing only), active (orderable and published), phase-out (sell remaining stock, no new purchase orders) and blocked (no sales, no purchasing, kept for history). Add a successor item to phase-out and blocked items, so sales staff and the webshop can point customers to the replacement instead of a dead end.
Item master vocabulary in English, German and Dutch
Wholesalers in the Netherlands, Belgium and Germany often work with suppliers, ERP consultants and software in all three languages. These are the terms you will meet; the German ones marked SAP are the names SAP itself uses in its German documentation, for example in its glossary.
- Item master: Artikelstamm (German), artikelstam (Dutch)
- Item master data: Artikelstammdaten, artikelstamgegevens
- Master data maintenance: Stammdatenpflege, stamgegevensbeheer
- Base unit of measure: Basismengeneinheit (SAP), basiseenheid
- Purchase order unit: Bestellmengeneinheit (SAP), besteleenheid
- Purchasing info record: Einkaufsinfosatz (SAP); Dutch has no fixed term, so describe it as inkoopgegevens per leverancier
- Packaging hierarchy: Verpackungshierarchie, verpakkingshiërarchie
Where the ERP item master ends and WISEPIM picks up
WISEPIM is a PIM, not an ERP, and it does not replace your item master. Its product record covers the item fields that channels need: GTIN with the check digit enforced when you save, brand or manufacturer, manufacturer part number, UPC, cost, weight and dimensions with explicit units, HS code and country of origin. Units are code sets with conversion factors, ETIM classes are assigned per product family in the optional Classification module, and products can follow lifecycle stages you define.
Several item master jobs stay with the ERP on purpose. WISEPIM has one free-text supplier field per product: no list of suppliers per product, no dedicated supplier article number field and no packaging-level records. Pack size or order unit for a BMEcat export can be stored as attributes. The practical setup is the ERP for identifiers, units, packaging and supplier relations, and WISEPIM for content, classification and the checks on top, such as a Quality Guard rule that keeps products without a valid GTIN out of a channel. See how that works for distributors on the PIM for wholesalers page.

