Documentation

SkuBrain 101

Getting started

If you’re using skuBrain for the first time, your basic plan of attack will be:

  1. Import your sales data
  2. Build a demand forecast
  3. Create a replenishment plan
  4. Reorder stock from suppliers

If you wanted to get a feel for skuBrain, you could race through all of those steps. That would give you a general idea of what the software does and it’s not a bad place to start. However if you really want to understand the software and the inventory optimization process more generally, you should definitely read the Demand forecasting and Inventory planning sections of this documentation.

Day to day

Later on, once you have a forecast prepared in skuBrain, you’ll probably skip the forecasting step most of the time. The reason is that skuBrain’s forecasts are either quarterly or monthly, so they won’t generally change from one day to the next.1

Typically then, you’d prepare demand forecasts once every one or two months (putting a bit of effort into making sure the forecasts were as accurate as possible) and then reuse these forecasts to create replenishment plans daily, weekly or however often you wanted to reorder stock from suppliers.

When using skuBrain day to day (or week to week) then, your workflow will probably be:

  1. Import recent sales data
  2. Create a replenishment plan
  3. Reorder stock from suppliers

Notes

  1. When you create a forecast on July 5th, skuBrain considers all sales prior to July 1st as part of the sales history. The month of July itself is considered part of the demand forecast. As such, if you then created another forecast on July 10th or July 20th, none of the sales history would have changed (and thus neither would any of the statistical forecast). Only on August 1st does skuBrain take the sales for July into account when analyzing your sales history… so there’s no reason to create statistical forecasts more often than once a month (although you can make manual adjustments to your forecasts as often as you like).