Skip to main content

Understanding Forecast Timing

Distributor guide to when orderIQ forecasts run each week in Encompass, what data syncs first, when suggested orders appear for upcoming stops and how they split across multiple stops. Requires v25.01+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 25.01

Pre-Conditions

  • OrderIQ is installed and scheduled
    ​
    ​

  • Understanding of customer delivery schedules

Steps

How Forecast Timing Works:

1. Weekly Forecast Cycle:

  • Forecasts are generated weekly, typically early in the week (Saturday night)
    ​
    ​

  • The forecast week runs Monday to Sunday
    ​
    ​

  • Predictions are based on the customer's next scheduled stop date

2. Data Synchronization:

  • Historical data is synced before forecasts run
    ​
    ​

  • This includes: stops, calendars, customer/product combinations, prices, sales, weather, and POS data
    ​
    ​

  • The sync process uses data from the previous week unless running a full import

3. When Suggestions Appear:

  • Suggestions appear for the upcoming week's scheduled stops
    ​
    ​

  • If a customer has a stop scheduled for Wednesday, the suggestion will be available starting Monday of that week
    ​
    ​

  • Suggestions update as forecasts complete processing

4. Stop Date Splitting:

  • If a customer has multiple stops in a week, the forecast is split across those stops
    ​
    ​

  • The SplitSequence indicates which stop (1st, 2nd, 3rd)
    ​
    ​

  • The split follows the OrderSize configuration

Fields And Definitions

  • Forecast Date: The Monday of the week being forecast
    ​
    ​

  • Sync Start Time: Start time for data synchronization (typically ForecastDate - 7 days)
    ​
    ​

  • Next Scheduled Date: Customer's next scheduled stop date
    ​
    ​

  • Week Date: The week (Monday) the forecast applies to
    ​
    ​

  • Date: The specific stop date within that week

Best Practices

  • Ensure routes and stops are configured correctly before the forecast runs
    ​
    ​

  • Changes to stop schedules after forecasts run may not be reflected until the next forecast cycle
    ​
    ​

  • If a customer's stop moves to a different day, the suggestion will follow the new stop date
    ​
    ​

  • For customers with Product Groups on stops, suggestions respect those groupings
    ​
    ​

  • Run data imports if significant historical corrections were made

Did this answer your question?