Eren Labs JOURNAL TR
WooCommerce Errors

“A new variation cannot be created” and “Variation cannot be imported” in WooCommerce: every reason a variation row is refused

When you update existing products, WooCommerce checks each new variation row against its parent and refuses the ones that would break. Without that box ticked, the same mistakes import without a word, which is often worse.

In this article14 sections

These messages come from the product importer when it is asked to create a variation while Update existing products is ticked. In that mode WooCommerce will add a new variation to a variable product that already exists, but first it checks that the variation can actually work under that parent. When it can’t, the row is skipped and the log says why.

The checks are a recent safety net, and they only run in update mode. Import the same file with the box unticked and none of them run: variations with no parent, the wrong parent or attributes the parent doesn’t offer are saved anyway, and nothing in the log tells you.

The exact message#

A new variation cannot be created because “XL” is not an option of the parent product’s “Size” attribute.

The same failure can also read:

  • A new variation cannot be created because the parent product has no “Color” attribute.
  • A new variation can only be created for a variable parent product.
  • A new variation cannot be created for a parent product that does not exist.
  • A new variation cannot be created without a parent product.
  • A new variation cannot be created without a SKU or a GTIN, UPC, EAN, or ISBN.
  • A new variation cannot be created for a row that specifies an ID.
  • Variation cannot be imported: Missing parent ID or parent does not exist yet.
  • Variation cannot be imported: Parent product cannot be a product variation

Who sees it: Store owners, in the log of the product CSV importer. The “A new variation cannot be created” messages appear only when Update existing products was ticked and the variation row matched no existing variation; the row is counted as skipped. WooCommerce 11.2.1 still contains the two “Variation cannot be imported” messages, but its own importer never shows them.

What WooCommerce checks#

The checks run for a row whose Type is variation, when Update existing products is ticked and the row’s ID, SKU or GTIN matches nothing in the store. WooCommerce stops at the first problem:

  1. The row must not have an ID. A new variation can’t be given an ID from the file.
  2. The row needs a SKU or a GTIN, so a later import can find the variation again.
  3. The Parent column must be filled in.
  4. The parent must exist and be a variable product.
  5. The parent must not be in the Trash.
  6. Every attribute named in the row must exist on the parent, and every value must be one of the parent’s options. An empty value is allowed: it makes an “any” variation.

A plugin can still veto a row that passes, in which case the log shows No matching product exists to update.

With the box unticked, none of this runs. In our tests on 11.2.1 a row with no parent was saved as a variation with no parent, a row under a simple product wasn’t refused, an attribute the parent lacks was dropped (turning the row into an “any” variation), and a value the parent doesn’t offer was saved but never offered to shoppers.

Causes and how to fix each one#

1. The value isn’t one of the parent’s options#

The parent offers Size: S and M, and the row asks for XL. For a custom attribute the value must match exactly, capitals included, so xl isn’t XL. For a global attribute the value must be a term assigned to the parent product, not just a term that exists under Products > Attributes. A cell with several values, such as S, M, is read as its first value.

Check: Open the parent product and look at the attribute on its Attributes tab. The values listed there are the only ones a new variation can use.

Fix: Add the missing value to the parent’s attribute, keep Used for variations ticked, update the parent, then import the row again.

2. The parent doesn’t have that attribute, or has the other kind#

The attribute name in the row must match one on the parent. A spelling difference such as Colour against Color is enough to fail. So is a mismatch between global and custom. When Attribute 1 global is 1 and Products > Attributes has an attribute with that name, the row means that global attribute; with 0 it means a custom attribute typed on the product. A parent that uses a custom Size attribute doesn’t have the global Size, and a parent that uses the global one doesn’t have a custom Size.

Check: Look for the attribute under Products > Attributes. If it’s listed there and the parent uses it, the row needs 1 in Attribute 1 global; if the parent’s attribute was typed on the product, it needs 0.

Fix: Correct the attribute name or the global column in the file so it describes the parent’s attribute exactly.

3. The Parent cell points at something that isn’t a variable product#

