How To Measure Case Velocity: Formulas, Data Sources, And Examples

Case Velocity The rate at which cases of a product are sold, ordered, or moved through a channel. Measuring that rate reliably requires careful data selection, conversion rules, and smoothing techniques so velocity drives practical reorder and allocation decisions rather than noise.

Measurement begins with selecting the right numerator (cases) and denominator (time) and then choosing the window and adjustment rules that match operational needs. The most common mistakes are failing to convert unit-level sell-through into cases consistently and using short windows that reflect temporary promotional behavior as the new baseline.

Basic Formulas And Conversions

Start with a simple, auditable formula and add normalization steps as required by your network. Consistency is more important than complexity.

• Case Velocity (simple): Cases per day = Total cases moved in period / Number of days in period.
• Derived from units sold: Cases per day = (Units sold in period / Units per case) / Number of days in period.
• Rolling average: Use a 7-, 30-, or 90-day rolling average to smooth short-term variation: Rolling Cases/day = Average(Cases/day over rolling window).

Choosing The Right Time Window

Selecting a time window depends on volatility and lead times. Fast-moving consumer goods often use 7- to 30-day windows for tactical replenishment; seasonal or slow-moving items benefit from 90-day or longer windows to avoid reacting to noise. For promotional planning, measure promoted case velocity separately over the promotional period and compare against baseline.

• Short window (7–30 days): Good for fast movers and high-rotation items; be cautious around promotions.
• Medium window (30–90 days): Balances responsiveness with stability for most items.
• Long window (90+ days): Useful for slow-moving or seasonal items and strategic planning.

Data Sources And Reconciliation

Reliable measurement requires combining several systems. Map each data source to the part of the supply chain it represents and reconcile differences regularly.

• Point-of-Sale (POS): Best for sell-through; convert units-to-cases using a case configuration table.
• Warehouse Management System (WMS): Shows cases shipped out of DCs — useful to confirm replenishment volumes and detect pack-break events.
• ERP / Order Management: Captures supplier orders and receipts in cases; important for lead-time planning.
• EDI/ASN feeds: Provide supplier-side counts and can validate inbound quantities.

Normalizing For Pack-Break And Returns

Stores often break cases to sell units. If you calculate case velocity from POS units, ensure you model cases consumed by unit sells and adjust for instances where stores consolidate or transfer units between locations. Returns, spoilage, and damage must be subtracted from gross movement to get net case velocity.

• Pack-break modeling: Apply a conversion factor that reduces reported case consumption when evidence shows units are sold but cases are not fully consumed.
• Returns and spoilage: Subtract return and damage quantities from shipped or sold cases for net movement.

Advanced Methods: Forecast Integration And Demand Sensing

Case velocity is both a measured metric and an input to forecasting. Demand-sensing systems ingest POS and ship data to predict short-term velocity shifts and suggest order adjustments. Integrating case velocity into a demand-sensing or replenishment engine improves the signal used to calculate reorder points and allocation plans.

• Demand sensing: Uses near-real-time sell-through to adjust short-horizon velocity estimates.
• Forecast blending: Combine historical case velocity with predictive models to set safety stock and order quantities.

Example Calculation And Practice

Example: A beverage SKU sells 12,000 cans in 60 days across a store cluster. Each case contains 24 cans. Convert: 12,000 / 24 = 500 cases over 60 days => 500 / 60 = 8.33 cases/day. If lead time is 7 days and target service level requires 95% availability, use demand variability around the 8.33/day estimate to compute safety stock before setting reorder points.

Practical Tips For Implementation

Operationalize case velocity by embedding it into daily dashboards used by replenishment planners, DC managers, and merchandisers. Automate unit-to-case conversions and flag items where pack configurations change (e.g., promotional multipacks). Maintain a clear audit trail from source records to computed velocity so you can diagnose variance quickly.

• Tip: Automate case-configuration lookups and alert on exceptions where the conversion fails.
• Tip: Compute velocity at the channel and cluster level — don’t use a single network average for all stores.
• Tip: Version your velocity windows and document which windows drive which rules (e.g., 7-day for daily picks, 30-day for weekly replenishment).

In short, the Case Velocity — the rate at which cases of a product are sold, ordered, or moved through a channel — is a measurable, actionable metric when calculated from consistent data, normalized for pack-break and returns, and integrated into replenishment processes. Done well, it reduces stockouts, lowers carrying costs, and aligns ordering to the realities of cases, pallets, and transport.