Case Pack Quantity
Is case pack quantity the same as MOQ?
No. Case pack quantity is the fixed number of units per carton; MOQ is the minimum quantity a supplier requires per order, which may be expressed in units, dollars, or whole cases.
Is case pack quantity the same as pack size or vendor pack?
Often yes in practice, but terminology varies by trading partner and system; sources use pack size, vendor pack, master pack, and case pack interchangeably in some contexts, while GS1 and ERP packaging hierarchies distinguish case, inner pack, and each.
Why does case pack quantity matter for ASN accuracy?
Advance ship notices and receiving systems frequently validate carton-level quantities against the stored pack configuration; if the declared carton count does not match the master data, the shipment can be partially received or held for exception processing.
Case Pack Quantity is the fixed number of sellable units contained in one master carton, case, or shipping case. In supply chain terms, it is the count of items that must be ordered, received, stored, and shipped as a single packaged unit. It acts as the ordering multiple or pack size, meaning buyers cannot always purchase arbitrary quantities without breaking a case.
On the shop floor and in distribution, case pack quantity anchors the packaging hierarchy that links eaches, inner packs, and cartons. ERP and WMS systems rely on this configuration to convert unit-level demand into pickable, shippable cases. When goods arrive, a single scan of the case GTIN resolves to the stored pack quantity, enabling automated putaway and quick receiving reconciliation without manual item-by-item counting. Replenishment planners also depend on it: forecasted unit demand must be translated into whole cases for purchase orders, which directly affects MOQ compliance, truckload utilization, and pallet build efficiency. At the packing line, the configured case pack tells operators exactly how many finished goods belong in each outbound carton. When the actual line count matches the master data, ASNs validate cleanly. For raw materials, a consistent case definition supports lot traceability and carton-level consumption tracking across pallet, case, and each storage locations.
Short-pick stockouts: Demand of 37 units with a 12-unit case pack forces an order of 36 or 48. Under-ordering triggers short picks at the dock or line-side; over-ordering locks cash into slow-moving inventory and consumes valuable floor space.
Receiving and ASN mismatches: If the supplier ships 10 units per case but ERP master data says 12, the WMS flags a quantity discrepancy, forcing manual recounts, delayed putaway, and either chargebacks or rejected receipts.
Barcode scanning errors from bad packaging hierarchy: Misconfigured case, inner pack, and each data makes the system treat a shippable carton as individual units or vice versa, causing wrong pallet configuration and fulfillment processing delays.