Cases Per Order vs Units Per Order: Which Metric Should Fulfillment Teams Use?

Cases per Order is the number of full or partial cases represented in a wholesale order. It is one of several metrics teams use to quantify order size; another common metric is units per order (UPO), which counts individual sellable units rather than cases.

Units per order and cases per order answer different operational questions. UPO is a fine-grained metric used for slotting, replenishment thresholds, and putaway density. Cases per order captures handling at the case level—how many cartons, pallets, or case-picks the warehouse will process. Choosing which to prioritize depends on your SKU mix, labor model, and whether your customers or carriers price by case.

When Cases Per Order Is The Right Primary Metric

Cases per order is preferable when a large portion of throughput is handled as full cases or when case-breaks are costly. Examples include beverage distributors, CPG wholesalers, and grocery distributors that ship by the case or pallet. Using cases per order simplifies wave planning, pallet build rules, and carrier booking because it aligns directly with physical handling units rather than individual units.

When Units Per Order Is Better

Units per order works best when pick-by-unit dominates—for example, e-commerce fulfillment, small-item retail, or direct-to-consumer subscription businesses. UPO provides better insight into pick density, SKU velocity at the unit level, and packing workstation capacity because labor effort scales with the number of discrete picks rather than the number of cases.

• Case-Dominant Networks: Use cases per order for labor planning, palletization, and carrier dimensioning.
• Unit-Dominant Networks: Use units per order for wave design, picker throughput targets, and cartonization optimization.
• Hybrid Environments: Track both metrics and use rules to switch the operational focus depending on order profile.

How To Use Both Metrics Together

Most fulfillment operations are mixed; a pragmatic approach is to maintain both metrics and derive one from the other. Store case-pack metadata so the WMS can convert between units and cases in real time. For example, a replenishment system may trigger on cases for slow-moving bulk SKUs but on units for fast-moving e-commerce SKUs.

Practical Rules For SLA And Billing

When contracts or carrier rates reference cases, clarify whether partial cases are billed as full cases, whether case-break fees apply, and how returns of partial cases are handled. Include these terms in 3PL SLAs and merchant agreements to prevent disputes. Internally, tag orders in the OMS as full-case, case-break, or mixed so billing and warehouse instructions match the metric used.

Operational Example

Imagine two customers: Customer A orders pallets of beverage (case-dominant), while Customer B is a chain of convenience stores ordering a mix of full cases and single units. For A, plan labor and trailer space using cases per order and pallet patterns. For B, monitor UPO to size pick lines and packing stations and use cases per order only for those SKUs shipped as full cases.

In short, the Cases per Order metric should be part of a dual-metric strategy: use cases per order where case handling drives cost and complexity, and units per order where unit picks define labor and throughput. Accurate case-pack data and WMS logic let teams convert between the two seamlessly so planning, billing, and operations stay aligned.