Difficulty Running Product Import Process
Bruce Paine
Dear Joomshaper Support team,
Software Versions:
Joomla: 5.x SP Page Builder Pro: 5.x (Latest Version) Site template: shaper_helixultimate EasyStore: Latest Version Environment: Local MAMP (PHP 8.1+) Joomla 5.4.3 EasyStore 1.7.7 PHP 8.3.14
I am a new user of the full JoomShaper suite.
I have spent a day or so trying to make the EasyStore product import work. However, despite all my efforts it keeps failing with the error message:
"Import Failed! There might be some problem with the CSV file structure"
I have tried everything I can think of including:
- Importing the sample products - which works AOK.
- Taking a copy of the sample csv file, replacing the data with my own - that does not work.
- Comparing fields one at a time to find and correct any differences.
- Checking there are the same number of fields, same column headings, csv utf-8 format with and without BOM, quoted data, leaving the final field "END" unquoted as in the sample data.
- Simplifying product descriptions and ensuring collections and categories exist (even though I understand they are automatically added if missing)
- Single product import vs multiple without success.
Despite my efforts the import continues to fail.
I have years of experience working with csv files and data import processes. I'm aware of the precision needed when setting up data for import. It is often easy to miss obvious mistakes in the data. I have rarely been beaten by an import system but this one is really testing me!
I have reached a point where I have run out of options and so I turn to JoomShaper support.
I’ve seen a related post from a year ago but decided to create a new one as as I assume there may have been updates or changes since then.
I am sharing a copy of my csv test data (just one record - see link in hidden copy) and the related media webp file. I have reduced this to a single-product CSV which fails, while the unmodified sample CSV imports successfully. This should allow your team to reproduce the issue easily.
Could you please confirm the exact CSV requirements for EasyStore import, including:
- Whether all field values (including numbers and empty fields) must be quoted
- Whether UTF-8 BOM is required or optional
- Any restrictions on HTML content within fields
- Whether there are required hidden/system fields beyond those shown in the sample CSV
It's critical that we are have an import process that works to help migrate products and reduce manual entry as much as possible. I’d really appreciate your guidance on whether this can be resolved, as a reliable import workflow is essential for us.
Kind regards,
Bruce
Ziaul Kabir
Accepted AnswerHi Bruce,
Thank you for your detailed follow-up and for sharing your findings — we really appreciate the time and effort you’ve put into investigating this.
You are absolutely correct: • The CSV file name must be exactly easystore_products.csv • The file must use Unix (LF) line endings, as CRLF can cause the import to fail
We also agree that the current error message can be misleading, as it suggests a structural issue in the CSV while the actual cause may be related to file naming or formatting. Your suggestion to make the message clearer is very helpful, and we will pass this feedback along to our development team for improvement.
Thanks again for highlighting this — it will certainly help improve the experience for other users as well.
If you run into any further issues during your testing, feel free to reach out anytime.
Best regards,
Bruce Paine
Accepted AnswerI would also like to make an observation about the vague error message wording:
"Import Failed! There might be some problem with the CSV file structure".
It says there might be some problem with the CSV structure. The word 'might' suggests that there might also be other explanations for the import failure. It makes me suppose there could be other issues, aside from the CSV structure, to make the product import fail.
Anyway, I'll keep trying with the test data - until the support team are able to respond to this.
Bruce Paine
Accepted AnswerFor the benefit of anyone else struggling with the product import process, I have figured out the problem.
The csv file name needs to be easystore_products.csv exactly. In my attempts to create my own data, I was using my own file names.
Another read through the documentation suggests I have the right answer.
Note: the importer is happy to run even if you forget to include the media folder in the zipped file.
I intend to carry out further testing and hopefully now my real data will be accepted.
Bruce Paine
Accepted AnswerI would like to suggest that it may be helpful to review the error messaging wording, as it appears to point to CSV structure even when the issue may lie elsewhere.
For example:
"Import Failed! There may be a problem with the CSV file structure or naming."
Something like that would have saved me about a day's work and frustration - not to mention re-reading the manual! ;-)
Bruce Paine
Accepted AnswerI have also just discovered that the csv data rows need to end with a Unix Lf (linefeed) rather than Windows CRLF (carriage return and line feed). CRLF will fail the import process.
Bruce Paine
Accepted AnswerHi Ziaul Kabir,
You are most welcome and I am happy if my efforts are helpful to others.
It has been a very long "adventure" for me!
Another discovery is that the import process permits jpeg (jpg) images. This is helpful because I have a large number of jpg images which would otherwise need converting to webp format.
Actually, when I converted one jpeg image to webp format, as per the EasyStore Product Import instructions, after importing to EasyStore Products, the edit window showed a blank image - i.e. just a placeholder. The image was only visible in the public view - not admin. However, when I imported another product with a jpeg instead, it appears in both admin and public views.
So I think jpeg is the better format.
All the best!