Black FridayCyber Monday 2026
15Days
08Hrs
09Mins
42Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WooCommerce

WooCommerce Product CSV Import Not Working? Fix Common Errors

Product imports fail for a few predictable reasons. Check the file format, column names, SKU matching, variations, images and server limits one by one.

wpallsolution 7 min read

WooCommerce CSV import not working usually means the product file does not match what the importer expects, or the server cannot finish the job. The importer reads a spreadsheet saved as CSV, matches its columns to product fields and creates or updates products. When rows fail, products duplicate, variations are missing or the import stops halfway, the cause is usually one of a handful of things. This guide checks them in order, starting with the import report.

Quick answer

Read the import report for failed or skipped rows first. Then check the file: UTF-8 CSV, headers that match WooCommerce’s product schema, boolean values as 1 or 0. Check the column mapping on the mapping screen. If products duplicate or do not update, use the “Update existing products” option and match by ID or SKU. For variable products, set the parent and variation rows correctly. If images fail or the import stops, check image URLs and your server’s time, memory and upload limits, and split large files.

How this guide was prepared: it is research-based. We used the official WooCommerce product CSV importer documentation listed under Sources, checked on October 23, 2026. We did not test your file or store. Importers differ between WooCommerce versions, so follow the screens you see.

How the importer works

You start it from Products → All Products by choosing Import. It reads a CSV file, maps each column to a product field (WooCommerce maps recognised columns automatically and skips unrecognised ones by default), and creates products or, if you choose, updates existing ones by ID or SKU. According to the documentation, the file should be saved as UTF-8 CSV with headers that match the product schema, dates use the store’s local time zone and boolean fields use 1 or 0. Values that hold several items are separated by commas, categories use > for hierarchy, and a comma inside a single value is escaped with a backslash.

The decision tree: why did the import fail?

Flowchart for a WooCommerce product CSV import that does not work: five questions about the report, file format, column mapping, SKU matching and variations or limits
Five questions show where the import went wrong.
  1. Report lists failed or skipped rows? Read the reasons first (Step 1).
  2. File not UTF-8 CSV or headers wrong? Fix the file (Step 2).
  3. Columns mapped to the wrong fields? Correct the mapping (Step 3).
  4. Duplicates or no updates? Match by ID or SKU with the update option (Step 4).
  5. Variations or images fail, or a timeout? Check parents, URLs and limits (Step 5).

Symptoms and likely causes

What you seeLikely causeStart with
Garbled characters or odd symbolsThe file was not saved as UTF-8Step 2
Columns are ignored or in the wrong fieldHeaders do not match the schema, or the mapping is wrongSteps 2 and 3
Products appear twice, or old ones do not changeUpdate existing products was not selected, or IDs and SKUs do not matchStep 4
Variations missing or detachedParent or type values are wrongStep 5
Import stops, or images are missingServer limits, large file or blocked image downloadsStep 5
Imported products show an unexpected statusThe Published value set the statusStep 3

5 steps to fix a WooCommerce product CSV import

Step 1: Read the import report

After the import, check the log, the import report or the failed and skipped rows report that WooCommerce provides. It tells you which rows failed and often why, such as a missing required value or a duplicate SKU. Fix those rows and re-import only them instead of the whole file.

Step 2: Check the file

Save the spreadsheet as CSV with UTF-8 encoding from your spreadsheet program; other encodings turn accents and symbols into garbage. Make sure the first row holds the headers and that the headers match WooCommerce’s product CSV schema; the easiest way to get exact headers is to export an existing product and use that file as the template. Use 1 or 0 for yes and no fields, and check dates and separators. If WordPress blocks the upload with the message “Sorry, this file type is not permitted for security reasons”, the documentation suggests uploading the file by SFTP or your host’s file manager and using the importer’s server file path option.

Step 3: Check the column mapping

On the mapping screen check that each column goes to the field you intend, or set it to Do not import. A wrong mapping can put prices into the wrong field. Pay attention to the Published column: the documentation lists an unexpected status as a common cause of products that seem missing, so check whether the products came in as drafts or private.

Step 4: Match existing products correctly

To update products instead of creating duplicates, tick Update existing products. WooCommerce then matches rows by ID or SKU. A row that supplies an ID or SKU that does not match will not fall back to another identifier. The documentation lists importing existing SKUs or IDs without selecting the update option as a common problem. SKUs must be unique, so duplicates in your file will also fail.

Step 5: Check variations, images and server limits

For variable products, the parent row must have Type set to variable and each child row Type variation, with the child’s Parent set to the parent’s SKU or id:123. Each variation needs its own unique SKU, and its attribute values must match the parent’s; see WooCommerce variations not working. For images, WooCommerce downloads each image URL into the Media Library; hosts that block requests, or require a login, can make this fail, and then you can upload the images yourself. If the import times out or stops, split a large file into smaller batches and check your server limits: memory, execution time and upload size. A plugin or theme conflict can also interfere; see how to find the plugin that broke your site.

Version and hosting differences

  • Newer WooCommerce versions add features, such as converting a simple product to variable in one import, so check your version’s documentation.
  • Limits for time, memory and upload size are set by your host.
  • Extensions that add product fields may need their own columns.

How to verify the import

  • The report shows no failed rows, or only ones you expected.
  • A sample of products has the right price, stock, category, images and status.
  • Variable products show their options on the product page.
  • No duplicates exist for the same SKU.

How to avoid import problems

Frequently asked questions

Why are my imported products drafts?

The Published value in your file sets the status. Check that column.

Why did the importer create duplicates?

You did not select Update existing products, or the IDs and SKUs did not match.

Why are variations missing?

The parent, type or SKU values are wrong. Check the variation rows and attributes.

Can I import images?

Yes, with image URLs that your server can download. If your host blocks it, upload the images manually.

What to do next

Read the report, fix the file and test with a small batch. If you need help with a large or complex import, wpallsolution offers a WooCommerce checkout service and plugin support. We cannot promise a result without seeing your file.

Sources and official documentation

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us