The CSV ("Comma Separated Value") file format is often used to exchange data between applications. CSV files are plain text files, which can contain numbers, letters, and symbols, and structure the data contained within them in a table form. Please check this guide on how to create a CSV file for more information.
Here is a list of common issues that can happen during CSV file import in Linnworks:
- Duplicate SKUs:
Each SKU needs to be unique and Linnworks will not allow using the same SKU numbers for item creation. Before importing, please make sure that there are no duplicates in the SKU column or import will return an error.
- Unusual characters:
Anything that is not an alphanumeric character in the SKU or another field may cause the CSV file to be rejected or as a result, you can get this:
- Empty column name / duplicate column name:
The column name is a mandatory field. If you do not fill out this field, then it will not be possible to perform mapping and therefore import the data. Each column name must be unique or it will not be possible to import it.
- Importing other file formats instead of a .csv file:
When saving the file, ensure you save it as a .csv file type, UTF-8 format, otherwise you will not be able to import it to Linnworks.
- Commas and Quotes:
Fields that contain commas should be enclosed in double-quotes. The same goes for text with multiple lines which may be part of your field data. Any fields containing a new line as part of its data need to be enclosed in double-quotes. If your fields contain double-quotes as part of their data, the internal quotation marks need to be doubled (escape character) so they can be interpreted correctly.
> If there is an additional coma in the value of the column then this will not work:
To retain the commas in "Title" column, we can enclose those fields in quotation marks. For instance:
As a result:
> If the field contains double-quotes as part of the data, the internal quotation marks need to be doubled so they can be interpreted correctly. For instance, given the following data:
In this case, simply enclosing the text in quotation marks will not work:
We can represent it in a CSV file as follows:
External double-quotes (") to escape internal comas and an additional double-quote (") before the actual double-quote in the text to get this:
When importing a file to Linnworks, in the mapping screen you can select the appropriate escape character (if required) for the format of your import file.
Linnworks allows 2 options:
Option 1: Quotes (") - used by default
Option 2: Backslash (\)
- Excel truncating long numbers:
Microsoft Excel can automatically truncate long numbers (phone numbers, tracking numbers etc). For example, it can turn 8 and 9 digit numbers into numeric references like 9.876+E. If this is happening with your file, then you can:
1. Try the workarounds explained here.
2. Use OpenOffice
- Export - Leading zeros
When exporting a file with data in some cases large numbers can loose leading zeros. For example phone numbers, product codes, account numbers, postal codes, etc. This article will help you keep your data in its original format – Leading zeros removed from values in exported CSV files.