Each
Each is an individual unit of measure used to count or price inventory items one by one, rather than by weight, length, volume, or package. In inventory and procurement systems, it typically means 'one item per count' in a master data or transaction record, serving as the smallest countable stock unit for discrete items like components or finished goods.
On the shop floor, each is the default counting unit when material moves as discrete pieces rather than bulk quantities. Receiving teams record cartons as individual units in the item master, then cycle counters scan bins and reconcile every piece against the system's transaction history. When production issues fasteners, connectors, castings, or electronic components, each receipt, pick, transfer, and scrap event is posted as a separate row, allowing live on-hand quantities to be recalculated by item and location. This unit-level tracking matters most in multi-location or line-side environments, where a mismatch between physical and system stock causes immediate stockouts on the wrong shelf or warehouse. Because each drives reorder levels, available-to-promise, and issue quantities, the entire replenishment loop depends on every movement being logged in the same discrete unit.
When should 'each' be used instead of EA, pcs, or unit?
Use it when the business process counts discrete items one by one. EA, pcs, and unit are common abbreviations, but the operational meaning is the same if the master data is configured consistently.
Does 'each' imply serialization or lot tracking?
No. 'Each' only defines the unit count. Serialization or lot/batch tracking is a separate control layer that records identity, traceability, production date, or expiry for individual units.
Why does 'each' matter in an ERP or inventory database?
Because the item's base unit of measure drives conversions, reorder thresholds, issue quantities, and stock reconciliation. If the base UOM is wrong, all downstream transaction math is wrong.