Instead of one T-shirt with a size selector, the store now has three separate products. First, check the CSV structure: the rows should describe a parent variable product and its variations. Similar names alone do not link records.
This article covers the built-in WooCommerce importer. The Product CSV Import Suite extension uses its own columns and separate documentation; the two schemas must not be mixed. Note the WooCommerce version and importer name before preparing the file.
How parent products and variations work
The parent product groups the product’s properties and available options. A variation specifies a particular combination: size M, blue color, its own price and stock. In the WooCommerce documentation on variations they are represented as objects associated with a particular product. This differs from several independent simple products.
In the built-in CSV, the parent has Type set to variable, and a variation has variation. The Parent column points to the parent’s existing SKU or to its ID in the format id:123. Each variation’s SKU should distinguish it from the others during subsequent updates.
Do not assume that a missing link will inevitably create a simple product. Some invalid rows may be skipped or result in an import error. A separately created simple product, a skipped variation, and a variation with incorrect attributes are different outcomes. Confirm which occurred in the report and product editor.
Example with two sizes
Imagine a T-shirt store. This is a fictional example: the parent has SKU TSH-BASE, and the variations have SKUs TSH-S and TSH-M. The product needs a local Size attribute with values S and M. It is helpful to first write the agreed structure as a table:
| Row | Type | SKU | Parent | Size |
|---|---|---|---|---|
| T-shirt | variable | TSH-BASE | Blank | S, M |
| T-shirt S | variation | TSH-S | TSH-BASE | S |
| T-shirt M | variation | TSH-M | TSH-BASE | M |
The attribute fields in the CSV have the exact names Attribute 1 name, Attribute 1 value(s), Attribute 1 visible, and Attribute 1 global. For a local Size attribute, global is set to 0. List the available sizes on the parent and the selected size on each variation. The column rules are given in the official schema for the built-in importer.
Do not copy the word “Blank” from the table into the file: it explains why the parent has no Parent value. Leave that cell empty in the CSV. The field containing the list S, M must be enclosed in quotes correctly if the file uses commas as separators.
How to check attributes before importing
Compare the attribute name and values in the parent and child rows. M, m, and Medium must not accidentally refer to the same size using different words. Remove extra spaces, then open the finished CSV in a text editor and check the saved values.
Decide whether to use a local attribute or a global attribute that has already been created in the store. A global attribute requires a consistent set of existing values. Do not switch global between rows just to get the import to run: this changes the data structure and may create unexpected variations.
In the test file, give each variation a clear price and stock quantity. After importing, it should be easy to see which row is selected on the storefront. If both variations have identical data, some errors may go unnoticed: the selection changes visually, but the customer sees information for a different size.
How to choose a process for your WooCommerce version
The current documentation describes behavior starting with WooCommerce 11.1: under certain conditions, importing updates can create new variations for an existing parent. When converting a simple product to a variable product, order matters: the parent row must come before the child rows. Do not automatically apply this approach to an older store.
If your version is earlier than 11.1 or you cannot ensure the row order, use the documented two-import process. First, update the parent product and its attributes. Then upload a separate file of new variations, linking them to the parent you have prepared. Choose create or update mode according to the contents of each file.
Update existing variations using their stable keys; create new ones first using the chosen process. Before uploading again, review the result of the previous run. Switching modes without checking can turn a straightforward task into a mix of new and skipped rows.
If you do not know the version, check the installed WooCommerce details and record it. Do not call the import successful just because there is no large red error on the screen. Check that the intended child records were created and linked to the parent.
How to investigate separate products that have already appeared
Open the intended parent and each separate product. Record their IDs, SKUs, product types, attributes, and URLs. Compare these with the source rows. If the child rows have Type set to simple, they described standalone products. Start the fix by correcting the file schema and planning a consistent data migration.
Do not delete the records immediately: they may have orders, links, and stock. Give the developer a mapping table with “existing record — expected parent — size — next action.” Specify which history and data must be retained. Simply changing Type without checking the relationships is not a complete fix plan.
If variations were skipped, review the reasons in the importer report: Parent, SKU uniqueness, and matching attributes. Fix a small file instead of uploading the full catalog again. Verify that one parent with two variations is created successfully before repeating the process in bulk.
How to check the product page on the storefront
Open the parent product page while logged out. Select S, then M, and compare the displayed information with the reference table. Make sure an unavailable combination is not offered for purchase and that the price and stock correspond to the selected variation.
Test adding the product to the cart on a test copy: the selected size should remain in the cart item. You do not need to place a real order to check the import structure. Decide in advance on a safe test environment and the minimum action needed to confirm that the correct variation is selected.
Check the store catalog and search. They should show a consistent representation of the parent product. Whether variations have separate indexable pages depends on how the site is set up; the Parent column does not create them.
What to give the developer and how to approve the work
Provide the WooCommerce version, import tool, source CSV, parent ID, and reference SKUs. Acceptance criteria for this example: one variable product, the two required variations, correct sizes, price and stock when selected, correct addition to the cart on a store copy, and a repeat update without new duplicates.
If manually entered metadata was lost during the import, investigate titles and descriptions overwritten by an import separately.
For a regular price list, use the guide to updating WooCommerce by SKU, and check published links with a technical audit. The work is complete when the data structure and storefront selection match. Search indexing and rankings are checked separately and are not confirmed by a message saying the CSV upload is complete.