You imported a batch of products. Everything looks fine in your dashboard. Then, a week later, a customer asks why a color they expected isn’t available and it turns out it was never actually created.
CSV imports are efficient, but they’re not always complete. Here’s a simple checklist to run right after any import, so you catch gaps before your customers do.
Why imports leave gaps
↑ Back to topMost CSV imports handle products and attributes well, but variation generation is a separate step. If your file doesn’t list every attribute combination explicitly, or the import tool only creates variations for rows it finds an exact match for, some combinations get skipped silently. There’s no failed-import warning, the product just ends up with fewer options than it should have.
This tends to happen more with:
- Large files with hundreds or thousands of products
- Products using shared/global attributes across many rows
- Imports done in stages (products first, variation data after)
Your post-import checklist
↑ Back to top1. Pick a sample of products to spot-check Don’t check all of them by hand – just a handful across different categories. Open the Variations tab and count the combinations against what you’d expect.
2. Look for round numbers that don’t add up If a product has 3 sizes and 4 colors, you should see 12 variations. Seeing 9 or 10 is a sign the import skipped some.
3. Run a full scan instead of guessing Spot-checking tells you if there’s a problem, not where every instance is. For that, scan your entire imported batch at once with Bulk Generate Missing Variations:
- Select the products you just imported
- Choose Find Missing Variations from bulk actions
- Review the full list of gaps across every product in one place
- Generate everything at once, or select combinations individually
4. Export the results before generating, if you’re not ready to publish If you want pricing or stock reviewed before anything goes live, export the missing combinations as a CSV first, fill in the details, and generate later. See the documentation for the full workflow.
5. Make this step part of every future import Once you’ve caught it after one import, it’s worth running the same scan every time you bring in new products, it takes a couple of minutes and catches gaps before they become support tickets.
One thing to keep in mind
↑ Back to topScanning and generating missing variations doesn’t touch anything that already exists, it only adds what’s missing. It’s safe to run after any import, even if you’re not sure whether there’s a problem.
