“0 rows updated”
Agile only reads headings that are lowercase, with no extra spaces, in the very first row. One capital letter and it ignores the column, so nothing imports.
Drop the file that failed
or
Read on your computer, never uploaded.
No file?
Try one:
Pick one to see what CSV Mapper does with it.
Also fixed here: Duplicates on re-importGarbled characters
"0 rows updated" in Agile Store Locator
Agile Store Locator shows "0 rows updated" when an import adds and updates nothing. The vendor wiki gives three causes. The tool above already has Agile Store Locator picked, so it writes the headers the importer expects.
The message
0 rows updated
Causes, most likely first
- Headers missing or capitalised. The header must be row 1, "in the smaller case without any extra spacing": title, not Title or " title".
- A bad update_id. It must be a store ID from an export made with "Export with Store IDs" switched on.
- A delimiter that is not a comma. Excel with some regional settings saves CSV with semicolons. Open the file in Google Sheets, as the wiki suggests: if everything lands in column A, the delimiter is wrong.
A header row that fails, and the fixed one
Fails: Title;Street;City;State;Zip Works: title,street,city,state,zip
Capitals and semicolons in the first line; lowercase and commas in the second.
Fix it
- Drop your file into the tool above. Agile Store Locator is already picked.
- If you are updating stores, export them from the plugin with "Export with Store IDs" switched on, answer Yes to "Do you already have stores in Agile Store Locator?" and drop that export. We copy each update_id onto the matching row.
- Download the CSV. It has lowercase headers in row 1 and comma delimiters.
- Import it on the plugin's Import/Export page.
Questions
Do Agile Store Locator headers have to be lowercase?
Yes. The wiki says the header "must be in the smaller case without any extra spacing", and it must be the first row.
Why does my import say 0 rows updated when the file looks fine?
Check the delimiter. A CSV saved by Excel with some regional settings uses semicolons, and the importer expects commas.
Related
Sources
Last checked against the vendor docs on 2 October 2026. Platforms change their importers, so check the source if something looks different.