Quick Rule Summary · Updated November 2026

A valid 2026 Shopify Product CSV must be UTF-8 comma-separated with an exact Row-1 header: single-SKU items need URL handle, Title, Price, and Status, while multi-variant items repeat the exact URL handle on child rows with Title left blank and Option1 value filled.

01 / INTERACTIVE STARTER BUILDERPick only the columns your import actually needs.

Shopify’s full sample file spans 61 columns, including dozens of optional unit-pricing and Google Shopping fields. Choose a store scenario below—or toggle individual field packs—to preview and download a clean UTF-8 starter CSV:

1. Choose a workflow preset 16 canonical columns
2. Toggle optional column packs
Scroll table horizontally to inspect all selected columns →
Open official sample in Workspace ↗

Delete the invented QA sample rows before importing into a live store. Save edits as UTF-8 comma-separated (.csv)—never semicolon-delimited or .xlsx.

02 / MULTI-VARIANT STRUCTUREWhy Row 3 leaves Title and Description blank.

The #1 formatting mistake in hand-built Shopify CSVs is repeating Title, Description, Vendor, and Tags on every size or color row. Here is how Shopify groups variants:

  1. Shared URL handle ties variants together: Every size/color of the same item must share the exact same lowercase URL handle (for example, qa-merino-crew-sweater) on consecutive rows.
  2. Product-level fields belong on the first row only: Put Title, Description, Vendor, Product category, Type, Tags, and Status on the product’s first row, and leave those cells completely blank on child variant rows underneath.
  3. Option names once, option values every row: Fill Option1 name (Size) on the first row only, then fill Option1 value (Small, Medium, Large), SKU, and Price on every variant row.
  4. Single-variant items still need Default Title: When a file mixes multi-variant apparel and single-SKU accessories, give single-SKU rows Option1 name = Title and Option1 value = Default Title.

03 / NEW VS. LEGACY HEADER DICTIONARYSearch canonical 2024+ names and older aliases.

Shopify updated its product CSV headers (for example, Handle → URL handle and Variant Price → Price) while keeping backward compatibility for older exports. Search below to verify what any column means—and never include both the old and new header in the same file:

Canonical Shopify product CSV headers, legacy aliases, requirement status, and multi-row rules
Canonical header Legacy alias Status Formatting & multi-variant rule

04 / PREFLIGHT BEFORE IMPORTCatch spreadsheet traps in your browser first.

Even when you start from a clean template, Excel, Numbers, and supplier VLOOKUPs silently introduce errors upon saving. Before uploading to Shopify Admin:

  1. Check barcode scientific notation & leading zeros: Spreadsheets turn 0012345678905 into 1.23457E+10 unless formatted as plain text.
  2. Strip currency symbols and accidental zero prices: Ensure Price contains plain numbers (24.00, not $24.00) and Compare-at price is blank rather than 0.00 when not on sale (see the price preflight guide).
  3. Run a local preflight in Row & Record: Drop your saved UTF-8 CSV into our in-browser workspace (up to 10 MB / 50,000 rows, zero server upload) or use the Row & Record Chrome Extension ↗ for instant header and price checks.

Keep a full store backup before updating existing products. Exporting a partial 6-column update CSV without dependent option columns or blanking mapped fields can overwrite live store values—always test 2–3 products in Shopify’s own import preview first.

Common questions.

Does Shopify require all 61 columns in a product CSV?

No. For creating simple new products, only Title is strictly required by Shopify, though including URL handle, Description, Status, SKU, and Price is strongly recommended. When updating existing products or importing variants, include URL handle, Title, and all dependent option columns so existing variant data is not lost.

Should I use URL handle or Handle, and Price or Variant Price?

Shopify’s current canonical template uses URL handle, Description, Price, SKU, and Product image URL, while still accepting legacy names like Handle, Body (HTML), Variant Price, Variant SKU, and Image Src. Pick one convention per file—never put both Handle and URL handle in the same CSV.

Why did Shopify create 3 separate products instead of 3 sizes of 1 product?

Every variant of the same product must share the exact same URL handle on consecutive rows, with Title and Description filled only on the first row of that product and Option1 value (such as Small, Medium, Large) filled on each row.

Why does Shopify reject my CSV saved from Excel?

Excel often saves regional CSVs using semicolons (;) instead of commas, smart curly quotes, or Windows-1252 encoding instead of UTF-8. Always choose CSV UTF-8 (Comma delimited) (.csv) and run a quick header check in Row & Record before importing.

RELATED CSV TOOLSNext Shopify CSV builders & validators

Filled out your template? Preflight it locally.

Verify headers, duplicate handles, and invalid prices in your browser—nothing leaves your device.

Open CSV Preflight Workspace ↗

Platform schema verified November 2026 against Shopify’s 61-column product CSV specification and Row & Record’s local preflight rules.

Shopify product CSV column referenceImporting products with a CSV fileRow & Record Chrome Extension ↗