On DoorDash Marketplace, POST to the item activation endpoint with is_active set to false for the target item ID to suspend it; note that GET menu endpoints do not return activation state, so track this state in your own system
On Uber Eats, use the item-level suspended_until field in a menu update request or use the store hours/availability endpoint to mark the item as unavailable
On Deliveroo, call the Menu API PATCH endpoint to update the item's availability field to false for the affected site
On aggregation middleware (Deliverect, Chowly, Otter), use their respective item availability or 86 endpoint or dashboard action; the middleware propagates the change to all connected channels
Log the timestamp and item ID for each channel-specific deactivation so you can reactivate systematically when stock is restored
To reactivate on DoorDash, POST to the same item activation endpoint with is_active set to true; use the equivalent reactivation call on each other platform
Known gotchas
DoorDash item deactivation via the activation endpoint is a suspension — it is distinct from marking an item inactive in a full menu update, which affects whether the item exists at all; use the correct endpoint for each operation type
On DoorDash, the deactivation state is not reflected in GET menu responses; you must track which items are currently suspended in your own data store to avoid race conditions on reactivation
Propagation latency varies by platform; an item may remain briefly visible on a channel after an 86 call — factor this into customer communication flows
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