Your stockist list changes: a store moves, a dealer closes, three new ones sign up. Keep editing the spreadsheet and import it again. Nearmio works out which rows it already knows.
How a row is matched
Each row is matched to an existing location by:
external_id, if the row has one. Use this if you have it — a store number, a CRM id, anything stable. The match then survives address corrections.- Otherwise, the address — street, city, region, postcode and country, compared after trimming and case-folding.
A matched row shows as Update in the preview; an unmatched one as New. Two rows in the same file that match each other are reported as Duplicate in file, and only the first is used.
What an update changes
- Filled-in cells overwrite what is stored.
- Empty cells are left alone. A blank
phonedoes not wipe a phone number you added in the app. To clear a field, edit the location by hand. - The pin is re-placed only if the address changed. If you corrected a pin by dragging it, and the row's address is the same as before, the pin stays exactly where you put it.
- Explicit
lat/lngin the file always win, address change or not.
What an import never does
It never deletes. A store that is gone from your spreadsheet stays in Nearmio until you delete it in the app — select it on Locations and press Delete, or tick several rows and delete them together.
Check it worked
In the preview, the updates count should roughly match the rows you changed, and new the rows you added. If everything shows as New when you expected updates, the addresses were written differently this time (a reformatted postcode, "St" for "Street"). Adding an external_id column fixes that for good.