The parent may be a simple or grouped product, or the Parent cell has a typo. A Parent SKU that isn’t in your store also ends here: the importer creates a temporary simple placeholder for it, so the check reports a parent that isn’t variable rather than one that doesn’t exist. In update mode you can’t create the parent in the same file either, because a new parent row is itself skipped.

Check: Search for the Parent SKU on Products > All Products and look at the product type of the result.

Fix: Create the variable product first, with its attributes and Used for variations ticked, or import it in a separate run with the box unticked. Then import the variations with the box ticked.

4. The parent is in the Trash#

A parent written as id:120 that is in the Trash gives A new variation cannot be created for a parent product that does not exist. A trashed parent referred to by its SKU isn’t found at all, which leads to the placeholder case above.

Check: Open the Trash view on Products > All Products and look for the parent.

Fix: Restore the parent product, then run the import again.

5. The row has no SKU or GTIN, or it has an ID#

WooCommerce won’t create a variation it could never match again, so a new variation row needs a SKU or a barcode. It also refuses a row with an ID: an ID from the file can’t be given to a new variation, and reusing one could damage the post that already has it.

Check: Look at the row’s SKU, GTIN and ID cells.

Fix: Give every new variation a SKU (the <a href=”/free-tools/sku-generator/”>SKU generator</a> can build them from the parent SKU and attribute values) and clear the ID cell. Keep IDs only for variations that already exist on this store.

6. You see “Variation cannot be imported” instead#

WooCommerce 11.2.1 still builds Variation cannot be imported: Missing parent ID or parent does not exist yet. and …Parent product cannot be a product variation, but its importer ignores them and saves the variation regardless. If your log shows one of them, it came from an importer other than the one in WooCommerce 11.2.1. In 11.2.1 a row with no parent is saved as a variation without a parent. A row whose parent is another variation is saved under that variation, without its attributes. Neither shows up on a product in the admin.

Check: Compare the “variations imported” count in the import summary with the number of variations on each parent’s Variations tab.

Fix: Fill in the Parent column with the parent’s SKU or id:ID, and put each parent row above its own variations, so the parent and its attributes already exist when the variation is read. The <a href=”/free-tools/woocommerce-product-csv-template/”>CSV template</a> shows a working variable product with its variations.

Quick reference#

CauseHow to checkFix
The value isn't one of the parent's optionsOpen the parent product and look at the attribute on its Attributes tab. The values listed there are the only ones a new variation can use.Add the missing value to the parent's attribute, keep Used for variations ticked, update the parent, then import the row again.
The parent doesn't have that attribute, or has the other kindLook for the attribute under Products > Attributes. If it's listed there and the parent uses it, the row needs 1 in Attribute 1 global; if the parent's attribute was typed on the product, it needs 0.Correct the attribute name or the global column in the file so it describes the parent's attribute exactly.
The Parent cell points at something that isn't a variable productSearch for the Parent SKU on Products > All Products and look at the product type of the result.Create the variable product first, with its attributes and Used for variations ticked, or import it in a separate run with the box unticked. Then import the variations with the box ticked.
The parent is in the TrashOpen the Trash view on Products > All Products and look for the parent.Restore the parent product, then run the import again.
The row has no SKU or GTIN, or it has an IDLook at the row's SKU, GTIN and ID cells.Give every new variation a SKU (the <a href="/free-tools/sku-generator/">SKU generator</a> can build them from the parent SKU and attribute values) and clear the ID cell. Keep IDs only for variations that already exist on this store.
You see "Variation cannot be imported" insteadCompare the "variations imported" count in the import summary with the number of variations on each parent's Variations tab.Fill in the Parent column with the parent's SKU or id:ID, and put each parent row above its own variations, so the parent and its attributes already exist when the variation is read. The <a href="/free-tools/woocommerce-product-csv-template/">CSV template</a> shows a working variable product with its variations.

Reproduced on a test store#

We set up each case below on a clean WooCommerce 11.2.1 store on 6 November 2026 and recorded exactly what it showed.

