Unit of Measure
A unit of measure is the unit stored in the item master in which an item is counted, stored, purchased and sold – such as piece, box, kilogram or litre. It defines what stock levels, prices and quantities refer to on every document.
A unit of measure is the unit in which an item is recorded by quantity in the ERP system – that is, counted, stored, ordered and sold. Typical examples are piece, pair, box, pallet, kilogram, litre or metre. As an attribute of the item master, the unit of measure determines what every quantity on a document refers to: without it, the number "12" is meaningless – only "12 pieces" or "12 boxes" produces an unambiguous, processable figure.
Because purchasing, warehousing and sales often handle the same item in different units, ERP systems usually maintain several units of measure per item with stored conversion factors. A beverage, for example, is purchased by the pallet, stored by the box and sold by the bottle. The unit of measure is therefore far more than a label: it is the basis for accurate inventory management, consistent pricing and automatable processes across all channels.
At a glance
- The unit an item is counted, stored, purchased and sold in (piece, kg, litre, box …)
- An attribute of the item master – without it, every quantity is ambiguous
- Usually several units per item with conversion factors (base, purchasing, sales, storage unit)
- The base unit is the reference quantity for stock and valuation
- An incorrect conversion leads to wrong stock levels, prices and invoices
What is a unit of measure and what types are there?
The unit of measure sets the scale in which the quantity of an item is expressed. In principle, a distinction is made between countable (discrete) units such as piece, pair or box and measurable (continuous) units such as kilogram, litre or metre. Countable items are kept in whole units, while measurable ones can take decimal quantities – a difference that, in the ERP system, affects the permitted decimal places and the price calculation.
In practice, the same item often carries several roles of units. They do not describe different products, but different packaging and handling levels of one and the same item, linked by fixed factors.
Base unit, purchasing, sales and storage unit
The base unit (also stock or inventory unit) is the smallest, indivisible reference quantity – usually piece or the relevant base measure. Stock is kept and valued in it. Derived from it are the purchasing unit (in which orders are placed, e.g. box or pallet) and the sales unit (in which items are sold, e.g. piece or pack). Every differing unit is linked to the base unit via a conversion factor, such as "1 box = 24 pieces".
How the conversion of units of measure works
At the heart of any multi-level unit handling is the conversion factor, which relates a unit to the base unit. If a system posts an order of "5 boxes" with 24 pieces per box stored, it internally creates a receipt of 120 pieces in the base unit. The sale of "3 pieces" reduces stock by exactly that quantity. In this way, stock remains consistent even though purchasing, warehousing and sales work with different units.
Prices are usually tied to a specific unit – for example a sales price per piece and a purchase price per box. When a document is created, the ERP system converts between the units so that line quantities, stock postings and valuations match. If the conversion factor is maintained incorrectly, the error propagates unchecked through stock, price calculation and valuation.
Distinction: unit of measure vs. packaging unit
The terms overlap but mean different things. The unit of measure is the abstract counting or measuring quantity of an item. The packaging unit specifically describes how many base units are grouped into one physical package (for example 24 bottles per outer carton). A packaging unit is therefore often a special, packaging-related form of a unit of measure with its own factor – relevant for picking, shipping and palletising.
The unit of measure in the ERP system
In the ERP system, the unit of measure is a mandatory attribute of every item master record and connects almost all modules. Purchasing orders and posts goods receipts in the purchasing unit, inventory management keeps stock in the base unit, sales creates quotes and invoices in the sales unit, and accounting values stock on the basis of the base unit. Because all processes access the same stored factors, quantities and values stay consistent across the entire process.
The role of the unit of measure becomes especially visible in e-commerce and multichannel sales. Shops and marketplaces expect clearly defined sales units, and stock synchronisation between channels only works reliably if the same base unit underlies everything. If one shop sells a "6-pack" and another sells a "single item", the system must map both to the same stock level via the correct factor – otherwise overselling or misstated availability threatens.
Units also play a role via interfaces and standards: EDI messages, product feeds and classification systems such as ECLASS carry units of measure in coded form. Internationally common is the UN/ECE code (Recommendation 20), which makes units such as piece (H87), kilogram (KGM) or litre (LTR) unambiguously machine-readable.
Why the right unit of measure matters
A cleanly defined unit of measure is a prerequisite for reliable stock levels and correct documents. If the unit or its conversion factor is wrong, stock discrepancies, incorrect line quantities and faulty invoice amounts arise – errors that are hard to spot in day-to-day business because the figures look plausible on their own. Particularly with measurable units, incorrect decimal places or confused weight and piece figures quickly lead to noticeable value and quantity deviations.
The unit is also decisive for analyses: metrics such as inventory turnover, sales volumes or days of supply are only comparable if they are based on a uniform reference quantity. If quantities of different units are summed without adjustment, any statistic becomes unusable. A consistent unit logic is therefore a quality factor not only operationally but also for controlling and planning.
DACH specifics and maintenance
In the DACH region, units of measure reach into legally relevant documents. On invoices, the quantity of goods delivered must be stated under the VAT Act (Umsatzsteuergesetz), which requires an unambiguous, traceable unit of measure. For price statements to consumers, the Price Indication Regulation (PAngV) additionally requires base prices per defined unit – for example per kilogram or litre – which makes correct storage of the base and sales unit in the ERP system necessary.
For maintenance, a deliberate, standardised approach to units is advisable: a manageable, company-wide list of permitted units of measure, clearly defined base units per item type and verified conversion factors. In a data migration to a new system, units and their factors are among the critical fields that should be harmonised and tested before transfer, so that stock levels and values are correct in the target system.
Example
Example: a beverage wholesaler keeps one item in three units
A beverage wholesaler sells a lemonade both to hospitality businesses and via its own online shop. In the ERP system it defines the base unit "bottle". On this it bases two further units: "crate" with a factor of 12 (12 bottles) as the sales unit for hospitality, and "pallet" with a factor of 720 as the purchasing unit towards the bottler.
When purchasing orders two pallets, the system posts 1,440 bottles as a receipt. When a restaurateur buys five crates, 60 bottles are issued. The online shop, in turn, sells individual bottles. Because all channels access the same bottle stock via the stored factors, availability stays synchronised everywhere, overselling is avoided, and the invoices each show the correct unit and matching price.
Frequently asked questions
Related services
Sources
Questions about Unit of Measure in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.