If your locations are showing up in the wrong place on the map, the issue is almost always with geocoding. Here's how to diagnose and fix it.

When you add a location, StoreRocket converts your street address into latitude/longitude coordinates using Google's Geocoding API. This is how the map knows where to place the pin. If the address is ambiguous or incorrect, the pin can end up in the wrong spot.

The address might be ambiguous. "Portland" exists in both Oregon and Maine. "Springfield" exists in dozens of states.

Fix: Make sure the full address includes city, state/province, AND country. The more specific the address, the more accurate the geocoding.

This means geocoding failed completely and the coordinates defaulted to 0,0.

Fix: Edit the location, check the address for typos or missing information, and save. StoreRocket will re-geocode with the corrected address. If it still fails, manually enter the correct latitude and longitude (you can find these by right-clicking on Google Maps and copying the coordinates).

If you sync from Google Sheets regularly and notice locations moving slightly each time, it's because each sync triggers a re-geocode. Minor variations in how Google interprets the address can cause small shifts.

Fix: If you have precise coordinates, add Latitude and Longitude columns to your spreadsheet. When these are provided, StoreRocket uses them directly instead of geocoding the address.

If a batch import placed locations all over the map seemingly at random, the address columns in your CSV might be misaligned. For example, city data ending up in the state column.

Fix: Download the import template and make sure your data lines up with the correct columns. Pay special attention to Address Line 1, City, State, Postcode, and Country.

If geocoding can't get the right location, you can always set coordinates manually:

These manual coordinates won't be overwritten unless you change the address and trigger a re-geocode.

Questions? Hit us up on live chat.