Case as Each vs Loose Each: Inventory, GTIN, and Picking Differences

Case as Each is a packaging configuration in which the case itself is the lowest orderable or sellable trade item and its contents are not sold separately. That strict definition separates it from configurations where individual items (each) are sold separately or where both case and each are orderable.

Comparing "case as each" to a loose-each model clarifies the operational, systems, and commercial consequences for warehouses, retailers, and carriers. This comparison covers unit-of-measure management, barcode and GTIN practices, picking strategies, storage, and cost implications.

Unit-of-Measure And SKU Management

Under a case-as-each model the case is the SKU. The WMS records inventory by case UOM. In a loose-each model the individual item (the each) is the SKU and the case is a parent or packaging container that may have its own GTIN but is not the primary sales unit. Hybrid models allow both case and each SKUs and therefore require conversion factors (e.g., 24 eaches per case) tracked in the system.

Barcodes, GTINs, And Electronic Commerce

Standards bodies such as GS1 define GTIN usage for trade items. When a case is the unit of sale its GTIN is used in purchase orders, invoices, and EDI transactions. In loose-each scenarios retailers and marketplaces expect the consumer UPC/GTIN associated with the individual item. Omitting or misapplying GTINs causes listing rejections, chargebacks, or scanning failures at POS or DC gates.

Picking And Fulfillment Differences

Picking workflows diverge sharply:

• Case as Each Picking: Fulfillment teams pick whole cases; pick lists show case quantities; staging and shipping are case-focused, often using pallet or multi-case cartonization.
• Loose Each Picking: Piece-picking or multi-SKU order consolidation is required; pickers handle individual items and may use pick-to-light, voice, or batch picking optimized for single units.
• Hybrid Complexity: Maintaining both case and each SKUs increases WMS complexity: conversion math, wave logic, and inventory reconciliation must always be handled precisely.

Storage And Slotting Impacts

Case-focused operations optimize for bulk storage: pallet racks, deep lanes, and case flow systems. Loose-each operations emphasize pick-face shelving, bins, and gravity flow for piece picking. Switching from one model to the other changes slotting rules, travel-time calculations, and space utilization. For example, case as each reduces the number of pick faces but increases the need for lift equipment and larger pick aisles.

Cost And Labor Trade-offs

Case-as-each reduces per-unit handling time because workers move larger lot sizes and perform fewer picks per order. This often lowers labor cost per sellable unit and speeds throughput. However, shipping costs may increase for small-quantity customers forced to buy whole cases. Loose-each supports direct-to-consumer and retail sales where customers buy single units, but it raises labor for piece-picking and increases packing materials used for small shipments.

When To Use Each Model

• Case as Each Appropriate: B2B channels, foodservice, wholesale distributors, and bulk retail where buyers accept case-level purchases.
• Loose Each Appropriate: E-commerce, brick-and-mortar retail selling single units, subscription boxes, and promotional distribution requiring single-item handling.
• Hybrid Appropriate: Businesses that sell to both distributors and consumers and can justify the systems cost to track both SKU types.

Practical Tips For Transition Or Mixed Environments

When a warehouse must manage both case-as-each and loose-each SKUs, follow these practices:

• Master Data Discipline: Maintain accurate conversion factors (items per case), GTINs, and packaging attributes in a single source of truth (ERP/WMS).
• WMS Rules Engine: Use picking logic that respects order type — auto-convert for mixed orders, and prevent accidental splitting of case-sold SKUs.
• Clear Labelling: Use case labels that show both case GTIN and inner-item GTIN when inner GTINs exist for traceability.
• Customer-Facing Messaging: Clearly state ordering units on product pages to avoid unexpected case purchases by consumers.

In short, the Case as Each model and the loose-each model represent two ends of a spectrum: one favors streamlined, high-throughput case handling and the other favors customer-level flexibility. Choose the model that matches your channel mix, WMS capabilities, and customer expectations to avoid inventory mismatch and service problems.