Most WooCommerce product import CSV problems start because the CSV file isn’t formatted the way WooCommerce expects. A CSV treats commas as separators — meaning every comma tells WooCommerce to move to the next column.

So if your product description has a comma like this:

A stylish, modern lamp

WooCommerce doesn’t see it as one sentence. It sees:

• “A stylish” → one column
• “modern lamp” → another column

This pushes information into the wrong place and breaks the import.

The fix is simple: Wrap descriptions with commas inside quotes:

“A stylish, modern lamp”

This tells WooCommerce to treat it as one piece of text.

WooCommerce​‍​‌‍​‍‌​‍​‌‍​‍‌ importer asks you to “map” each column to the proper product field when you import CSV in WooCommerce. This is basically giving WooCommerce a description of what each column contains – for instance, which column has the product name, which one is the SKU, which one is the price, and the like.

Just one column being mapped wrongly in a WooCommerce CSV import, results in WooCommerce putting the data there which is not the correct place.

Here’s​‍​‌‍​‍‌​‍​‌‍​‍‌ a straightforward method to understand it:

Imagine your CSV file contains a column named “Item Name”, however, when importing, you wrongly allocated a mapping from “Short Description” instead of “Product ​‍​‌‍​‍‌​‍​‌‍​‍‌​‍​‌‍​‍‌​‍​‌‍​‍‌Name”.

WooCommerce will then import:

• Your product name → into the description box
• The actual product name field → stays empty

As a result, you might see products with:

• Missing names
• Wrong descriptions
• No prices
• SKUs placed in the wrong field

Another common example:

If you map your “SKU” column to something else by mistake, WooCommerce may think you are updating existing products — and end up editing the wrong items.

Why this happens:

Many CSV files use different column names like:

• “Product Title”
• “Name”
• “Item Name”
• “Product_Name”

It​‍​‌‍​‍‌​‍​‌‍​‍‌ means that during mapping one can easily click the wrong option.

Basically, if your fields are not mapped properly, WooCommerce will be unaware of the place where it has to put the data hence this process will result in imported products with missing or mixed-up ​‍​‌‍​‍‌​‍​‌‍​‍‌details.

In​‍​‌‍​‍‌​‍​‌‍​‍‌ order to create a product correctly, WooCommerce requires certain pieces of information when a WooCommerce import products process is carried out. If the product name, SKU, price, or stock are among the most crucial pieces of information that are missing or in an incorrect format, the importer doesn’t know how to handle the data, hence it may be the case that the product is skipped, the fields are left blank or the operation fails without a visible ​‍​‌‍​‍‌​‍​‌‍​‍‌error.

Think​‍​‌‍​‍‌​‍​‌‍​‍‌ of it as completing a form:

Not being able to leave the “Name” part empty or writing something strange in the “Price” box, the form will not allow that.

Common examples of invalid or missing data:

• Absent SKU: The SKU is the single identification of the product. If it is not there, WooCommerce does not understand how to create or update a product, so it can just omit the ​‍​‌‍​‍‌​‍​‌‍​‍‌line.
• Blank product name: A product must have a name. If the “Product Name” field is missing, WooCommerce cannot show it in your store and usually, it rejects that line of the file.
• Price written as “$599” instead of “599”: WooCommerce is a system that only allows numbers for the price field. If there are symbols like ₹, $, or commas, WooCommerce cannot handle them, so the price is left empty after the import takes ​‍​‌‍​‍‌​‍​‌‍​‍‌place.
• Stock written as “ten” instead of “10”: The stock field must be a number. Writing words like “ten,” “in stock,” or “available” confuses WooCommerce, and it may treat the stock value as zero or ignore it completely.
• Invalid URLs: When an image URL is broken, is incorrectly spelled, or points to a private page, WooCommerce is unable to fetch the image. As​‍​‌‍​‍‌​‍​‌‍​‍‌ a result, your product is either imported without a featured image or with a gallery that has no images.

Here’s a simple real-life scenario:

If your CSV shows:

SKU: blank

Price: ₹1200

WooCommerce reads:

• No SKU → product can’t be created
• Price with symbol → price field becomes empty

So the product either fails to import or appears in your store with missing values.

