Sales velocity benchmarks: comparing very different stores

Sales velocity is the rate at which a product sells where it's actually available, and a fair sales velocity benchmark compares that rate only across stores that could plausibly be expected to sell alike. Raw averages across very different stores don't clear that bar. Most velocity arguments fall apart on the word "fair."

Why do raw averages mislead?

Independent stores vary widely. A high-traffic bodega beside a subway entrance and a quiet crossroads store in a small town might both stock your product, and averaging their sales tells you almost nothing about either. Store size, foot traffic, neighborhood income, category depth: each moves the number for reasons that have nothing to do with your brand's strength. The benchmark's whole job is to strip those differences out, or at least to name them out loud.

The distribution trap is the subtler problem. Say your item sells in its best 40 stores, the ones that adopted it first, and shows a handsome average velocity. Expand into 400 stores and the average falls, not because the brand weakened but because the newer stores are more ordinary. Anyone reading that falling average as decline would be exactly wrong; the business underneath it grew. Averages punish expansion, and that alone disqualifies them as a lone metric.

How do you build a fair comparison?

1. Count only stores that actually sell the item. Velocity per store selling, sales divided by the number of stores with any scans of the item, is the basic honest unit.
2. Match the comparison set. Compare urban stores with urban stores and similar formats with similar formats. A benchmark set you can't describe in one sentence is probably too loose.
3. Hold the time window identical. Same weeks for your item and its comparison, because seasonality bends everything.
4. Read units and dollars separately. Price differences across stores can make dollar velocity flatter one store and slight another.
5. Note category depth. A store carrying a deep category spreads its sales across more items, so each item's share looks thinner even where the category thrives.

When is a velocity gap meaningful?

When it persists and survives the obvious explanations. A one-week gap is noise; a gap that holds across months of same-store reads is a signal. Before treating it as strategy, rule out the mundane suspects: a price difference, a placement difference, out-of-stocks quietly zeroing days at a time.

A concrete version: suppose your item's per-store-selling velocity in one city runs behind a matched set in another city, month after month. Price checks come back similar, out-of-stocks don't explain it, and the category is healthy in both places. What's left is local: placement, a competitor's rack, a distributor gap. That short list is the benchmark's gift, since a rep can check all three in an afternoon.

A gap that survives that screening becomes useful in two directions. Below-benchmark velocity in a definable store cluster is a diagnosis: something about price, placement, or pack is wrong there, and it's findable. Above-benchmark velocity is ammunition: evidence for the distributor pitch, the expanded facing, the next store cluster. Either way the benchmark did its job, which was never to produce a number but to point at the next action.

Channel-level context calibrates all of it. Knowing how the independent channel moved overall in a given month, which is what the NRS Insights monthly report covers, keeps you from crediting your brand for a tide or blaming it for a storm. The July 2026 report is the current example, and the archive holds the running series.