Quick Rule Summary · Updated November 2026
Shopify’s Missing or invalid headers import error comes from three distinct Row-1 issues: an empty trailing comma/cell, duplicate column names (such as two Title columns), or unmapped vendor headers (such as Product Name instead of Title) or semicolon/UTF-16 encoding mismatches.
01 / LOCATE THE PROBLEMSeparate headers from product values.
The header row labels each column. The rows underneath contain the product data. A blank column label and an empty product-name cell are different problems: changing the label will not restore the missing value.
- Keep the exact message from Shopify’s import screen, if you have one. A finding in this workspace is our file check, not a reproduced Shopify error.
- Open a copy in your spreadsheet or a plain-text editor. Check that row 1 contains labels, each column has its intended name, and the data has the same number of cells per row.
- Save as comma-separated UTF-8 CSV. An XLSX workbook or semicolon-separated export needs to be saved in the supported format first.
Use Shopify’s current product CSV sample or a recent export from your own store as your reference. Shopify supports older column names too; do not replace your whole first row with a long header list copied from an unrelated file.
02 / CHECK THE TASKThe required columns depend on your import.
| Your task | Start by checking |
|---|---|
| Create new products | Title; also URL handle when adding variants. |
| Update existing products | URL handle and Title, plus columns required by the fields you update. |
| Update variant-related fields | Check the option-column dependencies in Shopify’s current documentation before excluding any columns. |
These are starting checks, not a complete import template. Keep fields that your products, variants or destination require. The workspace supports files up to 10 MB and 50,000 source records; it does not inspect your live store.
03 / SEE THE DIFFERENCEFour files. Three different problems.
Each download has three invented product records. Use the Create new products intent for these examples. The normal file is a reference layout, not an automatic replacement for one of your own files.
A / NORMAL HEADER
One label for each field.
Title,URL handle,Price
QA Shirt,qa-shirt,12.50The three products have names, handles and numeric prices. Review the recognized fields, then inspect the target preview.
B / EMPTY HEADER
The middle label is missing.
Title,,Price
QA Shirt,qa-shirt,12.50The workspace reports an empty header and blocks the target export. In this invented example the middle values are handles: restore URL handle in the source copy, save and reload. Check the actual meaning of your own column first.
C / DUPLICATE HEADER
Two columns claim to be Title.
Title,Title,URL handle,Price
QA Shirt,QA Shirt,qa-shirt,12.50Two source columns cannot map to the same target field. Here the title values are repeated copies. Resolve the duplicate in your source file and reload; do not delete a different column of useful data just to clear the message.
D / NO PRODUCT-NAME COLUMN
A SKU is not a product title.
SKU,URL handle,Price
QA-001,qa-shirt,12.50There is no product-name column to map to Title. Add the intended names from your source records, keep the SKU data, then reload. The tool will not invent product names for you.
All four examples are original, invented QA files. Do not import these demo products into a live store. The snippets show only the header and first product; each download contains all three records.
04 / LOAD, CHECK, COMPAREReview the corrected file before importing.
- Load your copy. Choose Choose my CSV in the workspace. Keep the original file elsewhere.
- Confirm what each column means. A supplier’s
Product Namecan map toTitleif it really contains product names. CSV templateFollow the supplier mapping example for that case. - Return structural fixes to the source file. Resolve empty headers, conflicting duplicate columns and uneven rows in the spreadsheet, save a new CSV and reload. For a genuinely absent value, use your actual source records.
- Review, then download. Follow the mapping, findings and target-preview steps. For the normal file above, the target has three product records and three fields. Check that names, handles and prices stayed under the intended labels.
- Use Shopify’s own import preview. Review the details before confirming an import. A clean result here does not check live products, every field dependency, image availability or the effects of overwriting saved data.
Keep the source-only columns. A selected target CSV contains the fields you mapped. Unmapped data stays in the original-column copy. Do not confuse “not selected for this output” with “safe to remove from a product update”.
Common questions.
Will renaming SKU to Title fix a missing-title message?
Only map a column to Title if its cells contain the product names you intend to use. Renaming an identifier does not create the missing product-name data.
Can this tool repair every Shopify header error?
No. It can suggest and confirm supported field mappings and report supported file problems. Empty labels, conflicting columns and broken row structure need deliberate correction in the source. Shopify’s own import message can depend on rules and store data this tool does not check.
What if a Title column exists but a product name is blank?
That is a missing value in a product record. Review that record against your source data. Repeating or renaming the Title header will not supply the intended name.
Do I need every column from Shopify’s sample?
No single shortened header list fits every task. Compare the current sample and the requirements for your create, update and variant fields. Keep dependent columns and verify the intended result in Shopify’s preview.
RELATED CSV TOOLSRelated Shopify CSV preflight tools
Check the first row. Keep the original.
Start with an example or review a copy of your own product CSV.
Platform references checked on 17 October 2026. Tool examples use the current Row & Record workspace.
Shopify product CSV formatCommon product CSV import problemsImport review and header matching