WooCommerce CSV import errors: a practical fix checklist

1. Check the import log before changing the CSV

WooCommerce reports why rows were skipped. A product may already exist with the same SKU or ID, the file may not match the product CSV schema, a publication value may behave differently than expected, or the server may be unable to process a large batch.

2. Save the file as UTF-8 CSV

WooCommerce recommends UTF-8. Encoding problems often show up as broken accented characters, strange symbols in the first header, or fields that map unexpectedly. Re-export as UTF-8 CSV instead of merely renaming a spreadsheet file.

3. Validate headers and row width

Every product row should line up with the header row. One unescaped comma or unclosed quotation mark can shift all later fields. Values containing commas should be quoted correctly, and custom headings need to be mapped during import.

4. Use WooCommerce’s accepted values

Core boolean fields use 1 or 0. The Published column supports 1, 0, and -1. Prices should use a period as the decimal separator and no thousands separator.

5. Resolve duplicate identifiers

SKUs need to be unique. When updating products already in the store, select “Update existing products” and use the correct product ID or SKU so WooCommerce can match the row.

6. Check variable-product relationships

Variation rows need a valid parent reference. Confirm the parent product exists, the variation type is correct, and attribute values match the parent’s variation attributes.

7. Split large catalogs into smaller batches

Very large imports can hit server memory, upload, or execution-time limits. Smaller batches are easier to diagnose and safer to retry.

8. Diagnose image-only failures separately

If products import but their images do not, check whether each image is already in the Media Library or available through a direct public URL. Sharing pages and redirect scripts may not work. See the product image import troubleshooting guide.