Shopify CSV import not working: isolate file, mapping and product errors
Use the actual error and a minimal sample to distinguish CSV syntax problems from unsupported product operations.
Preserve the error and the original file
If a Shopify CSV import is not working, save the exact error message and keep the file you submitted unchanged. Determine whether the problem happens while reading the file, mapping fields or creating product records. Those stages need different fixes. Do not repeatedly resave the only source copy or reimport the full catalog while experimenting. A spreadsheet and plain-text inspection can diagnose many simple CSV issues without a converter purchase. Create a small representative test copy containing the header, a normal row and a row that reproduces the failure.
Check delimiter, encoding and quoting
Inspect whether the file is comma-separated or uses another delimiter. Shopify requires each column to be separated by a comma, so a semicolon-delimited supplier export must be converted to comma-separated CSV before import. Values containing commas, quotation marks or line breaks need correct CSV quoting, and Shopify notes that illegal-quoting errors can also come from curly quotes that a spreadsheet inserted in place of straight quotes. A spreadsheet can show a file neatly even when the receiving importer interprets its delimiter differently. Shopify requires UTF-8 encoding and a first line that holds the column headers, so resave the file as UTF-8 and remove any report titles above the header row. Use an import preview or a CSV-aware reader instead of counting visible commas, because quoted punctuation belongs inside a field.
Check values independently from syntax
If the file parses but rows are rejected, compare the required headers and source-to-destination mapping. Check for blank titles, missing identifiers, unsupported price notation and unexpected whitespace. Treat SKU and barcode as text so leading zeros remain part of the stored string. Verify that price cells contain intended numeric values rather than currency symbols or locale-dependent display text. Correct the supplier source or mapping from evidence, then recreate the test file. A syntactically valid CSV can still contain invalid product values, so solving quoting alone may not resolve a row-level error.
Investigate duplicate and relationship errors
Compare repeated SKUs and handles rather than deleting every repeat automatically; Shopify's "Validation failed: options are not unique" error can mean that two different products in the file share one handle. Identical rows, conflicting product details and different strings that form the same handle are separate conditions. A keep-first rule can deliberately discard later information, so inspect the affected rows before selecting it. Check whether the file tries to update products already present or describes size/color variants, images or inventory beyond the chosen converter's scope. A new-simple-product tool cannot repair those relationships by renaming a column. Use a workflow that explicitly supports the catalog operation you are trying to perform.
Reconcile the retry rather than just its success message
After correction, test the small file and check the actual product records. Compare expected products with the records actually created and any reported line errors. If Rowmoss prepared the file, reconcile its exported, skipped and merged counts separately from Shopify's outcome. A shorter output is only explained when every omitted row has a reason. Do not import a previously successful subset again without checking what already exists; unless you select Overwrite products with matching handles, Shopify skips rows whose handle is already in the store and reports them as ignored lines. Keep a correction log with source row numbers and the final file used. If a conversion preview lists only some issues, inspect its total issue count and any complete skipped-row download before concluding that later rows are clean. A paid unlock does not fix errors by itself.
Use the line number to locate a parsed record
Keep Shopify's exact error text with the submitted file version. A quoted description can contain a line break, so a text editor's visual line number and the logical product row may not match your spreadsheet's expectation. Inspect the surrounding header and record with a CSV-aware reader before deleting anything. For an illegal-quoting error, check straight quote boundaries and doubled internal quotes as well as accidental smart quotes. Recreate a minimal file that still reproduces the issue, but do not remove unrelated fields from the only copy of the original. Preserve evidence of the failure before generating a corrected version.
Separate Rowmoss validation from Shopify errors
A Rowmoss preview error is raised before Shopify sees the file. Check the mapped fields, source row and supported limits there first. Even an unmapped description cell must fit Rowmoss's 1,000-character limit; leaving it unmapped does not bypass input validation. Shopify errors after upload need Shopify's own field and relationship rules instead. When retrying, keep a table of intended products, those already created, rows intentionally skipped and rows still unresolved. Reconcile Rowmoss's merged or skipped counts with its output, then compare that output with the store. A conversion success and a correct store import are separate checkpoints.
Where Rowmoss fits
Rowmoss validates a narrow new-product mapping; it cannot repair variant, image, inventory or existing-product update workflows. Input must be UTF-8 or Windows-1252 comma/semicolon CSV, at most 1 MiB, 2,000 rows, 30 columns and 1,000 characters per cell. XLS, XLSX, TSV, UTF-16, synchronization and saved supplier templates are unsupported. Explicitly choose dot-decimal or European prices; no currency conversion occurs. Free anonymous review shows twenty transformed rows, twenty issues, total counts and the full skipped-row list. Correct source errors or explicitly export valid rows before unlocking. Full CSV needs sign-in and a credit; another successfully unlocked revision uses another credit.
Preview your supplier CSV free Pricing details
Written by Zijian Xiao. Check the source, review the import details, and verify the resulting Shopify product records.