New item ramp curves: what "normal" looks like
A new item's sales in its first weeks rise for two reasons at once: more stores start stocking it, and shoppers try it. Those are different phenomena with different implications, and a ramp chart that blends them cannot tell you whether the product is working.
Separating them is the first analytical step in any launch review.
What does distribution build look like?
A rising store count, with sales rising roughly in proportion. If sales per stocking store are flat while total sales rise, the ramp is a distribution story and says nothing yet about demand.
That is the normal early pattern and it is frequently mistaken for momentum. Momentum would be sales per stocking store rising.
What does trial look like?
A high rate per store early, declining as curiosity is satisfied, settling at a repeat level. The settled level is the real number; the early peak is a one-off.
A launch judged at its peak looks better than it is, and a launch judged at the moment trial decays but before repeat stabilises looks worse. Both errors are common and they point in opposite directions.
When can a launch be judged?
Once sales per stocking store have stabilised across a meaningful number of stores. How long that takes depends on purchase frequency: a weekly-purchase category settles faster than a monthly one.
The practical rule is to wait for the flattening rather than for a fixed number of weeks. A calendar-based review date set before launch frequently lands in the middle of the decay.
What does a failing launch look like early?
Weak distribution build despite listings, or sales per stocking store that fall below a plausible repeat level quickly. The second is the more informative signal, because it says shoppers tried and did not return.
A launch with good distribution and poor per-store velocity has a product problem. One with poor distribution and good velocity has a sales problem. Those need different responses and the ramp chart tells them apart.
How does the independent channel differ?
Distribution build is slower and lumpier, because each store is an individual decision rather than a chain listing. A ramp in this channel can take considerably longer to reach its plateau and the early weeks are noisier.
That argues for patience and for measuring per stocking store from the first week rather than waiting for the total to look meaningful.
What should be measured alongside?
Repeat rate where the data supports it, the base brand's volume for cannibalisation, and the category total. Those three turn a launch chart into a launch assessment.
Without the brand total, a successful-looking launch may be moving volume from the brand's own existing items rather than adding anything.
What should be agreed before launch?
The review date criterion, the success threshold in velocity terms, and the action if the threshold is missed. All three before the first shipment, because the alternative is a review that negotiates the threshold.
How should a ramp be presented?
Two lines: total sales and sales per stocking store, with store count as a bar behind. One chart, and it makes the distinction visible without explanation.
Frequently asked questions
How long is a typical ramp?
There is no universal answer and be sceptical of one offered without knowing the category's purchase cycle. Frequent-purchase categories settle in weeks; infrequent ones take considerably longer.
Should I compare against a previous launch?
Yes, as the most useful available benchmark, provided the two had comparable distribution builds. Comparing a chain-led launch to an independent-channel one compares two different processes.
What about seasonal launches?
A launch into a season borrows the season's curve, and the ramp cannot be separated from it without a comparison. Launching into a rising season flatters everything.
Does promotional support at launch distort the ramp?
Substantially, and it should be noted on the chart. A supported launch measured during support is measuring the support.
How many stores are enough to judge?
Enough that per-store velocity is stable rather than driven by a handful. There is no fixed number; the test is whether the figure moves when one store is removed.
What if distribution stalls?
That is a finding, and an early one. Stalled distribution with good velocity is the clearest possible case for more field effort.
Should trial and repeat be modelled separately?
Where the data allows it, yes — it is the cleanest way to forecast the settled level from early weeks. Where it does not, the flattening of per-store velocity is the practical substitute.
Does the ramp tell me about the long run?
It tells you about the settled level, which is the input to a long-run view. Anything beyond that is forecasting and carries its own uncertainty.
What is the most common misreading?
Treating total sales growth as momentum when it is distribution build. It is the default chart in most reporting tools and it flatters every launch in its early weeks.
### What should a brand actually do with this?
Build the two-line ramp chart as a standing output for every launch rather than as a one-off for the ones that attract attention. A standing format means the awkward launches get the same scrutiny as the successful ones, which is where most of the learning sits.
Then keep the charts. A library of past ramps is the only realistic benchmark a brand has for what normal looks like in its own categories and its own channel, and it is more relevant than a general figure borrowed from elsewhere. Channel context is collected by NACS.
Working with retail data? See NRS Insights data solutions or contact NRS Insights.