Frequently asked questions
Planning task
To view the original task data, use the following link: https://courier.yandex.ru/vrs/api/v1/log/request/<task_id>
, where
task_id
is the ID of the completed task.
Yes, there is. By default, you can use one access key to launch no more than ten parallel planning tasks.
The geocoding of addresses depends on how you launch the task. If you launch planning:
In the Request processing time section, you can see the standard planning time for the Optimal setting. If you need set additional limits on the planning time, contact support.
No, you don't need to do that again. The task is saved under a unique number that you can find in the address bar: https://yandex.ru/courier/companies/<company_id>/depots/all/mvrp/<task_id>
, where
task_id
is the ID of the completed task.
company_id
is your company's ID.
To receive the solution, refresh the page where you launched the task.
Planning file
The Excel file doesn't support all the available parameters yet.
For more information, go to:
Orders
- A hard time window of a shift, depot, or order.
- Check the order's
penalty.drop
value. It mustn't be too small or zero. - Make all order windows soft.
- Remove order tags.
- Remove order load_types.
Orders may be unallocated for a number of reasons. Most often, it's because of hard restrictions that the algorithm can't violate:
In some scenarios, such behavior is expected (see Planning orders that can be rescheduled/Planning part of the orders).
To understand the reasons, look at the task conditions:
For a description of settings for this scenario, see Multiple time windows in the order.
For more information about long waiting times and how to reduce them, see Minimizing waiting time for couriers.
This is so that when orders are combined in multi-orders, the parking time is only counted once and the delivery time depends on the number of orders.
Couriers
The settings for managing courier workload are described in the following use cases:
No, within one planning task, you can select only one transport type for one courier.
A special case is planning in transit mode, where the courier uses public transport, gets off, and walks to the delivery point.
In each planning, take into account the couriers' work schedule on a specific day. If their schedules are different on different days, take this into account when forming an API request or when preparing data in Excel.
If you know orders for future dates and the couriers' schedule in advance, use the description of the Planning orders for multiple days case.
Add a garage
point and specify its ID in the vehicle.finish_at
field. The route will conclude at the specified point.
If the option to return to the depot at the end of a shift is enabled (parameter vehicle.return_to_depot = TRUE
), the courier will first return to the depot, and then go to the finish_at
point.
For more information, see the Returning to the depot at the end of the working day and Start or end of the route at an arbitrary point.
Penalties
Penalties are intended only for setting up the algorithm. They aren't linked to logistic cost analysis.
You can find recommendations on using penalties in the descriptions of logistic scenarios.
Integration with the API
- Via the Logistics Coordinator Workplace interface. This option supports editing routes and saving the results. For more information, see Edit a solution.
- At
https://courier.yandex.ru/mvrp-map#<task_id>
, wheretask_id
is the ID of the received solution. This option only supports visualization, without the ability to edit the solution.
For more information about this interaction method, see Running the API and editing the solution in the interface.
There are two options available: