WOOCOMMERCE CSV GUIDE

How to check a WooCommerce CSV before importing

Find file problems while they are still easy to review. This checklist works alongside WooCommerce’s import report and a small test import.

1. Start with a recognizable export

HassleKit supports the built-in WooCommerce exporter’s English and Italian headers. Supplier files and extension-specific columns may need mapping first. Save your file as UTF-8. The checker accepts comma, semicolon and tab separators, up to 10 MB and 50,000 product records.

Try a clean example CSV or an example with deliberate issues. Both are synthetic; their image addresses are placeholders.

2. Check what was actually analyzed

Select your CSV in the free checker. Parsing happens in your browser. HassleKit does not send the catalog to a server or store it for later.

Open the check-coverage details to see which checks were available. If columns are missing, the report explicitly says that the analysis is limited. Zero errors only describes the checks that could run.

3. Review identifiers and prices

Repeated SKUs are flagged as errors. A blank SKU is a warning because an import may use another identifier. For existing-product updates, WooCommerce can match by ID or SKU. Review the intended workflow before assigning new identifiers.

4. Follow variation links

A variation should reference its parent using a SKU or an ID with the id: prefix. Review its attribute names and options against the parent row. An absent parent in the CSV is a warning, since that product may already be in your store.

For example, a variation with Parent = TEE can link to a parent whose SKU is TEE. The checker can compare these rows when both are in the file.

5. Use the report to find the right product

Findings are grouped by issue type, with definite errors first. Select a group, then search by product name, SKU, ID or record. Each finding explains what was detected and what to review. Record numbers count CSV records, including the header; a multiline description can span several physical lines.

You can download the full report as JSON. It includes product identifiers and issue values, so treat it as catalog data. The free tool does not change or export a corrected CSV.

More help with specific findings

• How to find duplicate SKUs in a WooCommerce CSV
• How to review invalid prices in a WooCommerce CSV
• How to check missing variation parents in a WooCommerce CSV

6. Test before a full import

Keep a backup and test a small batch on staging. Check the importer’s column mapping and results, then inspect the products in the store.

HassleKit cannot check existing store records, image availability, plugin behavior or every WooCommerce import rule. A report without errors is not a guarantee that an import will succeed.

Core import format reference: WooCommerce Product CSV Importer and Exporter documentation. HassleKit is an independent tool and is not affiliated with WooCommerce.