WooCommerce Product Import Not Working? Here’s How to Fix It

Struggling with WooCommerce product import errors? You’re not alone. Many store owners run into errors that turn a simple CSV upload into hours of troubleshooting.

If your WooCommerce product import isn’t working, the cause is almost always one of a handful of common issues, such as incorrect CSV formatting, missing SKUs, file size limits, or mapping errors. Instead of guessing what went wrong, you can identify the exact problem and fix it quickly.

In this guide, you’ll find the most common WooCommerce product import errors explained in simple terms. Just match your issue to the symptoms listed, then jump straight to the step-by-step fix to get your imports running smoothly again.

Importing products into WooCommerce can feel like a straightforward task. You upload a CSV or XML file, map the fields, and expect everything to appear neatly in your store. But in reality, a lot can go wrong behind the scenes.

Here are the most common reasons product imports fail:

1. File Formatting Mistakes (CSV/Excel Issues)

Even the smallest error in your CSV file can cause big problems. A misplaced comma, merged cells from Excel, or incorrect text encoding might prevent WooCommerce from reading the file properly. 

If the structure doesn’t match what WooCommerce expects, the import may stop halfway or skip products entirely.

2. Incorrect Field Mapping

When importing, WooCommerce asks you to match the columns in your CSV with product fields (like SKU, Name, Price, Stock). If these are mapped incorrectly, say, a SKU column linked to “Product Name”, the result can be products with missing information or details in the wrong place.

3. Missing or Invalid Data

Some product fields, such as SKU, price, or stock, are critical. If these values are missing, left blank, or contain invalid data (e.g., letters where numbers should be), WooCommerce may reject those products or create incomplete records. This can also happen with dates, email addresses, or image URLs that don’t follow the correct format.

4. Plugin or Theme Conflicts

Sometimes, the issue isn’t with your data at all but with your site setup. Other plugins or themes may interfere with the import process, causing unexpected behavior or errors. For example, a custom product field added by another plugin may not align with your CSV data.

5. Server Limitations (Memory, Timeout Issues)

Large product catalogs can push your server to its limits. If your hosting environment has strict memory or execution time limits, imports may fail partway through, leaving you with incomplete product data. This is especially common for stores with thousands of SKUs or very large images.

A. File & Formatting Errors

1. Special Characters Showing as Symbols (’, �) After WooCommerce Import

Special characters (like accents, umlauts, or non-English letters) appear as gibberish symbols (� or strange characters) after import.

Why it happens: WooCommerce expects CSV files to be saved in UTF-8 encoding, but many spreadsheet editors, especially Microsoft Excel, default to other encodings, which corrupt special characters.

Fix:

• Re-save your CSV file in UTF-8 format using a reliable editor such as Google Sheets, Notepad++, or VS Code.
• Avoid saving CSVs directly from Excel, or if you must, use “CSV UTF-8 (Comma Delimited)” as the export option.

2. WooCommerce Import Failing or Creating Blank/Incomplete Products

When attempting to import your CSV file, WooCommerce throws an error saying certain fields are missing, most commonly: post_title → Product Name, sku → Stock Keeping Unit (unique product identifier), post_content → Product Description.

As a result, the import either fails entirely or creates incomplete products that don’t display correctly in your store.

Why it happens: WooCommerce requires specific core fields to identify and create products. If they are empty or mapped incorrectly, the system doesn’t know how to process the row.

Fix:

• Double-check that all required fields are present in your CSV.
• Make sure each row has a product name (post_title), unique SKU, and basic content (post_content).
• During import, map CSV columns correctly to WooCommerce fields.
  

3. Product Titles or Descriptions Getting Cut Off or Split During Import

When you import a CSV file, product descriptions or titles that contain commas (for example:

A durable, waterproof bag) doesn’t stay in one column. Instead, they get split into two or more columns, which scrambles the entire row. The result? Products imported with broken or missing descriptions, or the whole import may fail.

Why it happens: CSV files use commas as column delimiters. If a comma is inside the text itself, it tricks the importer into treating it as a new column.

Fix:

