Configure the return_to_store fields in your DoorDash Drive delivery creation request, including the return_address and return_instructions, so the platform knows where to send the Dasher if delivery fails
Subscribe to the DASHER_CONFIRMED_STORE_ARRIVED and DELIVERY_FAILED webhook events to track when delivery attempts fail at the customer address
On receipt of a DELIVERY_FAILED event with a failure_reason indicating customer_unavailable or access_denied, confirm the return-to-store flow is automatically triggered by DoorDash
Update your order management system to mark the order as return_in_progress and notify the merchant to expect the order back at the store
When the DELIVERY_RETURNED_TO_STORE event fires, trigger a customer notification and initiate the refund or re-delivery workflow based on business rules
Reconcile the Drive delivery fee for return flows; DoorDash typically charges a return fee in addition to the original delivery fee for completed return trips
Known gotchas
Return-to-store must be configured at delivery creation time via the return fields; it cannot be added retroactively after a delivery is active
Not all DoorDash Drive contract tiers include return-to-store as a default feature; verify your merchant agreement includes the return flow before relying on it operationally
Return delivery fees are charged per the Drive pricing tier and can equal or exceed the original delivery fee; factor this into refund policy design to avoid margin loss on failed deliveries
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