Free - No signup - Product data stays in your browser

Preflight a WooCommerce product CSV.

Check the built-in WooCommerce core schema, product identities, variable-parent relationships, images, downloads, and update intent before a small test import.

A WooCommerce core product CSV preflight checks complete local evidence before import. This private workspace separates the core importer from Product CSV Import Suite, masks product values, and blocks product-data exports until structural blockers are resolved.

01 - How it works

Review products as a relationship graph.

Variable products depend on parent identity and attribute structure. The validator checks the complete local file instead of treating each row as independent.

i. load

Open CSV or Excel

Drop a file, paste CSV, or load an imperfect or ready sample. Workbook sheet selection and parsing stay local.

ii. preflight

State schema and intent

Confirm the core importer, choose new or update intent, then review every header, row, value, and relationship finding.

iii. test

Keep relations intact

Export a normalized copy and a ten-root test that retains every locally matched variation for those roots.

02 - What it checks

Evidence before catalog mutation.

The workspace validates what a file can prove and labels every store-dependent uncertainty for manual review.

  • 01

    Core schema

    Detect core, premium-suite, hybrid, or unknown signatures; preserve duplicate headers; and limit safe fixes to exact case or outer whitespace.

  • 02

    Products and variations

    Check Name, ID, SKU, Type, Parent, variable-parent matches, attribute groups, and relationship-safe test selection.

  • 03

    Import values

    Review status and boolean tokens, tax, stock, backorders, prices, dates, dimensions, references, images, downloads, and external URLs.

  • 04

    Private handoff

    Findings and reports omit product values and filenames. Product-data exports require a blocker-free local result and preserve cell strings.

"A valid CSV is not automatically a safe catalog change."
csvtodashboard.com
Scope and handoff

Know what a local check cannot see.

The preflight never signs in to WordPress, installs a plugin, or requests an image. Store configuration and import behavior still need a controlled test.

  • No store state

    Existing IDs and SKUs, taxonomies, plugins, themes, stock, permissions, and product references are not queried.

  • No remote media check

    The tool checks URL or filename syntax only. Hosting access, redirects, media type, dimensions, and server download success remain unverified.

  • No acceptance guarantee

    Back up the catalog, use staging when possible, test intact parent relationships, inspect WooCommerce, and preserve a rollback copy.

03 - FAQ

WooCommerce product CSV questions.

Can I validate a WooCommerce product CSV before importing it?
Yes. This local preflight checks the built-in core schema, headers, row widths, product types, identities, values, variable-parent relationships, images, downloads, and import intent. It cannot query your store or guarantee acceptance.
No. WooCommerce core and the separate premium Product CSV Import Suite use different schemas. The validator detects suite and hybrid signatures, then blocks them instead of guessing a conversion.
No. Parsing, validation, masked evidence, normalization, the test batch, and reports remain in the browser tab. Image and download URLs are never requested.
Variation rows need a unique SKU and Name plus a Parent ID reference or SKU. Locally matched parents must be type variable, and attribute groups are checked for complete names, values, and flags.
It contains the first ten root or non-variation rows and every variation whose Parent matches a selected root ID or SKU. It preserves source order and cell strings.
No. The core product CSV importer can use preuploaded filenames or accessible image URLs, but its documented limitations say it cannot add, edit, or update image alt text.
There is no single core byte limit that applies to every store. The practical maximum depends on server upload and execution settings, so back up, use staging, and split large imports.
No. Local evidence cannot prove server limits, plugin or theme behavior, taxonomy, media reachability, current IDs or SKUs, stock state, or downstream acceptance.