• Always enclose fields with commas inside double quotation marks (“ ”).
• Example: “A durable, waterproof bag” will stay in one column.

4. Products Importing Into Wrong Categories or Attribute Dropdowns Showing Empty

After import, products don’t show up under the correct categories, or variation dropdowns fail to display properly. Sometimes products appear uncategorized, or attributes (like size or color) don’t connect to the variations you created in the CSV.

Why it happens: WooCommerce relies on exact matches between your CSV and its internal taxonomy (categories and attributes). If your CSV uses slightly different labels, slugs, or hierarchy, WooCommerce won’t know where to place the product.

Common causes include:

• Using category names instead of slugs in the CSV.
• Misspelled or differently capitalized attribute values (red vs Red).
• Forgetting to set up attributes (Size, Color, etc.) in WooCommerce before import.
• Incorrect formatting for multiple categories or nested categories.

Fix:

• Match Category Slugs Exactly. WooCommerce stores categories by slugs (the lowercase, hyphenated version of the name).
  

Example:

• Category Name: Men’s Shoes
• Category Slug: mens-shoes

• Use Hierarchical Category Format. For subcategories, use a > separator.
• Match Attribute Values Exactly. Attribute values in the CSV must be identical to WooCommerce terms (including capitalization).

Example:

If the attribute is “Red” in WooCommerce, don’t use “red” or “RED” in the CSV.

Format Attribute Columns Properly: Use WooCommerce’s expected header format:

• Attribute 1 name → Size

• Attribute 1 value(s) → S, M, L

5. Product Prices Showing as Zero or Dates Appearing Blank After WooCommerce Import

During import, you may encounter several issues. Product prices may appear incorrect, dates like “12/05/25” may not map correctly, leading to blank fields or date misinterpretation, or customer or order email fields may throw errors, preventing those records from being imported.

These errors often don’t crash the import entirely, but lead to incomplete or inaccurate data once products or users are in WooCommerce.

Why it happens: WooCommerce expects values in very specific formats. If your CSV contains extra symbols, inconsistent formats, or invalid entries, the importer either ignores the data or misplaces it.

• Prices: WooCommerce only accepts raw numbers. Adding currency symbols ($20, €15) or formatting (e.g., 20.00 USD) causes issues.
• Dates: WooCommerce uses the ISO format YYYY-MM-DD. If your CSV uses DD/MM/YYYY or MM-DD-YY, the importer won’t recognize it.
• Emails: Invalid formats (missing @ or domain, e.g., user@domain) break the import for customers or orders.
  

Fix:

• Keep numeric values clean: Use 20 instead of $20. Stick to decimals for prices: 19.99 (no currency code, no commas).
• Use the correct date format: Always enter dates as YYYY-MM-DD. Example: 2025-09-10 (not 09/10/25 or 10-Sep-25).
• Validate email addresses: Ensure every email has the correct format (e.g., [email protected]). Avoid placeholder or malformed values like customer[at]example.com.
  

B. Server & Performance Issues

1. WooCommerce Import Stops Halfway or Shows “Maximum Execution Time Exceeded

The import process stops abruptly with errors like “Internal Server Error” or “Maximum execution time exceeded.”

Why it happens: Large CSVs with thousands of products consume high memory and processing power. If server limits are too low, the process times out.

Fix:

• Split your CSV into smaller files (e.g., 50–100 products per batch).
• Increase server limits by editing php.ini or asking your host:
  
• memory_limit = 256M or higher
• max_execution_time = 300 seconds or more

• Use plugins with batch processing to handle imports in chunks.

2. WooCommerce CSV Upload Fails Immediately or Nothing Happens After Selecting File

The import fails before it even starts. You upload your CSV file, but instead of processing, WooCommerce shows an error, or nothing happens at all.

Why it happens: Most web servers limit the maximum size of files that can be uploaded through PHP. By default, this limit can be as low as 2MB – 8MB, depending on your hosting provider. If your product CSV file exceeds 20MB, the upload will be blocked before WooCommerce can even read it.

Large file sizes usually occur when:

