Multi-Vehicle Routing Release Notes

Jan. 31, 2026

• IMPROVED Added functionality to allow locking of portions of routes in the OptimizeSequence and OptimizeFull end points. With this functionality, a lock can be applied on a particular stop before optimization that prevents changes to stops either before or after the locked stop. The two options for locking are lockBefore or lockAfter. For example:
  • If a route has 10 stops and lockBefore is set on stop 4, and the solution is sent to the OptimizeSequence endpoint, stops 1,2,3,4 are not considered for optimization, only stops 5-10 can be optimized.
  • If stop 4 has lockAfter set, then only stops 1,2,3,4 are considered for optimization.

The stop lock is placed in your request body for the OptimizeSequence and OptimizeFull endpoints right after internalKey for the order you wish to lock. The appropriate values for lockBefore or lockAfter are only true or false. This change is backwards compatible.

Oct. 12, 2024

• FIXED Fixed the consolidation logic in the Multi-Vehicle Routing API. Consolidation is determined by the config > consolidation > consolidateBy setting. The possible consolidateBy values are:

  • none - Consolidation will not occur. (This is the default value.)
  • addressOnly - Consolidation occurs during loading when stops with the same latitude/longitude, EQCode, time window and other parameters match even if the accountID does not match.
  • addressandAccount - Consolidation occurs during loading when stops with the same latitude/longitude, EQCode, time window and other parameters match only if the accountID matches as well.

  Note: An unloaded stop will not consolidate with a loaded stop during load or optimize. The stop must be moved using the MOVE call to a sequence next to a loaded stop to consolidate them.