Resources

Forecast trends, snapshots, and accuracy

The forecasting worksheet now shows how demand has moved, lets planners freeze a forecast, and grades that forecast against what actually shipped.

The forecasting worksheet now shows how demand has moved over time, lets planners freeze a version of the forecast, and grades that version against what actually shipped.

A forecast is only useful if you know how far to trust it. Until now, the worksheet showed the current number and not much else. Checking last month’s forecast meant keeping a copy somewhere else. Now the platform keeps the record and does the checking.

See the trend behind the number

A new Trend tab charts the forecast against history for each product, with a confidence band around it. A product that sells the same every week and a product that swings with the season look different at a glance, before anyone reads a figure.

Freeze a forecast

Snapshots save a version of the forecast as it stood on a given day. Take one before a planning meeting, and the version everyone agreed to is still there next month, even after the live forecast has moved on.

Grade it against what shipped

The Forecast vs Actual view compares a snapshot with the quantities that really went out the door, SKU by SKU, and gives it an accuracy score. Over a few months you learn which products you forecast well and which ones need a person’s judgment.

Try it before you publish

Production requirements for every customer

The screen planners use to size new orders was rebuilt so every customer gets the same version. Order quantities and dates come pre-filled, with safety stock and projected stock-out dates alongside, so a planner starts from a proposal.

Improvements
  • Forecast confidence bands on the Trend tab
  • Forecast vs Actual accuracy score per SKU
  • Production requirements pre-fill quantities, dates, safety stock and stock-out dates
Fixes
  • Fixed an error that could stop a job order from completing
  • Fixed a scheduled planning job that could leave inventory allocations wrong