Docs

Routing optimisation.

Trackely uses a propose, explain, confirm, and apply workflow. The optimiser never auto-applies route changes.

Constraints

  • Time windows per stop, including hard and soft behaviour
  • Service time included in the arrival and lateness calculation
  • Vehicle capacity where weight, volume, or pallet data is provided
  • Driver eligibility based on driver documents

Scoring priorities

Candidate orders are ranked in this order:

  1. Hard constraint violations
  2. Total lateness minutes
  3. Cost estimate
  4. CO2 estimate
  5. Distance

How routes are built

Trackely uses its own heuristic (nearest neighbour, merge, and 2-opt improvement) and uses Google Routes for drive times. Routes with more than 25 stops use a local estimate for drive times. Results are estimates, not a promise of savings or arrival accuracy.

Eco score

ecoScore is a relative 0 to 100 score within the evaluated candidates, based on estimated CO2.

Google Routes configuration

  • GOOGLE_MAPS_SERVER_KEY for server-side geocoding and routes
  • NEXT_PUBLIC_GOOGLE_MAPS_API_KEY for browser-side map rendering

If these are unavailable, Trackely uses a deterministic local estimate instead of Google drive times.

Common failure modes

  • Missing depot or stop coordinates
  • Invalid time windows
  • Infeasible hard windows