Push real-time item availability (86ing) updates from a POS or inventory system to Deliverect to suppress sold-out items across all connected delivery channels
Authenticate to the Deliverect API using the credentials provided during partner onboarding
Identify the PLU code or Deliverect product identifier for the item to be 86'd; obtain this from the menu payload received during the initial menu sync
Send a PATCH or PUT request to the Deliverect availability endpoint with the product identifier and the new availability status (for example, unavailable) for the target account or location
Deliverect will propagate the availability change to all delivery channels (such as DoorDash, Uber Eats, Grubhub) configured for that location without requiring separate per-platform API calls
Implement a queue for availability updates to handle bursts (for example, end-of-night 86ing of multiple items) and retry on transient failures
Restore availability by sending a subsequent request setting the item back to available when the item is restocked
Known gotchas
Availability updates propagate asynchronously to delivery platforms; there may be a short delay before the item is hidden on consumer-facing ordering apps
Using the wrong product identifier (for example, a local POS ID instead of the Deliverect PLU) will result in a silent no-op or a 404 error; always use the canonical Deliverect product ID
Delivery platforms may cache item availability; confirm with Deliverect support the expected propagation latency for each connected channel
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