Sales Velocity in FMCG: How to Compare SKU Performance

TL;DR

FMCG sales velocity measures the rate at which a product sells within a clearly defined retail base and time period. A practical measure is units sold per eligible store-week. It helps distinguish a product that grows because it is sold in more stores from one that sells faster in comparable stores. For example, 900 units across 40 store-weeks equals 22.5 units per store-week, while 1,200 units across 80 store-weeks equals 15. The second product has higher total sales but lower normalized velocity. Distribution, availability, pack size and reporting coverage must be checked before treating the difference as shopper demand.

What Is FMCG Sales Velocity?

Sales velocity is the rate of product sales per defined selling opportunity. Depending on the category and dataset, it may be expressed as units per store per week, sales value per outlet per day or standardized volume per eligible store-week. The exact denominator matters as much as the numerator.

For category and sales teams, velocity is useful because total sales alone can reward the SKU with the widest distribution even when it performs less strongly in the outlets where it is present. Velocity provides a way to compare product movement on a more consistent basis.

How Is Sales Velocity Calculated?

A simple weekly calculation is:

Sales Velocity = Units Sold ÷ Eligible Store-Weeks

One store observed for one complete week contributes one store-week. Twenty eligible stores observed for two full weeks contribute 40 store-weeks. If the dataset uses selling outlets, listed outlets or available outlets instead, the definition should be stated because the resulting velocities answer different questions.

For a fixed base, a simpler formula is Units Sold ÷ Number of Eligible Outlets ÷ Number of Weeks. It works when every outlet is observed for the same complete window. Store-weeks are more flexible when the observed outlet count changes between weeks.

Worked Example: Two SKUs With Different Distribution

Consider two hypothetical FMCG products over the same two-week period. The values are educational, not TrendBox customer data. All outlets are assumed to have complete reporting for the stated store-weeks.

SKU A sells 1,200 units across 80 store-weeks, giving 15 units per store-week. SKU B sells only 900 units but across 40 store-weeks, giving 22.5 units per store-week. SKU A leads on total units; SKU B leads on normalized sales velocity.

This does not prove that SKU B will sell at the same rate if it expands to every store. Outlet mix, local category demand, pricing and availability may be different in the locations it does not yet reach.

What Are Store-Weeks and Why Do They Matter?

Store-weeks represent the total comparable outlet exposure during the measurement period. If 20 stores are eligible during Week 1 and 30 during Week 2, the base is 50 store-weeks, not 30 stores multiplied by two weeks.

Suppose those stores sell 900 units during the two weeks. The store-week velocity is 900 ÷ 50 = 18 units per store-week. Dividing by 30 × 2 would give 15, incorrectly assuming all 30 stores were in the base for both weeks.

For partial reporting periods, a team may use observed store-days and convert them to comparable weeks, as long as the method handles missing records and partial activity consistently. A missing observation should not automatically be treated as zero sales.

Should Velocity Use Selling Stores or All Listed Stores?

There is no single answer without a business definition. Units per selling store can show productivity among stores recording sales, but omits listed stores with zero recorded transactions and can overstate average movement for the full listed network. Units per listed store-week includes non-selling listed outlets where the data quality supports it.

For a distribution decision, the team should specify whether the opportunity is every eligible outlet, every carrying outlet or every outlet with positive sales. The same product can have different velocity values under these denominators.

How Is Sales Velocity Different From Total Sell-Out?

Sell-out counts the products actually sold to shoppers within the measured market. Sales velocity divides that sell-out by an outlet-and-time base to normalize the result. An SKU can have rising sell-out because distribution expanded, while velocity remains unchanged or declines.

For example, if a brand grows from 20 to 30 outlets while each outlet sells roughly the same units per week, total units rise even without stronger performance within individual outlets. Velocity separates those two parts of the story.

How Does Distribution Change Velocity Interpretation?

Numeric distribution describes breadth of reach; weighted distribution describes how commercially important the reached outlets are under a stated weighting method. Velocity measures the rate of sales within a defined subset of stores. Reading all three together helps a team avoid confusing reach with product productivity.

• Low distribution and strong comparable-store velocity: investigate whether selected new outlets could support growth.
• High distribution and weak velocity: examine demand, price, assortment and in-store execution.
• Rising numeric distribution and falling velocity: compare new and existing outlet groups before assuming demand weakened everywhere.
• Stable reach and slowing velocity: check availability, competitive conditions and pack mix.

Velocity growth should not be assumed simply because distribution is high. A large distribution base may include stores where the product is less relevant to shoppers.

