How to Prepare CSV for WooCommerce Import

By Online CSV Editor · Last updated: 2026-04-08

The safest way to prepare a WooCommerce CSV import is to start from the importer schema you actually use, then verify headers, SKUs, categories, attributes, variations, images, and encoding before a full upload. Most WooCommerce import failures come from product-structure mistakes rather than from CSV as a file format.

If this file is part of a broader handoff workflow, start with the CSV import and export guide. If your file still needs schema cleanup first, pair this page with how to rename CSV headers safely and how to prepare CSV for Shopify import to keep the platform-specific workflow differences clear.

Quick answer

  1. Start from a known-good WooCommerce export or the importer template you trust.
  2. Match or map headers deliberately instead of guessing from supplier column names.
  3. Verify SKUs, categories, attributes, and variation rows before touching bulk product data.
  4. Review descriptions, prices, stock values, and image URLs for quote, delimiter, and encoding issues.
  5. Export as clean UTF-8 CSV and test a small batch before a full catalog import.

What WooCommerce CSV import format really means

People often search for woocommerce csv import format as if there is one universal file shape. In practice, WooCommerce imports depend on the product schema your store expects, the importer mapping rules, and whether you are loading simple products, variable products, categories, tags, images, and custom metadata.

  • Headers need intent. Supplier or ERP column names often need cleanup before import mapping is reliable.
  • SKUs need to stay stable. Duplicate or drifting identifiers can create bad updates or duplicate products.
  • Attributes and variations need structure. Product options must remain grouped consistently so variable products import correctly.
  • Text fields need clean encoding. Descriptions, titles, and attribute values often carry quote or UTF-8 issues from copy-paste workflows.

Step-by-step: how to prepare a WooCommerce CSV import file

  1. Start with the destination schema. Use a recent successful export, the native importer format, or a plugin-specific template as your reference instead of building the file from memory.
  2. Clean the header row first. Fix naming, remove duplicates, and drop columns you cannot map confidently. If supplier headers are messy, repair them before you normalize row data.
  3. Validate identifiers and product structure. Confirm product type, SKU behavior, parent-child relationships, categories, and image fields before bulk editing descriptions or prices.
  4. Review attribute and variation columns carefully. This is where WooCommerce imports often go wrong. Make sure attribute labels, values, visibility, and variation-specific rows remain consistent.
  5. Check high-risk fields. Review prices, stock, tax class, sale dates, categories, tags, image URLs, and long descriptions for formatting damage or importer-mapping surprises.
  6. Review encoding and quoting. Product descriptions often include commas, quotes, and line breaks. Those values can be valid CSV, but only if the file stays properly quoted and is exported as UTF-8.
  7. Test a small batch. Import a few simple products and a few variable products first so you can catch mapping, variation, taxonomy, and image issues before the full catalog upload.

Common WooCommerce CSV mistakes

  • Using supplier headers without confirming how the WooCommerce importer will map them.
  • Importing duplicate SKUs or mixing update rows with new-product rows carelessly.
  • Breaking variable product structure by separating attribute and variation data inconsistently.
  • Letting spreadsheet tools reformat prices, IDs, dates, or long descriptions.
  • Uploading a full catalog before testing categories, images, and attribute mapping on a small batch.

Example: cleaning a supplier catalog for WooCommerce

Imagine you receive a supplier file with columns such as product_name, sku, category_path, color, size, price, stock, and image_link. The file opens, but it is not yet WooCommerce-ready.

  1. Map supplier headers to the WooCommerce importer schema you actually plan to use.
  2. Check that each SKU is unique or intentionally updating an existing product.
  3. Normalize categories, tags, and attribute labels before variation rows are imported.
  4. Review descriptions and attribute values for commas, quotes, and encoding noise.
  5. Spot-check prices, stock values, and image URLs before export.
  6. Run a small import covering both simple and variable products.

WooCommerce vs Shopify import prep: where people get confused

Shopify and WooCommerce both use CSV, but the product-model assumptions are different enough that you should not optimize one page for both intents. This page stays focused on WooCommerce product import formatting, while the Shopify CSV format guide stays focused on handles, variant grouping, and the Shopify product schema. If your main issue is broader import QA rather than WooCommerce itself, use the CSV import checklist.

Quick checklist before upload

  • Header names match or map cleanly to the WooCommerce importer schema.
  • SKUs and identifiers behave the way your update or create workflow expects.
  • Categories, attributes, and variations are structured consistently.
  • Descriptions, titles, and images keep valid UTF-8 text and safe quoting.
  • A small batch import succeeds before the full catalog upload.

FAQ

What format does WooCommerce want for CSV import?

WooCommerce wants a product CSV that matches the schema your importer expects, with deliberate headers, clean identifiers, and consistent product, attribute, and variation data.

Why does a WooCommerce CSV import fail even when the file opens correctly?

Because opening the file only proves the table is readable. WooCommerce importers also validate mapping, taxonomy values, product structure, images, and text encoding.

Should I test a small WooCommerce CSV import first?

Yes. A small import catches category, image, variation, and field-mapping issues before they affect the full catalog.

Do WooCommerce CSV headers need to match exactly?

The more closely they match the importer schema, the safer the result. Clear mapping prevents skipped or misinterpreted product fields.

Use Online CSV Editor before the final upload

Use the editor to review headers, SKUs, attributes, variation rows, descriptions, and image columns before you push a WooCommerce product CSV into a live store workflow.

Open the CSV editor

Canonical: https://csveditoronline.com/docs/woocommerce-csv-import-format