What Is an 'Each' in Fulfillment and Inventory Management?

Each is the lowest commonly sold or handled individual unit in a product packaging hierarchy. In fulfillment operations the term describes the single unit that a customer buys or a picker moves — one bottle, one shoe, one phone, or one packaged snack. This unit is the foundation for SKU definition, unit-of-measure (UOM) tracking, and many day-to-day processes in a warehouse or 3PL environment.

Understanding what qualifies as an Each matters because it affects how you receive, store, pick, price, and report inventory. Some goods have an obvious each (a single packaged item). Others — like bulk materials or prepack apparel — require a business rule to define when an item becomes an each (for example, after retail packaging or inner packs are broken).

Why The Unit Matters

Operational decisions hinge on the each: pick logic, storage density, SKU velocity classification, and customer-facing information such as shipping weight and UPC/GTIN. Confusing an each with a case or pallet leads to mispicks, inaccurate stock-on-hand, and billing errors — all of which drive returns and extra cost.

How Systems Represent An Each

Warehouse management systems (WMS), inventory platforms, and enterprise resource planning (ERP) systems usually store an each as the base UOM for a SKU. The each is often tied to a unique identifier (SKU, GTIN/UPC/EAN) and a barcode label used for scanning at receipt, pick, and pack.

• Identifier: The each is commonly associated with a GTIN/UPC that identifies the single sellable unit for POS scanning and ecommerce listings.
• SKU/UOM Relationship: Inventory records map the each to higher packaging levels — e.g., 12 each = 1 case, 48 each = 1 pallet — so conversions are automatic in transactions.
• Barcodes: Scanning the each-level barcode should decrement inventory by one and trigger pick/pack workflows accordingly.

Receiving, Putaway, And Counting

Checking incoming quantities against purchase orders requires clarity about whether the PO line is for each, case, or pallet. When suppliers ship mixed packaging, receiving must convert case quantities to eaches if the WMS tracks stock at the each level. Cycle counts and physical inventories should sample at the each level for high-turn SKUs and at higher pack levels for slow-moving items.

Picking And Fulfillment Impact

Pick methods differ sharply when orders are fulfilled by each. Single-SKU, single-each orders favor piece-picking strategies with discrete pick carts or zone pickers. Mixed orders containing both each-level and case-level items require integrated workflows to avoid double handling — for instance using break-pack stations where a case is opened and eaches moved into picking flow.

Pricing, Shipping, And Costing

Costs and freight calculations often start at the each level: dimensional weight, declared value, and cartonization depend on the number of eaches packed into a parcel or master carton. Accurate each-level weights and dimensions reduce carrier disputes and improve transit estimates.

Practical Example

Consider a beverage company that ships 24 cans per case. In the WMS the SKU's base UOM is an Each (one can) with a GTIN assigned. Retail orders for single cans require pickers to break cases at a pick face or use pre-picked each inventory. A PO from a distributor arrives as 50 cases; the receiving clerk converts 50 cases × 24 each = 1,200 eaches into inventory. Sales reports and reorder points operate on the each level so store replenishment triggers correctly.

• Inventory Accuracy: Treating the each as the canonical stock unit simplifies cycle counting and reconciliations with point-of-sale systems.
• Customer Experience: Listing the each's weight and dimensions ensures accurate shipping quotes and fewer delivery surprises.
• Billing: Invoicing by each avoids disputes when customers buy single units versus whole cases.

Tips For Managing Each-Level Inventory

Define the each unambiguously in SKU master data and document any conversion rules for inner packs and cases. Train receiving staff to capture inner-pack breaks and ensure your WMS supports multi-level pack hierarchies. Use barcode labels at the each level and enforce scanning at every transaction to maintain traceability and reduce phantom inventory.

In short, the Each is the operational building block for fulfillment. When it's defined, tracked, and enforced across systems and processes, it improves order accuracy, inventory visibility, and downstream costing — all critical for a performant warehouse or 3PL operation.