Multi-Quantity Order Labels, Packed Last

Where the mistake actually happens

Nothing goes wrong at the start of a batch. It goes wrong at parcel one hundred and forty, inside a rhythm of one label, one item, tape, next — and that rhythm is exactly what a multi-quantity order breaks. The digit is printed on the label. It is simply not where someone moving at speed is looking, and one short-packed parcel costs more than the sale it came from.

One checkbox, two changes

1. 1Every label with a quantity above one is pushed to the end of the file, keeping the order it already had relative to the other multi-quantity labels.
2. 2On those labels the quantity value itself is ringed in red, so the number that needs acting on is the one thing marked on the page.
3. 3Single-quantity labels are left completely alone — no ring, no move — so the bulk of the batch prints exactly as it would have.
4. 4The ring is drawn into the page's own content rather than added as a PDF comment, because many label-print pipelines drop the comment layer and print the page without it.

Why the end of the batch is the right place

Grouped at the back, they stop being interruptions and become a job: a short, dense run of nothing but multi-quantity orders, arriving when the packer is already in counting mode. Two of the same, then three of another, each with its count circled — checked against the batch and finished in one pass. Scattered through the file, every one of them is a stall in a rhythm that was working.

Your courier piles stay whole

If you also sort by Courier Partners, sending a Valmo label to the very end of the file would land it after the Delhivery block and quietly break a handover you had already counted. So the push stops at each partner boundary instead: multi-quantity labels go last inside their own courier run, and every pile stays intact. The same applies with Label with Invoice, which takes no crop at all and keeps each page whole — the ring is still drawn on it.