WooCommerce CSV Import Guides

Variation rows need attribute name/value pairs to form a valid variation combination.

Non-variation product rows should have a Name.

Visibility in catalog must be one of the four accepted values.

Understand how the WooCommerce product importer represents variable products with parent and child (variation) rows. Covers attribute columns, required fields per row type, and the most common import pitfalls.

How to correctly format WooCommerce product attributes in a CSV file — attribute naming, global vs. local attributes, variation attributes, and common mistakes.

Fix the most common WooCommerce product CSV import errors — missing SKUs, invalid types, variation row problems, price formatting, and attribute column issues.

An integer field (like Stock) contains a non-integer value.

This product row has no image URL.

One or more image URLs in the Images column are not valid http(s) URLs.

Regular price must be a valid number.

Sale price must be a valid number.

A price field contains a non-numeric value.

The Sale price should be less than the Regular price for the discount to be meaningful.

A missing SKU reduces update reliability and can break inventory tracking.

Two or more rows share the same SKU.

One or more required WooCommerce import columns are missing from the header row.

This column is not recognized by the WooCommerce importer.

The Type column is required and determines how the row is interpreted.

The Type value is not one of WooCommerce's supported types.

Boolean fields like Published, In stock?, and Is featured? expect 1/0 or true/false values.

Variation rows must link to a parent variable product using the Parent field.

Two or more variations under the same parent share the same attribute combination.