Why WooCommerce skipped products in your CSV import
A skipped row is usually a matching problem, an unsupported value, or a malformed CSV row. Check the import log first, then rule out file-level causes before changing plugins or server settings.
1. Read the failed-row log
WooCommerce records why an import row was rejected or skipped. Download the failures file when it is offered and start with the first repeated reason. The row number in that report should point back to the corresponding product row in your source CSV.
2. Decide whether you are creating or updating products
When Update existing products is selected, WooCommerce matches rows using a product ID or SKU. Rows that do not match an existing product are skipped. For a new-product import, leave the update option off. For an update, keep the correct existing ID or SKU in each row.
3. Resolve duplicate or conflicting identifiers
A new product can be skipped when its SKU or ID is already assigned in the store. It can also fail when the same non-empty SKU appears more than once in the CSV. Check products, variations, and trashed items before changing the identifier. Every product and variation should have its own unique SKU.
4. Check the Published value and required fields
A successfully imported product can appear to be missing when it was created as a draft or private product. The core CSV schema accepts 1 for published, 0 for private, and -1 for draft. New products also need a name.
5. Repair shifted columns and invalid values
An unescaped comma, mismatched quotation mark, or incorrect delimiter can move values into the wrong columns. Core boolean fields use 1 or0, prices should use a period as the decimal separator, and the file should be saved as UTF-8 CSV. FeedFixer checks these file-level problems locally in your browser.
6. Verify variation parents
A variation row needs the variation type, its own unique SKU, and a Parent value matching the parent product SKU or an existing ID written with the id: prefix. The parent must exist before a variation can attach to it.
7. Separate file problems from store problems
If a small, schema-valid test file still fails, the cause may be a plugin or theme conflict, an unavailable image URL, or a server limit. Very large catalogs should be split into smaller batches. Back up the store or test on staging before retrying a live import.
Get row-level answers without uploading your catalog.
Scan 25 product rows free, or unlock unlimited offline repairs for $9 once.