Header cleanup
Shopify CSV Invalid Header Fixer
Find invalid Shopify product CSV headers, fix common spacing and casing mistakes, and export a cleaner header row.
Local browser scanSafe fixes onlyShopify-focused checks
Browser-side scan
Drop a Shopify product CSV
No CSV selected
No CSV selectedUpload a Shopify product CSV to start the browser-side scan.
Private by default. Your catalog data stays in this browser session. The export applies only safe deterministic fixes and leaves manual-review items in the findings list.
Shopify product imports depend on exact header names. This page highlights header whitespace, casing drift, aliases, unknown columns, and missing required fields before row data is reviewed.
Import blockers
Common causes this scan checks
- Header cells include leading or trailing spaces that are hard to see.
- Column names use supplier wording instead of Shopify product CSV names.
- Casing and punctuation changed during manual spreadsheet edits.
- The file has duplicate, blank, or unknown headers mixed with real product data.
Workflow
How to use the cleaned CSV
- Scan the first row and review every invalid or unknown header.
- Apply safe header trimming and common alias normalization.
- Map or remove unknown supplier columns manually before import.
- Rerun validation after header cleanup to reveal row-level issues.
Auto-fix policy
What the export can safely change
- Trim leading and trailing header whitespace.
- Correct common case and spacing variations.
- Mark unknown columns for removal or mapping.
- Preserve cell data while replacing the header row.
FAQ
Shopify CSV questions
Why are Shopify CSV headers so strict?
The importer maps product data by header name. Small differences can prevent Shopify from reading the intended column.
Will the fixer delete unknown columns?
No. Unknown columns are flagged so you can decide whether to map, remove, or keep them outside the import.
Can header fixes change product data?
Safe header fixes only adjust the column names. Product row values are preserved unless you apply separate row-level fixes.