You've got a spreadsheet full of locations and you want them in StoreRocket. Good news: this only takes a few minutes. You can either upload a CSV file directly or connect a Google Sheets spreadsheet for ongoing sync.

CSV file upload is the fastest option. You upload a file, StoreRocket processes it, and you're done. Best for one-time imports or when you're setting up your account for the first time.

Google Sheets sync connects a live spreadsheet to your project. You can sync locations back and forth whenever you want, and even enable daily auto-sync. Best for teams that manage locations in spreadsheets and want changes to flow into StoreRocket automatically.

Both methods use the same column format, so everything you learn here applies to both.

Here's every column StoreRocket recognizes. You don't need to use all of them. At minimum, you need Name and an address (either split into parts or as a full address).

You can use individual address fields OR a single Full Address column. Don't use both.

Or use a single column instead:

If you provide individual address fields, StoreRocket combines them into a full address automatically. If you use Full Address, it gets geocoded as-is.

If you leave Visible empty, the location defaults to visible.

Don't worry about these. If you leave them blank, StoreRocket geocodes the address automatically and fills in the coordinates for you. Only include them if you already have precise coordinates and want to skip geocoding.

Hours use 24-hour format only. No AM/PM. Add one column per day of the week.

For a location that's open 24 hours, use 00:00-23:59. For closed days, write Closed or leave the cell empty.

Alternative: hours templates. If you've already created reusable hours templates in Hours, you can reference them by name using the Hours ID column instead of specifying each day:

The template must already exist in your project before importing.

This is the column that causes the most import problems, so it is worth reading carefully.

Filters go in a single column called Filters. For each location, list the filter names separated by commas.

How it works:

Common mistakes:

Custom fields let you store extra data on each location (store number, manager name, product lines, anything). The column header uses the Field: prefix.

Add a separate column for each custom field. If the field doesn't exist in your project yet, StoreRocket creates it automatically during import.

The column header format must be exact: Field: followed by a space and the field name.

You can add CTA buttons (like "Order Now" or "Book Appointment") using the Button: prefix. The cell value is the URL the button links to.

Add a separate column for each button. If the button doesn't exist in your project yet, StoreRocket creates it automatically. Leave the cell empty for locations that don't need a particular button.

If your locations exclusively serve assigned zip codes (dealer networks, franchises, service areas), you can set up those territories straight from your import. Add a column called Territory Zips and list the zip codes each location serves.

How it works:

Territories are part of Search Rules, available on Galaxy and above. On other plans the column is simply ignored (your locations still import fine).

Go to the Import page and click Download the template. This gives you a pre-formatted file with all the column headers in the right order.

Open it in Excel, Google Sheets, or Numbers and fill in your location data.

When your data is ready, save the file as CSV. In most spreadsheet apps, go to File > Save As (or Download as) and pick Comma Separated Values (.csv).

Don't delete any columns from the template, even if you're not using them. Leave unused columns blank. Removing default columns can cause the import to break.

Head to your Locations list and verify everything looks right. Then check your Widget preview to see them on the map.

Locations without coordinates will be geocoded in the background. This can take a few minutes depending on how many new addresses need processing.

There's a toggle on the import page: This file is my complete list. Remove any location that is not in it.

Turn it on when the file replaces everything. Locations in the file are updated, and anything missing from the file is removed.

Leave it off when you're adding to what's already there. Nothing gets removed.

Locations that appear in the file keep everything. They keep their analytics, their filters, their custom fields and their images. StoreRocket matches your rows against the locations you already have, so a store that's in both the file and your account stays the same store, not a new one.

Matching works two ways, in this order:

Keep the StoreRocket ID column when you can. It's the only thing that still matches a location after you rename it or correct its address, which name-and-address matching can't do.

If a store leaves your file and comes back later, its click history comes back with it. You don't need to do anything for that to happen.

Google Sheets sync creates a live connection between a Google spreadsheet and your StoreRocket project. You can push locations to the sheet, pull locations from the sheet, or set up daily auto-sync.

The spreadsheet is created in StoreRocket's Google Drive and shared with you. You can also share it with team members from the setup page.

Sync to Sheets (export): Pushes your current StoreRocket locations into the spreadsheet. Go to Sync page and click the sync-to option. This overwrites whatever is in the sheet with your current StoreRocket data.

Sync from Sheets (import): Pulls locations from the spreadsheet into StoreRocket. Go to Sync page and click the sync-from option. This updates your StoreRocket locations to match the spreadsheet.

You can enable daily auto-sync from the Setup page. When enabled, StoreRocket automatically syncs from your spreadsheet once a day. This is great if your team regularly updates the spreadsheet and you want changes to flow in without manual intervention.

You can download all your locations as a CSV file at any time.

This is useful as a backup before a big import, or if you want to make bulk edits in a spreadsheet and re-import.

This is the most common import issue, and it is almost always a column naming problem.

If you turned on "This file is my complete list" and it removed more than you expected:

Re-importing brings the locations back and reattaches the analytics they had, as long as the name and address match what they were before.

Need help with your import? Message us on live chat and we'll help you sort it out.