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.
The Meesho Supplier Panel shows a status against every order, and the SLA-related ones decide whether that order costs you money. This guide is a plain reference to every SLA state you will encounter, what each one means, what it costs, and exactly what action it demands — so you can glance at the panel and know instantly which orders need you right now and which can wait.
What “SLA status” means
SLA stands for Service Level Agreement — your commitment to dispatch an order within a defined window after it is placed. The SLA status on an order tells you where that order sits relative to its dispatch deadline: comfortable, closing, or already missed. Everything about penalties and account health follows from this one measurement, which is the gap between when the order was created and when the courier scanned the handover. Our full SLA in Meesho guide covers the deadlines and penalties in depth; this page is the status-by-status reference.
The states you will actually see
Three states carry real meaning. Within SLA means comfortable time remains; the order sits in your normal dispatch batch and needs no special handling. If most of your orders are not living here for most of their life, your batch is starting too late in the day. Breaching Soon is the warning zone — hours, not days, remain, nothing has been charged yet, and the order is fully recoverable, but it needs to jump the queue this session. For the detail, see Breaching Soon on Meesho.
Breached means the window closed without a handover. Now a penalty can apply, the order may be auto-cancelled, and the miss feeds your account health. According to Meesho’s supplier guidance, an order unshipped beyond its SLA is auto-cancelled and can incur a penalty of around 5% of product value per day from the order date — and the cancelled sale usually costs more than the fine itself. See Meesho order breach for the full cost.
Dispatch SLA versus delivery SLA
Some panel views distinguish dispatch SLA from delivery SLA, and the difference matters. Dispatch SLA is the window in which you must hand the order over — the one you are measured and penalised on, and the one you control. Delivery SLA is the promise to the customer about arrival date, which depends mostly on the courier network. Put your effort into dispatch SLA; the delivery side is largely out of your hands, and worrying about it wastes attention the dispatch clock needs.
Where the clock actually stops
No SLA status guide is complete without the single most misunderstood point on the whole platform: the clock does not stop when you print the label, pack the parcel, or mark it Ready to Ship. It stops only when the courier partner takes physical custody and the handover is scanned. An order can show “Ready to Ship,” sit fully packed by your door, and still breach — because no scan exists against it. This is why confirming the handover scan matters more than any status you set yourself, and why a courier that does not turn up is the most common cause of an avoidable breach.
How to read your queue each day
The practical routine is to sort your pending orders by time remaining rather than by order date, because SLA windows differ between orders and the oldest order is not reliably the most urgent. Work the shortest countdown first, always. Separate out the truly blocked orders — a stock-out or a label that will not download needs a different fix than a parcel that is simply unpacked — and never let one blocker stall the whole batch. Then confirm the handover scan for everything you dispatch. Our order processing checklist turns this into a repeatable ten-minute routine.
Reading statuses is easy; tracking dozens of them simultaneously, each with a different deadline, while packing and answering customers, is not. That is where breaches actually come from — not from sellers who did not care, but from attention that ran out across too many countdowns. The fix is visibility across every open order at once, which is exactly what an agentic OMS provides.
Sources & further reading
SLA windows, penalty rates and status labels are set by Meesho and can change. This guide explains how the system works; confirm current figures in your Supplier Panel and the official documentation:
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.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
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.
“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.
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.
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.
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.
Meesho label not downloading? Every cause & fix
The 7 real reasons a Meesho shipping label won't generate or download — order state, AWB assignment, browser blocks, sale-day queues — each with its fix, and what a stuck label costs in SLA penalties.
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.
Festival Sale Prep: Stock, SLA and RTO Buffers
Festival demand spikes reward sellers who prepared their operations and punish the ones who did not. How to buffer stock, protect dispatch SLA and plan for the RTO wave.