Skip to main content

Troubleshoot your forecast

This article helps you as a forecasting user to find the cause of numbers that seem misleading. It covers the most common causes, but not all of them.

Download the estimation log

You can download the estimation log for the scenario and see how the numbers in the forecast have been calculated.

  1. Click the blue button next to the scenario.

  2. Select Download estimation log

The log shows which data the calculations are based on, and in which iteration the data was calculated.

The setting leaves out your stock

With the setting Totals based on exp. supply, tracezilla only includes the expected supply you enter yourself. If you tick the box, what you have in stock is not included in the calculation.


Forecast per customer or total forecast

tracezilla supports both forecast per customer and forecast without a customer. Choose the method that fits your planning process, and do not mix them in the same scenario.

If you enter expected sales at customer level, you can export the sales forecast to get an overview of what has been entered per customer.


Double counting of expected sales and orders

Check that expected sales and the actual orders fall in the right periods. If you use weekly periods with expected sales of 100 pcs in week 1 and an actual sales order of 100 pcs in week 2, the system calculates a requirement of 200 pcs.


The forecast has not been recalculated

Every time you change a SKU or recipe, or create new orders, you may need to recalculate the forecast. Make it a habit to estimate the supply before you review the numbers.

It is also worth checking how long the period is set to in the scenario.


The master data is out of date

Forecasting is based on your SKU data, stock levels and recipes. If the quantities in the recipes are wrong, or if discontinued SKUs are still active, this shows up in the forecast.
​
​

Did this answer your question?