One file per courier, each still in packing order
Different couriers come at different times. Splitting the batch means each pickup gets exactly its own stack — and each stack is still sorted by product.
Two ways to keep the couriers apart
One PDF, courier by courier. A single print job, with each courier's labels in one contiguous block and a divider page naming the courier in front of each — including the first, because in one stack there is nothing else telling a packer whose labels these are. Inside each block the labels are still sorted by product.
A separate PDF per courier. One file each, when the pickups happen at different times and you would rather print them separately.
What the separate files look like
Choose A separate PDF per courier and a 344-label batch becomes:
- 344 21-8 Batch_2 - 338 E-Kart.pdf
- 344 21-8 Batch_2 - 6 Shadowfax.pdf
The batch name stays in front, so yesterday's export and today's do not blur together in a folder. The count and the courier come after, so you can tell what is in a file without opening it.
Reading the courier is not as simple as it looks
Flipkart prints the courier on the second line of the label. Meesho prints it about fifteen lines down, under both address blocks. So the top of the page is searched first, and only if that fails does it read further.
The deeper pass has a rule the first one does not: the courier name must be at the start of its line. That sounds fussy until you meet a customer whose address is "Flat 4, opposite the Delhivery depot" — which happens for real in a 500-label sheet. An address that merely mentions a courier does not begin with one, so it is not mistaken for the shipping courier.
And a real Shadowfax label readsSShadowfax E2E SDD COD — a doubled S where the logo overlaps the text. Matching has to survive that, and the file name must not inherit it.
Splitting and grouping together
The two are not alternatives. When a batch is split, each courier's labels are sorted through the same product groups, so a group prints as one block inside each courier's file. You pick one product, pack it, and everything in that run goes to the same pickup.
The pick list is written per file too, with page numbers that match that file rather than the original batch. When everything is in one PDF instead, the pick list gains a courier column and a total per courier — the number you check against the pickup slip.
Common questions
- Are the labels still grouped inside each courier's block?
- Yes, and that is the whole point. Each courier's labels are sorted by product using the same groups, whether they are in their own file or in a block of one shared PDF. Either way a pickup gets one stack that is still in packing order.
- What if a label's courier cannot be read?
- It goes into an 'Unknown courier' file rather than being dropped or guessed at. On the real files this does not happen, but a marketplace can add a courier tomorrow and a silently misfiled label is worse than an obviously unfiled one.
- Which couriers does it know?
- Shadowfax, E-Kart, Delhivery, XpressBees, Blue Dart, Ecom Express, Valmo, India Post and DTDC.
Try it on your own file
No signup, no card. Your PDF is read in your browser and never uploaded.