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 ETA and lateness calculation
  • Vehicle capacity where weight or volume data is provided

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

Eco score

ecoScore is a relative 0 to 100 score within the evaluated candidates.

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 fallback so optimisation still works in development.

Common failure modes

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