Destination Address doesn't geocode - troubleshooting

The task destination is one of the most fundamental concepts of an Onfleet task. In many cases, it is necessary to geocode (convert an address into latitude and longitude coordinates) the recipient's submitted address in order to determine a task's destination. 

Onfleet uses Google Maps API to geocode addresses, as they are the premier option with the most data available for this function. It does a very good job in most cases but, as with any geocoder, there are limitations, and there will inevitably be some unrecognizable addresses which cause geocoding (and hence, task creation) to fail. 

Onfleet will only accept geocoded solutions with a high degree of confidence. If there is any ambiguity, including multiple potential matches, geocoding will fail. 

There are several possible scenarios where geocoding fails, according to how tasks are created:

  • Task import
    • Result: Geocoding fails
    • Result: Geocodes to wrong destination
  • From the dashboard
    • Result: No destination suggestions
    • Result: Destination suggestion doesn't geocode (error will appear near Destination field)


  • Enter the address on Google Maps to determine whether the address is known
    • Use the address, as formatted by Google, to geocode
      • If the street number is missing in the fully resolved Google Maps address, there is not enough information about that address to geocode from Onfleet.
    • Use coordinates derived from Google Maps to create the task  
  • Remove any apartment/suite numbers in the address being geocoded. Those belong in 'Address Line 2' only.
  • Create the task from the Onfleet dashboard map
  • Make use of a secondary geocoding service and use resulting coordinates in Onfleet
  • Get the recipient's destination coordinates during your checkout process, and submit those coordinates when creating tasks to skip geocoding entirely. 

For more in-depth geocoding solutions, check out our 'Tricks for Importing Large Quantities of Tasks with Onfleet' blog post