Stops created from a place are now grouped automatically. When several such stops end up on the same tour — the classic stacked-tour case of two orders picked up at the same location — they are recognised as one group and completed together, with no manual grouping step and no custom integration to maintain.

How it works

Whenever a stop is created from a place and no group is provided, it receives an automatic group derived from the stop’s type and the place, of the form A-<type>-<place_id> (for example A-pickup-<place id>). This applies both when creating a booking and when inserting a custom stop:

Create a Booking Insert custom stop into existing tour Insert custom stop into existing booking

Because two stops built from the same place with the same type derive the same group, they line up automatically once they share a tour — and completing the first as a driver completes the rest of the group, exactly as if the group had been set by hand.

When a stop’s type is later changed via Update Stop Properties, its automatic group is updated to match the new type, so grouping stays correct as stops are edited.

Your custom groups are always respected

A group you provide yourself is never touched: if a stop is created with an explicit group, that value is kept, and it is never overwritten when the type changes. The leading A- prefix is what marks a group as automatically managed — any group without it is treated as yours to control, through Bulk Update Stop’s Groups as before.

To accommodate the new format, the maximum length of a stop group has been increased from 40 to 50 characters.

Adopting it smoothly

If you currently assign stop groups yourself — for instance through a customization or an automation scenario — you can now hand that job to the platform. To roll over without clobbering the automatic groups, make your integration set a group only when the stop does not already have one, rather than always writing it. Once the automatic grouping is in place, ordinary stop mirroring keeps groups consistent across the booking and its tour on its own, and the group-setting customization can be retired.

Why this matters

Automatic grouping makes the out-of-the-box behaviour match what operators expect: build bookings from places, stack them into a tour, and the shared stops group and complete as one — no extra configuration, and no race between competing integrations trying to set the same group. It removes a whole class of manual-dispatching and stacking edge cases and cuts the churn of redundant updates that those integrations used to trigger.