When this tool helps
Use this before WooCommerce’s built-in product CSV importer to review Name, SKU, Type, Published, Parent, Images, and row structure in one pass. With large catalogs, catching suspicious rows before the mapping screen saves a lot of backtracking.
For updates, WooCommerce can match existing products by ID or SKU. Keep the original export or a backup, because a syntactically valid CSV can still update the wrong product if identifiers are wrong.
A missing Name column is different from a blank Name cell
Name is part of the standard required schema. This checker reports a missing Name header separately from blank Name values so you know whether you have a template problem or a row problem.
Published accepts the documented status values, and variation rows need a Parent reference. Matching column counts alone does not prove that a variable-product hierarchy is valid.
Do not stop at “zero errors”
Duplicate SKUs can collapse distinct products onto the same identifier. A variation without Parent has no clear parent product. Image URLs can be checked for basic URL shape, but a local browser cannot prove that every remote image is reachable by WooCommerce.
Plugin-specific fields and `meta:` columns depend on WooCommerce’s mapping screen and installed extensions. This preflight intentionally focuses on the standard fields it can verify locally.
A practical workflow
For a 1,000-product price and stock update, export the current catalog, make a copy, and edit only ten representative products first. Run this checker, review WooCommerce’s mapping screen, complete the small import, then open the products and verify the result before scaling up.
That small live test often catches more than adding another dozen theoretical rules to the CSV checker.