Shopify product CSV guide

Invalid headers: compare exact names before deleting any column

Shopify’s current product CSV headings are case-sensitive, and import intent changes which identifiers are required. But an unfamiliar heading is not automatically invalid: market columns, product metafields, and one documented collection column require more careful classification.

Check the header row without uploading it. Run the local checker, select “Create new products” or “Update existing products,” and review each finding before editing.

Start with import intent

For a CSV that creates new products, Shopify’s current guidance identifies Title as required. When expressed variant data needs rows grouped into a product, URL handle is also important to that relationship. For a CSV used to update products, current guidance requires both Title and URL handle. The handle identifies which product the update addresses, so inventing, lowercasing, or replacing it automatically could target the wrong record. CSV SafeCheck reports the requirement but cannot confirm which handles already exist in your store or what an import will overwrite.

Check spelling, capitalization, and whitespace

Compare each static heading character for character with Shopify’s current product CSV table. Capitalization matters. Accidental spaces before or after a known heading can also make the header fail to match. CSV SafeCheck treats trimming edge whitespace from a header as its only launch safe auto-fix because the intended heading remains visible and no product cell value changes. A differently named field is not silently renamed.

Shopify also documents backward compatibility for older product CSV header names. That means a legacy export is not necessarily invalid simply because it does not resemble the newest table. This free launch checks a narrow current profile; it does not claim to classify every historical export or app-specific extension.

Do not reject every dynamic column

Some columns are dynamic rather than members of one fixed list. Product metafield headings can encode a definition, and market-related columns can depend on configuration. Shopify’s current product CSV guidance supports product metafields but says importing variant metafields with the product CSV is not supported. CSV SafeCheck flags a variant-metafield heading for review; it does not treat every product-metafield or market heading as invalid.

Collection is another documented exception: Shopify describes it as a column that can be added to an import file even though it is not part of the ordinary product export structure. A validator that rejects every extra header would create a false positive here. Keep the distinction between a misspelled known heading, a supported dynamic heading, an explicitly unsupported variant-metafield pattern, and a column whose meaning remains unverified.

A safe header repair workflow

Keep an untouched source copy and choose the correct create/update mode.
Compare the first row with Shopify’s current table and with the system that produced the export.
Trim only obvious edge whitespace. Correct case or spelling only when you can map the source field unambiguously.
Do not delete dynamic product metafield, market, or collection columns merely because a basic template lacks them.
Do not place variant metafield data into the product CSV based on a guessed heading; follow Shopify’s current supported workflow.
Re-run preflight and review a Shopify import preview against a backup before confirming an update.

Scope boundary: a header can be spelled correctly while its values are wrong for a particular store. CSV SafeCheck cannot validate taxonomy availability, market configuration, custom services, reference targets, or overwrite consequences without store context.

Primary sources

Retrieved 26 August 2026. Recheck the live Shopify guidance before a consequential import because schemas and supported workflows can change.