A WooCommerce product import fails most often on variable products and attributes, not on simple products. SKULaunch prepares the whole record, parents, variations, attributes, categories and images, and exports it in the structure WooCommerce expects, so ranges go live complete instead of half imported.
The problem
WooCommerce's CSV importer is strict. Variable products need a parent row and a row per variation, linked correctly. Attributes need names, values, visibility and a global setting, numbered per column. Categories need the right hierarchy separators, and images need working URLs. Supplier files look nothing like this, so someone builds the import file by hand, imports, finds broken variations, and starts again.
The pain grows with the range. Fifty simple products are a morning's work. Two thousand products with size and colour variations, spread across three suppliers who each name their attributes differently, is weeks of spreadsheet work that has to be repeated every time the range changes.
Before and after
An illustrative example from a lighting retailer importing a supplier range.
Before: the supplier rows
LED bulb E27 4W warm white; LED bulb E27 4W cool white; LED bulb E27 8W warm white. Each a separate product with its own description. Wattage written as 4W, 4 Watt and 4w across the file.
After: exported from SKULaunch for WooCommerce
- One variable product: LED bulb E27, with shared description and images
- Attributes: Wattage (4 W, 8 W) and Colour temperature (Warm white, Cool white), set as global and used for variations
- Each variation with its own SKU, price, stock fields and image
- Category path in WooCommerce hierarchy format, such as Lighting > Bulbs > LED
- Other specifications, such as base type and lumen output, as visible attributes that are not used for variations
How it works in SKULaunch
- Enrich and model the products. Fill attributes, group variants under a parent and set the variation axes in SKULaunch.
- Set up the WooCommerce channel. Choose which attributes go to WooCommerce, which drive variations and which are shown on the product page.
- Export. SKULaunch produces the WooCommerce structure with parents, variations, attributes, categories and image URLs in place.
- Import and update. Load into WooCommerce. When data changes, export again and update by SKU.
How a WooCommerce product import file is structured
The built-in importer reads one row per product or variation. The columns that cause most trouble are these:
- Type: simple, variable or variation. A variable parent and its variations are separate rows.
- SKU: unique across the store. It is also how updates find existing products.
- Parent: on each variation row, the SKU of its parent. Put the parent row before its variations.
- Attribute 1 name, Attribute 1 value(s): the parent lists every value, separated by commas. Each variation holds the one value that applies to it.
- Attribute 1 visible and Attribute 1 global: 1 or 0, controlling whether the attribute shows on the product page and whether it is a store-wide attribute.
- Categories: use the greater-than sign for hierarchy and commas to separate multiple categories.
- Images: full, publicly reachable URLs, separated by commas. The first is the main image.
The WooCommerce product CSV template shows the full column set with example rows.
Getting WooCommerce attributes right
WooCommerce has two kinds of attribute. Global attributes are defined once for the store and power layered navigation and filters. Local attributes exist only on one product. For anything customers filter on, such as size, colour or material, use global attributes with consistent values, or your filters fill with near-duplicate options. Only attributes marked for variations become selectable options. Everything else displays as specification. Most broken WooCommerce catalogues come from mixing these up during a manual import.
Common import mistakes
- Attribute names that differ by one character. Colour and Color become two attributes, and filters split.
- Inconsistent values. "4W" on one variation and "4 W" on another create two options for the same thing.
- Variation values missing from the parent. If the parent does not list a value, the variation using it does not work as expected.
- Commas inside values. A value such as "Black, matt" splits in two unless it is escaped.
- Private image URLs. WooCommerce downloads images on import, so links behind a login or on a supplier's expiring link fail.
- Changed SKUs. Edit a SKU outside WooCommerce and the next import creates a duplicate instead of updating.
Each of these is a data problem that shows up as an import problem. Fixing values and structure before the export, rather than in the CSV, is what makes the next import work first time.
What changes
Supplier ranges reach WooCommerce as proper variable products with clean, filterable attributes, and updates go out from one place instead of being rebuilt in spreadsheets.
Common questions
How do I import products with variations into WooCommerce?
Create a parent row of type variable that lists every attribute value, then one variation row per option that references the parent SKU and holds a single value per attribute. SKULaunch builds these rows from the variant model.
Does this replace the WooCommerce importer?
No. SKULaunch prepares the data and the structure. WooCommerce still imports it.
Can we update existing products?
Yes. Exports match on SKU, so existing products are updated rather than duplicated when you use the importer's update option.
What is the difference between global and local attributes in WooCommerce?
Global attributes are shared across the store and can drive filters. Local attributes belong to one product only. Use global attributes for anything customers filter on.
What about images?
Images are exported as URLs, from SKULaunch's Files Store or DAM, which WooCommerce downloads on import.
More on modelling product variants, standardising attribute values, importing supplier spreadsheets, ecommerce sync and catalogue enrichment.

.avif)