Often when we import files we run into errors that the file is not being read correctly. Where to start looking for the cause of the issue and how to solve this?
Follow these checkpoints to make sure that you have the basics right.
The template must use the same delimiters as your file has. The type of delimiters does not matter. To know what delimiters your file uses look at your file with Notepad for example.
Some examples of delimiters are:
|Sample||Field delimiter||Text enclosure|
The file must always be encoded in UTF-8 format. No other encoding is supported. See this video on how to save your file as UTF-8 using Notepad2 or this tutorial using LibreOffice/OpenOffice. This is important because files imported not in UTF-8 encoding will not import correctly with special characters like ë.
Use only fieldnames that are available for the type of import you are doing. To see which fieldnames are available go to CSVI ---> Available Fields and filter on the type of import you want to do. It is not possible to use any other name. This means that if your CSV file contains the names sku, price, name that these cannot be used, you have to translate them to CSVI fieldnames. Your column names will change like this:
Make sure the data is properly formatted according to the specifications on the Available Fields list.
Check the debug information
The debug report shows every step CSVI takes when importing the file. See the How to collect debug information on how to get your debug report. Check the debug information for anything that might be going wrong or post it in the forum.
After having checked these checkpoints your import should be running smoothly. Check out also this presentation on how to prepare your CSV file.