SEVEN-STEP CHECKLIST · REVIEWED 16 SEP 2026

Validate the product CSV before Shopify changes the store.

A spreadsheet that opens normally can still contain import blockers or destructive blanks. Data Preflight lets you check a Shopify product CSV in your browser without uploading the file. Use this checklist to separate file structure, Shopify rules, and risks that still need checking inside your store.

Preserve a rollback copyNever make the only export your working file.
Match intent to fieldsCreating, updating, and adding variants need different data.
Treat blanks as changesIncluded blank columns can matter during overwrite.
Test before scaleUse a representative subset before the full import.

WHAT VALIDATION MEANS

Passing a CSV parser is only the first layer.

File validation checks encoding, delimiters, quotes, row width, and headers. Shopify validation checks product identity, variant relationships, accepted values, and dependent fields.

A safe release adds a third layer: backup, overwrite review, representative testing, and confirmation inside the target store. No local tool can replace that final store-specific review.

VALIDATION CHECKLIST

Seven checks before a production import.

01
File format

Confirm CSV UTF-8 and comma-separated fields

Shopify requires UTF-8. Confirm the export uses commas between fields and that quotes, commas, and line breaks inside values are encoded correctly.

Evidence: Open a copy in a text editor when spreadsheet software hides encoding or quoting problems.

02
Header row

Compare headings with a current Shopify export

The first row must contain recognized product CSV headings. Exact names and related columns matter, especially when an older template has been reused.

Evidence: Export a small current product set or download Shopify’s sample instead of relying on a template saved months ago.

03
Product identity

Validate Title and URL handle by import intent

A new product needs a Title. Variant rows and product updates rely on the URL handle to connect each row to the intended product.

Evidence: Group rows by handle and flag blank identity fields before checking prices or inventory.

04
Dependencies

Check variant fields as a group

Variant SKU, weight, inventory, and fulfillment values can depend on option and related columns. A locally valid cell can still be incomplete in context.

Evidence: Verify Option1 name and value whenever variant-specific data is present, then confirm option combinations are unique.

05
Overwrite risk

Review every included column before overwriting

When matching handles are overwritten, blank values in included non-required columns can replace existing product values with blanks.

Evidence: Remove unintended columns, inspect blank cells, and keep an untouched product export for rollback.

06
External resources

Test image URLs without a login

Product image URLs must be publicly reachable during import. A syntactically valid URL can still fail because the host blocks access or the file no longer exists.

Evidence: Open each representative direct image URL in a private browser window before the full import.

07
Production safety

Import a representative subset first

Product imports cannot be canceled after they start. A small test should include a simple product, a multi-variant product, and an image row.

Evidence: Review Shopify’s import preview and confirmation results before scaling to the complete file.

LOCAL CHECK VS STORE CHECK

Know which questions need Shopify.

Useful before upload
  • UTF-8, delimiter, quotes, and row width
  • Empty, duplicate, or suspicious headers
  • Common handle, price, inventory, and variant conflicts
  • A written list of unresolved decisions
Confirm inside Shopify
  • Current store fields, locations, taxonomy, and metafields
  • Whether external images can be fetched
  • The exact effect of matching handles and overwrite settings
  • Preview counts and the imported sample products

A clear local result is a risk-reduction step, not a promise that every row will import into every store.

PRACTICAL RELEASE SEQUENCE

Move from spreadsheet to store without one big leap.

  1. 01
    Export and freeze the source

    Keep an untouched product export and edit a copy.

  2. 02
    Run structural and field checks

    Fix blockers before reviewing business decisions.

  3. 03
    Review included columns and blanks

    Make every overwrite intentional.

  4. 04
    Build a representative test file

    Include the riskiest product and variant patterns.

  5. 05
    Review Shopify’s preview and result

    Scale only after counts and sample records are correct.

中文速查

CSV 能打开,不代表适合直接导入。

先保存未修改的 Shopify 商品导出,再检查 UTF-8、首行字段、 Handle、变体组合以及相关字段依赖。覆盖现有商品前,应逐列确认空值是否真的要清空线上内容。

免费工具可以在浏览器本地发现常见结构和字段风险,但图片可访问性、店铺专属配置、 覆盖影响和最终预览仍需在 Shopify 内确认。

Data Preflight 的免费扫描无需上传 CSV,也无需连接店铺;文件留在当前设备。 扫描结果只是导入前的第一道检查,不等于 Shopify 的最终导入结果。

PRIMARY SOURCES

Check the current rule against Shopify documentation.

Product CSV format and columns Import workflow and overwrite behavior Common product CSV import problems Shopify CSV file guidance

NEED A SECOND PAIR OF EYES?

Start with a bounded $49 risk review.

One file up to 10,000 rows receives an annotated issue report and prioritized repair plan. Cleanup is quoted separately, so the first purchase stays small and clear.

Request the $49 review