The number everyone quotes
Ask any demand planner how accurate their forecast is and you will get a percentage. That percentage is almost always MAPE, the Mean Absolute Percentage Error. It is the default metric in every planning tool, every ERP report, and every board deck. And it is the metric most likely to be misinterpreted by the person reading it.
MAPE is not a bad metric. It is a useful metric used outside its limits. The problem is that MAPE behaves predictably when demand is steady and high, and behaves badly when demand is low, intermittent, or zero. Since most manufacturers have a long tail of slow-moving SKUs, MAPE on those SKUs is often meaningless, sometimes infinite, and always misleading if read the same way as MAPE on fast movers.
This article is a practitioner's guide to reading MAPE correctly. It covers what the formula actually computes, where it breaks, what a "good" MAPE actually looks like in different industries, and which metrics you should track alongside it to avoid being lied to by a single number.
The formula, plainly
MAPE is the average of the absolute percentage errors between your forecast and the actual demand, across all periods and SKUs in scope. Formally:
For each period, compute the absolute error divided by the actual demand, express it as a percentage, then average across all periods. The result is a single percentage that represents your average miss rate, weighted equally across all observations regardless of size.
The appeal is obvious. A single percentage is easy to communicate. "Our MAPE is 18%" sounds precise. Executives can track it over time. Tools can benchmark against it. The problem is that the equal weighting is the flaw.
Where MAPE breaks
MAPE has three well-documented failure modes. Every demand planner hits them. Most do not realise they have hit them because the metric still produces a number, it just produces a meaningless one.
First, MAPE explodes when actual demand is low. If you forecast 10 units and the actual is 1, your percentage error is 900%. If you forecast 10 and actual is 100, your percentage error is 90%. The same absolute miss produces wildly different percentages depending on the denominator. This means slow movers, which have low actual demand, will dominate your MAPE even if they are a small part of your revenue. A single slow mover with a 500% error can drag an otherwise healthy 15% MAPE up to 25%.
Second, MAPE is undefined when actual demand is zero. Division by zero. Many tools silently skip these periods, which means you are not actually computing the average across all periods. You are computing the average across non-zero periods. If 30% of your SKUs have zero demand in a given month (common for spare parts, seasonal items, new products), your MAPE is computed on a biased sample.
Third, MAPE weights all errors equally regardless of volume. A 50% error on a SKU that sells 2 units a month contributes the same as a 50% error on a SKU that sells 2,000 units a month. In revenue terms, the second error is 1,000 times more important. MAPE cannot see this. A weighted metric like WMAPE (Weighted MAPE) can.
What a good MAPE actually looks like
There is no universal good MAPE. The number depends on your industry, your product mix, your forecast horizon, and your level of aggregation. A 15% MAPE might be excellent for one company and terrible for another. Context is everything.
ToolsGroup, a supply chain planning vendor that has published forecast accuracy benchmarks across industries, reports that typical MAPE ranges for consumer goods sit between 20% and 40% at the SKU-location level for a one-month-ahead forecast. For stable, fast-moving consumer goods with strong historical patterns, best-in-class planners achieve MAPE in the 15% to 25% range. For promotional or fashion items with high volatility, MAPE often exceeds 40% even with good methodology.
A widely cited practitioner survey by Value Chain Planning found that the median respondent reported forecast accuracy (1 minus MAPE) between 70% and 80% at the SKU level, with significant variance by industry. Industrial manufacturers tended to report lower accuracy than consumer goods manufacturers, driven by longer lead times, lower volumes, and more intermittent demand patterns.
The honest benchmark is this: if your MAPE at SKU-location level for a one-month-ahead forecast is below 25% and your demand is not trivially stable, you are doing better than most. If it is above 40%, you have a problem. Between 25% and 40% is where most manufacturers sit, and where the biggest gains are available.
What to track alongside MAPE
No single metric tells the truth about forecast quality. MAPE should always be read alongside three other signals.
Bias. MAPE tells you the size of your errors but not their direction. Bias measures whether you systematically over-forecast or under-forecast. A MAPE of 20% with a bias of zero is a healthy forecast that misses randomly. A MAPE of 20% with a bias of positive 15% is a forecast that consistently over-predicts, which is a different and more fixable problem. Track bias per SKU, per category, and per planner. Persistent bias is more actionable than random error.
WMAPE. Weighted MAPE weights each error by the actual demand volume, so a miss on a high-volume SKU counts more than a miss on a low-volume SKU. This corrects MAPE's biggest flaw. If your MAPE is 30% but your WMAPE is 12%, it means your errors are concentrated in low-volume SKUs, which is usually tolerable. If your MAPE is 30% and your WMAPE is 28%, your errors are in high-volume SKUs, which is a serious problem.
Forecast value added (FVA). FVA measures whether your manual overrides actually improve the forecast or make it worse. It compares the accuracy of the statistical baseline to the accuracy of the final published forecast after overrides. If your statistical baseline has a MAPE of 22% and your final forecast (after planner overrides) has a MAPE of 25%, your planners are destroying value. This happens more often than planners admit. Track FVA per planner to find where overrides help and where they hurt.
The reading checklist
Before you report a MAPE number to anyone, including yourself, answer these five questions.
One. What level of aggregation is this MAPE computed at? MAPE at the product family level is always lower than MAPE at the SKU-location level. Comparing the two is meaningless. Always state the level.
Two. What forecast horizon is this MAPE for? A one-week-ahead forecast will always be more accurate than a six-month-ahead forecast. Always state the horizon.
Three. How are zero-demand periods handled? If they are skipped, your MAPE is biased. If they are included with a small epsilon added to the denominator, state the epsilon.
Four. What is the bias? A MAPE number without a bias number is half a diagnosis.
Five. What is the WMAPE? If you only report MAPE, you are hiding where the errors actually sit.
The takeaway
MAPE is a useful metric. It is not a verdict. Read it alongside bias, WMAPE, and FVA, always at a stated level of aggregation and horizon, and you will have a forecast accuracy picture that actually reflects reality. Read it alone, and you will have a number that sounds precise and tells you nothing.
The best demand planners do not optimise for a lower MAPE. They optimise for a forecast that the business can plan around. Those are not always the same thing.