Shipment Issues
Errors that stop a shipment from being created, and what to check before contacting support.
"Duplicate parcel numbers found"
The shipment is refused and the message names the parcel numbers that caused it:
Duplicate parcel numbers found: [06080000000001]
The same check runs wherever shipments are created — by hand, from a file import and through the REST API. Nothing is saved: the shipment is not created and no label is produced.
Why it happens
Every pickup address is assigned one or more parcel number ranges. The application takes the next number from the range each time a parcel is created, and before saving it checks whether that number has already been used for the same customer within the last 7 months (210 days). If it has, the shipment is refused rather than sent out with a number that is still in circulation.
Almost always the range has run out. A range marked as reusable does not stop at its last number — it starts again from the first one and hands the same numbers out a second time. That is harmless once the earlier shipments are older than 7 months. If the range wraps sooner, the reissued number collides with the shipment that still holds it, and every shipment that gets such a number is refused.
So the message normally means the range is too small for the volume you send, not that anything is wrong with the shipment data. Correcting the address, the service or the weight will not help.
A related message — Parcel range [… - …] exhausted and not reusable for customer … — means the range reached its last number and is not allowed to start again. The remedy is the same one described below.
Check the range
- Go to Settings
- Open About Configs
- Find the customer and the pickup address the shipment was created for
Every range assigned to that address is listed on its own line:
06080000000001 - 06080000009999 Size 10000 (12)
| Part | Meaning |
|---|---|
from - to | First and last parcel number of the range |
Size | How many numbers the range holds in total |
(n) | How many numbers are left before the end of the range |
A count of (0), or one in the low hundreds, on the range you print from is the confirmation: it is exhausted, or about to be. A range that has just wrapped shows a count close to its full size again — together with duplicate errors, that is the sign it has been round more than once.
What to do
Contact support and ask for a new parcel number range for that pickup address. Include:
- The invoicing number and the pickup address
- The range currently in use, exactly as About Configs shows it
- The parcel numbers from the error message
Adding a range leaves the existing ones untouched, and shipments already created keep their numbers. Once the new configuration is applied, the application prefers the least-used range, so it moves to the fresh one by itself and the error stops.
There is no workaround inside the application in the meantime: parcel numbers cannot be released early and cannot be entered by hand.
The number in brackets is the early warning. Check it in About Configs from time to time — a range that holds only a few weeks of your volume should be replaced before it runs out, not after.
With a file import
The shipment is rejected the same way, but nothing appears on screen while the import runs. Messages → Process logs shows the run finishing with Error; the reason itself is not in that entry, so open Imports, select the file and read its errors — see File Import Issues. Rows refused for this reason are not imported, so the same file can be imported again once a new range is in place.
Through the REST API
The API answers 400 Bad Request and repeats the parcel numbers in the message:
{ "debugMessage": "Duplicate parcel numbers found: [06080000000001]" }
The whole request is refused, batches included — there is no partial result and no failed list for this error, so nothing in the batch is created. Retrying the identical request produces the same 400; it only succeeds once a new range is assigned. See also API Issues.