catalogmender.
WOO CSV / TROUBLESHOOTING

Why WooCommerce product CSV rows get skipped

Start with the importer’s failed-row report. Then narrow the problem to a few rows before changing the whole catalog.

1. Read the failure report

WooCommerce’s built-in importer documentation says missing or skipped products commonly result from duplicate SKUs or IDs, columns that do not match the import schema, unexpected Published values, plugin/theme conflicts, or files too large for the server. Fixing those causes is more reliable than repeatedly uploading the same large file.

2. Check how columns were mapped

The import wizard automatically maps recognized headers. Unknown columns are not imported by default. Look at the mapping screen and decide whether each source field should map to a WooCommerce field or be deliberately omitted. Keep the source file and a record of anything you leave out.

3. Check parent and child rows together

For a variation that did not attach to its product, compare the child’s Parent with the parent’s SKU or ID. Give every variation a unique SKU, set Type=variation, and confirm its attribute name and value exist on the parent. The parent should appear before the children in a new import file.

4. Isolate images and file size

WooCommerce requires image URLs to be directly accessible. A syntactically valid link can still fail during import. Try a small staging import without images to separate catalog structure from remote image availability. For a large catalog, WooCommerce advises splitting it into smaller batches and checking server upload or memory limits.

Our current repair boundary: Catalog Mender catches some duplicate SKU, missing-value, price, and variation-structure errors after reviewing a supplier column mapping. It omits image URLs and does not diagnose plugin conflicts or server limits. See the required fields.

Source

WooCommerce: Product CSV Importer and Exporter, troubleshooting and supplier file guidance.