Skip to content

New Optimiser Beta

Welcome to the new Tarot Routing Route Optimiser v2!

We're hard at work bringing all of the powerful features from the existing optimiser into v2. In the meantime, here is a list of capabilities you might be missing today—and that will appear in the Beta over the coming weeks and months.

Features Coming Soon

Scheduling & Routing Constraints

  • Negative Time–Windowsexclude_period_start / exclude_period_end (customer closed intervals)
  • Breaks ‑ Fixed breaks (lunch_time, lunch_duration) ‑ Floating breaks (lunch_latest_start)
  • Range Limitsrange_limit (max kilometres per route)
  • Real-time Re-optimisationimmovable=true to lock already-served jobs ‑ initial runs integration

Advanced Constraints

  • Walkable‐Jobs Biaswalkable_threshold for very short adjacent drives
  • Fairnessallocate_fairly=true for balanced workload

Deprecated Features

These features are not planned to be added back, since they no longer align with our strategic direction. If you need them - ask - we can consider it.

Old Stopping Criteria

The quick_opt setting and the improvement_threshold_per_second are deprecated. Stopping criteria are now controlled more granularly via time_limit, unimproved_time_limit, iter_limit, and unimproved_iter_limit.

Priority Jobs

The boolean priority=true setting for jobs is deprecated. Use unserved_penalty_factor to say that some Jobs matter more than others if something has to be left unserved.

Pickup Delivery Interval

pd_interval_max for limiting the time-in-vehicle between the pickup and the delivery (useful for on-demand passenger transport) is deprecated.

Logical Capacity

Logical “or” | capacity rules on drivers (e.g., (boxes:25&bikes:0)|(bikes:10&boxes:0)) is deprecated.


Let us know

If you’d like early access, need a specific feature now, or have feedback, contact us:

info@tarotanalytics.com