Summary

When you upload a file again under the same job number, Shipstore replaces the order items with the items in the new file. It does not merge them. Anything that was on the first upload but is left out of the new file is removed. Always upload the complete list of items you want on the order.

Problem

You expect a second upload of the same job number to add new items and update the ones already there. Instead the order ends up with only the items in the newest file, and items from the first upload are gone.

Cause

The import updates the order to match the most recent file for that job number. It is a replace, not a merge, and the last file wins. There is no add-only option, so any item missing from the new file is dropped from the order.

How to check: compare the order's items with the file you uploaded last. If they match the newest file exactly, the replace worked as designed.

Fix

  1. Treat every re-upload as a full replacement of that job number's items.
  2. Before you upload again, build the file so it holds every item that belongs on the order, not only the rows that changed.
  3. Upload the file.
  4. Open the order and check that the items match the file.

What you should see

After the upload, the order shows exactly the items in the newest file. A complete file keeps every item you wanted.

If something goes wrong

You want a warning before a re-upload replaces an order: a stop-and-confirm popup for a job number that already exists, like the one on voiding a shipment, can be added as a paid customization. Email support@shipstore.com and include which import screen you use and how often this happens, so it can be quoted.

Related articles

See also: "Some batch import rows fail: international columns missing", "Batch import fails on a large file or reused shipment numbers", and "How To: Import Files".