Even though each import process is handled a little differently on the ShipStation side, there are some general troubleshooting steps you can take if you encounter issues with any CSV import.
If you need to open a file to review or edit the contents, import the file into the spreadsheet program you are using so the data is preserved. Using double-click to open a file can cause fields to be automatically formatted in incorrect ways. For example, long order numbers, SKUs, or UPC numbers may convert into scientific notation.
ShipStation does not support .xlsx or .numbers files for CSV imports. Those files can typically be converted to a CSV via a spreadsheet program like Excel or Google Sheets.
Depending on the import type, the CSV file may need to conform to a specific template. If a specific template is required, do not modify the column headers in the template.
Any numerical value field - like weight, item unit price, and length - require a numerical value and may cause failures if other characters are included. Similarly, date fields will only function if the value is formatted like a date.
'$10.00' is invalid for item unit price because of the $ symbol. The correct values would be '10' or '10.00'.
'16 oz' is invalid for weight because of the ' oz' portion of the value. The correct value would be '16'.
'Banana' is invalid for order date because it is not a date. A correct value would be '3/15/2018'.
If an error message for a CSV import includes a specific row in the exception message, the problem row is actually 1 higher than the exception message. This is because ShipStation will skip the column headers when processing the data, causing the error exception message to reflect a row 1 less than the actual file.
“ERROR - Row 6: Invalid product import status.” indicates an issue with Row 7 of the product CSV file (Row 6 from error + 1 row for Column Headers = Row 7).
If a CSV is importing most of the data without any errors, but certain fields are not updated in ShipStation, review the file to ensure there are no additional spaces in the column headers. A column header such as 'Shipping Paid ' (space after Paid) would cause the Shipping Paid field to not populate in ShipStation.
An easy way to check for this is to open the file in a text editor instead of a spreadsheet program. The space will be visible before the next comma, as shown in the image below:
ShipStation does not have a specific file size limit for CSV imports, but particularly large CSV files may run into issues when importing into ShipStation. If you're having trouble importing a large CSV file, we recommend you break the file into several smaller files of about 5 MB each.