Simply​‍​‌‍​‍‌​‍​‌‍​‍‌ put, WooCommerce requires data that is not only clear but also consistent in order to be able to carry out the importing of products from a CSV file in a seamless manner. So, if there are product details that are of great importance but are missing or are not formatted properly, a tiny thing such as an additional space or a symbol can make the WooCommerce importer to fail in reading the row properly, hence the cases of products being skipped or uploaded with incomplete data are the most common ​‍​‌‍​‍‌​‍​‌‍​‍‌outcomes.

Sometimes​‍​‌‍​‍‌​‍​‌‍​‍‌ it happens that a WooCommerce CSV import simply doesn’t fail due to the CSV file, but it is the website server that cannot handle the size of the file you are uploading and thus, the import fails. So each time you import products, WooCommerce must have enough memory and time to open your whole CSV file, process every row, download images, and create products in your database. If you have a restricted hosting plan, your server may be out of resources during the import process and thus, it will ​‍​‌‍​‍‌​‍​‌‍​‍‌stop.

What this looks like in a real scenario:

• Your import freezes halfway
• The page suddenly goes blank
• You get errors like “500” or “503”
• WooCommerce stops at a certain percentage and won’t continue
• Only some products get imported, not all

This​‍​‌‍​‍‌​‍​‌‍​‍‌ is most of the time a consequence of low PHP limits like memory, upload size, or execution time. There are usually heavy restrictions on shared hosting plans, and thus, when a CSV file contains thousands of rows or has long image URLs, the server is unable to complete the work within the allowed ​‍​‌‍​‍‌​‍​‌‍​‍‌time.

For Example:

What generally happens if a user of the WooCommerce platform tries to import a CSV file from a local file of 20MB that has 3,000 products while hosting it on a simple plan? Maybe the server will execute the operation for only the first few hundred products but later it becomes unresponsive.

In brief: when your server runs out of space, memory, or processing time, WooCommerce will not carry out the import to completion even if your CSV file is ​‍​‌‍​‍‌​‍​‌‍​‍‌flawless. Most of the time, it is a matter of upgrading your PHP limits or splitting your import into smaller batches, which thereby resolves the issue quite fast.

Should these problems appear too overwhelming and lengthy to you, there is always the option to hire WooCommerce developers who would be able to assist you in quickly resolving import errors and setting up a smoother ​‍​‌‍​‍‌​‍​‌‍​‍‌workflow.

Simply​‍​‌‍​‍‌​‍​‌‍​‍‌ put, the majority of those who operate stores and encounter difficulties with a WooCommerce product import or a WooCommerce CSV product import find that the source of their problem is the CSV file. To the letter, WooCommerce demands that every row, column, and value be formatted in a particular way and if you happen to have a tiny error in your file, then it is quite possible that you will have missing data, incomplete imports, or skipped products.

The first portion of the locally available issues which are present in the CSV data that causes you to run into trouble when you try to import CSV in WooCommerce is provided below along with easy and clear explanations for you to be able to repair ​‍​‌‍​‍‌​‍​‌‍​‍‌them.

Should there be any product information file that is saved in a format other than UTF-8, then, the product names or descriptions placed in WooCommerce may show different characters that one may not be used to seeing. Such characters may include the letter é, ü, or even the emojis that are shown as � or other arbitrary figures. Another example could be 8,, or 5,.

For Example: 

Normal text in your sheet:

Café Latte

Imported into WooCommerce as:

Caf� Latte

Why it happens:

Some spreadsheet tools save your file in older encodings (like ANSI), and the WooCommerce importer can’t read those characters correctly.

Quick solution:

• To​‍​‌‍​‍‌​‍​‌‍​‍‌ be able to re-save the whole file just like in UTF-8 format, your choices are either Google Sheets or Notepad++.
• It is good practice not to export a CSV file from an Excel version that is older than the one that has been recommended.

WooCommerce needs certain columns to be clean and complete before it can process them. If these fields are missing or blank, the importer may skip the row or create broken products.

Fields that cause issues when missing:

• Product Name → WooCommerce doesn’t know what to display
• SKU → WooCommerce can’t identify the product
• Price → Product appears with a blank or zero price
• Product Type → WooCommerce doesn’t know if it’s simple, variable, etc.

