What goes in each import column

A column by column reference for the import file: which values are accepted, which are optional, and the few that behave differently than they look.

Every column in the import template is optional except name, and column order does not matter. Most are self-explanatory. This page is for the ones that are not.

Name and description

  • name: the only required column. Rows without one are skipped.

  • info: free description text, shown with the location.

  • imageUrl: a public link to a photo. We use the address as it is rather than copying the file, so the image has to stay reachable there.

Where the location sits

  • address, city, province, zipCode, country: put the whole address in address, or split it across the five. Both work. country takes either a full name or a two-letter code, so United Kingdom and GB are equally fine.

  • lat and lon: optional. Leave them empty and we geocode from the address, which is why a file of 2000 uncoded rows can take an hour. A decimal comma is not accepted: 51,5034 fails as an invalid coordinate, so use a dot instead.

Addresses we cannot resolve get a placeholder position near Lviv. A cluster of pins in Ukraine therefore means those addresses failed to geocode, not that the import broke. Fixing those.

Opening hours

  • hours_mon to hours_sun: one column per day, as 09:00-17:00 or closed.

  • hours_timezone: an IANA name in Region/City form, like Australia/Sydney. Abbreviations such as AEST and offsets such as GMT+10 are not recognised, and a location carrying one shows as closed to shoppers around the clock. Empty is read as UTC.

Hours too irregular for a grid go in a column of their own mapped to openingHours, never alongside the day columns, which overwrite it. More on both formats.

Contact and social

phone, fax, email and website take plain values. facebook, google, linkedin, instagram and twitter each take the full profile URL rather than a handle.

Organising your locations

  • tags and groups: both accept several values separated by a semicolon, and anything new is created for you. They differ in job: tags are the filters shoppers narrow the map with, groups are the headings your locations sit under in the list.

  • marker: the name of a marker style you already created. An unknown name falls back to the default pin.

  • active: 1 or 0, also true and false, or yes and no. Missing means visible.

  • priority: a sort weight that does nothing by itself. It only changes anything once the locations list is set to sort by priority in Settings.

What to do next

  • Tags earn their keep once they are grouped into categories. How that works.

  • Columns we do not recognise are simply left unassigned in the preview, so extra columns in your own spreadsheet do no harm.

  • Custom fields are the exception: create them in the app before importing, or their columns have nothing to land in.

Stuck on any of this? Open the chat in the bottom right corner of the app and we will help you set it up.

Did this answer your question?
😞
😐
😁