Base module
how will the system predict it?
How many weeks does the system need so that it can build a forecast based on sales data for a new position? forecast value?
The total forecast for the week is equal to the sum of all its components.
Prediction components can be viewed in the Analysis form by selecting them in the "Components - In pieces" menu.
Example: the forecast is built on the basis of the actual price, seasonality and the base level. We choose the predictors "A.
Price", "Seasonality", "Base" from the menu "Components - In pieces", summarize, their sum for each week will be equal to the forecast value.
Example: the value "A. Price" = 20, "Seasonality" = 25, "Base" = 100. The forecast value will be equal to 145.
The situation when the forecast is equal to sales - its almost impossible.
However, if the differences in forecast and sales are not significant and are covered by a small safety stock which is calculated by the system, then this situation is normal.
If the differences are significant, then it is necessary to try to determine which factor is not taken into account in the forecast.
The algorithm of actions is as follows: the situation is normal? We will lose sales if the forecast is lower.
The last statement is not true, since there will be sales losses only if the sales exceed the forecast and the safety stock in total.
If sales exceed the forecast, but remain within the safety stock, there will be no loss of sales.
Safety stock is calculated individually for each item in each store.
Safety stock is the standard deviation of past sales from the forecast.
However, in practice, the system always tries to make it more accurate, counting on different forecast ranges.
For this, the forecast is divided into 3 ranges: Further, the standard deviation is considered separately for each of these periods.
Thus, the safety stock, for example, for ice cream or kvass in winter and summer will be different.
Safety stock for promotional periods and non- promotional periods will also be different.
The percentage of safety stock in relation to the forecast will also be different for different positions, but the general rule is as follows: case?
It could be. However, this can only be a problem for the top, best-selling items.
For such positions, we recommend increasing the safety stock using SS coefficients.
In this case, the safety stock will be multiplied by this coefficients.
For non-top positions, it is recommended to leave the SS coefficient by default.
Usually it is equal to one, this is a system setting and it can be changed. offs of perishable goods?
Since sales of specific positions are often volatile, and the lower the sales rate, the higher the demand volatility, as a rule, it is important to find the right balance between the availability of goods to cover the extremes and the level of write-offs.
The general recommendation is to reduce the SS coefficient for such positions and set it to less than one.
And for top positions, where the delivery time does not significantly exceed the sales period of position, set this coefficient close to zero.
This just does not need to be done.
By adjusting the coefficients, you accumulate experience, and you should not constantly change them.
For more information on the application of SS coefficients, see the section "Safety Stock adjustments".
If the Promo module is not used, it is recommended to enter a master forecast for promotional periods.
You can also use the master forecast to adjust the forecast for new products, if you have not set an analog.
The master forecast is introduced at a general level (SKU-all stores) and distributed proportionally to the system forecast at the level of specific stores, raising or lowering the total forecast of all stores to the level of the master forecast.
Region 0 presents aggregated sales data for all stores in the chain.
For region 0, a separate forecast is being built, which may differ from the sum of forecasts for all stores.
The level "region 0" is used as the highest level of the geographic hierarchy when building forecasts of lower levels.
SKU" levels in the "Forecasts - View" form?
The level "Sum stores - SKU" is a forecast built at the level of each store and summed up.
The "All stores - SKU" level is a forecast built at the level of region 0, which represents aggregated data for the entire chain.
the forecast at the region 0 level?
The difference is that when building a forecast at the store level, the system analyzes the sales dependencies on influencing factors at detailed levels, which in certain cases, when there is enough data, can give a more accurate result, and in some cases the dependencies may not be determined.
forecast for all stores?
For different positions - in different ways, it depends on is it enough sales history at detailed levels to make a forecast.
With insufficient history, a forecast at region 0 level may be more accurate.
Another advantage of using the forecast at the region 0 level is that it allows you to determine the chain-wide sales dependence on influencing factors (price, seasonality, etc.) and use them at more detailed levels.
of "Anomalies and Excluded"? This is not necessary.
The Anomalies and Excluded functionality is used in exceptional cases if anomaly sales are identified in the forecast analysis process.
Also, if the customer's system has dedicated sales by reservation, it is recommended to download them so that the engine takes them into account as anomalies.
In some cases, if the promo module is not used and there are requirements for the engine to predict regular and seasonal sales, those weeks for which the master forecast with the Promo type is set are automatically pulled into the forecast exceptions.
network? The list of such items is configured in the system.
Before you use Ń„ neural network to forecast a position, you need to verify the forecast, i.e. check visually.
This can be done using the "Brain" forecast profile. the opening or closing of a competing store.
How quickly will MySales respond to such changes? Most likely, the reaction of the system will not be instant.
This is done in order to smooth out local extremes in sales.
But after 1-3 weeks, the system will see these changes and begin to take them into account in the future forecast.
This can be checked on real, already happened examples, rolling back in the forecast 1-3 weeks ago.
You can do this in the "Analysis" form by clicking on the "Settings" link and choosing the last week of sales that the system can see when building the forecast.
Also, immediately after the first week of increased sales, the system will begin to raise the safety stock, doing it carefully and without creating an increased stock where it is only one such week in history In this case, there are several options: items (clothes, shoes)?
Clothing and shoes that are ordered on a regular schedule can be ordered based on the system's forecast.
If the purchase of clothes and shoes is done for each season, then the organization of this process should be built a little differently.
Initially, it is worth using the forecast for groups of models (for example, men's sports shoes), in order to determine the potential demand for them.
Next, you need to expertly select models for potential demand and also expertly make a decomposition of the forecast at the level of model groups to specific models, and then to the dimensional grid to get specific numbers of positions for the order.
- To do this, go to the Analysis form and start calculating the forecast for interested position. The main and most effective forecast check is visual. It is recommended to visually evaluate the sales dynamics of current and previous year, comparing it with the current forecast in order to determine the use of seasonality in the forecast. You can also add a price to the chart to evaluate the effect of the price on the forecast and on sales. You can also use visual analysis of other factors.
- Because the system recalculates forecasts everyday to take into account the latest sales data
- In the Analysis form, in the parameter selection area, click the settings button, and then select the required last week of sales in the week field, which the system will see when making a forecast.
- There are two methods: with an analogue, or based on sales of an average position in the group. If system has an analogue, then the sales history of one or several analogues, multiplied by a coefficient, is used. If forecast is based on sales of an average position in the group, then the sales of the group are divided by the number of positions in it, after which they are adjusted for the price elasticity of the group with the price of a specific new item.
- The forecast for the expansion of distribution is based on sales at the group-store level, sales at the group-region level and sales at the SKU-region level. To simplify, the proportion is taken: [SKU-store forecast] = [SKU-region forecast] * [group-store sales] / [group-region sales]
- It is recommended to use analogue sales data from 6 to 13 weeks, depending on the system settings. However, this does not mean that for 6-13 weeks the system will not see data on the actual sales of the new position. As soon as the first data on the sales of new items appear, the system will already use it in the forecast, and the sales data for the analogue will only be used for those periods where there were no sales. The system can make a forecast for a new product without an analogue even when there are only a few weeks of sales, however, to more accurately determine the dependencies of sales on various factors (seasonality, price, promo), it is recommended to allow the system to use analogue sales data for a longer period of time
- The forecast for new stores is based only on one or more analogues (similar stores). As with new positions, it is recommended for new stores to allow the system to use sales data for similar stores for 9-13 weeks, so that the system can more accurately determine the dependence of sales on various factors. However, after the first weeks of sales appear, the system will see the sales data for the new store and use them in the forecast. The system will use data on sales of analogue stores only for those periods where there are no sales / stocks of a new store
- For the first week of sales, the system will not build a forecast at all, but after the first week of sales, the system will build a forecast without taking into account the dependencies, based only on the sales of the first weeks. With the accumulation of history for the new store, the forecast will become more accurate. However, it is recommended to add analogues for new stores.
Check the forecast at the SKU-region level for region 0 (the entire chain), either at the level of a specific region or at the store level
In the "Models" window, determine the factors that have the highest correlation coefficients
Check if these factors are taken into account in the forecast
If all the significant factors are taken into account, it is necessary to analyze and find out which factor the system does not know about
If not all the significant factors are taken into account, then it is necessary to add these factors to the chart and evaluate visually whether their influence is fully taken into account
If you can't understand for yourself whether all significant factors have been taken into account or not, contact MySales for analytical support.
High range - promotional periods and periods of high seasonal sales
Low range - periods of seasonal decline or periods without a promotion, if the position has a slightly expressed seasonality
Normal range - other periods
The higher the speed of sales, the greater the mass of demand for it, the more accurate the forecast, respectively, the lower the percentage of safety stock
The slower the position is sold, the greater its safety stock in percent, but at the same time less in pieces. To understand this, imagine a simple case where the forecast is equal to average sales. If on average, a position is sold 0.5 units per week (every 2 weeks), then its safety stock will be slightly less than 0.5 in units, but at the same time, it will be almost 100% of the forecast.
Check other forecast models that the system has built and select the most suitable. You can check the models in the "Analysis" form by selecting them from the "Components - Analysis" menu and checking visually on the chart. It is recommended to start from more accurate to less accurate. Further, the desired model can be fixed for the engine by clicking the "Models" button and selecting it there, however, it is recommended to do this at specific levels (SKU-region, SKU-store, group-region, group-store).
Correct the forecast of the system using the "Master" functionality at the SKU-all stores level
In exceptional cases, you can download a detailed forecast at the SKU-store level
You can also request analytic support from MySales.