“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.
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.