CPG Terms Explained, a series by Cyril Ovely

What Is Velocity in CPG? The Retail Sales Rate That Reveals True Product Performance

Velocity is the rate at which a product sells through retail outlets, measured as units per store per week or sales per $MM ACV. It is the productivity metric for distribution: high velocity means products sell fast where placed; low velocity signals assortment, pricing, or execution problems.

The short answer

Velocity tells you how fast a product moves off the shelf, not just how many stores carry it. How well does it actually sell?

Two common expressions: units per store per week counts how many items a typical outlet moves each week. Sales per $MM ACV normalizes dollar sales by the ACV distribution footprint for cross market comparisons.

Why velocity matters in CPG

Distribution gets a product into stores. Velocity determines whether it stays there. Retailers have finite shelf space, and every SKU competes for it. A product in 5,000 stores selling one unit per store per week is occupying shelf real estate without earning its keep.

The decisions velocity informs:

  • Diagnosing distribution quality: "We're in 1,200 stores, but velocity is half the category average. Wrong stores, or a product problem?"
  • Benchmarking against competitors: "Our velocity is 4.2 units per store per week. The leading brand moves 8.1. What are they doing differently?"
  • Predicting listing success: "If we pitch this new SKU, what velocity can we demonstrate from comparable markets?"
  • Promotion planning: "Baseline velocity is 3.0. The last promotion lifted it to 7.5 for two weeks. Was the margin tradeoff worth it?"

Without velocity, you only know where your product is. Velocity tells you how well it performs.

For the technically minded: Velocity is a per-store-per-week rate metric feeding directly into forecasting and replenishment systems. It's computed as total units sold divided by (stocking stores × weeks). Forecasting engines use this rate to predict store level demand, and replenishment algorithms convert it into order quantities. It's a rolling calculation that updates each period as new scan data arrives.

How velocity works in practice

Scenario: A snack brand across four retail chains:

Retail ChainStores CarryingWeekly Unit SalesUnits/Store/Week
MegaMart1202,16018.0
SuperSave2802,5209.0
QuickStop4001,2003.0
FreshFoods903604.0
Total (weighted avg.)8906,2407.0

The aggregate of 7.0 units per store per week masks enormous variation. MegaMart moves 18 units weekly; QuickStop manages only 3. The product thrives in large format stores but underperforms in convenience. Maybe QuickStop needs smaller pack sizes, or those 400 stores would be better replaced with 100 higher velocity locations.

Velocity vs. distribution: the tradeoff

Expanding into new stores almost always lowers average velocity because the marginal stores sell less than the ones you already have.

  • Selective distribution (fewer stores, higher velocity): strong average velocity, but total volume is capped by limited reach.
  • Broad distribution (more stores, lower velocity): maximum reach, but weaker stores dilute the average.
  • Optimal distribution is where total volume is maximized without wasting supply chain cost on stores that barely move product.

Leading teams plot velocity against cumulative ACV to find the inflection point where adding more stores no longer justifies the cost.

Key metrics & related concepts

  • Units Per Store Per Week (UPSW): the most common velocity expression; total units divided by stocking stores and weeks
  • Sales per $MM ACV: dollar velocity normalized by distribution weight; useful for cross market comparisons
  • Rate of Sale (ROS): often used interchangeably with velocity, though some reserve ROS for individual SKU performance
  • Velocity × Distribution = Volume: the fundamental identity; total sales equal the velocity rate multiplied by stocking stores
  • ACV Distribution: the weighted store coverage metric that velocity is often normalized against

Common mistakes & misconceptions

Mistake #1: Confusing velocity with total sales.
A brand doing $10M annually might look successful. But if that requires 5,000 stores, velocity could be quite low. Total sales measure scale; velocity measures efficiency.

Mistake #2: Not normalizing by distribution.
Comparing raw sales across markets without accounting for store counts is misleading. A 200 store market will outsell a 50 store market even if per store productivity is identical.

Mistake #3: Using velocity in isolation.
A product with 20 units per store per week in only 10 stores has impressive velocity but negligible market impact. Pair velocity with distribution metrics.

Mistake #4: Ignoring the time dimension.
New launches may show artificially high velocity from trial. Seasonal products have velocity spikes. Always compare across equivalent time periods.

Regional variations

Global: Velocity is universal, but practices vary:

  • US: Circana provides standardized velocity data from scanner panels. Units per $MM ACV is the dominant expression.
  • UK: Kantar and Nielsen report velocity through EPOS data, with channel breakdowns for multiples and convenience.
  • India: Velocity measurement is challenging due to fragmented traditional trade. Distributor systems provide estimates, but store level velocity is less precise than in organized markets.
  • NZ/AU: NielsenIQ and Circana (formerly Aztec) calculate velocity from scanner data. With concentrated retail, velocity differences between chains are a key strategic input.

How leading CPG teams use velocity

Modern commercial teams treat velocity as the diagnostic heartbeat of distribution strategy. Tracking velocity at the store chain level reveals which partners deliver the best return on shelf space. Integrated with field execution platforms, velocity data connects to on shelf availability and promotional effectiveness, closing the loop from distribution to sell through.

Sources and further reading


Lighthouse for CPG

See how Lighthouse turns these terms into retail execution

Lighthouse connects distribution, execution, trade, and supply into one system your commercial teams act on at the store and SKU level.

Request a demo
Cyril Ovely
Co-Founder and CTO, Vxceed

Cyril is the Co-Founder and CTO at Vxceed. With over two decades of experience in engineering and entrepreneurship, he focuses on building scalable SaaS solutions that transform demand chain execution and help businesses operate with greater agility in evolving markets.