What a batch of labels can tell you
Before a day’s orders are packed, they are already a small dataset: what sold, how much of it, which couriers are collecting, where it is all going, and how much of it is cash on delivery. That information is sitting in the label PDF you have just downloaded, and most sellers never read it because reading it by hand means paging through fifty sheets.
This tool reads the same file and reports what is in it. It produces no PDF and changes nothing — it is a read of the batch, downloadable as an Excel workbook if you want to keep it.
“Order value” is not your revenue
This is the most important thing on the page, and it is worth being blunt about. The only money printed on a shipping label is the customer invoice total— what the buyer paid. That is not what you receive.
Marketplace commission, shipping fees, payment-gateway charges and settlement deductions never appear on a label, because the label is a document for the courier, not a statement of account. So every money figure here is called order value, never revenue, profit or payout. It tells you the size of the day’s trade, which is genuinely useful. It does not tell you what will land in your bank, and no tool reading labels can.
If you want to know what actually arrived, that lives in your bank statement — which is what the statement analyser is for.
What the report covers
- Order value for the batch and per order, with the caveat above.
- SKU counts— what is selling and how many of each, which is the number that tells you what to restock and what to pick first.
- Courier split— how many parcels each carrier is taking, so you know the size of each handover before you sort into piles.
- Destination states, read from the address block. Useful for spotting when a day is unusually weighted toward far zones, which changes both cost and delivery time.
- Payment mix — how much of the batch is COD versus prepaid.
- A per-order breakdown, so any total can be traced back to rows.
Where the numbers get soft
A label is a printed document, not a database export, and some fields simply are not on it. Rather than filling those gaps with plausible values, the report leaves them visibly empty.
Payment mode is the usual example: a good number of Meesho labels print no payment mode at all, so a COD split calculated from that batch is a split of the labels that said, not of the batch. Destination state depends on the address block being readable, and courier detection depends on the carrier’s name being printed. A count that says “Unknown” is telling you something true about the document.
Mixed marketplaces in one pass
Flipkart, Meesho and Amazon labels are all read, including the structural difference between them — Flipkart and Meesho put the label and invoice on one page, Amazon puts them on separate pages. A batch drawn from more than one marketplace is summarised together rather than needing a run each.
When to run it
First, before anything rewrites the file. The summary is most useful as the thing you read while deciding how to work the batch: it tells you which SKUs to pick, how big each courier handover will be, and whether the day is COD-heavy. Then check for duplicates, split by courier, and crop for printing.
Your files
Nothing is stored. The PDF is sent over an encrypted connection, read, and discarded once the summary is returned — no account, no retention, and nothing kept after your download. Our privacy policy sets it out in full.