Demand Forecasting Diagnostic Tool

Upload sales data or enter manually. Detect trend, seasonality, and variability. Auto-select the best forecasting model. Get forecast volumes, MAPE, and bias — instantly.

What this tool does

Mathnal's Forecasting Diagnostic Tool auto-detects demand patterns (trend, seasonality, intermittence, level shifts), recommends an appropriate model (ARIMA / ETS / XGBoost / LSTM / Prophet) and computes MAPE, wMAPE, RMSE, MAE, MASE, bias and tracking signal — instantly, browser-based, no signup.

📂 Upload Excel / CSV
✍️ Enter Manually

Results loaded. Clear all to start fresh.

Upload Sales Data Excel / CSV

Upload a file with columns: SKU Name, Category, Sub-Category, Warehouse, Period 1, Period 2, ... Period N (12–30 periods). Max 10 SKUs per file.

📁

Click to upload or drag & drop

.xlsx, .xls, .csv · Max 10 SKUs · 12–30 periods of sales data

→ Or load sample data to try it out

Enter Sales Data Manually Up to 10 SKUs

Free Demand Forecast Accuracy Audit — MAPE, Bias & Model Selection

Upload sales history or enter it manually, and Mathnal's forecasting diagnostic detects your demand pattern, recommends the right model, and computes MAPE, wMAPE, MAE, MASE, bias and tracking signal — instantly and free.

What is forecast accuracy and how is it measured?

Forecast accuracy measures how close your demand forecast is to actual sales. The most-used metric is MAPE (Mean Absolute Percentage Error) — below 10% is excellent, below 20% is good, above 30% needs intervention. But MAPE alone hides systematic error, so this tool also reports bias (chronic over- or under-forecasting) and the tracking signal that flags when a model has drifted.

How do you choose a forecasting model?

The right model depends on your demand pattern. Stable demand suits moving averages and exponential smoothing; trended or seasonal demand suits ARIMA or ETS; intermittent demand suits Croston's method; complex patterns may suit Prophet or XGBoost. This tool auto-detects trend, seasonality, intermittence and level shifts, then recommends an appropriate model so you don't guess.

Why does forecast bias matter more than error?

A forecast can have low average error yet still be consistently wrong in one direction. Positive bias (under-forecasting) drives stockouts; negative bias (over-forecasting) drives excess inventory and write-offs. Because bias compounds period after period, detecting and correcting it usually delivers more value than chasing a slightly lower MAPE.

Who is this forecast audit for?

Demand planners, S&OP teams, category managers and analysts who want a quick, objective read on forecast quality and a defensible model recommendation — without setting up Python or paying for forecasting software.

Frequently Asked Questions

Everything you need to know
How to detect trend and seasonality in sales data?
Trend is detected by computing the Pearson correlation between time index and sales values. Correlation above 0.3 indicates upward trend, below -0.3 indicates downward trend. Seasonality is detected by computing autocorrelation at different lag periods and identifying the lag with the highest autocorrelation above 0.3 threshold. Common seasonal periods are 4 (quarterly), 7 (weekly in daily data), 12 (monthly), and 52 (weekly in yearly data).
Which forecasting model should I use for my data?
Model selection depends on the time series patterns present. Data with no trend and no seasonality suits Simple Moving Average or Simple Exponential Smoothing. Data with trend but no seasonality suits Holt Linear Trend method. Data with both trend and seasonality suits Holt-Winters method. Data with only seasonality suits Seasonal Naive. The Mathnal tool auto-races 7+ models against your data and selects the best by lowest MAPE on a holdout set.
What is a good MAPE for demand forecasting?
MAPE benchmarks vary by industry: below 10% is excellent, 10–20% is good, 20–30% is fair for volatile demand, and above 30% typically needs intervention. Stable FMCG products often achieve 5–15%, while fashion or new products may see 30–50%. However, MAPE should be assessed alongside forecast bias — a forecast with 15% MAPE but consistent 10% over-forecast bias is more damaging than 20% MAPE with zero bias.
How to calculate forecast bias?
Forecast Bias = Average of (Actual - Forecast). Positive bias means chronic under-forecasting (stockout risk), negative bias means chronic over-forecasting (excess inventory). Bias should ideally be within plus or minus 5% of average demand. Track bias alongside the tracking signal (CFE/MAD) — when tracking signal exceeds plus or minus 4, the forecast is systematically biased.
What is a tracking signal in demand forecasting?
A tracking signal is the cumulative forecast error divided by the mean absolute deviation (MAD). It measures whether forecast errors are random or systematic. Values between –4 and +4 indicate a well-calibrated forecast. Beyond ±4, the model has statistically significant bias and should be recalibrated or replaced.

📰 Latest from Mathnal Insights

Supply Chain Intelligence You Can't Afford to Miss

Issue #10 · Crisis Analysis

Iran-Israel-USA War: Quantified Supply Chain Impact & 12 Mitigation Strategies

Hormuz closure disrupts 20% oil, 34% helium, 46% urea. Brent +55%, freight +50%. Every route, cost & mitigation quantified.

Issue #9 · ESG & Scope 3

ESG Compliance & Scope 3: Genuinely Compliant or Exposed to Greenwashing Risk?

EU CSRD fines 5% revenue, UK CMA 10% turnover, 150+ US lawsuits. 6 regulations, 8 warning signs, 6-pillar compliance framework.

Free Tool · Interactive Simulator

Supply Chain Risk & Resilience Simulator (SCRRS)

Bayesian risk engine, 45 scenarios, Monte Carlo simulation, VaR/CVaR — simulate the Hormuz crisis on your supply chain.

View all 10 newsletters →  |  Free diagnostic tools →  |  CSCOP Certification →