Forecasting & Anomalies
Every night the forecast reads ninety days of a location’s own trading and sets each of the next seven days from the same weekday behind it — a line with a high and low band, not one number. As each day closes, its real figure is written back against the forecast that named it, so the error stays on the page beside the line. A day that lands far outside the run of days behind it is flagged with what was expected against what was taken, and it stays on the list until someone acknowledges it.
- Insights · Add-on
- Forecasts and flags from your own numbers
What it does.
- Net sales and paid order counts forecast seven days ahead
- A high and low band on every forecast day
- Each day set from the same weekday behind it
- Past forecasts scored against the days that have since closed
- A flag on the day that lands far outside its own baseline
- Observed against expected on each flag, acknowledged once handled
Needs Business Intelligence switched on as well.
It does not work alone.
These sit on the same order record, so what one of them writes the next one can already read.
Book a RestoMama demo
Tell us about your restaurant and the workflows you want to launch first.
- One replyA person from the team, not an autoresponder sequence.
- One serviceWe walk your own dinner rush end to end — bill, KOT, payment, dispatch, day close.
- No hardwareIt runs in the browser on the machines and printers you already have.
See a real service, end to end.
We will take one dinner rush the whole way — ring a bill, print the KOT, call the token, mark the payment, dispatch the order, pay the agent and read the day close. On your menu, with your zones, in about thirty minutes.
- Billing and the counterOrder, modifiers, receipt, token
- The kitchen screenKOT routing, stations, prep state
- Payments and closingUPI, card, cash, wallet, day-end
- Dispatch and payoutsZones, assignment, tracking, settlement