For Example:

Row in your CSV: T-shirt, , 599 

WooCommerce does not know how to arrange or follow the product when the SKU field is empty. Therefore, the row might be ignored.

Why this matters:

SKU and product name act like “identifiers.” If they are missing, WooCommerce can’t create a proper product entry.

Easy Fix:

• Fill in every product name
• Make sure every SKU is unique
• Use only plain numbers (no extra characters)

This ensures WooCommerce can read and create each product correctly.

A CSV file treats commas as separators. So if your product description contains a comma but isn’t wrapped in quotes, your entire row gets shifted into the wrong columns.

For Example:

Description in CSV: A stylish, modern lamp

WooCommerce reads this as two separate fields unless it’s written as:
 “A stylish, modern lamp”

One tiny comma can move everything to the wrong place and break your WooCommerce CSV import and break your import.

Quick solution:

• Wrap descriptions with commas inside quotes.
• Remove unnecessary line breaks inside cells.

WooCommerce expects clean, consistent values. Anything outside the accepted format can break the import or give you incomplete products.

Common formatting mistakes:

• The point of using dates like 10-05-25 instead of 2025-05-10
• Writing stock as “ten” instead of “10”
• Adding broken or private image URLs

Why this matters:

The WooCommerce CSV product import system reads data literally. Without a proper match between the value and what WooCommerce needs, the system will either skip the field or take the wrong import of it.

Quick solution:

• Use plain numbers for price and stock
• Make use of the date format that is universally accepted in “YYYY-MM-DD” format
• Test image URLs in your browser before importing

When you import CSV in WooCommerce or handle a large WooCommerce product import, your website needs enough power to read the file, process every row, download images, and create products. If your hosting plan doesn’t give your site enough memory or time to finish that job, the import can suddenly stop — even if your CSV is perfectly fine.

What this looks like to a normal user:

• The import freezes at 10%, 20%, or 50%
• You get a blank white screen
• The import page refreshes by itself
• Only half your products show up
• Errors like “500”, “503” or “Maximum execution time exceeded” are the types to be in view.

In most cases, your file is almost perfect, but the reality is that the server is limited in ‘space’ or ‘power’ to carry on with the operation.

Let’s say you gave an enormous pile of documents to a person to sort but allowed him only 10 seconds for the task. The person will manage to sort out only half of the work and then he will stop because the time is up. It is analogy with the lack of WooCommerce memory or representing overcoming of execution time.

It is exactly the same case when WooCommerce lacks the memory or execution time.

Why it happens:

Most basic hosting plans have strict limits on:

• How much memory your site can use
• How long it can run a task
• How large your uploaded files can be

Large CSVs with thousands of products or image URLs overwhelm these limits.

How you can fix it:

• Split your import into smaller CSV files (100–300 rows each)
• Ask your hosting provider to increase PHP memory and execution time
• Upgrade to a slightly better hosting plan if you regularly import large files

In short, if your WooCommerce import suddenly stops or freezes, it’s usually because your server doesn’t have enough resources and not because your CSV is wrong.

To​‍​‌‍​‍‌​‍​‌‍​‍‌ differentiate between various products after a WooCommerce import, the platform relies on elements such as SKUs and product IDs in the CSV file. In case these identifiers are absent, duplicated, or misdirected, the importer will be confused and thus, it can happen that items are skipped, existing products are overwritten, or variations are created incorrectly.

The​‍​‌‍​‍‌​‍​‌‍​‍‌ typical problems in this category are repeated SKUs, conflicting product IDs, and variations that are not correctly linked to their parent product. These issues can definitely mess up your import, however, they are easy to avoid once you familiarize yourself with ​‍​‌‍​‍‌​‍​‌‍​‍‌them.

In​‍​‌‍​‍‌​‍​‌‍​‍‌ WooCommerce, it is mandatory to have a unique SKU for each product. When there are two products with the same SKU, WooCommerce during the import, confuses the files and as a result, the rows are skipped, products are overwritten, or variations are getting imported ​‍​‌‍​‍‌​‍​‌‍​‍‌wrongly.

Simple example:

