Manifest and handover: the gap where penalties hide.
Closing the manifest and handing over are two separate acts, and the gap between them is where the costly mistakes live — parcels manifested but never handed over, missing handover scans, counts that do not match. Here is what each step means and how to close a clean dispatch.
- The manifest is the handover document listing every parcel you are giving the courier in a pickup.
- The costly mistake is "manifested but not handed over" — the system thinks it shipped; it never moved.
- Close the manifest after packing, against exactly those parcels — never before parcels are ready.
- The handover scan is your custody proof; a missing scan leaves you without evidence if a parcel goes missing.
- Robnu reconciles manifested parcels against handover scans and flags the gap before it becomes a penalty. Free while we figure out pricing.
Manifest and handover feel like formalities at the end of a dispatch day, which is exactly why they are where penalties quietly accumulate. The manifest says what you intend to ship; the handover scan proves what actually left. When those two disagree, the system trusts the manifest and your order pays the price. This guide closes that gap.
Every dispatch ends with two acts that look like paperwork and behave like a trap. Closing the manifest declares your intent; the handover scan records reality. Sellers treat them as one step, close the manifest, and assume the parcels are gone — and the gap between intent and reality is where late dispatches and penalties are born. This guide separates the two and shows you how to close cleanly.
What the manifest actually is
A manifest is the handover document that lists every parcel you are giving the courier in a single pickup. Closing it is a declaration: these are the shipments I am dispatching now. The courier then scans against that list at pickup to take custody. So the manifest sits at the exact boundary between your responsibility and the courier’s — it is the moment custody is supposed to transfer, which is precisely why the boundary has to be clean. It is the final link in the scan, label, manifest dispatch chain.
The mental model that saves you is this: closing the manifest does not move a single parcel. It only records an intention to move them. The parcels move at handover, and only the ones that are actually scanned. Hold those two facts apart and most manifest mistakes become obvious before they happen.
The big one: manifested but not handed over
The most common and most avoidable mistake is a parcel that is on a closed manifest but was never physically given to the courier. The system now believes the shipment is on its way; in reality it is sitting on your table. Against the order’s dispatch SLA, that reads as a late or failed dispatch, and repeated occurrences erode your account health and expose you to penalties.
It usually comes from closing the manifest too early — before every parcel on it is genuinely packed, labelled, and ready to hand over. The parcel that was not ready never makes it into the pickup, but it is already on the record as dispatched. The fix is sequencing, which we come to below.
The handover scan is your custody proof
The handover scan is the courier scanning each parcel at pickup to take custody against your manifest. It is far more than a formality: it is your evidence that the parcel left your hands and entered the network. A parcel that is manifested but never scanned has no custody trail. If it later goes missing, there is no proof it was ever picked up — so you carry the loss, and you have nothing to contest a wrong charge with.
This is where manifest discipline connects to the money. A clean handover scan is part of the evidence chain that lets you dispute a bad deduction later; a missing one leaves you exposed exactly when you need proof. It feeds directly into payment reconciliation and returns recovery, both of which lean on a complete custody trail.
When the counts do not match
A clean dispatch has one property: the number of parcels manifested equals the number handed over and scanned. Any mismatch is a problem. More manifested than handed over means parcels recorded as dispatched that never moved — the late-dispatch trap. More handed over than manifested means parcels in the network with no proper custody record — the missing-proof trap. Both create reconciliation gaps, and both, repeated, become penalty exposure. The count match is the single cleanest test of whether your dispatch closed correctly.
How to close a clean dispatch
The routine is fixed and the order is everything. Pack and label first — every parcel physically ready. Close the manifest against exactly those parcels — not a parcel more, not a parcel less. Hand over and confirm every scan — each parcel scanned into the courier’s custody. Check the counts match before you walk away. At low volume a checklist enforces this; at higher volume, a single missed scan in a large pickup is easy to overlook, which is why the reconciliation between manifested and handed-over parcels is worth automating. It is the same discipline behind reliable bulk label download and clean invoice printing.
Sources & further reading
Manifest and handover procedures vary by courier partner and change over time. Confirm against the official documentation:
Two separate acts, one dangerous gap
Closing the manifest is a declaration of intent. The handover scan is a record of reality. Treating them as one step is the root of almost every manifest penalty — because the system trusts the declaration and only the scan proves the truth.
Hold the two apart and the mistakes become obvious: a manifest closed before parcels are ready, a parcel that never gets scanned, a count that quietly does not add up. Each is a gap between what you declared and what actually moved — and each feeds the SLA clock whether you notice or not.
Four manifest mistakes that cost you
Every one of these comes from the gap between manifesting and handing over. Every one is avoidable with a fixed sequence and a count check.
Manifested, not handed over
A parcel on the closed manifest that never reaches the courier. Reads as a late or failed dispatch against the SLA. Caused by closing the manifest before parcels are ready.
Missing handover scan
A parcel handed over but never scanned. No custody trail, no proof it was picked up — so a later loss or dispute lands on you with no evidence to contest it.
Count mismatch
Manifested and handed-over counts that do not agree. Either failed dispatches or missing custody records — both create gaps that, repeated, become penalty exposure.
Manifest closed too early
Closing before every parcel is packed and labelled. The root cause of the other three: parcels get counted as dispatched before they are physically ready to move.
Reconcile the pickup, not just close it
Manifest penalties survive because the mistake is invisible on screen — the order shows dispatched even when the parcel is still on your table. Robnu is an agentic OMS: it closes the manifest only against parcels that are genuinely packed and labelled, then reconciles the manifested count against the handover scans.
Any parcel that was manifested but not handed over is flagged before it becomes a late dispatch, and the handover scan is tied into the SLA clock so a stuck parcel is raised as an urgent gap rather than discovered after the penalty lands. The custody trail stays complete, which protects you when a later charge needs contesting.
You sell, Robnu runs the rest — and closes every dispatch clean.
Manifest and handover, answered
A manifest is the handover document that lists every parcel you are giving the courier in a single pickup. Closing the manifest tells the system "these are the shipments I am dispatching now," and the courier scans against it at pickup. It is the bridge between your packed parcels and the courier taking custody — and the point where a mismatch between what you manifested and what you actually handed over becomes a problem.
It means a parcel was included on a closed manifest but never physically given to the courier at pickup. The system believes the shipment is on its way, but it never moved. This gap shows up as a late or failed dispatch against the order's SLA, and repeated occurrences erode your account health. It is one of the most common and avoidable manifest mistakes.
After. Pack and label every parcel first, then close the manifest listing exactly those parcels, then hand over. Closing the manifest before parcels are actually packed and ready is what creates the manifested-but-not-handed-over gap — the system counts shipments that are not yet physically ready to move.
The handover scan is the courier scanning each parcel at pickup to take custody against your manifest. It is your proof that the parcel left your hands and entered the network. A parcel that is manifested but never scanned at handover has no custody trail — so if it goes missing, there is no evidence it was ever picked up, and you carry the loss.
A mismatch — more parcels manifested than handed over, or vice versa — means the record and the physical reality disagree. Manifested parcels not handed over read as failed dispatches; handed-over parcels not on the manifest have no proper custody record. Both create reconciliation gaps and, if repeated, account-health and penalty exposure. Clean dispatch means the count matches exactly.
Yes. If a parcel is not scanned at handover, its custody trail is incomplete, which weakens your position if the shipment is later lost, delayed, or disputed. A clean handover scan is part of the evidence chain that lets you contest a wrong charge; a missing one leaves you without proof exactly when you need it.
Run a fixed routine: pack and label first, close the manifest against exactly those parcels, then confirm every parcel is scanned at handover and the counts match. At low volume a checklist works; at higher volume the reconciliation between manifested and handed-over parcels needs to be automated, because a single missed scan in a large pickup is easy to overlook.
An OMS closes the manifest only against parcels that are genuinely packed and labelled, reconciles the manifested count against the handover scans, and flags any parcel that was manifested but not handed over — before it becomes a late dispatch. It also ties the handover scan into the SLA clock, so a parcel that is manifested but stuck is raised as an urgent gap rather than discovered after a penalty lands.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
Scan, label, manifest: the Meesho dispatch chain end to end
Dispatch is not four separate jobs — it is one chain: scan, label, pack, manifest, hand over. Run as a routine, it flows; broken up, it leaks time and triggers penalties. The full chain, in order, and where each link fails.
Meesho invoice printing and the GST mistakes sellers make
The Meesho invoice carries your GST details, and the mistakes on it are the ones that come back to bite. How invoices generate, the GST fields that matter, the common errors, and how to print them cleanly at volume.
Meesho cancellation penalties: what they cost and how to avoid them
A cancelled order costs the penalty, the lost sale, and a compounding account-health hit. What triggers seller vs auto-cancellations, and how to catch orders before they reach that point.
What is a batch order on AJIO & Meesho? Batch day explained
Batch, batch day, open vs closed — decoded. What a batch really is, why the cut-off is unforgiving, and how to close every batch cleanly before the deadline.
Meesho dispatch SLA: timelines, penalties and waivers
One measurement drives every dispatch penalty you pay. Where sellers lose orders they had already packed, and the manifest evidence that reverses an unfair penalty.
Meesho bulk label download: 100 orders labelled in minutes
Downloading Meesho labels one order at a time does not scale. Here is the batch dispatch workflow — bulk-select ready-to-ship orders, generate labels and invoices as one merged PDF, print, and manifest without touching each order.
Meesho Supplier Panel: a full walkthrough of every section
The Meesho Supplier Panel runs your whole business — orders, catalog, payments, returns, ads, support. A section-by-section walkthrough of what each does, where sellers get stuck, and what the panel does not do for you.
Meesho OMS: The Honest Buyer's Guide for Sellers
What an order management system for Meesho actually is, what to look for before you commit, the questions that separate real tools from dashboards, and where Robnu fits in as one honest option.