Implement graduated order-intake throttling during a rush using prep-time extension rather than a hard store pause, across DoorDash, Uber Eats, and Grubhub

Steps

1. Monitor an internal signal for kitchen load (open ticket count, average ticket age) and define thresholds for 'slow down' versus 'stop' rather than only a binary open/closed state
2. On Uber Eats, use the POS order accept flow to extend the quoted prep time on acceptance instead of immediately pausing the store, which reduces incoming order velocity without fully cutting off demand
3. On DoorDash, use store pause/unpause at the most severe threshold only, since pausing removes the store from customer search entirely rather than just slowing intake
4. On Grubhub, use location-level configuration (e.g., adjusting delivery radius or minimum order amount) as a softer lever before resorting to a full pause
5. Automatically reverse all throttling actions once ticket load drops back under threshold, and log each throttle/unthrottle event for later prep-time SLA analysis