When one shipment prints many duplicate labels or tracking numbers, the cause is almost always an input device, not Shipstore: a stuck or held Ship key (often F10) that fires again and again, or a barcode scanner that reads the order number twice. Check the keyboard and scanner, not the shipment data.
Problem
Processing one shipment makes many labels with different tracking numbers (in one case over 100). Voiding the extras can show a "running post void routines" message, because each void also tries to update the integration.
Cause
The Ship action was triggered over and over. There are two common input-device causes: a sticky or held-down Ship key (F10, or a custom ship key) that repeats the ship command, or a scanner that duplicates the scanned order number so the same order is processed more than once. Both are hardware issues at the station; Shipstore processes each ship command it receives.
Fix
- Find the station where the duplication happened.
- Check the Ship key (F10 or your custom key) for sticking. Test with a different keyboard, or disable or replace the key.
- If you scan orders, check the scanner for duplicate output (the order number read as the same value twice). Reconfigure or replace the scanner.
- Void the extra shipments. If voiding shows a "running post void routines" message, void them one at a time and let each integration update finish.
- Watch the station after you replace the keyboard or scanner.
What you should see
Processing one shipment now makes exactly one label and one tracking number, and the order number is not duplicated.
Related articles
- Batch reprint only prints the labels shown on the page
- Duplicate shipments in Shipping History