• You’re importing thousands of products in one CSV.
• The file includes high-resolution image URLs or lengthy product descriptions.
• Supplier-provided catalogs are bulk exports that aren’t optimized for WooCommerce.

Fix:

• Increase the upload_max_filesize and post_max_size values in your php.ini.

Example:

upload_max_filesize = 64M

post_max_size = 64M

• Alternatively, compress the file or split it into smaller CSVs.
  

C. Data & ID Conflicts

1. WooCommerce Import Overwriting Existing Products or Showing “ID Conflicts With Existing Post”

During import, the log shows messages like: “Importing (ID) conflicts with an existing post.” This usually means WooCommerce is trying to assign a product to an ID that’s already in use by another product, page, or post in WordPress.

Why it happens: WordPress assigns a unique ID to every piece of content products, pages, blog posts, and even media files. These IDs are stored in the database and can’t be duplicated.

When your CSV includes a column for ID:

• If the value matches an existing post/product ID, WooCommerce assumes you want to update that entry.
• If you’re actually trying to add new products, this causes a conflict because WooCommerce attempts to overwrite an existing post instead of creating a fresh product.

This issue is common when:

• Migrating products from one site to another where IDs differ.
• Using supplier CSV files that include IDs irrelevant to your store.
• Forgetting to remove the ID column when creating a new import.

Fix:

• For new imports, remove the ID column and let WooCommerce assign unique IDs.
• For updates, use SKU as the unique identifier instead of ID.
  

2. WooCommerce Import Skipping Rows or Updating the Wrong Products

When importing your CSV file, some products fail to import, or existing products don’t update as expected. You may notice skipped rows in the log or overwritten product data.

Why it happens: WooCommerce uses the SKU (Stock Keeping Unit) as a unique identifier for each product and variation. If two or more products share the same SKU:

• The importer can’t decide which product to update.
• A new product might overwrite an existing one.
• Variations may not link correctly to their parent product.
  

This often occurs when:

• Supplier files recycle the same SKUs across multiple product lines.
• You copy/paste rows when building your CSV and forget to change the SKU.
• Variations are listed without unique SKUs, sharing the parent product’s SKU.
  

Fix:

• Review your CSV and ensure every row has a unique SKU.
• Use an SKU generator tool if necessary.
  

D. Variation & Attribute Import Problems

1. WooCommerce Product Variations Importing as Separate Individual Products

Instead of being grouped under a single variable product, variations (like Size S, Size M, Size L) import as separate simple products. This clutters the catalog, confuses customers, and makes it harder to manage inventory.

Why it happens: WooCommerce uses a parent–child relationship to link variations to their variable product. If your CSV doesn’t define this relationship properly, the importer assumes each variation is a standalone product.

Common causes:

• Missing parent product row in the CSV.
• Variation rows don’t include the correct parent reference (ID or SKU).
• Incorrect product type values (simple used instead of variable/variation).

Fix:

• Include a parent product row with type = variable.
• Each variation row should have “type = variation” and a matching parent_sku pointing to the parent product.
  

2. Size, Color, or Other Attribute Dropdowns Missing or Empty After Import

After importing products, the variation dropdowns (like Size or Color) are empty, or attributes don’t display at all on the product page. Variations may exist in the database, but aren’t linked properly, leaving customers unable to select options.

Why it happens: WooCommerce requires attributes to be defined and consistent across the database and the CSV. If the data in your file doesn’t align with WooCommerce’s predefined attributes, the system fails to connect them.

Common causes:

• Attributes (like Size or Color) don’t exist in WooCommerce before import.
• Incorrect column header format in the CSV (e.g., Size instead of Attribute 1 name).
• Attribute values in the CSV don’t exactly match the terms in WooCommerce (red vs. Red).
• Variations are imported without the correct attribute assignment.

Fix:

• Make sure the attribute exists in WooCommerce (go to Products → Attributes).
• Format CSV columns properly, e.g., Attribute 1 name and Attribute 1 value(s).
• Ensure attribute values match exactly (spelling, capitalization) with the terms in WooCommerce.
  

E. Image Import Failures

1. WooCommerce Product Images Not Showing After Import

