Your Shopify CSV import can quietly wipe data. Most merchants find out after they click Import.

I’m not guessing. Shopify’s own help page says it. So do merchants on Shopify Community, in threads that read like small disasters.

Here is what the documentation says.

A blank cell is not “no change.” It’s “clear this.”
If your file includes a column like Vendor and the cell is empty, Shopify overwrites the existing value with nothing. This applies when “Overwrite products with matching handles” is on.

Changing an option value creates a new variant.
Rename “X-Large” to “XL” and Shopify treats it as a new variant, not an edit. The old variant ID is deleted. One merchant on Shopify Community reported inventory vanishing across 1,500+ items after something like this. That’s a merchant report, not something I’ve reproduced.

Leaving a variant row out can remove that variant.
Shopify’s how-to for deleting variants with a CSV is exactly this: delete the rows and import with overwrite on. Do it by accident and you get the same result.

Some things people fear don’t happen.
A CSV import cannot delete products. A product missing from your file is left alone. I’ll say that plainly, because a good checker shouldn’t scare you about things that aren’t real.

The problem

You can’t see any of this before you import. Shopify shows you a file. It doesn’t show you the consequences.

A variant, if the word is new: one T-shirt in Small, Medium, Large and Extra Large is four variants. Each has its own price, SKU and stock count. Drop one row from your spreadsheet and that Extra Large may be gone.

What I built

A small tool. You give it two files: your current Shopify product export, and the CSV you plan to import. It tells you, in plain English, what the import could change, overwrite or delete.

It doesn’t install into your store. It doesn’t need store access. It compares two files.

It flags things like:

• A blank Vendor or Description that would clear existing data
• A variant that exists in your store but is missing from your file
• A renamed option value that becomes a new variant
• A price that jumps from 48.00 to 480.00
• A handle with a typo, which would create a duplicate product
• A SKU that lost its leading zero, or turned into 1.2E+10 after a trip through Excel

It also separates what Shopify documents from what is only possible. Some of its warnings are labeled “needs verification” because I haven’t tested them yet. I’d rather show that than pretend.

Why I’m writing this instead of launching it

I’ve built several tools that never saw the light of day. Good code, no users. I always asked “can I build it?” and never “does anyone need it?”

This time I’m asking first.

I’ve already messaged merchants and freelancers directly. Almost nobody replied. That’s fine. I know cold messages don’t always work, not that the problem is fake. So I’m asking in public.

Your comments decide whether I keep going. If nobody cares, I stop and move on. That’s a real outcome and I’m okay with it.

What I’m asking

Answer any of these in the comments. One line is enough.

1. Have you ever had an import go wrong? What did it cost you: hours, money, lost sales?
2. What do you do today before you import a large CSV?
3. How often do you import, and into how many stores?
4. If a tool showed you what a file would change before you uploaded it, would you use it? What would make you trust it?
5. Would you pay for it? Roughly how much, and for what: one report, or ongoing?

If you’d like to test it, say so in a comment. I’ll run your files through it and send you the report. Please don’t send customer or order data, only product CSVs.

If you think I’m wrong, say that too. “Shopify will fix this itself” and “I just use a backup” are useful answers.

No pitch. No newsletter trap. Tell me whether this problem is real.

A Shopify CSV Import Can Delete Your Variants. I Built a Checker. Would You Use it? was originally published in Bash_DevOps_AI on Medium, where people are continuing the conversation by highlighting and responding to this story.