On Uber Eats, call POST /eats/stores/{store_id}/status with the updated prep time value to increase the time communicated to couriers and customers; use this endpoint to set the store offline when overwhelmed
On DoorDash Marketplace, use the store deactivation API with a short end_time to temporarily pause order intake; provide a valid reason code from the accepted list (e.g., KITCHEN_BUSY)
On Deliveroo, use the store availability endpoint to mark the site as temporarily closed with an estimated reopen time
Automate throttling logic by monitoring an order queue depth metric in your system; trigger prep time increases when queue depth exceeds a defined threshold
Reactivate or restore normal prep times by calling the corresponding reactivation or status reset endpoint on each platform after the rush subsides
Log all throttle and reactivation events with timestamps for post-incident analysis and to correlate with order volume data
Known gotchas
DoorDash's store deactivation API no longer supports indefinite deactivations initiated by POS providers; if no end_time is set, the store auto-reactivates after two weeks — always set an explicit end_time for short-term throttling
On Uber Eats, setting a store offline via POST /status is the recommended mechanism for capacity-based pausing; support for this endpoint is strongly recommended by Uber's developer documentation
Throttling through the native delivery platform APIs only affects orders on those specific platforms; if orders also come through a native app or other channels, apply throttling there separately
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp