What Is Case Velocity and Why It Matters in Retail

Case Velocity The rate at which cases of a product are sold, ordered, or moved through a channel. In retail, this simple definition becomes the basis for inventory planning, replenishment cadence, promotional sizing, and distribution-center slotting decisions.

Case velocity is a blunt, operational metric that translates consumer demand (units sold) into the pallet-and-case world used by suppliers, distributors, and warehouses. Retailers and 3PLs track case velocity to match order quantities to handling units, reduce stockouts, size reorders, and forecast space and labor needs. While unit-level sales data and SKU-level velocity are important, case velocity is the link between store or DC demand and the physical containers carriers and suppliers actually move.

What Case Velocity Covers

Case velocity measures flows at the case level rather than the single-unit level. That means it captures activity that directly affects packaging, transportation, and handling: shipment frequency, case quantities per pallet, and replenishment cycles. It does not inherently capture point-of-sale nuances like multi-SKU bundles or consumer pack-break activity unless those are translated back into cases.

• Sales-to-ship correlation: Tracks how many cases must leave the DC or supplier to satisfy downstream sales.
• Order planning: Drives order frequency when suppliers minimums or pack sizes are specified in cases.
• Warehouse operations: Informs pick locations, palletization, and dock scheduling.

Why Case Velocity Matters To Retailers And 3PLs

Case velocity affects cost, service, and operational efficiency. Fast-moving cases demand frequent replenishment and tight safety-stock controls; slow movers need storage optimization to avoid wasting prime pick locations. For retailers negotiating with suppliers, case velocity provides bargaining power around lead times, minimum order quantities (MOQs), and promotional allocation. For 3PLs and warehouses it helps determine labor plans, cross-dock frequency, and yard/dock capacity.

• Cost-to-serve: High-velocity items reduce per-case handling cost but increase freight frequency; low-velocity items can cost more per case to store and handle.
• Service levels: Accurate case-velocity forecasts reduce stockouts at stores and e-commerce backorders.
• Space planning: Drives decisions on reserve vs. pick storage and pallet racking needs.

How Case Velocity Is Calculated

The basic calculation is straightforward: divide the number of cases sold, ordered, or moved during a period by the length of that period. The challenge lies in selecting the right period and data source so the metric reflects operational reality.

• Simple formula: Cases per period = Total cases (sold/ordered/moved) / Number of days (or weeks) in period.
• Rolling averages: Use 7-, 30-, or 90-day rolling windows to smooth seasonality and promotional spikes.
• Normalized velocity: Adjust by store cluster or channel (e.g., club vs. convenience) to reflect differing demand patterns.

How It Varies Across Channels And Seasons

Case velocity is channel- and context-sensitive. A grocery chain's case velocity for an item will differ between mass-market stores, online fulfillment, and club channels. Promotional events, holidays, and weather can create short-duration surges that inflate short-window velocity and mislead reorder triggers if not reconciled with normal demand.

• Channel mix: E-commerce orders may break cases more often than club-channel bulk purchases.
• Promotions: Temporary uplifts require promoted-velocity tracking to size temporary replenishment correctly.
• Seasonality: Use seasonal indices to convert observed velocity into a normalized baseline.

Data Sources And System Integration

Reliable case-velocity measurement depends on integrating POS, WMS, and ERP/TMS data. Point-of-sale registers provide sell-through. Warehouse systems show ship quantities. Supplier EDI or ASN feeds can show inbound case counts. Reconciliation between systems removes double-counting where stores break cases or where returns and spoilage impact net movement.

• POS data: Best source for sell-through but must be converted from units to cases.
• WMS/ERP shipment data: Shows how many cases were moved from DCs or suppliers.
• EDI/ASN feeds: Useful for supplier-side confirmation of cases shipped and received.

Practical Example

A regional grocery chain sells 3,000 units of canned tomatoes at a store cluster over 30 days. Cases contain 24 cans each. Convert units to cases (3,000 / 24 = 125 cases). The 30-day case velocity is 125/30 = 4.17 cases/day. Use a 30-day rolling average and compare to historical seasonal baselines before setting reorder points and safety stock.

Common Pitfalls And Tips

Case-velocity signals are powerful when interpreted correctly. Avoid using short windows during promotions as the only input for reorder quantities. Explicitly account for pack-break (when stores sell units from a case), returns, and spoilage. Where packaging varies between regions, normalize by GTIN and case configuration.

• Tip: Maintain a case-configuration master file (cases per SKU) to automate unit-to-case conversions.
• Tip: Segment items by velocity band (fast, medium, slow) and apply different replenishment rules.
• Tip: Combine case velocity with lead-time variability to compute reorder points rather than using velocity alone.

In short, the Case Velocity metric — the rate at which cases of a product are sold, ordered, or moved through a channel — converts demand signals into the practical language of cases and pallets. When measured, normalized, and integrated with systems, it supports smarter ordering, better DC planning, and lower total supply-chain cost.