Merchant operations / CSV safety / Free local tool

Before importing a product CSV, check what might go wrong.

A spreadsheet can look tidy while an update clears supplier names, misses variant identities, or creates duplicate option combinations. Shopify's native CSV importer has precise overwrite semantics. This guide explains them, then offers a small browser-only preflight. Start with Shopify's free built-in export and small-sample test; use this checker only as an extra set of eyes.

Who this is for: Shopify merchants and catalog managers preparing a product-update CSV. Status: free experimental checker, not a Shopify App, live store connection, import simulator, certified validator or client-tested production release.

Four failures to check before a bulk import

RiskWhat Shopify documentsPractical check
Blank included fieldsWith overwriting enabled, an included non-required column with blank cells can replace existing values with blanks. Omitted non-required columns keep existing values.Remove columns you are not updating; verify intentional blanks per row before import.
Missing variant dependenciesIncluding variant-specific data without the relevant option-name/value columns can delete existing variant data.Export a current sample and keep the full identity columns needed for each modified variant.
Duplicate optionsTwo variants under one product cannot resolve to the same option combination.Compare option values by product handle; review repeated combinations, including size/color pairs.
Changed variant identityChanging option values can create replacement variant IDs and disrupt integrations that refer to old IDs.Check dependencies and test a single product in a safe, reversible workflow first.

These rules are documented in the official Shopify CSV guide, import workflow, and troubleshooting page. The exact import behavior depends on the file, catalog state and selected settings; this page does not infer your store's outcome.

Free Shopify CSV preflight — no account, no upload

Find structural review flags in a CSV

Choose a local CSV or paste its text. It stays in this browser tab: the checker does not send cell contents to Moruneva, store a copy, or change any Shopify data. The report excludes handles, SKUs and cell values; it shows record numbers and field names only.

Load the fictional example to see repeat-option and blank-column flags.

Limits: 5,000 records, 60 columns, 900,000 characters. Supports ordinary comma-delimited UTF-8 CSV, escaped quotes and embedded newlines. The record number counts the CSV header as record 1; quoted multiline fields may span physical lines. Checks are deliberately conservative and can produce false positives on image-only or intentionally blank rows. No external import simulation.

Why a repeated handle is not automatically a duplicate product

One Shopify product can contain many variant or image rows sharing a Handle. Repeated handles are expected. The checker therefore looks at combinations of option values within the same handle when there is variant data. It flags a repeated combination for review rather than declaring that Shopify will remove a variant. The same SKU under different handles is also only a review signal; it is not proof of a broken product.

For example, a fictional tea set has two SKU rows under the same handle, both using Size = Small. The preflight should identify both involved record numbers without revealing their SKU values. A blank Vendor cell on the second row gets its own warning. This is a sample invented solely for testing, not a merchant's data.

Preparing for Black Friday 2026? See our dedicated promotion-price and catalog change checklist for the differences between automatic discounts and sale-price edits, the dangers of wide CSV restores, and honest future-feature research.

What to do when the checker finds a risk

  1. Export a fresh backup from Shopify and keep it unchanged. Do not rely only on a supplier file.
  2. Use Shopify's native importer first: inspect the exact column names and Overwrite products with matching handles setting before uploading anything.
  3. Minimize the update file: retain the required handle and variant identity columns; remove optional columns you do not intend to update. Never infer that deleting a column from an unknown import format is harmless.
  4. Investigate flagged records: open the CSV in your own spreadsheet and inspect the specific row, field, option combination and intended blank. The local report intentionally omits identifiers, so you remain in control of private data.
  5. Test one product or small batch, inspect live option count, prices and inventory, and only then scale. Stop and restore if the results differ.
Important boundary: a static CSV check cannot know your current live Shopify catalog, external app references, imported images, currency configuration, app-specific metafields, or the true effect of a checked overwriting option. A clean result does not prove a safe import; this tool cannot approve deletion, overwrites, inventory changes, or variant replacement.

Why this is a real problem — and why free methods still matter

In 2026, independent merchant discussions described broken product-option structures and lost variants after CSV imports. These reports establish that the work is fragile; they do not establish that any seller is looking to pay Moruneva. See the Shopify merchant discussion and a WooCommerce store owner's variation-loss report. The WooCommerce case is a different platform with different importer rules, so do not apply this Shopify-specific checklist to WooCommerce unchanged.

Strong free alternatives already exist: Shopify's official exporter and importer, a spreadsheet filter for blank columns, and a key/option-pair duplicate check. For comparing a before/after export rather than preflighting one Shopify CSV, try Moruneva's free two-tab change preview. Neither of our experimental tools is a substitute for an actual test import and independent verification.

Help improve this tool with an actual task

If you prepare product import files, we'd value one concrete answer: Which check would have prevented your last catalog mistake that Shopify's native import preview or your spreadsheet did not catch? Please send the general issue and an anonymized field list, never a customer export or credentials, to hello@moruneva.com. We record independent first use and repeat use separately from article visits and automated tests.

Source notes: Shopify Help: CSV files; common import issues; importing products. Updated November 12, 2026.