Case
A case, in inventory and warehousing, is a master pack, case pack, or vendor pack: the larger outer carton containing multiple inner packs or selling units. It is also a pack-size unit of measure in item master data used for receiving, put-away, replenishment, pick/pack, and production issue, enabling tracking by each, inner pack, and case.
On the shop floor and in the warehouse, case-level unit of measure lets receiving teams book inbound cartons exactly as shipped, then convert them to inventory balances for storage, kitting, or production issue without counting every piece. Master packs standardize pallet build, slotting, replenishment, and carton handling, reducing touchpoints and making stock movement controllable. In manufacturing, raw materials and subassemblies are often consumed in fixed carton quantities; ERP or WMS decrements inventory by case, inner pack, or each depending on transaction type. Case-based structure supports variance control by comparing received cases with purchase orders and triggering discrepancy workflows before stock is released. Case identifiers tied to lot, batch, or supplier shipment records allow quality holds, recalls, and FEFO/FIFO at carton level. This carton-level traceability improves inventory accuracy and reduces reconciliation effort across raw material, WIP, and finished goods.
- Unit-of-measure mismatch: PO says ten cases, but item master is in eaches. Wrong conversion creates receiving errors, phantom inventory, and unreliable MRP signals that trigger shortages or unnecessary replenishment.
- Broken case integrity: Cases are broken early or mixed with full cases without clear rules. This skews bin balances, increases cycle-count errors, and leaves production with partial material when a full case is required for batch issue.
- Supplier pack-size drift: Supplier changes case count or labeling, but master data stays old. Receipts mismatch, traceability gaps appear, and planners see shortages because one case no longer equals the planned quantity.
Why does case-level tracking matter in MRP?
Planning accuracy depends on correct conversion factors between case, pack, and each. Wrong conversions distort demand, safety stock, reorder points, and available-to-promise quantities.
When should a case be broken?
When the process requires smaller issue quantities, such as kitting, line-side replenishment, or customer pick eaches. Otherwise, intact cases preserve handling efficiency and inventory accuracy.
What data fields are typically needed for case control?
Item number, case-pack quantity, inner-pack quantity, UOM conversion, lot/batch, supplier pack spec, receipt quantity, bin/location, and transaction timestamp.