Order list with sales forecasts
Sales expectations is the third — and most forward-looking — of the order list's generation modes, alongside Order to par and Burn rate (see order list overview). The other two extrapolate from the past, which is a great signal when the future looks like the past — but neither can anticipate a holiday weekend, a heat wave, a new menu item, or a planned catering pickup. Sales-expectations mode swaps in forecasted sales as the demand input, then rolls those forecasts down to ingredient-level quantities.
How it differs from burn-rate mode
| Burn-rate mode | Sales Expectation mode | |
|---|---|---|
| Demand source | Historical consumption average | Per-day forecasted sales per menu item |
| Reacts to upcoming events | No | Yes (weather, day of week, operator context) |
| Needs sales data | No | Yes — at least 30 days uploaded |
| Reacts to menu changes | Slow (after burn rate window catches up) | Fast |
| Best for | Steady, predictable demand | Known upcoming variation |
How the math works
In Sales Expectation mode, for each ingredient:
- Look up every menu item that uses it.
- For each menu item, multiply the forecasted units × the menu item's recipe quantity for this ingredient × portion multiplier.
- Sum across all menu items and across the projection window (until the next delivery + buffer).
- Compare to current stock; flag if stock can't cover projected demand.
Sub-recipes are exploded automatically — if "marinara" is used inside another sauce, its ingredient demand chains through.
Prerequisites
- Pro tier with
demandForecastenabled. - Sales data uploaded — at least 30 days of historical sales matched to menu items. See the sales data page.
- Menu items linked to recipes — recipes are how forecasted sales become ingredient demand.
- Current forecast — refreshed on the demand forecast page if business context or weather has changed.
Without one of these, Sales Expectation mode either falls back to burn-rate behavior or shows incomplete results.
Switching modes
Unlike Order to par and Burn rate — which build the moment you pick a supplier — Sales expectations needs your expected sales first, so it has an explicit Update list step.
Go to Order list and pick a supplier on the left.
- In the Start from list, choose Sales expectations.
Enter expected daily sales per menu item in the sidebar (or Load from forecast if you have a current one), then tap Update list.
- Review the new quantities — some products will move a lot, others won't — and submit.
The order list remembers your mode per restaurant — once you pick Sales expectations it stays selected on your next visit, until you switch back. Glance at the Start from list before ordering so you know which signal you're acting on.
What kinds of products see the biggest difference
- Sales-driven ingredients with weather or weekday sensitivity (lettuce, buns, cheese, ice cream).
- Ingredients in seasonal menu items.
- Items used in only one or two menu items — the forecast for those items pins ingredient demand sharply.
Staple ingredients used across many menu items (salt, oil, eggs) tend to smooth out, so the two modes often agree on those.
Banner warning: missing forecast or sales
If you switch to Sales Expectation mode and you're missing data, the order list shows a banner explaining what's missing and links to the docs for how to fix it. Read the banner — the projections won't be meaningful until you address it.
Common mistakes
Using forecast mode with stale forecasts
Forecasts can go stale fast if business context shifts. Refresh on the demand forecast page first.
Treating forecast quantities as orders-as-binding
A forecast is a probabilistic prediction. The order list takes it as truth for the projection, but you should sanity-check the answer for big events.
Switching between modes mid-order without re-reviewing
The quantities change as soon as you flip the toggle. Don't toggle and then submit without re-reading the list.