Fix addresses that weren't found
Spot and fix Not Found stops in Upper after an import. Open the stop, correct the address, and let Upper re-check it so the stop is ready to route.
When you import stops into Upper, every address is checked against a map. Addresses that can't be located are marked Not Found — and a Not Found stop can't be routed or sent to a driver until you fix it. This guide shows you how to find Not Found stops after an import and correct them.
This article uses Upper's default labels (driver, delivery). Your workspace may be set up to show Technician or Service instead — the features are the same.
Why it matters
A Not Found stop is a stuck stop: it isn't placed on the map, so the route can't include it. Catching and fixing these right after an import is the quickest way to a clean, routable list.
Find your Not Found stops
After an import, a single red address-validation icon appears above the stops list. Click it to see every flagged stop grouped by status — Verified, Needs Review, Not Found, and Duplicate. Each row in the stops list also shows its status in the Review column, so you can scan for Not Found at a glance.
Fix a Not Found stop
Open the stop
In the stops list, open the Action (…) menu for the Not Found stop and choose Edit Stop. The stop opens in a side panel on the Basic Info tab.
Correct the address
In the Address field, fix what's keeping the address from being located:
- Correct a typo in the street name, city, or zip/postal code.
- Add any missing parts — the full city, the state or province, the zip or postal code.
- Spell out abbreviations that may not be recognized (for example, "St" → "Street", "Ave" → "Avenue").
Save the stop
Click Done to save. Upper re-checks the updated address and assigns it a new validation status.
For a destination that has no standard street address — a job site, a new build, or a remote location — you can enter it as GPS coordinates in your import file instead, either as a bracketed latitude,longitude value in a single cell or as separate latitude and longitude columns. Keep your file consistent: if other rows use a single full-address cell, don't mix in separate columns, and vice versa.
Common causes of Not Found
| Cause | What to do |
|---|---|
| Typo in the street name | Correct the spelling |
| Missing city, state, or zip code | Add the full address |
| Abbreviations that aren't recognized | Spell out the full street name |
| Address in an unsupported region | Use GPS coordinates in your import file |
| New build or unlisted address | Use GPS coordinates in your import file |
Troubleshooting
Related
Download a sample import file
Download Upper's sample import file from the Add Stops tab. It includes every supported column with example data — the fastest way to format your stops.
Handle import errors and validation issues
After import, Upper validates every address and flags issues you can review by status. Filter, check, and fix Needs Review, Not Found, and Duplicate stops.