MAPE vs WMAPE: Which Forecast Error Metric to Use

The MAPE vs WMAPE choice looks like a math nitpick. It isn't. It's the difference between a forecast KPI that reflects where your money actually moves and one that lets a quietly broken supply chain post a green dashboard. I ran demand planning at a $250M furniture manufacturer, and switching our primary metric from MAPE to WMAPE changed which SKUs the team fought over, which is to say it changed where we spent our working capital. If you're choosing between MAPE and WMAPE, choose WMAPE for almost every executive and planning use case. Here's exactly why, with the numbers.

What each metric actually measures

Both start from the same place: absolute error, the gap between forecast and actual without regard to direction.

MAPE (Mean Absolute Percentage Error) calculates the percentage error for each item, then averages those percentages with equal weight:

MAPE = (1/n) × Σ ( |Actual − Forecast| / Actual ) × 100

WMAPE (Weighted Mean Absolute Percentage Error) sums the absolute errors and divides by total demand, so each item's contribution is weighted by its volume:

WMAPE = Σ |Actual − Forecast| / Σ Actual × 100

The one-line version: MAPE treats a $40 lamp and a $4,000 sectional as equally important. WMAPE weights them by how much they actually move. For a manufacturer with a wide catalog, that distinction is everything.

The example that ends the debate

Take five SKUs across one week:

MAPE = (11.1 + 9.1 + 14.3 + 100 + 100) / 5 = 46.9% → accuracy 53.1%

WMAPE = (20+15+10+3+2) / (180+165+70+3+2) = 50 / 420 = 11.9% → accuracy 88.1%

Same forecast. Same actuals. MAPE says you're failing. WMAPE says you forecast the items that fund the company within 12%. The 35-point gap is entirely two cheap, low-volume items where a 3-unit miss reads as a 100% error.

If you run your S&OP meeting on MAPE, your planners will spend their week trying to fix the lamp and the cushion to drag the average down, while the sectional that pays the mortgage gets less attention. That's the metric driving the wrong behavior.

Why MAPE breaks specifically on low-volume items

MAPE has a structural flaw: it divides by the actual. As the actual approaches zero, the percentage error approaches infinity. Forecast 5, sell 1, and you've booked 400% error. For any business with a long tail of slow movers, spare parts, or intermittent demand, MAPE is dominated by the least important items.

MAPE also has no upper bound on the over-forecast side, so a handful of dead SKUs can drag a company-wide average into the red even when your core business is forecast tightly. WMAPE has neither problem, because the small items contribute small numerators and small denominators.

When MAPE still earns its place

WMAPE wins the default, but MAPE isn't useless:

• Single-SKU tracking over time. For one stable, high-volume item, MAPE is a clean, intuitive trend line. No weighting needed when there's one thing.
• Comparing your error to academic or vendor benchmarks. A lot of published forecasting research reports MAPE, so you may need it to compare apples to apples.
• Communicating to non-planners. "We're 10% off on this product" lands faster than explaining a weighting scheme.

For anything that aggregates across a catalog, though, switch to WMAPE.

Quick decision table

The upgrade most teams miss: weight by margin, not units

Standard WMAPE weights by unit volume. The sharper move is to weight by revenue, or better, by gross margin. A point of error on your highest-margin line costs more than the same point on a thin-margin commodity, and a margin-weighted WMAPE puts your accuracy effort exactly where the profit is.

We ran a margin-weighted WMAPE alongside the unit version, and the two told genuinely different stories. The unit-weighted metric flattered us on high-volume, low-margin items; the margin-weighted version exposed that our profit center was the line we forecast worst. That's the kind of finding that changes a quarter.

Neither metric without bias

Whatever you choose, MAPE and WMAPE both take absolute values, so neither tells you direction. A team can post a great WMAPE while systematically over-forecasting into stranded inventory. Always run a signed bias number next to your error metric. Error tells you how wrong; bias tells you which way, and the second one is what fills the warehouse with dead stock.

AI-native platforms like Pigment let you slice WMAPE by unit, revenue, and margin and overlay bias on the same view, so you're not maintaining three spreadsheets to see the full picture. The metric choice still matters more than the tool. WMAPE, weighted by margin, with bias alongside, is the honest scorecard.

Find out what your metric is hiding

If you're still running on MAPE, your dashboard and your warehouse probably disagree. We'll run a free planning-maturity and stranded-inventory teardown on your data: WMAPE by unit and margin, bias by family, and the dead stock your current metric masks. Book a 30-minute call and bring one product line's forecast history.