Every Meesho SLA status, decoded.
One clock decides whether an order is profitable or penalised. Here is what each SLA state means, when it turns expensive, and the one moment that actually stops the countdown.
- SLA status = where an order sits against its dispatch deadline. Three states matter: within, breaching soon, breached.
- Dispatch SLA is yours to control. Delivery SLA mostly belongs to the courier.
- The clock stops at the courier handover scan — not at label print, not at packing.
- Breaching Soon costs nothing yet. Breached costs a penalty plus likely cancellation.
- Robnu watches every countdown and surfaces at-risk orders before Meesho flags them. Free while we figure out pricing.
SLA is the most consequential number in day-to-day Meesho operations, and the one most often misread. This guide is a plain reference: every state you will encounter, what it means financially, and what action it warrants.
What SLA is measuring
SLA stands for Service Level Agreement. On Meesho it refers to your promise to dispatch within a defined window after an order is placed. The platform measures the gap between order creation and courier handover, and everything else follows from that single measurement. Our full SLA in Meesho guide covers the deadlines and penalties in depth.
The reason SLA generates so much seller anxiety is that the consequences are disproportionate to the delay. An order handed over a few hours late does not arrive meaningfully later for the customer — but it can be cancelled outright, costing you the sale as well as the penalty.
The states you will actually see
Each carries a different cost and a different required response.
Within SLA
Healthy. Comfortable time remaining, handled in your normal batch. If most orders are not sitting here for most of their life, your dispatch routine is starting too late. Cost: nil.
Breaching Soon
The warning zone — hours remaining, nothing charged yet, fully recoverable. Jump this order ahead of the queue. See the full breakdown. Cost: nil, if you act.
Breached
Window closed without handover. Penalty applies, auto-cancellation likely, account health affected. Cost: penalty + often the whole sale.
Delivery SLA
The customer-facing promise about arrival date. Driven by the courier network, not by you. Worth monitoring, not worth losing sleep over. Cost: indirect.
A clock that watches itself
Reading SLA statuses is easy. Tracking forty of them simultaneously, each with a different deadline, while packing parcels and answering customers, is not. That is where breaches come from — not from sellers who did not care, but from attention that ran out.
Robnu is an agentic OMS. It holds the dispatch clock for every open order, surfaces the ones drifting toward their deadline before the platform flags them, and keeps the batch moving so the handover actually gets scanned. The status stops being something you check and starts being something that is handled.
You sell. Robnu runs the rest — and makes sure every rupee is paid correctly.
Meesho SLA status, answered
SLA status is Meesho's label for where an order sits relative to its dispatch deadline. SLA stands for Service Level Agreement — the commitment you make to hand an order to the courier partner within a defined window. The status tells you whether that window is comfortable, closing, or already missed.
In practice you will encounter three meaningful states: within SLA (comfortable time remaining), breaching soon (the window is nearly up and the order needs immediate attention), and breached (the window closed without a handover, so penalties and cancellation risk apply). Separately, some views distinguish dispatch SLA from delivery SLA — the first is yours to control, the second largely belongs to the courier.
No, and this misunderstanding causes a lot of avoidable breaches. Printing a label, packing the parcel and marking it ready are all seller-side actions that do not stop the clock. The SLA is satisfied when the courier partner takes physical custody and the handover is scanned. Until that scan exists, the countdown continues.
Dispatch SLA is the window in which you must hand the order over — this is the one you are measured and penalised on. Delivery SLA is the promise made to the customer about when the parcel arrives, which depends mostly on the courier network. Focus your operational effort on dispatch SLA, because that is the part you actually control.
The Supplier Panel shows the SLA state and remaining time against each pending order. The useful discipline is to sort by time remaining rather than by order date, because SLA windows differ between orders and the oldest order is not reliably the most urgent one.
Individual breaches cost you a penalty and often the order itself through auto-cancellation. Repeated breaches are more serious: they feed into account health metrics that influence catalogue visibility, and sustained poor performance can lead to restrictions. The compounding reputational cost usually exceeds the individual fines.
Where the cause was demonstrably outside your control — a courier that failed to arrive for a scheduled pickup, or a verified platform or regional disruption — you can request a waiver through seller support. Success depends almost entirely on evidence: pickup attempt records, manifest timestamps, and a clear ticket trail.
Stop treating dispatch as a reactive task. Process orders in one early batch rather than order-by-order through the day, verify that the handover scan actually happened rather than assuming pickup occurred, and monitor the countdown rather than the order list. Most breaches are visibility failures rather than effort failures.