How is an order flagged when it sits in a status beyond its KPI threshold?

If an order sits in a status longer than its KPI threshold, an escalation/alert is raised to admin and it appears on an exception dashboard. Because every status change is timestamped, the system knows how long an order has lingered and can surface the laggards — the order stuck in "packing" for too long, the fulfilment that's overdue. This turns silent bottlenecks into visible…

If an order sits in a status longer than its KPI threshold, an escalation/alert is raised to admin and it appears on an exception dashboard. Because every status change is timestamped, the system knows how long an order has lingered and can surface the laggards — the order stuck in "packing" for too long, the fulfilment that's overdue. This turns silent bottlenecks into visible exceptions an operator can act on, which is central to running on fulfilment-speed KPIs.