CCSV Local Tools
Product import preflight

Check a WooCommerce product CSV before import

Choose whether you are adding products or updating existing ones. The checker reports row-level risks and links every rule to the current WooCommerce importer documentation.

No uploadNo accountFree to use
1

Choose your CSV

Local processing
Drop a CSV hereor choose a file · up to 50 MB Download a safe WooCommerce sample

Not sure? Start with UTF-8 and change this if the preview is garbled.

2

Configure the result

Choose a CSV to begin.
How it works

From source file to checked output

  1. 1

    Load a WooCommerce product CSV and choose new-product or update mode.

  2. 2

    Run conservative checks based on the current core importer documentation.

  3. 3

    Download the row-level report, correct the source, and test a small import on staging.

Rules and evidence

A preflight check, not a compatibility promise

The checker covers documented core fields such as Name, ID, SKU, Type, Published, stock flags, prices, variation parents, and structural CSV errors. It does not execute WooCommerce, inspect plugins, or guarantee an import will succeed.

Read the current WooCommerce Product CSV Importer documentation.

Independent utility

WooCommerce is a trademark of its owner. CSV Local Tools is not affiliated with or certified by WooCommerce or Automattic.

Worked example

Catch a broken variation before upload

Input

Type,SKU,Name,Published,Regular price,Parent
variation,TSHIRT-S,,yes,free,

Expected result

row 2 → blank Name
row 2 → invalid Published
row 2 → non-numeric price
row 2 → missing Parent

Boundary: This preflight covers conservative core-format checks. It cannot evaluate plugins, themes, server limits, remote image availability, or custom importer code.

Continue the workflowSplit a large product importInspect SKU collisionsConvert the source to UTF-8
Built for operations

Useful before it becomes a workflow

These tools target repetitive catalog and operations tasks. Today each action is free and local. Reusable mappings, batch execution, automation, and APIs will only be built when repeated demand is proven.

Important boundary

Always validate output against the destination system’s current specification. This site is independent and is not certified by a marketplace.

Questions

Before you process a file

Which WooCommerce rules are checked?

The current preflight checks UTF-8 guidance, structural parser errors, duplicate IDs and SKUs, new-product names, update identifiers, documented product types, Boolean fields, numeric fields, visibility, tax status, and variation parents.

Does a clean report guarantee the import will work?

No. Plugins, themes, server limits, custom metadata, remote images, and store configuration can still affect an import. Test a small file on staging and read the WooCommerce import log.

Why are non-comma delimiters warnings instead of errors?

WooCommerce can use a custom delimiter in Advanced options. The warning reminds you to match that setting or export a default comma-delimited CSV.