Market Withdrawal Rate KPI

Market Withdrawal Rate serves as a critical indicator of a company's ability to manage its product portfolio effectively.

High withdrawal rates can signal issues with product-market fit, leading to lost revenue and diminished brand reputation.

Conversely, a low rate reflects strong market alignment and operational efficiency, contributing to sustained profitability.

This KPI influences key business outcomes such as customer satisfaction, inventory management, and overall financial health.

By tracking this leading indicator, organizations can make data-driven decisions that enhance their strategic alignment and improve ROI metrics.

Ultimately, it helps firms optimize their offerings and maintain a competitive position in the market.

How Market Withdrawal Rate Connects to Your Strategy

Market Withdrawal Rate appears in KPI Depot's New Product Development KPI group, one of the largest groups tracked at sixty KPIs. At priority thirty-five it sits past the group's midpoint, well below the eight metrics the group treats as headline: Customer Satisfaction with New Products holds the top priority, followed by New Product Success Rate, New Product Revenue, Percentage of Revenue from New Products, New Product Profit Margin, Customer Feedback Incorporation, Time to Market for New Products, and Product Development Cycle Time. Its low priority does not make it a minor metric; it makes it a metric the group only needs once something has already gone wrong.

Its balanced scorecard placement, internal, is worth pausing on, because Market Withdrawal Rate reads on its face like a market outcome, a product either sells or it does not, but the group's graph places it as a process signal instead. Read that way, a withdrawal is not simply evidence that customers rejected a product; it is evidence that something upstream in the development process, feedback incorporation, launch timing, quality control, did not hold. That makes it one of the most lagging metrics in the KPI group's set: by the time it moves, New Product Success Rate, Customer Satisfaction with New Products, and Customer Feedback Incorporation have already had their say, and withdrawal is the outcome those earlier metrics failed to prevent.

The clearest tension is with Time to Market for New Products and its close relative, Product Development Cycle Time, priorities seven and eight in this KPI group. The group's own guidance treats these two together explicitly, noting that discrepancies between them reveal bottlenecks in the pre-launch phase, and its worked OKR example for accelerating delivery pairs faster cycle times directly against Customer Feedback Incorporation, on the reasoning that speed alone does not guarantee a successful launch. A team that compresses Time to Market without holding Customer Feedback Incorporation steady is choosing the exact conditions under which Market Withdrawal Rate rises later, well after the calendar win has already been booked and is much harder to walk back.

Measuring Market Withdrawal Rate in Practice

The formula behind Market Withdrawal Rate, withdrawn products divided by launched products, needs a denominator boundary decided before the rate means anything. Launched can mean every SKU or variant that ever reached a shelf or website, including minor line extensions, or it can mean only the launches significant enough to appear on a product roadmap. A broad denominator dilutes the rate with routine SKU churn that was never meant to be permanent; a narrow one concentrates it on the launches leadership actually cares about. Pick one and keep the population consistent across the periods you compare, since switching it mid-series will move the rate independent of any real change in product quality.

The bigger trap is timing, and the benchmark literature on this metric makes the shape of the problem visible even though the figures themselves are gated: the tracked sources follow drug approvals for years, sometimes over a decade, before counting a withdrawal against that cohort. A product launched eighteen months ago has not had time to fail in every way it eventually might, so measuring Market Withdrawal Rate against a recent launch cohort will understate the true rate simply because the clock hasn't run out yet. Decide how long a product has to be on the market before its absence from an active-products list counts as a withdrawal rather than an ongoing product, and apply that window consistently, or a portfolio full of young launches will always look artificially healthy.

What counts as withdrawn is a fork worth resolving explicitly. A full market exit, a regulatory recall, and a quiet discontinuation for low sales are three different events that a single count can blur together. If the organization wants this rate to diagnose market-fit or quality problems specifically, as the KPI's own definition suggests, a routine SKU rationalization driven by portfolio strategy should probably not count the same way a quality-driven recall does, even though both remove a product from the market.

Where the underlying data lives matters for whether any of this is even measurable. The launch side usually sits in a product roadmap or PLM system; the withdrawal side sits in a separate discontinuation or deactivation record, often owned by a different team, supply chain or sales operations rather than product management. Joining them honestly means matching a withdrawal back to its original launch record rather than to a generic active-products list, since a product that was modified and relaunched under a new SKU can otherwise look like a withdrawal followed by a new launch instead of what it actually was, a single product's evolution.

Segmentation matters most by launch tier. A blended rate across major strategic launches and minor incremental ones rewards teams that ship a large volume of low-risk variants, since those rarely get formally withdrawn, while burying the failure rate of the handful of major bets that actually carry the KPI's diagnostic intent. Break the rate out by launch tier or business unit before using it to judge a product organization's overall discipline.

