Meesho dispatch SLA: the clock that decides your penalties.
One measurement — order to handover — drives every dispatch penalty you will ever pay. Here is exactly what it measures, where sellers lose orders they had already packed, and how to get an unfair penalty reversed.
- Dispatch SLA measures order creation to confirmed courier handover. Nothing else counts.
- 'Ready to Ship' does not stop the clock. Only the handover scan does.
- A miss costs a penalty plus likely auto-cancellation — the lost sale usually exceeds the fine.
- Courier no-shows are waivable, but only with a signed manifest and same-day evidence.
- Robnu holds the dispatch clock on every open order so nothing falls out of attention. Free while we figure out pricing.
Dispatch SLA is the most consequential number in daily Meesho operations. It is also widely misunderstood in one specific way that costs sellers real money — and that misunderstanding is worth correcting before anything else.
Everything hinges on the handover scan
The SLA is a single interval: from when the order is created to when the courier partner takes custody and scans it. Every seller-side action in between is preparation, and none of it registers against the clock.
This is why so many breaches feel unjust. The seller did the work — confirmed, printed, packed, marked ready — and still breached because the parcel sat unscanned by the door. From the platform’s perspective nothing happened at all.
The waiver case, built properly
Waivers are granted for causes outside your control. They are decided on documents, and the documents have to exist before you need them.
The signed manifest
A manifest the courier signs and stamps proves goods were ready and handover was attempted at a specific time. Without it you are asserting; with it you are documenting.
Same-day ticket
Raised while the problem is happening, not after the penalty appears. The timestamp is the point — it shows you flagged it in real time.
Order state screenshots
Showing the order ready and the pickup not completed. Cheap to capture, and the difference between a granted and rejected waiver.
A clock nobody has to watch
Understanding dispatch SLA is easy. Tracking dozens of independent countdowns, each with a different deadline, while packing parcels and answering customers, is not. That gap is where every breach comes from.
Robnu is an agentic OMS. It holds the dispatch clock on every open order, sequences the batch by real urgency, flags orders where the handover has not been scanned, and keeps the evidence trail that makes a waiver request winnable when a courier lets you down. It also checks that any penalty applied was actually warranted.
You sell. Robnu runs the rest — and makes sure every rupee is paid correctly.
Dispatch SLA, answered
It is the window within which you must hand an order to the courier partner after it is placed. Meesho measures the interval between order creation and confirmed handover, and everything about penalties and account standing follows from that single measurement. It is distinct from delivery SLA, which is the promise made to the customer about arrival.
At the courier handover scan. Not when you confirm the order, not when the label prints, not when the parcel is packed and sitting by the door. Until a scan exists showing the courier has taken custody, the clock is running. Orders that breach while fully packed are the most common and most avoidable failure in marketplace operations.
A penalty applies, and the order becomes exposed to auto-cancellation. The cancellation is usually the more expensive half — you lose the entire sale value, not just the fine. Repeated misses also feed into account health metrics that influence catalogue visibility over time.
Where the cause was outside your control, yes, and waivers are granted. The two situations that succeed most often are a courier that failed to arrive for a scheduled pickup and a documented platform or regional disruption. What decides it is evidence gathered at the time, not an explanation offered afterwards.
A manifest signed and stamped by the courier is the strongest single document, because it establishes that goods were ready and handover was attempted at a specific time. Add timestamped screenshots of the order state and a support ticket raised on the day. Without a manifest, a waiver request is your account of events against a scan record.
Windows vary with when the order arrives relative to your working hours and pickup schedule, and with your account configuration. This is why sorting your pending queue by order date is actively misleading — a newer order can have less time remaining than an older one. Always work by time remaining.
No. Ready to Ship is a seller-side status indicating your preparation is complete. It carries no weight against the SLA because it does not involve the courier. Only the handover scan closes the window, which is why confirming the pickup actually happened matters more than any status you set yourself.
Run one early batch rather than processing reactively, align your pickup slot with when orders actually arrive, and verify at the end of each batch that every dispatched order has a real handover scan. Most breaches are visibility failures — an order that fell out of attention — rather than sellers who could not pack in time.