Detection of route point visits

Visits to route points (orders and depots) are detected automatically. This helps to log violations of the delivery sequence (if the Delivery by order statuses option is off) and to automatically detect deliveries .

Detection parameter settings

Detection radius, m

The detection radius is set to 500 m at the company level by default. You can specify a different value in the company settings yourself (only when automatic delivery detection is enabled) or by contacting support (if you don't want to enable automatic delivery detection). The maximum detection radius is 2000 m.

You can set individual detection radiuses:

• For all orders on a route that starts from a specific depot, in which case use the "mark_delivered_radius" parameter in the API method when creating a depot or editing one or several depots. This radius takes priority over the company-level radius.
• For a specific order, use the "mark_delivered_radius" parameter in the API method when creating or editing one or several orders. This radius takes priority over the company-level and depot-level radiuses.

You can set the depot visit detection radius (different from the company-level setting) via the interface in the company settings or using the API method for creating one or several depots in the mark_route_started_radius parameter.

Detection coefficient

The default value is 0.5. You can specify a different value in the company settings yourself (only if automatic delivery detection is enabled) or by contacting support (if you don't want to enable automatic delivery detection).

Time to spend in the radius for detection, sec

A visit is detected after the period of $N$, during which the courier must remain within the detection radius (in the delivery area).

Note

If you don't specify the time parameters, the visit will be detected when the courier enters the radius.

For the order, the time when the courier is in the delivery area is calculated using the formula:

$N = coef_{detection} * \times(t_{order} + t_{address})$, where

• $coef_{detection}$ is the detection coefficient.
• $t_{order}$ is the service_duration_s order handling time.
• $t_{address}$ is the shared_service_duration_s address handling time.

The calculation for the depot uses the service_duration_s loading/unloading time. You can also set this value using the API method for creating one or several depots. You have to set this parameter if you use depot detection.

Dependency on ETA calculation

The moment when a visit detection is triggered depends on the selected ETA calculation method:

• For arrival_time: After $N$ seconds after the courier enters the delivery area.
• For delivery_time: After $N$ seconds after the start of delivery, but not before the delivery window.

How visit time is recorded

The point visit is detected using the time on the courier's device.

For example, the courier visited the order at 17:00, but the internet connection on their device was lost and only restored at 17:10. At 17:05, the Routing workspace dashboard won't show that the order has been visited. The manager will receive information about the order visit only at 17:10 after the courier's internet connection was restored and the device sent data to the Track & Trace server. In this case, the order visit time will be recorded as 17:00.

Contact support