New Product Launch Tracking: 7 Metrics Every FMCG Brand Should Monitor
New product launches in FMCG have a brutal failure rate. Industry estimates vary, but across Indian FMCG, somewhere between 70–80% of new SKUs fail to sustain distribution beyond their first year. The product itself isn't always the problem. Often, the brand simply couldn't see what was happening fast enough to intervene because the metrics they were watching didn't tell the real story.
Most FMCG brands track exactly one launch metric in real time: primary billing. How much did we ship to distributors? That number tells you how well your sales team sold the trade scheme. It tells you almost nothing about whether consumers are buying the product, whether retailers are reordering, or whether the launch has any chance of sustaining beyond the initial pipeline fill.
Fire AI's decision intelligence platform changes what's trackable and how fast. By connecting your Tally, Zoho, SAP, Bizom, or Botree data through pre-built pipelines, Fire AI surfaces launch-level metrics at the SKU, market, and outlet level, continuously, not in a post-mortem deck 90 days later.
Here are the seven metrics that separate brands that catch launch problems in week two from brands that discover them in month four.
1. Pipeline Fill vs. Secondary Offtake Ratio
What it measures: How much of your initial billing to distributors is actually converting into retail sales.
This is the single most important early signal for a new launch, and it's the one most brands ignore because it requires connecting two data sources they don't usually connect: primary billing (from Tally or your ERP) and secondary sales (from your DMS — Bizom, Botree, or equivalent).
A healthy launch shows a pipeline fill ratio that converges toward 1:1 within 4–6 weeks. You ship 10,000 cases to distributors in month one, and secondary offtake reaches 8,000–10,000 cases by month two. If that ratio stays at 3:1 or 4:1 after six weeks, your product is sitting in distributor warehouses, not moving off shelves.
Fire AI's data pipelines unify primary billing and secondary sales data automatically, giving you this ratio at the SKU-and-market level from day one — not from a manually stitched Excel tracker that arrives two weeks late.
2. Outlet Strike Rate
What it measures: Of the outlets where the new SKU was placed, what percentage have placed a repeat order?
Initial placement tells you your sales team executed the launch plan. Repeat ordering tells you the product has a pulse. An outlet that was billed the new SKU once but never reordered is not a successful placement — it's dead stock waiting to come back as a return.
Track this at the beat and territory level. If one territory shows 60% strike rate and an adjacent territory with similar demographics shows 20%, the problem isn't the product — it's execution, pricing, or visibility in that specific market.
Fire AI surfaces outlet-level ordering patterns from your DMS data, and Ask FireAI lets territory managers query it in natural language: "which outlets ordered the new face wash in March but haven't reordered?" The answer comes with a drill-down by distributor and beat, instantly. (Related: Beat productivity analysis: how top FMCG brands optimize field force ROI)
3. SKU Velocity by Channel and Market
What it measures: Units sold per outlet per week, segmented by channel (general trade, modern trade, e-commerce) and geography.
Averages lie. A new SKU might show respectable national velocity, but when you break it down, modern trade in metros is doing all the heavy lifting while general trade in Tier-2 and Tier-3 is flat. That's not a successful launch — it's a channel-dependent one, and it won't scale.
Fire AI's dashboards display velocity at whatever granularity your data supports — market, channel, distributor, beat. More importantly, the platform's anomaly detection flags velocity drops automatically. If a market that was trending well in week three suddenly stalls in week five, a smart alert fires before anyone needs to manually review the numbers.
4. In-Store Visibility Compliance
What it measures: Whether the new SKU is actually visible to shoppers in outlets where it's supposedly placed.
This metric requires field force data — typically captured through your SFA app as part of a visibility audit. Most brands collect this data but review it in aggregate, weeks later. For a new launch, aggregate visibility numbers are meaningless. What matters is visibility compliance at the outlet level, correlated with ordering behaviour.
When Fire AI ingests field audit data alongside secondary sales, the causal chain can trace a direct relationship: outlets where the new SKU had shelf presence and POS material showed 2.5x higher reorder rates than outlets where it was placed but not visible. That's not a guess it's a quantified causal link that tells your trade marketing team exactly where to focus visibility drives.
5. Cannibalisation Rate
What it measures: Whether the new SKU is growing the category or stealing volume from your existing products.
This is the metric most launch teams don't want to look at, because the answer is often uncomfortable. You launched a premium variant at ₹50, and sales of your ₹35 core SKU dropped 15% in the same outlets. That's not incremental growth — that's internal cannibalisation.
Fire AI's causal chain analysis is purpose-built for this. It maps the relationship between the new SKU's secondary sales and the movement of adjacent SKUs in the same category, at the outlet level. When the new SKU's sales rise, does the category grow — or does the existing portfolio shrink? The answer determines whether your launch is creating value or redistributing it.
Ask FireAI makes this queryable: "What's the net category growth in outlets stocking the new premium variant vs. outlets that don't have it yet?" If the answer is flat or negative, the launch strategy needs rethinking — faster pricing differentiation, different target outlets, or a harder look at whether the product occupies a genuinely distinct need state. (Related: Measuring promotion effectiveness: a data-driven guide for FMCG marketers)
6. Scheme Impact on Off-Take
What it measures: Whether the launch trade scheme is driving genuine trials or just loading distributor shelves.
Every new launch comes with a scheme — introductory discounts, free goods, display incentives. The question is whether the scheme is translating into consumer pull or just inflating pipeline fill.
Fire AI tracks this by connecting scheme cost data (from Tally credit notes and accrual entries) to secondary off-take at the SKU level. The platform compares off-take velocity during the scheme window against a post-scheme baseline, quantifying the true incremental lift vs. the trade-loading effect.
If the scheme drove a 50% spike in primary billing but only a 10% lift in secondary sales, you've funded distributor inventory — not consumer trial. Fire AI's scheduled reports surface this weekly during the launch window, so the commercial team can adjust scheme mechanics mid-flight instead of discovering the leakage in a post-launch review.
7. Time to Sustained Rate of Sale
What it measures: How many weeks after launch the new SKU reaches a stable, repeatable weekly velocity — and whether it holds.
This is the metric that separates a successful launch from a flash-in-the-pan trial spike. A new SKU might show strong velocity in weeks 2–4 (driven by scheme-funded initial orders and field force push) and then decline steadily from week 5 onward. That trajectory tells you the product hasn't achieved organic pull.
Fire AI's anomaly detection and trend tracking monitor this automatically. The platform establishes a baseline velocity as data accumulates and flags when the SKU's rate of sale deviates — either a concerning decline or, more usefully, an unexpected acceleration in a specific market that deserves investigation and replication.
What This Looks Like When It Comes Together
Scenario: The Launch That Was Saved in Week Three
Kavita leads marketing for a mid-sized oral care brand launching a new herbal toothpaste variant across four southern states. The launch plan was standard: introductory scheme for distributors, 60-day target of 12,000 outlets, field force visibility push in the first month.
By the end of week two, primary billing looked strong — 85% of target distributors had billed. The sales team was optimistic. But Kavita had Fire AI's NPD tracking dashboard running from day one, pulling data from Tally (primary billing), Bizom (secondary sales and field audit data), and scheme cost entries.
Three signals appeared simultaneously in week three. First, the pipeline fill ratio was 4.2:1 — distributors had stocked heavily, but secondary offtake was a fraction of what was billed. Second, outlet strike rate in Tamil Nadu was 52%, but in Kerala it was 11% — nearly nine out of ten outlets that were billed hadn't reordered. Third, Fire AI's causal chain showed a correlation between visibility compliance and reorders: outlets with shelf placement and POS had 3x the reorder rate, and field audit data showed that only 35% of Kerala outlets had any visibility execution.
Kavita didn't wait for the month-end review. She used Ask FireAI to pull the specific outlets and beats in Kerala with zero visibility compliance, shared the drill-down with the regional ASM, and redirected the field team to a two-week visibility blitz focused on the 200 highest-potential outlets. Simultaneously, she paused the volume-linked distributor scheme in Kerala (which was just building dead stock) and replaced it with a retail-activation scheme tied to display and secondary offtake.
By week eight, Kerala's outlet strike rate had climbed from 11% to 38%, and the pipeline fill ratio across all four states had normalised to 1.6:1. The launch wasn't a runaway success — but it was no longer heading for a quiet failure, which is what would have happened if the first real data review had been the 90-day post-launch deck.
Why Most Launch Trackers Fail
The problem with most NPD tracking in FMCG isn't the metrics — it's the data infrastructure. When primary billing, secondary sales, field audit data, and scheme costs live in four disconnected systems, building a unified launch tracker is a manual project that takes weeks and goes stale the moment it's compiled.
Fire AI eliminates that infrastructure gap. Its 250+ pre-built connectors pull data from wherever your operational truth lives — Tally, Zoho, SAP, Bizom, Botree, field apps — and unify it into a single analytical layer. The platform's causal chain, anomaly detection, and natural-language query engine then make launch metrics accessible to everyone from the brand manager to the national sales head, continuously, without waiting for someone to build a report.
New product launches are time-sensitive decisions operating on stale data. Fire AI makes the data as fast as the decisions need to be.
Launching a new SKU? Track your next launch with Fire AI → FireAI
Posted By:
Ishita Shah
Content Editor, FireAI
10+ years of leading Product Management, New Ventures and Project roles at Delhivery, Zomato, and eInfo Solutions. Notion Affiliate and Member of Insurjo Cohort.
10+ years of leading Product Management, New Ventures and Project roles at Delhivery, Zomato, and eInfo Solutions. Notion Affiliate and Member of Insurjo Cohort.
Loading...