“Breaching Soon” on Meesho: the last free warning.
It is not a penalty. It is Meesho telling you an order is hours away from missing its dispatch window — and that you can still save it. Here is what the flag means, what a real breach costs, and how to clear the queue before the clock runs out.
- Breaching Soon = an order is close to its dispatch deadline but has NOT breached yet. Nothing has been charged.
- It is a countdown, not a fine. The order is fully recoverable if you hand it over in time.
- A real breach is the expensive one: penalty, possible auto-cancellation, and account-health damage.
- Packed is not dispatched — the clock stops at the courier handover scan, not at the label print.
- Robnu watches every dispatch clock for you and flags at-risk orders before Meesho does. Free while we figure out pricing.
If you sell on Meesho, “Breaching Soon” is one of the first labels that makes your stomach drop. The good news is that it is the cheapest warning on the platform — at the moment you see it, you have paid nothing. The bad news is how easily it slips past a two-person team on a busy day. This guide explains the label precisely, what happens on either side of it, and how to stop seeing it altogether.
“Breaching Soon” is the most misread status on the Meesho Supplier Panel. Read correctly, it is a free gift — a warning that arrives while you can still act. Read wrongly, it becomes the moment a saveable order quietly turns into a penalty and a cancelled sale. This guide explains exactly what the label means, what happens on either side of it, what a real breach costs in rupees, and how a two-person team can stop seeing it at all.
What “Breaching Soon” actually means
Every order you receive on Meesho carries a dispatch SLA — a Service Level Agreement, which is simply a promise that you will hand the parcel to the courier partner within a defined window after the order is placed. On Meesho that window is typically two to three days from the date you receive the order. “Breaching Soon” appears when that window is nearly up and the handover has not yet been recorded against the order.
The single most important word in the label is soon. The order has not breached. No penalty has been applied. Nothing has been deducted from your settlement. Meesho is surfacing the order specifically so you can rescue it, because the platform would far rather you dispatched the parcel late-but-inside-window than not at all. In other words, it is a countdown, not a fine — and it is the cheapest warning the platform will ever give you.
Where sellers lose money is in the translation. Under time pressure, “Breaching Soon” gets read as “already breached,” the seller assumes the penalty has landed, and the order is de-prioritised in favour of ones that feel more urgent. That single misunderstanding converts a free warning into a real charge plus a lost sale. The fix costs nothing: treat every Breaching Soon order as still saveable, because it is.
The three states of the dispatch clock
An order moves through three states relative to its dispatch deadline, and knowing which one you are in tells you exactly what to do next. The first is within SLA: comfortable time remaining, the order sits in your normal dispatch batch and needs no special handling. Most of your orders should live and die here. If they do not — if orders are routinely reaching the warning zone — the real problem is that your dispatch batch is starting too late in the day, which we return to below.
The second state is Breaching Soon: the warning zone. Hours, not days, remain. Nothing has been charged, and the order is completely recoverable — but it now needs to jump the queue ahead of everything else you are packing today. This is a same-session action, not something to add to a list for tomorrow.
The third state is breached. The dispatch window closed without a handover. Now a penalty can apply, the order may be auto-cancelled, and the miss begins to feed your account health. From here it is damage control: dispatch the order if it is still possible, and gather evidence if the cause was outside your control. For the full breakdown of what a breach costs and how it is recorded, see our guide on the Meesho order breach.
Where the dispatch clock really stops
This is the detail that catches out more sellers than any other, so it is worth stating plainly: packed is not dispatched. The SLA clock does not stop when you confirm the order, when you print the label, or when you seal the bag and mark it Ready to Ship. It stops at one moment and one moment only — when the courier partner takes physical custody of the parcel and the handover is scanned.
The practical consequence is brutal in its simplicity. An order can be fully packed, labelled and sitting by your door, and still breach, because no courier scan exists against it. Sellers describe this as the most frustrating way to lose an order, precisely because all the real work was done — the failure was in the last, invisible step. This is also why confirming the handover scan actually happened matters more than any status you set yourself: your “Ready to Ship” means nothing to the clock; the courier’s scan means everything.
What a real breach costs — in rupees
The reason Breaching Soon deserves your immediate attention is what sits on the other side of it. According to Meesho’s own supplier penalty guidance , an order that remains unshipped beyond its SLA is auto-cancelled, and the penalty can run to 5% of the product value per day counted from the order date. On a ₹599 order, that is not a rounding error — it compounds daily until the order is closed out.
But the penalty is rarely the largest cost. When an order is auto-cancelled you lose the entire sale, which is typically several times the fine itself. Worse, the miss feeds two performance signals that compound over time. The first is your Late Dispatch Rate (LDR): sustained late dispatches reduce your visibility in the Meesho app, which directly reduces future sales. The second is even sharper — catalogs with auto-cancellation rates above 2% can be systematically demoted in search layouts for up to 30 days. In other words, a run of breaches does not just cost you those orders; it quietly suppresses the orders you would otherwise have won over the following month.
Why orders reach the warning zone in the first place
If Breaching Soon shows up once a month, it is bad luck. If it shows up weekly, it is a process problem — and in almost every case it is one of four. The most common is a courier that simply did not arrive: your parcel was ready, nobody collected it, and the clock kept running. This is also the cause most likely to be waived, provided you kept the evidence — which we cover in the pickup escalation playbook.
The second cause is a batch that started too late. Orders processed at six in the evening have a fraction of the runway that the same orders would have had at eleven in the morning. The third is the packed-but-never-handed-over trap described above — the bag by the door that the panel keeps counting against. And the fourth is the quietest: nobody was watching the clock. Across forty orders with forty different deadlines, human attention simply does not scale, and orders fall out of view not through carelessness but through sheer volume.
Notice that three of those four are visibility problems rather than effort problems. The seller was not lazy; the information was not in front of them at the moment it mattered. That distinction is the whole game, because visibility problems are exactly what software solves and heroics do not.
Clearing a Breaching Soon queue today
If you are staring at a list of at-risk orders right now, work in a fixed order. First, sort by time remaining, not by order date — SLA windows differ between orders, so the oldest order is not reliably the most urgent, and working the shortest countdown first is the only safe rule. Second, separate 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 one blocker should never stall the whole batch.
Third, get the handover physically scanned. Do not assume a pickup that was “collected” was also scanned — confirm it, because an unscanned pickup leaves the clock running and is the cruellest way to breach. Fourth, log evidence for anything that still slips. If an order breaches because a pickup failed, screenshot the attempt record and the timestamp and raise it: where the cause was genuinely outside your control, Meesho states it will not charge a penalty, and to dispute an incorrect charge you visit the Supplier Panel, open Support, choose Payments & Penalties, and select the option for an issue with a penalty on an order.
Stop reacting to the warning
Everything above is something a diligent seller can do by hand — for a while. The problem is that watching dozens of independent countdowns, each with its own deadline, while packing parcels and answering customers, is exactly the kind of work humans are worst at and software is best at. The breaches that hurt are almost never the result of a seller who did not care; they are the result of attention that ran out.
This is the half of the problem Robnu is built to remove. As an agentic OMS, it tracks the dispatch clock on every open order, surfaces the ones drifting toward their deadline before Meesho flags them, and keeps the dispatch batch moving so the handover actually gets scanned. You stop discovering at-risk orders and start never having them — and on the money side, our penalty guide and reconciliation catch any charge that should not have been applied in the first place.
Sources & further reading
The penalty figures and dispute process above are drawn from Meesho’s official supplier documentation. For the current, authoritative details, always check the source directly:
- Meesho Supplier Hub — Penalty structure & handling incorrect penalties
- Meesho Supplier Hub — Shipping & delivery charges
Penalty rates, SLA windows and support paths are set by Meesho and can change. This guide explains how the system works; confirm current figures in your Supplier Panel.
What the label actually means
Every Meesho order carries a dispatch SLA — a promise that you will hand the parcel to the courier partner within a defined window after the order is placed. “Breaching Soon” appears when that window is nearly up and the handover has not been recorded.
The critical word is soon. The order has not breached. No penalty has been applied. Meesho is surfacing the order so you can rescue it, which is genuinely helpful — the platform would rather you dispatched late-but-inside-window than not at all.
Safe, Breaching Soon, Breached
An order moves through three states relative to its dispatch clock. Knowing which one you are in tells you whether to act now, act today, or start a claim.
Within SLA
Comfortable time remaining. The order sits in your normal dispatch batch and needs no special handling. Most orders should live and die here — if they do not, your batch timing is starting too late in the day.
Breaching Soon
The warning zone. Hours, not days. Nothing charged yet, and the order is completely recoverable — but it now needs to jump the queue ahead of everything else you are packing today. This is a same-session action.
Breached
The window closed without a handover. Now a penalty can apply, the order may be auto-cancelled, and the miss feeds your account health. From here it is damage control: dispatch if still possible, and gather evidence if the cause was not yours.
Why the flag keeps appearing
If Breaching Soon shows up once a month, it is bad luck. If it shows up weekly, it is a process problem — and almost always one of four:
- The courier did not turn up. Your parcel was ready; nobody collected it. This is the most common cause and the one most likely to be waived — if you kept the evidence.
- The batch started too late. Orders processed at 6pm have far less runway than the same orders processed at 11am.
- Packed, never handed over. The bag sat by the door. The panel kept counting. Nobody noticed.
- Nobody was watching the clock. Across forty orders with different deadlines, human attention simply does not scale.
Notice that three of the four are visibility problems, not effort problems. That is the part software actually fixes.
Clearing a Breaching Soon queue today
If you are staring at a list of at-risk orders right now, work in this order.
Sort by time remaining, not by order date
The oldest order is not always the most urgent — SLA windows differ. Work the shortest countdown first, always.
Separate the truly blocked
Out of stock or a label that will not download needs a different fix than a parcel that is simply unpacked. Do not let one blocker stall the whole batch.
Get the handover scanned
Physically confirm the scan happened. A pickup that was “collected” but never scanned leaves the clock running and is the cruellest way to breach.
Log evidence for anything that slips
If an order breaches because a pickup failed, screenshot the attempt record and raise it. See the pickup escalation playbook.
Stop reacting to the warning
Every fix above is something a diligent seller can do by hand — for a while. The problem is that watching dozens of independent countdowns is exactly the kind of work humans are worst at and software is best at.
Robnu is an agentic OMS: it tracks the dispatch clock on every open order, surfaces the ones drifting toward their deadline before Meesho flags them, and keeps the dispatch batch moving so the handover actually happens. You stop discovering at-risk orders and start never having them.
That is the spine of the product: you sell, Robnu runs the rest — and makes sure every rupee is paid correctly.
Breaching Soon, answered
Breaching Soon is a warning label Meesho puts on an order whose dispatch deadline is close but has not passed yet. It means the order is still inside its SLA window — you have not been penalised — but the remaining time is short enough that Meesho is flagging it. Treat it as a countdown, not a penalty. The order is still fully recoverable if you dispatch it before the window closes.
The warning typically appears in the final hours of your dispatch window, so you should assume hours rather than days. The exact remaining time is shown against the order in your Supplier Panel — that countdown is the number that matters, not the label itself. If you are seeing the flag for the first time on a given order, act on it the same working day.
Once the dispatch window closes without a handover, the order moves from Breaching Soon to breached. At that point Meesho can apply a penalty, the order may be cancelled automatically, and repeated breaches feed into your account health and visibility. The cancellation is often the more expensive half — you lose the sale as well as paying the penalty.
No. Breaching Soon on its own is free — it is a warning, not a charge. Nothing is deducted at this stage. The cost only lands if the order tips over into an actual breach. This is precisely why the flag is useful: it is the last free moment to save the order.
Packing is not dispatch. The SLA clock stops when the parcel is handed over and scanned by the courier partner, not when you print the label or seal the bag. Orders sitting packed but not handed over will keep counting down. If you are seeing this pattern repeatedly, the bottleneck is your pickup or manifest step, not your packing.
Sometimes. Where the cause was outside your control — a courier failed to arrive for pickup, or a verified platform or regional disruption occurred — you can raise the case with seller support and ask for a waiver. Evidence decides it: pickup attempt records, manifest timestamps and ticket history. Keep those, because a waiver request without proof rarely succeeds.
The reliable fix is structural rather than heroic. Process orders in one batch early in the day instead of reacting order-by-order, make sure the handover scan actually happens rather than assuming pickup occurred, and watch the deadline clock rather than the order list. Most breaches happen not because a seller was lazy but because nobody was watching a countdown across dozens of orders at once.
No, and the distinction is worth money. Breaching Soon means at risk but still inside the window. Breached means the window has closed and the consequences apply. Sellers often use the words interchangeably and then assume a penalty has already landed when it has not — and stop chasing an order that was still saveable.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
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 orders stuck in pending: what it means and how to clear them
Blocked does not mean paused — the dispatch clock usually keeps running. The four causes, which two you can fix yourself, and what to document when you cannot.
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.
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.
One Screen for All Your Orders: The Case for Centralized Order Processing
Selling on three marketplaces means three dashboards, three SLA clocks and three ways to miss an order. Here is why a single order screen — an agentic OMS that runs them all — is the fix.
Account health metrics that actually trigger action
Which seller metrics carry real consequences, which are informational, and the quiet four-stage sequence that runs before a restriction ever appears.
Order breach in Meesho: what it is and how to prevent it
What a breach flag means, the seven ways orders drift past the dispatch promise, what one costs at settlement, and the daily loop that keeps the count at zero.