Scan, label, manifest: dispatch as one chain.
Dispatch is not four separate jobs — it is one chain, where each link depends on the one before. Run it as a routine and it flows; break it up and it leaks time and triggers penalties. Here is the full chain end to end, in order, and exactly where each link fails.
- Dispatch is one chain: select ready orders, label, pack, close the manifest, hand over against a scan.
- Each link has preconditions set by the one before — order matters as much as the steps.
- The time leak is doing the per-order steps serially; the fix is batching each link across the whole day.
- Closing the manifest is the riskiest link — the system trusts it even when the parcel never ships.
- Robnu runs the whole chain as one routine, keeping the links in order. Free while we figure out pricing.
Most dispatch advice treats scanning, labelling, and manifesting as separate how-tos. That framing is the problem: it hides the fact that they are links in a single chain, each depending on the last. Run them as disconnected jobs and you get the classic failures. Run them as one routine and dispatch becomes the fastest, most predictable part of your day. This guide is the whole chain, in order.
Every parcel you send follows the same path from accepted order to courier custody, and that path is a chain: each link hands off to the next, and a weak link anywhere breaks the whole run. Understanding dispatch as one chain — rather than a set of separate tasks — is what lets you run it fast and close it clean. Here is the chain, link by link, with the failure mode of each.
Link one: scan or select the ready orders
The chain starts by answering one question: which orders are we dispatching in this batch? You scan or select the orders that are genuinely ready to ship — accepted, clean listing, no hold. This link looks trivial and is not: a sloppy selection that drags in orders which are not ready is what makes the very next link stumble. A clean selection is the foundation the whole chain stands on. This is where a label that will not generate usually traces back to.
At low volume you eyeball the list; at higher volume you filter to a ready-to-ship view so the selection is clean by construction. Either way, the discipline is the same: only genuinely ready orders enter the chain, so no unready order can break a downstream link.
Link two: generate and apply the label
With a clean selection, you generate the shipping label for the whole batch and apply one to each parcel. The efficient form generates the label together with the tax invoice as a single merged PDF per parcel, so each box gets one document with everything the courier and buyer need. This link is where the biggest time leak lives — not because labelling is hard, but because doing it one order at a time multiplies a few clicks by the whole day. Batching the generation is the single largest speed win in dispatch, covered in full in bulk label download.
Link three: pack the parcel
Each parcel is packed with its merged label-and-invoice document. This is the physical link — the point where a digital order becomes a real box — and it is where the chain becomes irreversible: once packed and labelled, the parcel is committed. Packing quality matters beyond neatness, because a parcel that looks damaged gets refused at the door and becomes a return to origin. Good packing is the last cheap defence against an RTO before the parcel ever leaves.
Link four: close the manifest
Now you close the manifest — the document listing every packed parcel in this pickup. This is the riskiest link in the chain, because closing the manifest is a declaration the system trusts even when reality disagrees. Close it against a parcel that is not actually packed and ready, and the order reads as dispatched while the parcel sits on your table: a manifested-but-not-handed-over penalty waiting to surface. The rule is absolute: close the manifest after packing, against exactly the parcels you have, never before.
Link five: hand over against a scan
The chain closes when the courier scans each parcel at pickup to take custody against your manifest. This handover scan is your proof the parcel left your hands and entered the network. A chain that ends at “manifest closed” but not “handover scanned” is not truly complete — the custody trail is missing, which exposes you to loss and weakens any later dispute. Confirm every parcel is scanned and the counts match the manifest. That complete trail is what feeds clean payment reconciliation and returns recovery downstream. For the neighbouring reference material, see the glossary.
Sources & further reading
Dispatch steps and panel actions vary by courier partner and change over time. Confirm against the official documentation:
One chain, not four jobs
The reason dispatch feels chaotic is that it is usually run as separate tasks — a bit of labelling here, a manifest there — when it is really one chain where each link depends on the last. Reframe it as a chain and the failures become predictable and preventable.
A clean selection makes labelling flow. Labelled parcels make packing possible. Packed parcels make the manifest honest. An honest manifest makes the handover match. Break any link and everything after it wobbles — which is why the manifest and handover mistakes almost always trace back to an earlier link run out of order.
The five links, and where each one fails
Run in this order, batched by link across the whole day, dispatch becomes fast and predictable. Each card is one link and its failure mode.
Scan / select
Choose only genuinely ready orders. Fails when a sloppy selection drags in unready orders that stall the labelling link right after it.
Label (merged with invoice)
Generate one merged label-and-invoice PDF per parcel, for the whole batch. Fails when run per order — the biggest time leak in dispatch.
Pack
Turn each labelled order into a real, well-packed box. Fails when packing is poor — a damaged-looking parcel gets refused and becomes an RTO.
Manifest & hand over
Close the manifest against exactly the packed parcels, then hand over against a scan. Fails when the manifest closes early or a handover scan is missed — the penalty links.
The whole chain, run as one routine
Dispatch penalties and lost hours both come from the same root: running the chain as loose, out-of-order jobs. Robnu is an agentic OMS: it runs the whole chain as one routine — filter the ready orders, generate merged label-and-invoice documents, isolate any failures, close the manifest only against genuinely packed parcels, and reconcile the handover scans against what was manifested.
Because it treats dispatch as a chain rather than four jobs, the links stay in order and the classic penalties are avoided by construction. The same run keeps a complete custody trail, which feeds clean reconciliation downstream. An hour of serial clicking becomes a few minutes of checking a batch.
You sell, Robnu runs the rest — the whole dispatch chain included.
The dispatch chain, answered
It is the sequence of steps that takes an order from accepted to handed-over: scan or select the ready orders, generate and apply the label, pack the parcel with its merged invoice, close the manifest listing every parcel, and hand over to the courier against a scan. Each link depends on the one before it, which is why treating dispatch as a single chain — rather than four loose jobs — is what makes it flow.
Because each step has preconditions set by the one before. You cannot label an order that is not cleanly ready; you should not close the manifest before parcels are packed and labelled; you cannot hand over what was not manifested. Run the steps out of order and you get the classic failures — labels that will not generate, manifests closed on parcels that never ship, missing handover scans.
In the repetition of the per-order steps — opening each order, generating each label, printing each document — done one at a time. The chain itself is simple; the time leak is doing it serially instead of batching each link across the whole day's orders at once. Collapsing that repetition is the single biggest speed win in dispatch.
Scanning (or selecting) is identifying which orders you are dispatching in this batch. Labelling is generating and applying the shipping document to each parcel. Scan/select answers "which orders?"; label answers "what goes on the box?". They are separate links because a clean selection is what lets the labelling step run without stumbling on orders that are not ready.
Because it is a declaration the system trusts even when reality disagrees. Close the manifest on a parcel that is not actually packed and handed over, and the order reads as dispatched while the parcel sits on your table — a late-dispatch penalty waiting to surface. The manifest link is where an out-of-order chain does its most expensive damage.
The handover scan is the courier taking custody of each parcel against your manifest. It is the final link and your proof that the parcel actually left. A chain that ends at "manifest closed" but not "handover scanned" is not really complete — the custody trail is missing, which exposes you to loss and weakens any later dispute.
Yes, and you should. The efficient routine batches each link across all the day's ready orders — select the batch, generate all labels and invoices as merged PDFs, pack, close one manifest, hand over against one scan session. Batching the chain rather than running each order end-to-end is what turns an hour of dispatch into a few minutes.
An OMS runs the whole chain as one routine: it filters ready orders, generates merged label-and-invoice documents, isolates any failures, closes the manifest only against genuinely packed parcels, and reconciles the handover scans against what was manifested. Because it treats dispatch as a chain rather than four jobs, the links stay in order and the classic penalties are avoided by construction.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
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 manifest and handover mistakes that trigger penalties
Closing the manifest, the handover scan, and the gap between them is where Meesho penalties hide. The mistakes that trigger them — manifested-but-not-handed-over, missing scans, wrong counts — and how to close cleanly.
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 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.
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.
Bulk Invoice Download on Amazon: Generate GST Invoices at Scale
Downloading Amazon GST invoices one order at a time does not scale. Here is how bulk invoice generation works, why it matters for GST filing, and how Robnu handles it end to end.
The Daily Routine for a 2-Person Marketplace Team (AJIO, Meesho, Amazon)
An hour-by-hour daily ops routine for a lean two-person team running AJIO, Meesho and Amazon together: order intake, SLA cutoffs, dispatch batching, returns, reconciliation and claims — with a clear division of labour.
The 10-minute Meesho order processing routine
Most missed dispatch windows come from reacting to orders all day instead of clearing one early batch. The six-step sequence, in the order that matters.