The daily Meesho routine that stops breaches.
Most missed dispatch windows are not caused by slow packing. They are caused by processing orders reactively all day instead of clearing them in one early batch. Here is the sequence that fixes it.
- One early batch beats reacting to orders all day — every order inherits maximum runway.
- Sort by time remaining, never by order date. Windows differ between orders.
- Separate blocked orders immediately so one stock-out does not stall twenty parcels.
- The most-missed step is confirming the handover scan actually happened.
- Robnu sequences the batch by urgency and tracks every clock. Free while we figure out pricing.
There is nothing clever about this routine. It is deliberately boring, because the thing that breaks marketplace operations is not difficulty — it is the accumulation of small decisions made repeatedly under time pressure. A fixed sequence removes the decisions.
Processing orders reactively through the day is why parcels breach SLA and labels get missed. This guide lays out a single-batch routine that clears a day of Meesho orders without anyone watching a clock — deliberately boring, because the thing that breaks marketplace operations is not difficulty but the accumulation of small decisions made under time pressure.
Batch, do not react
Handling orders as they arrive feels responsive. In practice it means switching contexts dozens of times a day, doing each step badly, and giving your latest orders the least runway. Batching means downloading all labels once, packing in one pass, and handing over as a single consignment. The decisive argument is runway: an order processed at 11am has hours of buffer before its window closes; the same order picked up at 7pm may have almost none. Nothing about your packing speed changes that — only when you start. See SLA status for what the clock is doing.
The six-step sequence
Run these in order every day. Sort the pending queue by time remaining, not order date. Triage blockers — stock-outs and label failures get handled separately, not in the flow. Print all labels in one pass. Pack and record the weight as you go, because that record is your evidence in any later weight dispute. Get the manifest signed as proof a handover occurred. And run a close-out check confirming every dispatched order has an actual scan and nothing new has drifted into the warning zone.
When the routine outgrows the person
This checklist works until volume outpaces the state a human can hold, at which point the failures are not carelessness but orders that genuinely fell out of attention. That transition is where a system stops being optional. Holding the queue sorted by urgency, tracking the dispatch clock on every open order, flagging blockers before they stall a batch, and telling you when a handover has not been scanned is exactly what our agentic dispatch tracking does — so the routine stops depending on anyone remembering it. See the two-person team playbook for the operating model.
The bigger picture for your catalogue
Whatever the specific status, charge or process, the underlying reality of selling on Indian marketplaces is the same. The platforms are built to move enormous volume, their interfaces speak in operational shorthand rather than plain language, and the money at stake hides in charges that arrive as silent settlement deductions requiring no approval from you. The sellers who stay profitable are not the ones who avoid every problem — that is impossible at scale — but the ones who understand what each event means, know which charges are genuinely owed, and reconcile every settlement so the wrong ones are caught and reclaimed while the claim window is still open.
That discipline is simple to describe and hard to sustain by hand, because it is precise, repetitive work layered on top of actually running the business. It is exactly the kind of task that a two-person team does inconsistently under volume and that software does reliably every cycle. Robnu exists to close that gap: it runs the daily operations these guides describe, reconciles the charges they represent against what you actually shipped and sold, and files the claims you are entitled to — so the vocabulary becomes something handled rather than something you have to master and police yourself. You sell; Robnu runs the rest, and makes sure every rupee is paid correctly.
Sources & further reading
Charges, policies and processes vary by marketplace and category and change over time. The details here are drawn from official documentation and reputable industry sources; always confirm current specifics against your own seller panel and settlement reports:
Batch, do not react
Handling orders as they arrive feels responsive. In practice it means switching contexts dozens of times a day, doing each step badly, and giving your latest orders the least runway. Batching means downloading all labels once, packing in one pass, and handing over as a single consignment.
The runway argument is the decisive one. An order processed at 11am has hours of buffer before its window closes; the same order picked up at 7pm may have almost none. Nothing about your packing speed changes that — only when you start does.
Six steps, same order, every day
Run them in this order. The sequence matters as much as the steps.
Sort by deadline
Open the pending queue and order it by time remaining. Anything already in breaching soon jumps the queue.
Triage blockers
Pull out stock-outs and label failures. They get handled separately, not in the flow.
Labels in one pass
Download and print everything together. One printer session, one stack, no switching between the panel and the packing table.
Pack and weigh
Record the weight as you go. That record is your evidence in any later weight dispute.
Manifest and hand over
Get the manifest signed. This is your proof a handover occurred if a courier delay is later attributed to you.
Close-out check
Confirm every dispatched order has an actual scan, and that nothing new has drifted into the warning zone. Two minutes, saves tomorrow’s penalty.
When the routine outgrows the person
This checklist works, and it keeps working until volume outpaces the amount of state a human can hold. At that point the failures are not carelessness — they are orders that genuinely fell out of attention while attention was elsewhere.
Robnu is an agentic OMS. It holds the queue sorted by urgency, tracks the dispatch clock on every open order, flags blockers before they stall a batch, and tells you when a handover has not been scanned. The routine stops depending on anyone remembering it.
You sell. Robnu runs the rest — and makes sure every rupee is paid correctly.
Order processing, answered
In one batch, early, in a fixed sequence — rather than reacting to orders as they arrive through the day. Batching means you handle each step once for all orders instead of context-switching repeatedly, and starting early gives every order in that batch the maximum possible dispatch runway. Reactive processing is the single biggest cause of avoidable SLA breaches.
As early in your working day as your order flow allows. An order processed mid-morning has substantially more runway before its window closes than the same order processed in the evening. If you can only run one batch, run it early; if you can run two, make the second one a catch-up rather than the main event.
By deadline, always. Dispatch windows differ between orders, so the oldest order is not reliably the most urgent. Sorting by time remaining rather than order date is a small change that prevents a specific and common failure — breaching a newer order while working carefully through older ones.
Confirming the courier handover actually got scanned. Sellers reliably print labels, pack parcels and mark orders ready — then assume pickup happened. An order that is packed but never scanned keeps counting down toward a breach, and it is the most frustrating way to lose an order because all the real work was done.
Separate them out immediately rather than letting them stall the batch. A stock-out and a label that will not download need different responses, and neither should hold up the twenty orders behind them. Deal with the flowing orders first, then work the blocked pile with whatever time remains.
It is strongly worth having. A manifest that the courier signs is your evidence that a handover took place at a given time — which is exactly what you need if an order is later marked as a seller dispatch delay when the courier failed to collect. Without it, a waiver request is your word against a scan record.
The sequence stays the same; what breaks is the human tracking layer. At five orders a day you can hold the state in your head. At twenty-five you cannot, and the failures shift from effort problems to visibility problems — orders forgotten rather than orders skipped. That transition is where a system stops being optional.
Two things: that every order you intended to dispatch has an actual handover scan, and that nothing has quietly appeared in the breaching-soon state while you worked. A two-minute close-out check at the end of the batch catches almost everything that would otherwise become tomorrow's penalty.
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.
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.
One Screen for All Your Orders: The Case for Centralized Order Processing
Selling on three marketplaces means three dashboards, three SLA clocks and three ways to miss an order. Here is why a single order screen — an agentic OMS that runs them all — is the fix.
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.
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 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.
AJIO Seller Panel Guide: A Walkthrough of AJIO Seller Central
A practical, screen-by-screen walkthrough of the AJIO seller panel — onboarding, catalogue, orders, dispatch SLAs, returns and payouts — plus the reports that decide whether you get paid correctly.
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.