Imagine your CSV has these two rows:

• Row 1 → SKU: TSH-001
• Row 2 → SKU: TSH-001 (same as above)

Both products are using the same SKU, even though they are two different products.

WooCommerce now has two products with the same “identity.” And since it can’t understand which one is new or which one should be updated, it may:

• Skip the second row
• Replace the first product with the second
• Or import both with errors

Why this happens:

Duplicate SKUs often show up when:

• You copy/paste product rows
• Supplier files reuse SKUs across different product lines
• Variations share the same SKU as the parent product
• You import old data that already exists on your site

That is the important thing how you can get things right:

• Be aware of the fact that every product should have a different SKU
• Adopting an SKU pattern similar to TSH-001, TSH-002, TSH-003 is a brilliant choice
• Each variation should have an individual SKU (do not use the parent SKU)
• Use spreadsheet filters to quickly find duplicates before importing

In short, if two products share the same SKU, WooCommerce won’t know what to do with them which then leads to missing, overwritten, or incorrectly imported products. Keeping SKUs unique fixes the problem instantly.

In​‍​‌‍​‍‌​‍​‌‍​‍‌ WordPress each product has a number that is not visible to you directly and this number is called ID. It is something that you normally do not see, and there is no need for you to worry about it unless you have an ID column in your CSV file.

Why​‍​‌‍​‍‌​‍​‌‍​‍‌ does this happen to be a problem:

If the CSV file which you are uploading to WooCommerce has product IDs that refer to the products that are already in your WooCommerce site, the importer does not know what to do. It sees that you want to update those products that already exist with the new data from the CSV file whereas actually, you want to create new ones.

Therefore, WooCommerce may be updating a product that already exists with old data from the CSV file instead of making a new ​‍​‌‍​‍‌​‍​‌‍​‍‌product.

For explanation with a simple example:

Your current site already has:

• Product ID 25 → “Blue Sneakers”

Your CSV also has a row with:

• ID 25 → “Formal Shoes”

WooCommerce will think: The ID is the same for both, which means the user wants to update the Blue Sneakers product.

And hence it overwrites “Blue Sneakers” with “Formal Shoes.”

Why this happens: 

ID conflicts usually occur when:

• You export products from one website and import into a new one
• You forget to delete the “ID” column from the CSV
• Supplier data contains their internal product IDs
• You re-import older backup files

Here’s how you can fix it:

• Remove the ID column completely if you’re adding new products
• Only keep IDs if you’re intentionally updating existing items
• Rely on SKUs instead, as they are safer and more reliable for updates

And hence, if your CSV contains ID numbers that already exist on your website, WooCommerce may overwrite the wrong products. Removing the ID column is the easiest and safest solution when importing new items.

Variations are one of the trickiest parts of a WooCommerce product import or import products WooCommerce CSV process. One​‍​‌‍​‍‌​‍​‌‍​‍‌ of the most frequent problems that store owners encounter is that if the data is not formatted in the exact manner that WooCommerce requires, your variations may fail to connect to their parent product, be displayed as separate items, or even show with missing ​‍​‌‍​‍‌​‍​‌‍​‍‌sizes/colors.

The good news? Once you understand how WooCommerce connects variations to the main (parent) product, this becomes very easy to fix.

If,​‍​‌‍​‍‌​‍​‌‍​‍‌ for instance, you bring in variable products (T-shirts with S, M, L sizes) that differ then WooCommerce needs a way to connect each variation to the parent product. A scenario where the link is missing or faulty leads WooCommerce to change the variations into individual simple products thus they are shown separately on the shop page instead of being grouped under one ​‍​‌‍​‍‌​‍​‌‍​‍‌product.​‍​​‍​‌‍​‍‌​‍​‌‍​‍‌

What this looks like to a store owner:

• Variations show up as separate products (“T-shirt – Size M”, “T-shirt – Size L”)
• The main product doesn’t display any size or color options
• Some variations don’t import at all
• “No attributes found” error during import
• Drop-down options (Size/Color) don’t show on the product page
  

Simple example to understand this:

Let’s say you have a parent product called: “Cotton T-Shirt”

And three variations:

