SKU not recognised during CSV Import

The csv file is a converted json file because is from a supplier which provides only JSON or TSV files. And the TSV is very difficult to convert.

Firstly please double-check that the column header matches what you’ve used on your site.

Next, can you check that there are no hidden characters added when the file is converted?

Export a few products from the site so you can compare side-by-side, checking for spaces or anything that doesn’t look identical.

If you find something, you could try Paste Special > Values Only if you are using Excel, or paste into a text file and back again to get just the number values.

The columns match, there are not hidden characters and the codes are the same. I also tried to import directly (not updating) and it indeed imported the code in the correct position. Strangely the codes used were the same of the existing products and there wasn’t any warning about it.

I have another wordpress/woocommerce installation with the same products (but WordPress 5.0.4) that I use for testing and is working fine.

• This reply was modified 5 years, 7 months ago by glaeswer.

WooCommerce 3.6.2 is just released and includes some adjustments to CSV import behaviour. When you have a moment please backup your site, then update WooCommerce and try the import again.

Tried again…nothing has changed.

I’m slowingly resolving the issue. I’m rewriting the SKUs on the catalogue one by one.I cannot find something wrong in them and they worked in the past, but something must be wrong.

For some obscure reason this is the procedure: first I must put a letter before the SKU number, then save, delete the letter and save again.

I am having exact same problem as of the past 2 days.

I might be remembering things incorrectly, but when I get to the import log, it shows:

Product Reason for failure
SKU 273820514068 No matching product exists to update.
SKU 303135127353 No matching product exists to update.

I don’t recall the actual header SKU being in that column before on the error results (I typically just expect the actual SKU without the “SKU” prefixing it).

I have done everything exactly as I have for years when the importer was successfully used (apart from a couple months ago when I had to use the Disable Real MIME Check plugin to get around the errors about the file format).

Yes, I don’t remember what was the header before too! Anyway I resolved the problem and now is updating also the new products.