TroubleshootingUpdated 2026-08-25

Fix stores without map coordinates

What this article helps you do

Add map coordinates to stores that an import or sync did not geocode.

Before you start

  • You completed a CSV import or Google Sheets sync.
  • The result shows that Mapstore did not geocode one or more addresses.
  • You know if Settings has a Google Maps API key.

Step-by-step instructions

1. Understand when geocoding runs

  • CSV or Sheets import: Mapstore does bulk geocoding when Settings has a correct Google Maps API key. Without that key, Mapstore does not add coordinates to rows without lat and lng.
  • Manual store create or edit: Use the geocode action in the store form. You can also enter coordinates manually.

2. Add lat and lng to your CSV when possible

If your data has coordinates, include lat and lng columns. Mapstore skips geocoding for rows that have correct coordinates. This prevents rate limits and failures for those rows.

3. Check address quality

Geocoding fails when addresses are:

  • Missing required parts or not specified, such as “Downtown” or “Store #5”
  • Misspelled or nonstandard
  • Missing city, state, or country
  • Internal codes, not street addresses

Add the full street, city, state or region, and country to each address.

4. Add a Google Maps API key for bulk imports

If rows do not have coordinates, save and test a Google Maps API key before you run the import again:

  1. Go to Mapstore settings.
  2. Add your Google API key.
  3. Test your Google API key. See Set up a Google API key.
  4. Run the import again.

5. Handle Google Geocoding limits

  • OVER_QUERY_LIMIT / quota exceeded: The requests reached a Google rate or daily limit. Wait or increase your quota. Mapstore adds a short delay between requests.
  • REQUEST_DENIED: API key issue or Geocoding API not enabled. Fix in Google Cloud Console.
  • INVALID_REQUEST: The address format can be incorrect. Check for empty or malformed addresses.
  • ZERO_RESULTS: Google did not find the address. Add more address information or add lat/lng manually.

6. Use existing coordinates

For large imports, include lat and lng in the CSV or sheet. Coordinates prevent rate limits and errors from ambiguous addresses.

How to verify it worked

  1. Make sure that the import summary shows fewer or no geocoding failures.
  2. Make sure that the corrected stores have lat and lng in the store editor.
  3. Make sure that the store-locator map shows the corrected locations.

Troubleshooting

Issue Fix
Many addresses not geocoded Add lat and lng to your file, or save a correct Google Maps API key before importing again.
“X address(es) could not be geocoded” Add all required address parts. Add lat/lng where possible. Check the API key and quotas for Google.
OVER_QUERY_LIMIT / quota exceeded Wait and try again, or increase the Google quota. Use a smaller import or add coordinates to the CSV.
REQUEST_DENIED Enable Geocoding API. Correct the API key. See Set up a Google API key.
ZERO_RESULTS for specified rows Fix those addresses or add lat/lng manually.
Stores not on map after import Mapstore does not show stores without lat/lng on the map. Geocode them or add coordinates manually.