• Cotton T-Shirt (of Size S)
• Cotton T-Shirt (of Size M)
• Cotton T-Shirt (of Size L)

For these to import correctly, WooCommerce needs:

• One row that represents the parent product
• Additional rows for each variation
• A matching reference (usually parent SKU) that tells WooCommerce:  “These variations belong to this main product.”

If the parent SKU is missing or typed differently in the variation rows, WooCommerce can’t connect them.

Why this happens:

• The parent product row is missing
• Variation rows don’t include the correct parent SKU or parent ID
• Variation product type is set to “simple” instead of “variation”
• Attribute values don’t match exactly (e.g., “L” vs “Large”)
• Attributes are not created in WooCommerce before import

A link can be broken even with a minor mismatch (extra space, wrong letter, difference in case).

How to fix it:

• First of all, ensure that each item is equipped with a singular SKU that is not shared with any other product.
• Each variation row must use type = “variation”
• Add a “parent_sku” column that matches the parent product exactly
• Attributes (like Size or Color) that are used in WooCommerce must be confirmed to exist beforehand
• Always write attribute values in the same form and manner in every row (M ≠ m ≠ ​‍​‌‍​‍‌​‍​‌‍​‍‌Medium).

This is the case, for example, when WooCommerce cannot establish a direct connection between the variation rows and the parent product that it numbers them as individual objects.

Product images can also cause issues in a WooCommerce CSV import even if your product data is flawless. Due to the necessity for WooCommerce to access every image through the provided URL, a tiny problem, such as a broken link or a slow server, might result in the image being unable to load. During the imports, this is one of the mainly faced problems by shopkeepers.

When importing products, WooCommerce reads the image URLs from your CSV and tries to download each one. If anything goes wrong during that process even something small the image won’t appear on your product page. The product will be imported, but the picture will be missing.

What this looks like to a store owner:

• The product shows up without a featured image
• Gallery images are missing
• Placeholders or blank image boxes appear
• The import completes but with warnings
• Only a few images import while others fail

Simple example:

In your CSV, your image field looks like this:

https://example.com/images/blue-shirt.jpg

If this link is broken, moved, private, or slow to load, WooCommerce can’t download the file. So the product imports are like this:

• Name: Blue Shirt
• Price: 599
• Image: missing

Even though the CSV is correct, the image doesn’t appear because WooCommerce couldn’t access the URL.

Why this happens:

• The image link doesn’t exist anymore
• The link is misspelled or incomplete
• The image is on a private server or blocked by a firewall
• The​‍​‌‍​‍‌​‍​‌‍​‍‌ image file is huge and hence the operation is getting timed out during downloading
• The CSV has the relative path rather than the absolute URL
• The server that is hosting is running slowly or is ​‍​‌‍​‍‌​‍​‌‍​‍‌overloaded

How to fix it:

• Always test a few image URLs in your browser as they should open instantly
• Use full, direct URLs (e.g., https://domain.com/image.jpg)
• Avoid very large image files (compress them before import)
• Make images publicly accessible (no login or password needed)
• If migrating from another WooCommerce site, upload images to the new site first instead of pulling them remotely

Hence, if WooCommerce can’t open or download an image from the link in your CSV, it will import the product without it. Ensuring correct, accessible URLs and reasonable image sizes fixes most image import problems.

WooCommerce product imports can feel overwhelming, especially when a tiny formatting issue or a hidden CSV mistake brings the whole process to a stop. As you’ve seen throughout this guide, most import errors come down to a few predictable problems such as mismatched fields, missing data, server limits, broken image URLs, or variation links that are not set correctly.

Once you understand why these issues happen, everything becomes much easier. Basic​‍​‌‍​‍‌​‍​‌‍​‍‌ actions such as putting the description in quotation marks, verifying SKUs, tidying up your data, or dividing a big CSV file into smaller files can be your next WooCommerce CSV import will go perfectly smoothly without you having to make any manual operations.

Have this manual as a speedy control list of readiness when you work with ​‍​‌‍​‍‌​‍​‌‍​‍‌CSV. It helps you avoid most common errors long before they appear. And if you ever face complex challenges such as large catalogs, advanced variations, or tricky migrations, know that expert help is available whenever you need it.