Skip to content
ML Academy

Time series and forecasting · insight-0216

Match the forecasting level of a hierarchy to the noise and the decision

Evidence type
practitioner heuristic
Difficulty
medium
Roles
Data scientist, Data analyst
Industries
retail, telecom, aviation

Summary: situation, action, reason, boundary

  1. Situation

    Store-SKU daily sales are too noisy to forecast well, but replenishment decisions are made per store and SKU.

  2. Action

    Compare bottom-up, top-down and middle-out approaches in a backtest, measuring accuracy at the level where each decision is made, and use reconciliation when several levels feed decisions.

  3. Reason

    Aggregates are smoother and easier to forecast, while disaggregation proportions can drift; the best level depends on the data and the user.

  4. Boundary

    Retail, telecom traffic, airline origin-destination markets.

Symptom or risk

Pure bottom-up forecasting passes noise up the hierarchy; pure top-down loses item-level patterns such as promotions and local holidays.

Exceptions

When the bottom level has long, stable histories, bottom-up is often adequate.

Trade-offs

Middle-out is easy to explain but needs a stable split rule below the middle level.

Pitfalls

Using historical proportions for top-down after the mix has changed.

Lessons and concepts

Claims and their sources