Product imports are useful because they move a lot of data at once.
That is also why they can make a mess quickly.
A CSV import, migration, supplier upload, or bulk product update can touch titles, descriptions, variants, prices, compare-at prices, inventory, tags, images, and more. Most of it may come through fine. One tiny pricing mistake can still create a real problem.
A missing price.
A placeholder price.
A $0.00 variant.
A compare-at price in the wrong place.
A sale tag that no longer matches the pricing.
None of these are dramatic technical mysteries. They are normal catalog cleanup problems. The issue is catching them before customers do.
Quick answer
After a Shopify product import, check product and variant prices, compare-at prices, sale tags, and any products that came through with missing, placeholder, or $0.00 pricing.
Pay special attention to variants. A product can look normal while one size, color, or option has the wrong price.
If you only import products once in a while, a manual review checklist may be enough. If you import often, migrate catalogs, use supplier files, or manage lots of variants, a small guardrail can help flag products that need pricing review.
Why imports create pricing cleanup work
Shopify’s product import docs explain that product CSV files can be used when switching to Shopify from another platform or when making many product or inventory changes.
That is powerful.
It also means one spreadsheet issue can affect a lot of products.
A column might be blank. A value might be copied from a template. A row might be outdated. A supplier file might use a placeholder price. A migration might handle variants differently from your old platform.
The import did what the file told it to do.
The cleanup starts when you need to confirm the file told Shopify the right thing.
Mistake 1: Missing prices
The first thing to check is obvious but important: products or variants with missing prices.
A product might be created with most of its data filled out, but pricing still unfinished.
That can happen when:
- products are imported before final pricing is ready
- supplier data is incomplete
- a CSV column is blank
- a migration file does not map pricing correctly
- a product was meant to stay in draft but gets reviewed with active products
Missing pricing is not always the same as $0.00 pricing, but both deserve attention.
After an import, review the products that were added or updated and make sure every product or variant that should be sellable has a real price.
Mistake 2: $0.00 placeholder prices
A $0.00 price is one of the easiest problems to miss and one of the most annoying to find later.
Sometimes a $0.00 price is intentional. Stores may use free items for samples, warranties, replacement parts, bundle components, or internal workflows.
But after an import, $0.00 often means something was unfinished.
A placeholder price might come from:
- a product setup template
- an old platform export
- a supplier file
- a draft product
- a migration cleanup spreadsheet
- a row someone meant to come back to later
The dangerous part is variants.
A product can have nine correctly priced variants and one variant sitting at $0.00. If you only skim product titles or top-level product data, you may miss it.
Mistake 3: Wrong variant prices
Variants make import cleanup harder.
Shopify’s variant docs explain that variants are the different versions of a product, such as size or color.
That means pricing review needs to go deeper than the product title.
For example:
- Small: $24.00
- Medium: $24.00
- Large: $0.00
- XL: $24.00
Or:
- Single pack: $12.00
- Two pack: $12.00
- Four pack: $12.00
That second one might be wrong if the pack sizes should have different prices.
After imports, check variants that are easy to overlook:
- uncommon sizes
- color variants
- bundle quantities
- pack sizes
- replacement parts
- add-ons
- variants created during migration
A product can look fine while one variant is not fine.
Mistake 4: Compare-at price mistakes
Compare-at price is another field that can get messy during imports.
Shopify’s sale pricing docs explain that compare-at price is used to show an original price when the current price is lower. The compare-at price should be higher than the product price for sale pricing to display correctly.
After an import, check for problems like:
- compare-at price lower than the price
- compare-at price equal to the price
- compare-at price missing on products meant to show as on sale
- compare-at price left behind after a sale ended
- compare-at price applied to only some variants
- compare-at price copied from an old campaign
These mistakes may not make the product free, but they can still make pricing look wrong.
A product might appear on sale when it should not. Or it might fail to show as on sale when it should.
Mistake 5: Sale tags falling behind
Pricing and tags are separate.
A product can have sale pricing without a sale tag. A product can have a sale tag even after the sale pricing is gone.
That is why imports and bulk updates can make tag workflows messy.
For example:
- a product gets a lower price but no
saletag - a product loses its compare-at price but keeps the
saletag - a supplier file updates pricing but not tags
- a migration brings over old sale tags from a previous store
- only one variant is discounted, but the product tag does not reflect your rule
If you use sale tags for collections, merchandising, or internal review, price cleanup and tag cleanup both matter.
They are connected, but Shopify does not automatically keep every custom tag in sync with every price change.
Mistake 6: Duplicate or outdated rows
CSV files can have stale data.
That is not a Shopify-specific problem. It is a spreadsheet problem.
A product file may include:
- old rows from a previous export
- duplicate products
- duplicate variants
- products that should no longer be active
- prices from an old sale
- test products
- placeholder SKUs
- supplier data that was never cleaned up
If outdated rows make it into an import, they can bring old pricing with them.
After any import, check the products that were changed. Do not assume the file was clean just because the import completed.
Mistake 7: Import assumptions from another platform
Migrations are especially risky.
Different platforms can represent variants, options, pricing, discounts, and product status differently. A field that worked one way before may not land the same way in Shopify.
That can create pricing surprises:
- variants created differently than expected
- placeholder prices imported as real prices
- old sale data turned into compare-at prices
- free items imported without context
- draft-only products published too soon
- bundles or replacement parts treated like normal products
The import may be technically successful while still needing review.
That is why post-migration cleanup matters.
Post-import pricing checklist
After an import, use a simple pricing cleanup checklist.
- Review products created or changed by the import.
- Check product prices.
- Check variant prices.
- Look for blank, placeholder, or $0.00 prices.
- Check compare-at prices.
- Look for compare-at prices that are equal to or lower than the current price.
- Check products with many variants first.
- Review sale tags and sale collections.
- Confirm intentional free products are documented or tagged.
- Fix pricing mistakes in Shopify.
- Tag products that need a second review.
- Keep notes on what was intentional so the same products are not reviewed again later.
This is not exciting work.
That is the point.
A boring checklist catches boring mistakes before they become customer problems.
When manual review is enough
Manual review is fine when imports are rare.
You can probably handle it by hand if:
- your catalog is small
- you do not use many variants
- one person manages product data
- supplier uploads are rare
- migrations are not happening often
- pricing mistakes are easy to spot
- intentional free items are clearly documented
In that case, keep it simple.
Run the checklist after each import. Fix what is wrong. Move on.
You do not need a giant catalog system for a few imported products.
When automation starts to help
Automation helps when post-import review keeps coming back.
If you import products often, work with supplier files, manage lots of variants, or have multiple people touching product data, manual review gets old fast.
A useful guardrail is simple:
- Check products for variants priced at $0.00.
- Add a review tag when a product has at least one $0 variant.
- Remove the tag when the product no longer has a $0 variant.
- Let the merchant decide what price is correct.
That last part matters.
Software should not guess your product prices.
It should point out the product that needs attention, then let you make the call.
Tiny tool option
ZeroPrice Guard tags products that have at least one $0.00 variant, so they are easier to find and review after imports, migrations, bulk edits, or normal catalog cleanup.
It does not edit prices. It does not create discounts. It does not hide products. It does not change checkout, theme code, or storefront behavior.
It is built for the boring guardrail work: finding possible pricing mistakes before shoppers do.
Keep the import cleanup boring
Imports move a lot of product data quickly.
That is useful.
It also means small pricing mistakes can move quickly too.
After every import, check the prices. Check the variants. Check compare-at prices. Check the sale tags. Look for $0.00 values and placeholders.
If it only happens once in a while, a manual checklist is enough.
If it keeps coming back, add a small guardrail.
Not a pricing platform. Not a giant dashboard.
Just a way to catch the products that need a second look.