Shopify CSV Prices That Look Right but Still Fail: A Pre-Import Checklist

A Shopify CSV can look perfectly normal in a spreadsheet and still fail, skip values, or change the wrong variants after import. Price columns are a common reason: spreadsheet locale settings, currency symbols, thousands separators, and variant-row matching can all change what Shopify receives.

Here is a practical pre-import checklist.

1. Start from a Shopify export

Use a recent product export as your baseline. Keep the original file untouched, then make a working copy for edits. Confirm that the file uses Shopify's expected headers, especially Handle, Option1 Value, Variant SKU, Variant Price, and, when relevant, Variant Compare At Price.

Do not rebuild a large catalog from a blank spreadsheet unless you have a strong reason. The export preserves the row structure that Shopify uses to group products and variants.

2. Make the price format unambiguous

Before saving the CSV, check that:

• prices use a decimal point, not a locale-specific decimal comma;

• currency symbols are not embedded in the cell value;

• thousands separators are not left in values such as 1,299.00 unless your cleaning step removes them safely;

• empty cells are intentional, especially on continuation rows;

• compare-at prices are reviewed together with the selling price.

If the spreadsheet displays a value as currency, inspect the raw cell value before exporting. A display format can hide characters that end up in the CSV.

3. Verify variant identity before changing prices

A correct price on the wrong variant is still a bad import. For each product, check that:

1. every variant row keeps the same Handle;

2. option names and values stay paired;

3. SKU or another stable identifier matches the baseline export;

4. the update file does not accidentally include blank columns that could overwrite existing data;

5. the number of variant rows is unchanged unless you intentionally add or remove variants.

For a large catalog, test one representative product with multiple options before preparing the full file.

4. Scan the working copy

Run the working CSV through a local checker and review critical findings before exporting a cleaned copy. Pay special attention to malformed prices, unexpected headers, encoding warnings, duplicate handles, and file-size warnings. Treat the report as a preflight review; it cannot know whether a particular sale price is commercially correct.

For a quick browser-side check, use the Shopify CSV price format fixer to review price cells and export a cleaned copy when the correction is unambiguous.

5. Import a tiny batch and compare

Import a small set of products first. After Shopify finishes, compare the result against the baseline:

• selling price and compare-at price;

• variant SKU and option values;

• inventory policy and availability;

• product count and handle count.

If the result differs from the plan, stop before uploading the full catalog. Keep the original export and the tested CSV so you can explain exactly what changed.

Final caution

A CSV preflight does not replace Shopify's importer, change market-specific pricing, or guarantee that a theme or app will display prices as expected. It helps narrow down file-level risks so the next import is easier to verify.