Typing 200 stockists into a form one by one is nobody's idea of an afternoon. Almost every brand already has them in a spreadsheet — from a sales rep, an ERP export or a distributor list — so the fastest way into a store locator is a CSV. The import is easy. Getting every row onto the map, in the right place, is where most locators go wrong.

The columns that matter

name, address, city, state, zip, country, phone, website, tags
Corner Coffee Co, 12 King St, Toronto, ON, M5H 1A1, CA, +1 416 555 0101, cornercoffee.ca, Café
Bean There, 401 Main St, Vancouver, BC, V6A 2T7, CA, , , Café;Stockist
  • name is the only column you can't skip.
  • An address or coordinates. A row with neither can't go on a map.
  • Address split into columns (street, city, state, zip, country) geocodes far more reliably than one long address cell.
  • Country as a code (CA, US, GB) avoids "Georgia the state" vs "Georgia the country".
  • tags become filters on the locator — "Café", "Stockist", "Showroom".

Opening hours in a spreadsheet

The easiest format is one column per day:

monday       tuesday      ...  saturday   sunday
09:00-17:00  09:00-17:00       10:00-14:00  closed

Split days work too ("9-12, 13-18"), and so does "24h". With hours per day, the locator can show an Open now label in each store's own time zone.

Why rows go missing or land in the wrong place

  • Silent skips. A row without a name, or without an address, is dropped and nobody is told. Always look at the import summary, not just the map.
  • Approximate matches. When a geocoder can't find the exact address, it often returns the centre of the city or postcode. The pin is on the map, just in the wrong place, which is worse than no pin.
  • Re-import duplicates. Importing the updated sheet again doubles every store. Use a stable id column so a second import updates rows instead of adding new ones.
  • Wrong delimiter. Spreadsheets saved in some regions use semicolons instead of commas, and every row ends up in one column.

A clean import, step by step

  1. Add an id column with your own store code, even if it's just 1, 2, 3.
  2. Split the address into street, city, state, zip and country.
  3. If you already know latitude and longitude for some stores, add lat and lng columns: those pins are placed exactly and skip geocoding.
  4. Import, then read the list of skipped rows and approximate matches before you publish.
  5. When something changes, export, edit in Excel or Google Sheets, and import again.

Importing with Kerbmap

Kerbmap matches columns by name — "postcode", "zip" and "postal code" all work — and detects commas, semicolons or tabs. Before anything is saved, the preview shows how many stores will be added or updated and lists every skipped row with the reason ("no name", "no address and no coordinates"). Rows with an id, or the same name, street and postcode, update in place, so exporting and re-importing never duplicates.

After import, each address is geocoded in the background. Approximate matches and failures go toNeeds attention, where you drag the pin to the right spot. A pin you placed by hand is never moved by a later import. CSV import and export are on every plan, including Free (25 locations); Pro adds sync from Google Sheets, so the sheet you already maintain stays the source.

Next: add the locator to your store, or read why Kerbmap needs no Google Maps API key.