We have introduced return as a new stop type, enabling return-flow booking patterns where items are brought back to a designated location after delivery. This extends the existing stop types (pickup, dropoff, task) with a fourth option that can be used on bookings and tours.

Webhook events

The following webhook events now include stop_type: "return" as a possible value in their payload. If your integration inspects the stop_type field, make sure your webhook handlers accept this new value:

Service configuration

Services can now be configured with return stop settings through the admin API. When return is included in a service’s stop_types array, the following configuration fields become available:

• return_stop_duration_seconds — expected duration at the return location (default: 300 seconds)
• return_label_translations — customizable label for the return stop in multiple languages
• return_stop_default_maximum_driver_distance_meters — geofencing distance for the return location
• return_stop_default_auto_arrival_distance_meters — distance for automatic arrival marking

Creating and managing return stops

Return stops can be included when creating bookings or inserted into existing tours and bookings. The stop type on existing stops can also be changed to or from return via the update stop properties endpoint.

The public service listing also reflects whether return is enabled as a stop type: