Infor M3 & CloudSuiteFree calculatorPDF, Excel, Word exportInfor M3

M3 Exponential Smoothing Forecast Calculator

Choosing smoothing constants by feel is how forecast models drift. This calculator walks one period of Holt's linear method so you can see exactly what alpha and beta do to level, trend and the next forecast.

Your numbers

units

The smoothed level from the last period.

units/period
units
0.3
0.1
periods

Your results

Forecast for next period
1,039.84
Forecast at horizon
1,066.72
Forecast that was made for this period
1,012
Forecast error (actual minus forecast)
48
Absolute error
4.5%
New level
1,026.4
New trend
13.44

Illustrates the standard Holt method one step at a time. Check how your M3 forecast model is actually parameterised before mapping these constants.

Save results:

New level and next forecast vs alpha

Sweeps Level smoothing (alpha) from 0.05 to 1, holding your other inputs fixed.

Measure forecast accuracy

Optional: have forecast error and bias calculated across your M3 item base.

Optional. The tool and every export work without this. No spam.

How to use it

Enter the level and trend carried forward from the previous period and the latest actual demand. Choose alpha for how fast the level reacts and beta for how fast the trend reacts. The calculator shows the forecast that was made for this period, the error, the updated level and trend, and the forecast for the next period and for a horizon of your choice. Repeat the step with the outputs as next period's starting values to roll the model forward.

  • Higher alpha reacts faster but amplifies noise
  • Beta is usually kept small
  • Test the same period with two alpha values
  • Track error over many periods, not one

The Holt method

The new level is alpha times the actual plus (1 minus alpha) times the old level plus old trend. The new trend is beta times the change in level plus (1 minus beta) times the old trend. The forecast h periods ahead is the level plus h times the trend. With beta set to zero the trend freezes, and with alpha at 1 the level simply equals the latest actual.

Interpreting the output

A large absolute error with a stable trend usually means a one-off event, so avoid chasing it with a high alpha. Persistent error in one direction means the trend is not keeping up, so raise beta slightly. The chart shows how the new level moves from sluggish to fully reactive as alpha rises. Pick an alpha at which the level responds to genuine shifts but does not copy every spike.

  • Typical alpha for stable items is 0.1 to 0.3
  • Typical beta is 0.05 to 0.2
  • Flag outliers before they enter the history

Common mistakes

Applying a trend model to seasonal items produces forecasts that overshoot in the off season. Initialising level and trend badly also biases early periods. Another mistake is optimising alpha on a single month. Use a rolling error measure such as mean absolute deviation across at least a dozen periods, and compare against a naive forecast to confirm the model adds value.

Frequently Asked Questions

Does M3 use Holt exactly as shown?

Do not assume so. Forecast models in any ERP differ in initialisation and parameter naming. Use this tool to understand behaviour and compare against your system's documented forecast model before mapping constants.

What alpha should I start with?

Start around 0.2 for stable demand and raise it only if error analysis shows the forecast lags real shifts. Values near 1 mostly echo the latest actual and give little smoothing.

When should the trend be switched off?

Set beta to 0 for flat or noisy items without a real direction. A trend fitted to noise extrapolates badly, particularly at long horizons.

How do I handle seasonality?

This tool does not include a seasonal component. For seasonal items, deseasonalise first or use a model with seasonal indices, then apply smoothing to the adjusted series.

If you want forecast accuracy measured across all your M3 items and compared across models, Netray can build that analysis on your sales history.