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.
Meesho dispatch SLA is the clock that decides your penalties. One measurement — order to handover — drives every dispatch penalty you will ever pay. This guide covers exactly what it measures, where sellers lose orders they had already packed, and the manifest evidence that reverses an unfair penalty.
The clock stops at the handover scan
Meesho measures the interval between an order being created and the goods being handed to the courier partner and scanned. Everything in between — confirming, printing, packing, marking Ready to Ship — is preparation, and none of it stops the clock. An order can be fully packed and sitting by your door and still breach, because no courier scan exists against it. This is the same structural point as SLA status, and it is the single most common cause of an avoidable breach. Confirming the handover scan matters more than any status you set yourself.
What a miss costs
A missed dispatch SLA carries a penalty, and per Meesho’s guidance an order left unshipped beyond its window is auto-cancelled, with a penalty that can run to around 5% of product value per day from the order date. The cancelled sale usually costs more than the fine, and repeated misses feed your Late Dispatch Rate and can trigger a search-visibility demotion. See Meesho penalties for the full deduction picture and order breach for what a confirmed breach costs.
Getting an unfair penalty reversed
Where the cause was outside your control — a courier that failed to arrive, or a documented disruption — a waiver is worth requesting, and Meesho states it will not charge a penalty for delays outside your control. What decides it is evidence gathered at the time: a manifest signed and stamped by the courier is the single most valuable document, because it establishes that goods were ready and handover was attempted at a specific time. Add timestamped screenshots and a same-day support ticket. To dispute an incorrect charge you open the Supplier Panel, go to Support, choose Payments & Penalties, and select the option for an issue with a penalty. Holding the dispatch clock on every open order, so nothing falls out of attention, is exactly what our agentic dispatch tracking is built for. See the daily routine that prevents breaches.
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:
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.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
AJIO SLA breaches: every penalty and how to avoid them
What AJIO measures on dispatch, why the penalty is the smallest part of the cost, and the signed manifest that turns a courier no-show into a waived breach.
SLA in Meesho: full form, dispatch deadlines & penalties
SLA stands for Service Level Agreement — your Meesho dispatch promise. Every status type, the 17:30 cut-off, what a miss costs, and how to never miss one again.
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.
Every Meesho SLA status decoded (and what each one costs)
Within SLA, Breaching Soon, Breached, dispatch vs delivery SLA — every state explained, what it costs, and the one moment that actually stops the clock.
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 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.
“Breaching Soon” on Meesho: what it means and how to clear it
Breaching Soon is a warning, not a penalty — the order is still saveable. What the flag means, how long you have, and how to clear the queue before the clock runs out.
Can you change your Meesho SLA? The honest answer
There is no SLA field to edit. What you can actually adjust — working days, holiday mode, pickup timing, batch start — and why that buys you the same hours.