Import Builder/Guides/ShipStation product import errors
Logistics

ShipStation Product Import Errors and How to Fix Them

ShipStation imports products from a CSV file and replaces what it already holds. These are the problems that erase weights and locations, update the wrong products, drop tags or misread weights, and how to fix each one.

ShipStation's import rules

A header row, with columns matched to ShipStation's fields
SKU and Name on every row
A SKU that exists updates that product, and can't be renamed
A blank cell replaces the stored value with nothing (except Tags and Active)
WeightOz in ounces, tags up to 29 characters
TRUE or FALSE for UseProductName, Active and IsReturnable

Where the file goes

Open the Products tab, click Import and choose Import Products. Attach the file, match its columns to ShipStation's fields and choose Upload and Preview, then Start Import. The window has an option to overwrite existing values for all fields in the file, so read it before you tick it.

Common errors and their fixes

Fields are blank after the import

Cause: A product CSV replaces existing product details, and a blank cell enters a null value. Only Tags (which can be added but not removed) and Active (which is left alone when blank) are exceptions.

Fix: Fill in every column you want kept for every product in the file. Export your products first, edit that file, and import it, so nothing you didn't mean to clear is missing.

Existing products now have the wrong details

Cause: A row whose SKU already exists in ShipStation updates that product. SKU is how ShipStation matches, and there is no match by name.

Fix: Include only the products you want added or changed, and check that new products have SKUs that aren't already in use.

A SKU can't be changed

Cause: Once a product record is saved its SKU can't be edited. A changed SKU in a CSV is a different product, not a rename.

Fix: Use Combine Products in ShipStation to merge a duplicate SKU into the right one, and keep the same SKU in your file from then on.

The file has no column headers

Cause: ShipStation no longer needs a template, but the file must have a header row so you can match each column to a field.

Fix: Make the first row the field names, such as SKU, Name and WeightOz, and check the column matching on the preview screen before you start the import.

SKU or Name is missing

Cause: SKU and Name are the two required fields in the product file.

Fix: Give every row both. Rows without them can't be created as products.

A tag is missing, or won't go away

Cause: A tag of 30 characters or more is not added, so the limit is 29. Tags can be added through the import but not removed by it.

Fix: Shorten long tags, and remove tags from products inside ShipStation.

Weights are 28 times too big

Cause: WeightOz is in ounces. Shopify exports product weights in grams, so a 500 g product is read as 500 ounces.

Fix: Convert grams to ounces before importing: divide by 28.35.

TRUE and FALSE flags not read

Cause: UseProductName, Active and IsReturnable take the values TRUE or FALSE.

Fix: Use TRUE or FALSE only, not Yes, No, 1 or 0.

A product stays inactive, or active, when you didn't want it to

Cause: If the Active column is blank, ShipStation ignores it and leaves the product as it was.

Fix: Set Active to TRUE or FALSE on every row where you want the status to change.

Aliases don't come in with the product file

Cause: Product aliases and product preset groups can't be added or removed with a product import. Aliases have a separate import that needs a SKU and an Alias, and the store names must match ShipStation's exactly.

Fix: Import aliases separately. To turn an existing SKU into an alias, use Combine Products instead of an import.

SKUs and UPCs lose leading zeros

Cause: A spreadsheet reads 00471 as a number and shows 471, so the SKU no longer matches the product in ShipStation. UPC codes are affected too.

Fix: Format the SKU and UPC columns as text before pasting. See leading zeros in CSV files.

Dangerous goods details don't import

Cause: Dangerous goods information has its own import. The regular product file doesn't carry it.

Fix: Use ShipStation's dangerous goods product import after the products exist.

The import failed

Cause: The import runs in the background. When it finishes you get a notification, and a failed import shows a message with the likely reason.

Fix: Read that message, fix the file and import again. Close the import window if you like: you can keep working in ShipStation while it runs.

After importing

Open a handful of products and compare them with your file: the weight, the warehouse location, the customs details and the tags. If a field is blank that shouldn't be, the file had an empty cell for it.

Keep the exported product file from before the import. Because an import replaces what is there, it is the quickest way to put the old values back.

Checklist before you import

A header row, and the columns matched on the preview
SKU and Name on every row
SKUs and UPCs kept as text
Only the products you mean to add or update
Every column you want kept is filled in
Weights in ounces
Tags no longer than 29 characters
TRUE or FALSE in the flag columns, and Active set where it should change
A copy of the products exported before importing

Collecting product details from warehouses or suppliers?

Send each one a form instead of a spreadsheet. The ShipStation products template uses ShipStation's field names, flags repeated SKUs and limits tags to 29 characters. For buying labels from a spreadsheet, see the Shippo orders template.

Try the products template

Import Builder is an independent product and is not affiliated with, endorsed by, or sponsored by ShipStation. ShipStation is a trademark of its owner. Import rules as described in ShipStation's help center, November 2026.