Common Pitfalls

Many organizations overlook the implications of a high Market Withdrawal Rate, assuming it reflects normal business cycles.

• Failing to analyze customer feedback can lead to repeated mistakes. Without understanding why products fail, companies risk launching similar offerings that may also struggle in the market.
• Neglecting market research often results in poor product development decisions. Companies may invest heavily in features that do not resonate with target customers, leading to higher withdrawal rates.
• Overcomplicating product lines can confuse consumers. A cluttered portfolio may dilute brand messaging and make it difficult for customers to identify core offerings.
• Ignoring competitor actions can leave firms vulnerable. If competitors are successfully meeting customer needs, companies may find their products withdrawn more frequently due to lack of differentiation.

Improvement Levers

Reducing the Market Withdrawal Rate requires a proactive approach to product management and customer engagement.

• Conduct regular market research to stay attuned to customer preferences. Engaging with customers through surveys and focus groups can provide insights that inform product development and adjustments.
• Implement a robust product lifecycle management system to streamline processes. This can help teams track performance metrics and make timely decisions regarding product adjustments or discontinuations.
• Enhance cross-functional collaboration between marketing, sales, and product teams. Sharing insights can lead to better alignment on customer needs and market trends, reducing the likelihood of withdrawals.
• Utilize data analytics to identify patterns in product performance. Analyzing sales data and customer feedback can help pinpoint potential issues before they escalate into withdrawal decisions.

KPI Depot is trusted by consulting, strategy, finance, and analytics teams at leading organizations worldwide, including those listed below.

Market Withdrawal Rate Benchmarks

We have 2 relevant benchmarks in our benchmarks database.

Browse the Top Benchmarked KPIs in New Product Development

Reading the Benchmarks for Market Withdrawal Rate

The two sources tracked for Market Withdrawal Rate, JAMA and Open Medicine, are both drawn from pharmaceutical research: studies of new chemical entities and new active substances that were approved and later withdrawn from national markets. That's worth flagging before using either as a stand-in for a broader new-product benchmark, because a pharmaceutical withdrawal is a heavily regulated event, usually triggered by a safety finding or a regulator's own action, not a market-fit failure in the sense a consumer goods or software team would mean by the term. Applying a rate built on regulated drug withdrawals to a product launched in an unregulated category compares two different failure mechanisms under the same label.

The two sources also differ in geography and follow-up window in ways that matter before comparing them to each other, let alone to your own numbers. One tracks United States approvals with withdrawals followed over an extended multi-decade window; the other tracks a different national market with its own separate follow-up period. A longer observation window has more time to catch a slow-developing safety signal, so two studies covering different follow-up periods are not counting the same universe of eventual withdrawals, even before you get to how each one defines a launch or a withdrawal event. Before treating either figure as a reference point, check the regulatory context it came from, the follow-up window used, and whether withdrawal in that source means a full market exit or something narrower, like a label restriction or a paused sale.

OKRs That Use Market Withdrawal Rate

New Product Development's worked OKR set does not put Market Withdrawal Rate into a key result directly, but its first objective, accelerate delivery of market-ready products that resonate with customers, is built on exactly the pressure that produces withdrawals: substantial cuts to Product Development Cycle Time and to Time to Market for New Products. The objective's own rationale is explicit that speed alone does not guarantee a successful launch, and it pairs those cycle-time cuts with a target for Customer Feedback Incorporation for that reason. A team pursuing this objective has good reason to add Market Withdrawal Rate as a guardrail key result underneath it, framed as holding the rate flat or improving while cycle time comes down, so a genuine speed gain doesn't get bought with a hidden increase in launches that don't hold up.

The group's market-penetration objective, built on User Adoption Rate, Customer Retention Rate Post-Launch, New Product Market Share, and Customer Satisfaction with New Products, offers a second connection from the other direction. Its rationale treats Customer Satisfaction with New Products as a leading indicator for adoption and word of mouth. Market Withdrawal Rate is what that chain looks like when it fails all the way through, not a slow adoption curve but a product pulled entirely. A team already working this objective could reasonably set an illustrative target to keep Market Withdrawal Rate at or below a level it defines for itself as its portfolio grows, treating a rising rate as the clearest sign that the adoption and satisfaction gains reported elsewhere are not translating into products that survive.

See OKR Examples for New Product Development

Free Whitepaper

Want to achieve performance excellence in New Product Development? Download our in-depth whitepaper: Definitive Guide to New Product Development KPIs.

Download the Free Guide

KPI Categories

This KPI is associated with the following categories and industries in our KPI database: