Unit of Measure

A retailer buys drinks by the case and sells them by the bottle, so its inventory system needs to know how many bottles are in each case, otherwise both stock and unit cost can be wrong. Microsoft's Business Central guidance describes setting up item units of measure and quantities per unit, so the base unit lets transactions convert consistently, though the exact field names differ by software.

A fictional cafe buys a case of 24 bottles for $72, so its purchase cost is $3 per bottle before other costs, and if it records the case as one bottle its inventory and margin reports fail. Units can describe counts, weight, volume, length or time, so choose a unit that matches the physical product and business process, since an each is not interchangeable with a kilogram.

Some conversions are fixed, such as metres to centimetres, as Oracle's inventory documentation explains for conversions within and across unit classes, while others depend on the item: a fictional hardware seller buys screws by the carton and stocks them by the box, and a different screw pack may have a different conversion. Packaging levels add complexity because one pallet may contain several cases and one case several items, so validate the hierarchy with supplier data, and for variable-weight goods such as cheese wheels use an actual-weight process where required.

Unit labels should be visible on purchase orders, receipts, stock records and invoices, because a supplier may quote per hundred pieces while the buyer expects each. A conversion error can multiply a cost or quantity by ten or more, so review unusual unit prices and negative stock.

A fictional builder orders 100 metres of cable but a system treats the quantity as 100 rolls, which would make the purchase order far larger than intended, and a clear unit field and approval check prevent the error. Selling units may differ from stock units.

A retailer can sell a six-pack assembled from individual cans, so the system needs to remove six cans from stock for each pack sold. Returns need the same conversion logic, since a returned case should restore the correct item count and condition and a damaged or open pack may need a separate inventory status; a fictional wholesaler that receives back half a case cannot simply add one full case to available stock.

Cost per selling unit is purchase cost divided by the number of selling units when the pack conversion is fixed, and freight, waste or other landed costs are added separately if the costing policy includes them. A fictional bakery buys flour in 25-kilogram bags and uses recipes in grams, so it maps kilograms to grams and records waste.

Global operations may use different measurement systems, so convert carefully and specify rounding rules, because small rounding errors can matter in bulk commodities or regulated labels. Changing a unit setup after transactions exist can affect history and open orders, so test the impact and follow software controls instead of silently altering a conversion to make one count balance.

Master data should have an owner, and suppliers may change pack sizes while keeping a similar product name, so conversions should be reviewed when new stock arrives. A unit of measure is a small field with large consequences: define the base, purchase and selling units, validate item-specific conversions and check transaction results to support reliable stock, costing and invoices.