The feature is derived from pre-existing data within the system. And as imperfect as it is, it's the state of the order as the internal POS views it. The system is using the exact same data internally to do stuff like track ideal labor needs and tell you when it's time to cut staff for the night, recommend weekly schedules, etc. Which, depending on the franchisee, managers have to justify every time they deviate from the system recommendations. So the system having a flawed perception of the overall system state of orders is as much a hassle internally as externally.
[1] https://news.ycombinator.com/item?id=21251266
[2] The recent "text me when my driver is x minutes away" feature was not part of the initial rollout, and I can't say if that's another passive feature derived from existing data or involves some new form of active tracking.
Imagine a situation where you have a device telling you that an order has been placed and you have X minutes to complete the next step; you know it will only take a minute to make that pizza, and you’d rather chill for most of the time, no need to rush. So you wait until X minutes are almost over, then click “sure, I’m totally preparing it” - and keep chilling. Next step threshold comes up “yep, it’s all good boss”, and keep chilling. Then you actually make it, but will keep pushing buttons only when the thresholds are close, as to maximise your downtime without raising red flags (even if Delivery is reached too early, it’s the most flexible step so Corporate won’t mind it too much in reports).