Why WooCommerce Product Variations Fail to Import

By Ramesh, Altrix Web · Updated 14 October 2026

When a WooCommerce variation import does not produce the expected products, first separate three situations: a row was rejected, a row was imported into the wrong relationship, or the variation exists but is not purchasable on the storefront. Each requires a different investigation. Keep the original file and review the import report before retrying.

1. Identify the exact failing rows

Record the affected SKU or source row, the reported error and whether the row belongs to a parent or a variation. Compare one failing product with one that imported correctly. Avoid changing the entire catalogue when the issue is confined to a particular attribute or supplier batch.

If the import stopped partway through, inspect what already exists before uploading the same file again. A retry should use a deliberate create-or-update strategy.

2. Check product types and parent references

A variable product and its variations need a valid relationship. Confirm the file’s product types and how each variation references the intended parent. Do not use a supplier’s internal row number as if it were a product ID in your store.

Build a small example with one parent and two variations. Check the current importer’s schema and version requirements. The official WooCommerce importer documentation explains the supported parent references and variation behaviour.

3. Compare attribute names and values

Check that each variation’s options belong to the parent’s intended attributes. “Colour” and “Color” may represent different fields in a supplier file. “Navy” and “Dark Blue” may be a genuine distinction or inconsistent naming; decide with the catalogue owner.

Record how global and product-specific attributes should be used before changing them. A blanket text replacement can alter intentional values or disconnect existing records. Review our variation attribute checklist for related checks.

4. Inspect matching identifiers

Check for repeated SKUs, blank identifiers and spreadsheet formatting changes. Establish how the selected import mode matches existing records. New-product creation and existing-product updates should be tested separately.

When the same identifier appears on several source rows, find out whether those rows are duplicates or represent different variants. Do not invent new identifiers without confirming the intended business rules.

5. Review the field mapping

A correct spreadsheet can still fail when its columns are mapped to the wrong destination fields. Review the mapping screen, especially parent, type, SKU and attribute columns. Do not assume an unfamiliar supplier heading is recognised automatically.

Save a record of the agreed mapping for the test batch. If you change a heading later, review the mapping again before the next import.

6. Separate data problems from environment problems

If the same small valid test file fails repeatedly, investigate the import report and environment. Large files may expose resource limits that do not affect small batches. Custom importer extensions can introduce their own field rules.

Use a staging copy for plugin-conflict investigations and changes that could affect live purchasing. Keep the working configuration recorded so a test can be reversed.

7. Verify the result from both admin and storefront

After the test, confirm that the intended variation records exist under the right parent. Then check options, prices and stock behaviour on a public product page. An imported record is not proof that a customer can buy the intended combination.

If the records exist but the public selector is wrong, continue with our WooCommerce variable products not showing troubleshooting guide.

Before importing the rest

• Keep the backup, original file and import report.
• Resolve the cause for the representative failing rows.
• Confirm the parent relationships, identifiers and attribute mapping.
• Test a small batch using the intended import mode.
• Review product records and the public buying experience.

For general file preparation, read how to prepare a WooCommerce product CSV. You can also review data with our Product CSV Checker; it does not replace testing in your actual store.