Register a webhook endpoint with Deliveroo's partner team that accepts order_created, order_updated, and order_cancelled event payloads
Validate incoming webhook signatures using the shared HMAC secret provided at integration setup time
On receipt of an order_created event, inject the order into the POS system and respond to Deliveroo with an order acceptance within the required acknowledgment window (typically 30 seconds)
Map Deliveroo's item IDs and modifier IDs to POS product codes using a pre-built mapping table maintained in a config store
Send order status updates back to Deliveroo via the order status update API as the kitchen progresses through preparation, ready, and collected states
Handle order_cancelled events by voiding the POS order and issuing a refund if payment was already captured
Known gotchas
Failing to acknowledge an order_created event within the acceptance window results in an automatic cancellation and a potential penalty against partner SLA metrics
Deliveroo does not retry failed webhook deliveries indefinitely; implement a Deliveroo-side polling fallback to catch orders that were missed due to endpoint downtime
Modifier mapping is the most common failure point; Deliveroo uses its own modifier ID namespace that must be explicitly mapped to POS modifier codes before go-live
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