What we didWhat WooCommerce showed
Variable product with SKU VP and a custom attribute Size with values S | M, Used for variations ticked. Update existing products ticked. Import header Type,SKU,Name,Parent,Attribute 1 name,Attribute 1 value(s),Attribute 1 global and row variation,VP-XL,,VP,Size,XL,0.A new variation cannot be created because "XL" is not an option of the parent product's "Size" attribute.
Same parent and settings. Row variation,VP-RED,,VP,Color,Red,0.A new variation cannot be created because the parent product has no "Color" attribute.
Simple product with SKU SP. Update existing products ticked. Row variation,SP-S,,SP,Size,S,0.A new variation can only be created for a variable parent product.
Parent VP as above. Update existing products ticked. Row variation,,,VP,Size,S,0 (no SKU, no GTIN column).A new variation cannot be created without a SKU or a GTIN, UPC, EAN, or ISBN.
Move VP to the Trash and note its ID (say 120). Update existing products ticked. Row variation,VP-S2,,id:120,Size,S,0.A new variation cannot be created for a parent product that does not exist.
Update existing products unticked. Row variation,VN1,,,Size,S,0 (Parent empty).No message.
Saved as a variation with no parent product.

For developers#

The refusals come from WC_Product_CSV_Importer::can_create_variation() and validate_new_variation_attributes(), and are logged as skipped rows. A row that passes can still be vetoed:

add_filter( 'woocommerce_product_import_create_variation_of_existing_product', function ( $create, $row ) {
	return $create;
}, 10, 2 );

The filter only receives rows that passed validation, so it can refuse a creation but not force one. To find orphaned variations left by earlier imports, run this in wp shell:

var_dump( get_posts( array( 'post_type' => 'product_variation', 'post_parent' => 0, 'post_status' => 'any', 'fields' => 'ids', 'numberposts' => -1 ) ) );

Where this lives in WooCommerce 11.2.1:

  • includes/import/class-wc-product-csv-importer.php, WC_Product_CSV_Importer::can_create_variation: Row ID, SKU or GTIN, Parent, variable parent, parent not trashed or a placeholder, in that order.
  • includes/import/class-wc-product-csv-importer.php, WC_Product_CSV_Importer::validate_new_variation_attributes: Each attribute in the row must exist on the parent, and each non-empty value must be one of the parent’s options.
  • includes/import/class-wc-product-csv-importer.php, WC_Product_CSV_Importer::import: Runs those checks only for unmatched variation rows when update_existing is on, then the woocommerce_product_import_create_variation_of_existing_product filter.
  • includes/import/class-wc-product-csv-importer.php, WC_Product_CSV_Importer::parse_relative_field: A Parent SKU that doesn’t exist yet gets a temporary simple placeholder product.
  • includes/import/abstract-wc-product-importer.php, WC_Product_Importer::set_variation_data: Builds the two “Variation cannot be imported” errors, but process_item() ignores its return value.

Back to the WooCommerce error reference.

Frequently asked questions#


Why does the importer accept these rows when Update existing products is off?

The checks only run when updating. When creating, WooCommerce 11.2.1 saves the variation even with no parent or with values the parent doesn’t offer. Check each parent’s Variations tab after an import.


Can I add variations to an existing variable product by import?

Yes. Tick Update existing products, give each new variation a SKU, leave the ID empty, and put the parent’s SKU in the Parent column. The parent must already have every attribute value the variations use.


Why does it say the parent isn't variable when the Parent SKU is right?

If the SKU doesn’t exist in your store yet, or belongs to a trashed product, the importer makes a temporary simple placeholder for it. Create the variable parent first.


What is an "any" variation?

A variation with an empty attribute value. It matches every value of that attribute, so one row can cover all sizes, for example. An empty value passes the import checks.


Where do orphaned variations go?

They stay in the database with no parent, so they don’t appear on any product or in the Products list. To attach them, import the same rows again with Update existing products ticked and the Parent column filled in.


More in WooCommerce Errors

Keep exploring

All articles