Skip to main content

Operational alerts

You need: Sales reports.

Three reports that return only the stores currently outside a threshold you set. Where the operations report shows everything, these show you only what needs attention.

The three

Alert Flags a store when Default threshold
Delivery load Pending deliveries per active driver exceed the threshold 2
Cancellations The share of valid orders falls below the threshold 90%
On-time On-time percentage is below the threshold and average delivery time exceeds the maximum 80% and 60 min

Each threshold is a parameter you pass when running the report, not a saved setting. Change it and re-run to widen or narrow what comes back.

The on-time alert needs both conditions

This is the one people misread. A store is only flagged when it is both below the on-time percentage and above the average-time limit.

That is deliberate. A store missing its target by a little while still delivering quickly is a different problem from one that is slow across the board — and only the second is worth interrupting someone for.

If you want the looser view, raise the maximum-minutes value rather than lowering the percentage.

These are not the Hub alarms

Easy to confuse, genuinely different:

Operational alerts Branch alarms
Where Reports Hub
Threshold Passed per run, by you Configured chain-wide
Lifecycle Recomputed each time you run it Raised, then archived
Use Reviewing a period Acting during service

Use these when reviewing; use Branch alarms when running the shift.

A workflow that works

  1. Run all three at their defaults for yesterday.
  2. For any store that appears, open the Operations report filtered to it.
  3. Check the store configuration changelog — did something change?
  4. If several stores appear together, suspect a shared cause before working through them one at a time.
  5. If the same store appears every day, the threshold is describing normal for that store. Either fix the store or accept it — a permanently-flagged store is noise.
Back to top