Possible logistic scenarios

For all logistic scenarios, be sure to specify depots, orders, and couriers. The data set is dependent on the couriers and orders in it. If they can be divided into independent parts (so that a group of orders is only carried out by certain vehicles and there's no mixing), we recommend making multiple separate planning runs, each with its own set of orders and couriers. For example, do this if:

  • There are several depots, each depot ships its own set of orders, and each depot has its own set of vehicles.

  • Cargo is delivered from the depot and taken to the depot by different vehicles (and these are different independent orders).

  • A depot has several geographical zones, each of which is served by its own set of vehicles.

The logistic scenarios described below can be combined. If the above examples don't describe your business task, contact your RouteQ manager or support at routing-support@yandex-team.ru.

Delivery from one depot

This is the default scenario when you need to plan the delivery of goods to your clients or build a route that visits a specified set of points. It's used if there's only one depot in the request, and orders have the delivery type specified in the location field, or this field isn't set (see Order type). The algorithm will build a route for delivery of all orders from the specified depot.

Diagram

Example

There are 30 orders in this solution. All of them are delivered from a single depot. The order type isn't explicitly specified, so its default value is delivery .

API request (JSON) ⋅ API response ⋅ View on map

Cargo collection to the depot

This is the default scenario when cargo is collected from your clients to be delivered to the depot. For examples, this cargo may include:

  • Medical tests that are taken at home.

  • Clothes for dry cleaning.

  • Goods that your clients return to the depot.

In the last case, this scenario is often combined with delivery from a single depot.

To specify pickup points, set the order type = pickup (see Order type). After that, different options are possible:

  1. All couriers should return to the depot at the end of the day (see Returning to a depot at the end of the working day), meaning that return_to_depot = true. In this case, you don't need to configure anything else, and the courier completes the route at the depot by default.

  2. The cargo must stay in the courier's vehicle and be returned to the depot the next morning when the courier arrives for their next shift. To do this, set return_to_depot = false. The route will end at the last pickup point. You don't need to configure anything else in this case, either.

  3. Not all couriers return to the depot at the end of the day. The algorithm chooses which ones must return. For couriers, the return_to_depot = false option is used, and for pickup orders, you specify whether it's mandatory to return to the depot in the current route pickup_must_reach_depot = true or set up delivery_deadline, which is the time of order delivery to the depot.

    If the order is linked to a depot (one or more depots are given in the depot_id field), the pickup order will be delivered to one of these depots in the current route, regardless of the pickup_must_reach_depot value.

Schemes

  • Cargo delivery to the depot.

  • Delivery of cargo to one of several depots.