How Do Pack Size and Unit Definitions Affect Velocity?

Units sold and physical product volume do not describe the same thing when pack sizes vary. Ten 500 ml bottles and ten 1 litre bottles are 10 packs each but represent 5 and 10 litres respectively. A comparison between pack formats should state whether the metric is packs, litres, kilograms or sales value per store-week.

When comparing price architecture or physical demand, standardized volume can be helpful. When evaluating checkout movement and replenishment of distinct SKUs, pack units may be the better measure. Do not combine unlike categories into an unexplained “volume” total.

Can Low Velocity Be an Out-of-Stock Problem?

Yes, but POS sales data alone cannot establish that a product was unavailable. Recorded sales can decline because shoppers want less of the product, because the shelf is empty, or because outlet reporting was incomplete. A zero-sale store is not necessarily an out-of-stock store.

Where suitable stock signals or field observations exist, compare them with transactions for the same SKU, outlet and period. Listing, physical availability and recorded sale should remain separate states in the diagnostic workflow.

Why Might New Outlets Reduce Average Velocity?

Expansion can bring the product into stores with smaller category turnover, lower demand or partial observation windows. That may reduce average units per store-week without harming the commercial value of the additional distribution.

Compare new outlets with a stable existing-store group and evaluate total incremental units alongside velocity. A decline in average productivity is not automatically a reason to stop expansion; the business may still generate worthwhile additional sales, depending on costs and opportunity.

How Should FMCG Teams Compare Velocity Across Regions?

Use the same SKU and unit definition, consistent outlet eligibility, aligned observation periods and comparable reporting completeness. A region with larger stores may generate more units per outlet than another, even when relative category performance is similar. Where possible, show outlet format or category sales alongside velocity.

Teams may also review the median outlet velocity, the distribution of outlet-level rates and the share of stores with zero recorded sales. Averages can conceal a small number of exceptionally productive outlets.

How Can Sales Velocity Inform Assortment Decisions?

A product with low total sales and high velocity in existing outlets may justify testing distribution expansion. A product with high total sales but weak velocity may deserve an assortment, placement or price review. Neither pattern directly proves the correct action.

A practical decision sequence is to identify a change in total sell-out, compare distribution, calculate consistent velocity, locate the relevant regions or stores, then test a specific action and monitor the result. For the wider performance framework, read FMCG market share analysis.

How Does TrendBox Support FMCG Sales Velocity Analysis?

TrendBox’s FMCG Tracker includes market share, distribution, price and velocity in one consistent measurement view. Retail Pulse provides sell-out-focused tracking, and Location-Based Analytics offers geographic context for performance reviews. The platform is positioned around Türkiye’s traditional trade and daily-refreshed measurement.

The exact active-outlet definition, reporting cadence and available SKU-level breakdowns should be set for the measurement scope. These published capabilities should not be interpreted as a guarantee that every brand has the same data coverage in every channel. Review TrendBox features and FMCG data analytics to see the broader approach.

Frequently Asked Questions About FMCG Sales Velocity

What is sales velocity in FMCG?

It is the rate at which a product sells over a defined number of outlet and time opportunities, such as units per eligible store-week.

What is the sales velocity formula?

A practical measure is units sold divided by eligible store-weeks. The eligible outlet definition and reporting period should be stated.

Is a higher velocity always better?

Not necessarily. Price, margin, distribution cost, pack size and product role also matter. Strong velocity in a small subset of outlets does not guarantee the same performance after expansion.

Can sales rise while velocity falls?

Yes. Total sales can rise because a product reaches more outlets, while average sales per outlet-week decline.

Is selling-store velocity the same as listed-store velocity?

No. Selling-store velocity excludes outlets with zero recorded sales, while listed-store velocity includes the appropriate listed base. They answer different questions.

How do store-weeks work when outlet count changes?

Add eligible outlets for each week, rather than multiplying the final number of stores by the full period. Twenty stores in one week plus thirty in the next equals fifty store-weeks.

Is low velocity proof that a product was out of stock?

No. Low or zero POS sales can also reflect weak demand or missing reporting. Availability must be checked using appropriate supporting data.

Does TrendBox track sales velocity?

TrendBox publicly lists velocity within its FMCG Tracker and retail performance measurement offerings. The detailed scope and outlet definitions should be agreed for each use case.

Compare SKU Performance on the Right Basis

For meaningful FMCG decisions, total sales need context: distribution shows where a product reaches shoppers, and velocity shows how it performs within a comparable network. Contact TrendBox to discuss SKU, category and outlet-level performance measurement for your market.