Route optimization not working

Usually one of: too few stops, bad addresses, or Mowzey already had the best order.

Mowzey uses Mapbox's Optimized Trips API — a real road-graph router, not just straight-line distance. When the Optimize button doesn't seem to help, it's almost always one of a few specific issues. Work through them in order below.

Run these checks

1
Make sure you have at least 2 stops. Optimization needs something to optimize. With 0 or 1 jobs on a day, the button does nothing visible.
2
Check that every customer has a valid address. Optimization geocodes each address to a lat/lng. If Mapbox can't geocode one (typo, missing ZIP, fictional street), that stop gets dropped from the optimization and the order looks wrong. Open each customer on the day and look for a "couldn't geocode" warning. Fix the address (be specific: full street number, real street name, ZIP).
3
Trust that Mowzey may already have the best order. If you only have 3-4 stops and they're roughly on a line, the original drag-and-drop order may already be optimal. The button is more dramatic when you have 8+ stops or geographically scattered jobs.
4
Re-load the schedule. Refresh the Schedule Builder page. Cached route data sometimes lingers between sessions.

When to skip auto-optimize

Optimization minimizes drive time, but it doesn't know your business context. Override it manually when:

  • You always start near the dump or your shop and end there too.
  • You have a customer who's only available before 10am (Mowzey doesn't yet support time windows).
  • One stop has equipment you need for several other stops (e.g., the customer who lets you fill up water).
  • You promised a specific arrival window.

Hybrid approach

Drag your fixed stops (first and last) into position, then hit Optimize. Mapbox will reorder only the middle stops.

Still wrong after all this?

Email support@mowzey.com with the day + crew that's misbehaving and screenshots of both the order Mowzey suggested and what you expected. We can look at the actual Mapbox response and see what happened.