# Forecast Accuracy Calculator: MAPE, Bias, and the Cost of Forecast Error > Source: https://netray.co/tools/forecast-accuracy-calculator > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Turn your forecast and actual history into MAPE, accuracy, and bias figures, then price what that error is costing you across the year. ## Category manufacturing ## Tool **Kind:** calculator **Inputs:** #### Total forecast units **Key:** total_forecast_units **Type:** number **Default:** 100000 **Min:** 1 **Max:** 1000000000 **Step:** 100 **Unit:** units **Help:** Sum of forecast quantities across all items and periods in the window you are measuring. #### Total actual units **Key:** total_actual_units **Type:** number **Default:** 92000 **Min:** 1 **Max:** 1000000000 **Step:** 100 **Unit:** units **Help:** Sum of actual demand across the same items and periods. #### Sum of absolute errors **Key:** sum_absolute_error_units **Type:** number **Default:** 18000 **Min:** 0 **Max:** 1000000000 **Step:** 100 **Unit:** units **Help:** Add up the absolute difference between forecast and actual for every item-period, then enter the total here. #### Number of periods measured **Key:** num_periods **Type:** number **Default:** 12 **Min:** 1 **Max:** 260 **Step:** 1 **Unit:** periods **Help:** Months, weeks, or buckets covered by the data above. Twelve monthly buckets is the usual choice. #### Average unit value **Key:** avg_unit_value **Type:** number **Default:** 40 **Min:** 0.01 **Max:** 1000000 **Step:** 1 **Unit:** $ **Help:** Average standard cost or sale value per unit, used to price the consequence of forecast error. #### Blended cost of forecast error **Key:** error_cost_factor **Type:** select **Default:** 0.3 **Help:** Share of unit value lost per unit of error through excess inventory, expedites, and missed sales combined. **Options:** ##### Conservative - 15% of unit value per error unit **Value:** 0.15 ##### Typical discrete manufacturing - 30% **Value:** 0.3 ##### High-mix or short shelf life - 45% **Value:** 0.45 **Outputs:** #### MAPE (mean absolute percentage error) **Key:** mape_pct **Expr:** sum_absolute_error_units / max(total_actual_units, 1) * 100 **Format:** percent **Description:** Total absolute error as a share of total actual demand. **Primary:** true #### Forecast accuracy **Key:** forecast_accuracy_pct **Expr:** max(0, 100 - mape_pct) **Format:** percent **Description:** The complement of MAPE, which is how most executives prefer to see the number. **Primary:** true #### Forecast bias **Key:** bias_pct **Expr:** (total_forecast_units - total_actual_units) / max(total_actual_units, 1) * 100 **Format:** percent **Description:** Positive means you consistently over-forecast; negative means you under-forecast. #### Average absolute error per period **Key:** avg_error_per_period **Expr:** sum_absolute_error_units / max(num_periods, 1) **Format:** number **Description:** Typical unit error you are absorbing in each planning bucket. #### Estimated annual cost of forecast error **Key:** annual_error_cost **Expr:** sum_absolute_error_units * avg_unit_value * error_cost_factor **Format:** currency **Description:** Blended cost of excess inventory, expediting, and lost sales attributable to this error level. **Disclaimer:** Estimates only. Weighted MAPE calculated on aggregate volumes understates the error visible at item level. Use this for directional benchmarking and cost framing, not for statistical model validation. ## Content **Intro:** This free forecast accuracy calculator gives demand planners, S&OP leaders, and operations executives a fast, defensible read on how good their demand plan really is. Enter total forecast units, total actual units, the summed absolute error, the number of periods measured, and an average unit value, and the tool returns MAPE, forecast accuracy, forecast bias, average error per period, and an estimated annual cost of that error. Separating bias from absolute error matters, because the two have completely different fixes and only one of them can be corrected by a settings change. **Sections:** #### How MAPE, accuracy, and bias are calculated **Body:** This tool uses weighted MAPE: total absolute error divided by total actual demand. With the defaults, 18,000 units of absolute error against 92,000 actual units gives 19.6% MAPE, or 80.4% forecast accuracy. Bias is a different measurement entirely - it is total forecast minus total actual, divided by actual, which here gives plus 8.7%. That means the plan is systematically high, not merely noisy. Weighted MAPE is preferred over simple averaged MAPE for manufacturing because it stops low-volume items with wild percentage swings from dominating the number. It does, however, mask item-level pain, so use this figure for executive reporting and always keep a segmented view underneath it. #### Forecast accuracy benchmarks by product profile **Body:** Accuracy expectations depend heavily on volume, mix, and how far out you are forecasting, so a number quoted without those three qualifiers is not comparable to anything. The ranges below reflect monthly aggregate forecast accuracy at the product family level, measured one month ahead, across discrete manufacturers we work with. Two rules of thumb travel well. Accuracy degrades roughly five to ten percentage points for every additional month of horizon, which is why long-horizon plans should drive capacity decisions rather than order quantities. And accuracy improves substantially with aggregation, so family-level numbers will always flatter you compared with the item-level error your buffers must actually absorb. **Bullets:** - High-volume, stable product families commonly achieve 85-95% accuracy at the family level one month out. - Typical discrete manufacturing at family level lands between 70% and 85%, degrading sharply at item level. - High-mix, low-volume aerospace and defense demand often sits at 50-70% and is dominated by program timing rather than statistics. - Item-level accuracy is routinely 15-25 percentage points worse than family-level accuracy for the same business. #### Bias matters more than accuracy **Body:** If your bias is near zero, your forecast is noisy but honest, and the correct response is buffering with safety stock rather than chasing model improvements. If bias is materially positive, as in the default example, you are systematically over-forecasting and the cost shows up as excess inventory, obsolescence, and capacity you built for demand that never arrived. Persistent positive bias usually comes from sales targets leaking into the demand plan. Persistent negative bias produces chronic expediting and missed shipments and often comes from planners deliberately sandbagging to avoid inventory criticism. Bias is a process and incentive problem, and it is almost always cheaper to fix than absolute error, which is bounded by genuine demand uncertainty. #### How Netray helps you improve the number **Body:** Netray builds forecast accuracy measurement directly into your ERP reporting so it is produced every cycle without a planner assembling spreadsheets, segmented by family, item, and planner so accountability is real. We deploy on-prem statistical and machine learning baseline models against Infor SyteLine, CloudSuite Industrial, Infor LN, and Baan history, including causal signals like program milestones and customer schedule shares that pure time series models miss. Because the models run inside your firewall, ITAR and CMMC constraints in aerospace and defense are not a barrier. Most engagements begin by instrumenting accuracy and bias on your top families, which typically exposes a correctable bias worth more than any model upgrade. **Cta:** Get a personalized forecast accuracy and bias diagnostic with a prioritized improvement plan from Netray's demand planning specialists. **Faq:** #### What is a good MAPE for a discrete manufacturer? **Answer:** It depends entirely on volume and mix. High-volume, stable families can reach 5-15% MAPE at family level one month out. Typical discrete manufacturing lands between 15% and 30%, and high-mix, low-volume aerospace work frequently exceeds 30% no matter how good the process is. The number that matters is your own trend and your bias. A stable 22% MAPE with near-zero bias is far more manageable than a 15% MAPE that is consistently high. #### Why does my item-level accuracy look so much worse than family level? **Answer:** Aggregation hides offsetting errors. Over-forecasting one variant while under-forecasting its sibling nets out at the family level but still causes real stockouts and excess at the item level, which is where planning parameters actually operate. Expect item-level accuracy to be 15-25 percentage points worse. Report family accuracy to executives for trend, but drive safety stock and reorder point decisions from the item-level error, since that is the variability your buffers must absorb. #### Should I invest in better forecasting or in bigger buffers? **Answer:** Check bias first. If bias is significant, fix the process, because you are paying for a correctable error. If bias is near zero and MAPE remains high, you are up against genuine demand uncertainty, and buffering plus shorter lead times will beat further model investment. The practical rule is that forecast improvement pays off on stable high-volume items, while responsiveness and buffering pay off on volatile, low-volume items where no model will ever be accurate. ## Search terms forecast accuracy calculator, MAPE calculator, how to calculate forecast accuracy, forecast bias calculation, demand forecast accuracy benchmark, MAPE formula manufacturing, forecast error cost --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json