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:
- Hard constraint violations
- Total lateness minutes
- Cost estimate
- CO2 estimate
- 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_KEYfor server-side geocoding and routesNEXT_PUBLIC_GOOGLE_MAPS_API_KEYfor 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