---
metadata:
  - name: generator
    content: Diplodoc Platform v5.19.6
alternate:
  - https://docs.routeq.com/doc/en/vrp/post-optimization.md
title: RouteQ — properties and options — sequence post-optimization
---
> **Documentation Index:** Fetch the complete configuration index at https://docs.routeq.com/doc/en/llms.txt


# Sequence post-optimization

If during planning you use [balancing](https://docs.routeq.com/doc/en/vrp/balanced-groups.md) with high penalties or [geographical grouping](https://docs.routeq.com/doc/en/vrp/grouping-routes.md) with the `global_proximity_factor` option, enable sequence post-optimization mode using the `post_optimization` option:

```json
"options": {
    "post_optimization": true
}
```
The algorithm will perform post-optimization of the sequence of each individual route at the end of the planning task.

**Example 1 (no post-optimization)**

This example uses `global_proximity_factor` and the balancing option.

[API request (JSON)](https://courier.yandex.ru/vrs/api/v1/log/request/aee41300-8406de1d-ab4f74e9-615f4d6f) ⋅ [API response](https://courier.yandex.ru/vrs/api/v1/result/aee41300-8406de1d-ab4f74e9-615f4d6f) ⋅  [View on map](https://yandex.com/courier/mvrp-map#aee41300-8406de1d-ab4f74e9-615f4d6f)

**Example 2 (with post-optimization)**

Same as example 1 but with the added `post_optimization` option. The result is lower total mileage and reduced time en route and in motion. Routes have become more predictable.

[API request (JSON)](https://courier.yandex.ru/vrs/api/v1/log/request/fdb6b452-fc870c1b-35e063e5-9d71d6a7) ⋅ [API response](https://courier.yandex.ru/vrs/api/v1/result/fdb6b452-fc870c1b-35e063e5-9d71d6a7) ⋅  [View on map](https://yandex.com/courier/mvrp-map#fdb6b452-fc870c1b-35e063e5-9d71d6a7)

{% include [warehouse-feedback](_includes/feedback-81845556eeea.md) %}