Your CSV imports successfully, products appear in the catalog, but no images show up. The featured image slot is blank, or galleries are missing, even though the CSV contains image links.

Why it happens: WooCommerce fetches images during import based on the URLs provided in your CSV. If those URLs are broken, incorrect, or inaccessible, the importer cannot download and assign them.

Common causes include:

• Broken URLs: Image links don’t exist or point to a deleted file.
• Incorrect file paths: Relative paths (e.g., /images/product1.jpg) instead of full URLs.
• Private or restricted sources: Images are hosted on a server that requires login or is blocked by a firewall/CDN.
• Slow/large image files: The import times out before images finish downloading.

Fix:

• Test each image URL in a browser to confirm accessibility.
• Ensure the server’s firewall isn’t blocking external requests.

2. Featured Image or Gallery Photos Blank After WooCommerce Product Import

Products are imported successfully, but only a single image shows up. Even if your CSV lists multiple image URLs, WooCommerce only pulls in the first one. As a result, the featured image appears, but the product gallery is empty.

Why it happens: WooCommerce (and most import/export plugins) expects multiple image URLs to be separated by a specific delimiter. If the wrong separator is used or if URLs are incorrectly formatted, the importer only processes the first image and ignores the rest.

Common mistakes:

• Using spaces instead of separators.
• Mixing commas (,) and pipes (|) inconsistently.
• Forgetting to enclose multiple URLs in quotes.

Fix:

• Use the correct delimiter. Separate multiple image URLs in your CSV with the correct delimiter (commonly a comma (,) or a pipe (|), depending on the plugin).

The first URL should be the featured image, and the rest will be gallery images.

Importing products doesn’t have to be stressful. A few smart habits can save you hours of frustration and keep your store data clean and consistent. Here’s what to keep in mind:

1. Always Start With a Sample CSV From WooCommerce or Your Plugin

Instead of creating your file from scratch, download a sample template first. This way, you’ll have the correct column headers and formatting right from the beginning. Just copy your product details into the file, and you’ll avoid many common mistakes.

2. Use Consistent SKUs Across All Systems

Think of SKUs as your product’s fingerprint. They need to be unique and consistent across your store, supplier feeds, and marketplaces. If two products share the same SKU, WooCommerce won’t know which one to update, and that’s when problems start.

3. Clean Your Data Before Exporting to CSV

Before you hit the import button, spend a few minutes in Excel or Google Sheets cleaning up your data. Remove extra spaces, make sure prices are numbers (not “$20”), and check that categories and attributes match what you already have in WooCommerce. A little preparation here goes a long way.

4. Automate Regular Imports

If you work with suppliers or frequently update large catalogs, don’t do everything manually. Set up scheduled jobs, so WooCommerce can automatically pull in updated product data at regular intervals. This keeps your store fresh and saves you from repetitive tasks.

5. Use a Reliable Import-Export Plugin

WooCommerce’s built-in importer is handy, but for bigger stores, you’ll want more power. A plugin like WebToffee’s Product Import Export for WooCommerce gives you advanced filters, batch processing, error handling, and even scheduling, everything you need to keep imports smooth and stress-free.

Product imports don’t have to be a nightmare. Yes, errors like duplicate SKUs, broken image links, or category mismatches can derail your workflow, but now you know exactly how to prevent and fix them. Most issues come down to a few simple mistakes, and with the right preparation, you can avoid them altogether.

Think of it this way: once you set up your process with clean data, consistent SKUs, and the right tools, imports become fast, predictable, and stress-free. Instead of dreading CSV uploads, you’ll know your products will land in WooCommerce exactly as intended.

The best part? You don’t have to do it all manually. With a reliable solution like WebToffee’s Product Import Export Plugin for WooCommerce, you get advanced filters, scheduling, batch processing, and built-in error handling, all designed to take the guesswork out of imports.

We hope this guide has given you clear insights into the most common WooCommerce product import issues and practical ways to prevent them before they cause headaches.

Got questions or stuck on a tricky import? Drop your comments below. We’re always happy to help and guide you through the process.

Thanks for reading, and here’s to smoother, error-free imports for your store!