Uploaded a zipcode CSV but the codes won’t validate on the storefront — or accented characters (å, ä, ö) turned into “?”? In almost every case the issue is in the CSV file itself, not the app. Here’s how to clean it up.
- Check for extra spaces. Open your CSV and make sure the zipcode column contains only the codes — no leading or trailing spaces. Stray spaces are the most common reason imported codes don’t match. Remove them and re-upload under Settings → Create Zipcode Rule → CSV.
- Check for stray text in the zipcode field. Make sure nothing but the postal code lives in that column (no labels, notes, or extra characters mixed in). Clean it out and re-upload.
- While you’re at it, confirm the column headers match the sample file exactly:
zipcode, estimated_day, exchange_and_return, cash_on_delivery. Renamed or reordered headers are a common reason a file won’t import cleanly.
- While you’re at it, confirm the column headers match the sample file exactly:
- Fix garbled special characters using Google Sheets. If characters like å, ä, or ö are showing as “?”, that’s an encoding problem in the file. The reliable fix:
- Open the CSV in Google Sheets.
- Confirm every character displays correctly (no “?” marks).
- Export a fresh copy from Google Sheets → File → Download → Comma-separated values (.csv).
- Re-upload that downloaded file.
Why Google Sheets? It exports clean UTF-8 and strips the stray formatting that Excel and some editors leave behind — so it fixes both the encoding and any hidden spaces in one step. We recommend preparing all your zipcode CSVs this way going forward.
Still stuck? Send us the CSV file you’re uploading and we’ll take a look — reach out at support.