Meesho SLA: what a missed dispatch actually costs you.

SLA is the single most consequential number in daily Meesho operations, and the one most often misread. It decides whether an order is quietly profitable or expensively penalised, and the gap between those two outcomes is often just a few hours of runway. This guide covers what SLA means, exactly when your dispatch window closes, what a miss costs in rupees, and how to stay ahead of every deadline without watching a clock all day.

What SLA means on Meesho

SLA stands for Service Level Agreement. On Meesho it refers specifically to your commitment to dispatch an order — that is, to hand it to the courier partner — within a defined time window after the order is placed. In practical terms, orders are expected to be shipped within roughly two to three days of the date you receive them, though the exact window attached to any given order is shown against it in your Supplier Panel.

The platform measures one thing: the gap between order creation and courier handover. Everything else — penalties, account-health effects, visibility changes — flows from that single measurement. This is why SLA generates so much seller anxiety: the consequences are large and they hinge on a number that keeps moving whether or not you are looking at it.

When the dispatch window actually closes

The most expensive misunderstanding about SLA is believing the clock stops earlier than it does. It does not stop when you confirm the order, when you print the label, or when you mark the parcel Ready to Ship. It stops at the moment the courier partner takes physical custody and the handover is scanned. Until that scan exists, the countdown continues, regardless of how much work you have already done on the order.

The practical fallout is that an order can be fully packed and sitting by your door and still breach, because no courier scan was ever recorded against it. Sellers rightly find this the most galling way to lose an order, because every visible task was completed — the failure was in the last, invisible step. The discipline that prevents it is simple to state and easy to skip: verify the handover scan actually happened, rather than assuming the pickup occurred.

What a missed SLA costs — in rupees

The reason SLA deserves relentless attention is what sits on the other side of a miss. According to Meesho’s supplier penalty guidance, an order left unshipped beyond its SLA is auto-cancelled, and the penalty can run to around 5% of the product value per day, counted from the order date. On a mid-value order that compounds quickly — and the fine is only the beginning.

The larger cost is usually the cancelled sale itself, which is typically several times the penalty. Beyond that, a miss feeds two performance signals. The first is your Late Dispatch Rate: sustained late dispatches reduce your visibility in the app, which directly reduces future sales. The second is sharper still — catalogs with auto-cancellation rates above a low threshold can be demoted in search layouts for up to 30 days. A run of SLA misses therefore does not just cost you those orders; it suppresses the orders you would otherwise have won over the following month.

Dispatch SLA vs delivery SLA

It is worth separating two things that share the name. Dispatch SLA is the window in which you must hand the order over — this is the one you are measured and penalised on, and the one you control. Delivery SLA is the promise made to the customer about when the parcel arrives, which depends mostly on the courier network rather than on you. Put your operational effort into dispatch SLA, because that is the part that is actually in your hands. Our full SLA status guide breaks down every state you will see against an order.

Why orders drift toward a breach

If SLA misses are occasional, they are bad luck. If they are regular, they are a process problem — and almost always one of four. A courier that did not arrive for a scheduled pickup is the most common, and also the most likely to be waived if you kept the evidence. A dispatch batch that started too late in the day gives every order less runway than it needed. A parcel that was packed but never handed over keeps counting down by the door. And across dozens of orders with different deadlines, nobody was watching the clock, because human attention does not scale to that many simultaneous countdowns.

Three of those four are visibility problems rather than effort problems. That distinction matters, because visibility is exactly what a system fixes and willpower does not. The seller who breaches is rarely the seller who did not care; they are the seller whose attention ran out at the wrong moment. For the last-free-warning before a breach, see Breaching Soon on Meesho.

How to stay ahead of every deadline

The reliable fix is structural, not heroic. Process orders in one early batch rather than reacting to them through the day, so every order inherits maximum runway. Sort your pending queue by time remaining rather than by order date, because SLA windows differ and the oldest order is not reliably the most urgent. Align your pickup slot with when orders actually arrive, so a courier is reliably available before windows close. And confirm the handover scan for every dispatched order, rather than assuming the pickup happened.

Where a miss does occur through no fault of yours, Meesho states it will not charge a penalty for delays outside your control — and 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 on an order. Keep pickup attempt records and timestamps, because a waiver stands or falls on evidence gathered at the time. On the money side, our penalty guide and reconciliation catch charges that should never have been applied.

The two-person team problem

Most Meesho sellers running into SLA trouble are not enterprises with a warehouse team; they are one or two people doing everything — sourcing, listing, packing, customer replies and dispatch. At five orders a day, a careful person can hold every deadline in their head. Somewhere around twenty-five orders a day, they cannot, and the nature of the failure changes. It stops being mistakes and becomes forgotten orders: parcels that were never wrong, just never seen at the moment they needed handling.

This is the wall almost every growing seller hits without noticing, and it is why SLA performance often gets worse as a business grows rather than better. More orders mean more simultaneous countdowns, and the human ability to track them does not increase with volume — if anything it degrades, because each order gets a smaller slice of attention. Recognising this as a structural limit rather than a personal failing is the first step to solving it, because the solution is a different way of working, not simply trying harder. Our two-person team playbook and 1-to-25 orders a day guide go deeper on the operating model that scales.

SLA and your other marketplaces

If you sell on more than one platform, a further trap awaits: the dispatch habits that satisfy Meesho do not automatically satisfy AJIO or Amazon. Each marketplace sets its own windows, measures them its own way, and penalises misses on its own schedule, all against the same single physical dispatch operation you run from one table. Holding two or three independent sets of deadlines in your head at once is where multi-channel sellers start dropping orders that a single-channel seller would have caught. See AJIO SLA breaches for how the same clock behaves under different rules, and selling on multiple marketplaces for the operational reality of running them together.

A worked example: the cost of one bad week

It helps to make the numbers concrete. Imagine a seller doing twenty orders a day at an average product value of ₹500, running a catalogue that is normally healthy. One week, a courier partner starts missing scheduled pickups in their area. Parcels are packed on time and stacked by the door, but three or four a day are not collected, and because the seller is busy they assume “handed to courier” means “scanned.” By the end of the week, a dozen orders have breached.

The visible damage is the penalty — at roughly 5% of product value per day from the order date, a handful of orders sitting unshipped for two or three days each adds up to a real deduction on the next settlement. But the invisible damage is larger. Those twelve orders are auto-cancelled, so the sale value is gone entirely. The Late Dispatch Rate for the week spikes, and because the auto-cancellation rate crossed the demotion threshold, the catalogue’s visibility is quietly reduced for the following weeks. The seller notices their order count falling and assumes demand has dropped — when in fact their own catalogue was demoted out of the search results where buyers would have found it.

This is the compounding nature of SLA misses that makes them so much more dangerous than they first appear. A bad week is not a bad week; it is a bad week followed by a suppressed month. And crucially, the root cause — a courier not scanning pickups — was both detectable and waivable, if anyone had been watching the handover step closely enough to catch it while it was happening. The entire loss traces back to a gap in visibility, not a gap in effort. That is the pattern behind almost every serious SLA problem, and it is exactly the pattern a system that watches every clock is built to close.

Sources & further reading

The penalty figures and dispute process described here are drawn from Meesho’s official supplier documentation. Rates and windows are set by Meesho and can change, so confirm current figures directly:

• Meesho Supplier Hub — Penalty structure & incorrect penalties
• Meesho Supplier Hub — Shipping & delivery charges