CPG Terms Explained, a series by Cyril Ovely

What Is Rate of Sale (ROS)? The CPG Metric That Tells You How Fast Products Actually Move

Rate of Sale (ROS) is the number of units a product sells per store per time period, usually measured weekly. It is a fundamental indicator of how quickly a product moves off the shelf at the individual store level.

The short answer

Rate of Sale (ROS) answers a deceptively simple question: how many units of this product does the average store sell each week? If your cereal brand moves 12 boxes per store per week, that is your ROS. No weighting, no normalization, just raw movement at the shelf.

ROS is one of the most granular performance measures available to CPG teams. While market share tells you how you compare across a region, and ACV tells you how wide your distribution reaches, ROS tells you what is actually happening in each store, one shelf at a time.

Why it matters in CPG

Picture this. Your brand is listed in 2,000 stores across a territory. The total weekly sales look healthy at 18,000 units. But when you divide by store count, the average ROS is just 9 units per store per week. Some stores move 40 units. Others move 2. The average hides enormous variation, and that variation is where the real decisions live.

The decisions ROS informs:

  • Assortment planning: "Should we keep this SKU in underperforming stores, or delist it and replace it with a better performer?"
  • Space allocation: "Stores with a ROS above 20 need more shelf facings. Stores below 5 may not justify the space."
  • Store benchmarking: "Store A and Store B have similar footprints, but Store A's ROS is three times higher. What is different?"
  • Promotion evaluation: "ROS jumped from 8 to 22 during the promo week. Did we gain new buyers or just pull forward demand?"
  • New product launches: "The new variant is doing 6 units per store in week one. The benchmark for a successful launch is 10."

Without ROS, you are managing your brand by aggregate numbers that smooth over the store level realities where products actually win or lose.

For the technically minded: ROS is a per-store, per-period scalar that feeds directly into replenishment algorithms and planogram optimization engines. In a data model, each SKU store combination carries a ROS value computed as units_sold / period_days, typically normalized to a 7-day window. Downstream systems use this scalar to calculate days of supply, trigger auto replenishment orders, and score planogram compliance. It is the atomic input that connects point of sale data to supply chain execution.

ROS vs. velocity: what is the difference?

These two terms get used interchangeably in casual conversation, but they are not the same thing. Understanding the distinction matters when you are building reports or making decisions.

AspectRate of Sale (ROS)Velocity
DefinitionUnits sold per store per time periodUnits sold per store per time period, normalized by ACV or distribution
ScopeRaw, store level measureWeighted or normalized measure
Typical useStore level performance, shelf planningMarket level benchmarking, distribution efficiency
FormulaUnits sold ÷ number of selling stores ÷ weeksUnits sold ÷ ACV weighted distribution ÷ weeks
Answers"How fast does this product move in a typical store?""How fast does this product move relative to its distribution footprint?"
Example12 units/store/week$4.80 per ACV point/week

In practice, ROS is the raw input and velocity is the derived metric. You need ROS first before you can compute velocity. Confusing the two leads to apples-to-oranges comparisons, especially when evaluating brands with very different distribution profiles.

How it works in practice

Scenario: You manage a snack brand with four SKUs across a chain of 300 stores. Here is the weekly performance data:

SKUStores SellingWeekly Units SoldROS (units/store/week)
Classic Chips 150g2903,48012.0
BBQ Chips 150g2502,0008.0
Salt & Vinegar 100g1805403.0
Premium Truffle 80g901351.5
Brand Total300 (unique)6,155~6.2 avg

The Classic Chips SKU is your workhorse, moving 12 units per store per week across almost the entire chain. The Premium Truffle variant sells just 1.5 units per store per week and only reaches 90 stores. The brand average of 6.2 units masks a wide gap between your top and bottom performers.

What a CPG team does with this data:

  • Classic Chips gets priority shelf space and more facings in every store.
  • BBQ Chips is a solid performer but could benefit from promotional support to close the gap with Classic.
  • Salt & Vinegar needs a decision. Is the low ROS a placement problem (poor shelf position) or a demand problem (shoppers do not want the flavor)?
  • Premium Truffle may only belong in high income stores where its ROS could justify the listing.

Key metrics & related concepts

  • ROS (Rate of Sale): units sold per store per time period, the raw shelf movement measure
  • Velocity: ROS normalized by ACV or distribution weight, used for market level comparisons
  • Days of Supply: how many days the current on-hand inventory will last at the current ROS rate
  • Facings: the number of product units visible on the shelf, directly influenced by ROS
  • Out of Stock (OOS): when a product is unavailable on the shelf despite consumer demand, often caused by underestimating ROS
  • ACV (All Commodity Volume): the total sales volume of a store, used as a weighting factor for velocity calculations

Common mistakes & misconceptions

Mistake #1: Using brand average ROS to set store level decisions.
An average ROS of 6.2 units does not mean every store sells 6.2 units. Store level ROS can range from 0 to 40. Applying the average to all stores leads to overstocking in slow locations and stockouts in fast ones. Always look at the distribution of ROS values, not just the mean.

Mistake #2: Ignoring the difference between selling stores and total stores.
If your product is listed in 300 stores but only 180 are actually selling it, your ROS should be calculated against the 180 selling stores, not all 300. Including zero sale stores deflates the metric and gives a misleading picture of shelf performance.

Mistake #3: Treating ROS as a static number.
ROS fluctuates with seasonality, promotions, competitor activity, and even day of the week. A single week's ROS is a snapshot, not a trend. Track ROS over rolling 4-week or 13-week windows to separate signal from noise.

Mistake #4: Confusing high ROS with high profitability.
A product moving 30 units per store per week at a thin margin may generate less profit than a niche item moving 5 units at a healthy margin. ROS measures movement, not margin. Pair it with profitability data for a complete picture.

Regional variations

Global: ROS is used in every CPG market, but the way it is collected and applied varies by region:

  • US: Scanner data from Circana (formerly IRI) provides store level ROS as a standard metric. Retail Link from Walmart and similar retailer portals give suppliers direct ROS dashboards.
  • UK: Kantar and Nielsen calculate ROS from EPOS data. The concept is sometimes referred to as "sales velocity" or "weekly off take" in retailer planning teams.
  • India: With a large traditional trade segment, ROS estimation often relies on distributor sales data and beat level reporting rather than scanner data. AI powered field force automation platforms are increasingly filling this gap with real time ROS tracking.
  • NZ/AU: NielsenIQ and Circana provide ROS metrics, but the highly concentrated retail landscape (Coles and Woolworths dominate) means ROS analysis often focuses on banner level performance rather than individual store counts.

How leading CPG teams use ROS

Modern commercial teams treat ROS as the foundational input for store level execution. Leading organizations combine ROS data with on shelf availability checks, planogram compliance scores, and promotion tracking to build a complete picture of what is happening at the point of sale. When ROS is integrated with AI powered replenishment and route to market platforms, brands can shift from reactive reporting to proactive store level optimization, ensuring the right product is in the right store with the right facings at the right time.

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.