Order breach on Meesho: what it is, what it costs, and how to make it stop.
“Breach” is the panel's cold word for a missed dispatch promise — and behind that one word sits a penalty at settlement, a cancellation risk, and a slow drag on how often buyers see your catalogs. This guide explains how orders drift into breach, what one actually costs, and the daily routine that makes breaches structurally impossible.
- An order breach means the dispatch deadline passed without a valid courier handover scan. The deadline is set when the order is placed and never pauses — not for a stuck label, a missed pickup, or a weekend.
- One breach costs three ways: a possible penalty at settlement, an auto-cancellation risk that takes the whole order value, and a mark on dispatch metrics that decides how often Meesho shows your catalogs.
- Breaches are a routine problem, not a bad-luck problem. A fixed 15-minute daily loop — accept, label, pack, confirm pickup, re-check the panel — removes almost all of them. Evidence with timestamps handles the rest.
A missed promise, with a clock that never pauses
When a buyer places an order, Meesho commits to a dispatch window on your behalf, and the supplier panel shows you the resulting deadline on every order row. Meeting it requires a chain of small steps: the order accepted, the label generated, the parcel packed, the courier pickup completed, and the handover scan recorded. A breach is simply the deadline arriving before that last scan does. The panel does not ask why. It does not distinguish between a stock-out, a browser problem, and a courier who never showed up — it records the miss.
That indifference is exactly why breaches are worth engineering away rather than arguing about afterwards. The deadline is known the moment the order lands, which means every breach was visible hours or days before it happened. A seller who checks deadlines once a day, in one place, sees the drift early — while every fix is still cheap. A seller who discovers breaches at settlement is paying for information the panel gave away for free a week earlier.
The seven drifts that end in a breach flag
Almost no seller decides to breach an order. Orders drift there through one of seven small failures — each one boring, each one preventable.
- 01
The label gets stuck on dispatch day
A label that will not generate or download blocks everything behind it, and the clock keeps running while you retry. Diagnose within the hour — order state, AWB assignment, browser blocks — and screenshot anything that fails on Meesho's side. A stuck label is the single most common first domino.
- 02
The pickup never shows up
Parcels packed, labels on, and the courier does not come. If you assume the pickup happened instead of confirming it, the miss surfaces two days later as a breach. Confirm every pickup the same evening, and raise the no-show ticket the same day — that ticket is also your waiver evidence.
- 03
Stock ran out after you accepted
Accepting an order you cannot pack starts a countdown you have already lost. Stock-outs usually trace back to selling the same inventory on two marketplaces without reconciling counts daily. Fix the count discipline, and when a genuine stock-out happens, decide fast — a quick cancellation is cheaper than a breach followed by a cancellation.
- 04
The panel goes unchecked for days
Meesho orders do not wait for your next login. A panel checked every two or three days means some orders spend half their dispatch window invisible. The fix costs nothing: one fixed morning check, every day including Sundays, even when you expect zero orders.
- 05
A sale event triples the volume
Routines that work at 8 orders a day quietly fail at 25. Sale-day breaches cluster because labels queue, pickups overflow, and packing runs past the cut-off. Before an event: pre-pack bestsellers, print in batches by deadline, and ask for the earliest pickup slot you can get.
- 06
Packed, handed over — never scanned
The breach check runs on the courier's handover scan, not on your memory of the handover. A parcel that leaves without being scanned is, to the system, a parcel that never left. Watch the scan happen, keep the manifest copy, and match scans against orders the same evening.
- 07
Everything waits for the cut-off hour
Dispatch compressed into the final hour has no slack for a printer jam, a login glitch, or one missing polybag. Sellers who label in the morning and pack by early afternoon breach rarely — not because problems skip them, but because their problems land with hours of margin instead of minutes.
- Connect
- Sync
- Batch
- Confirm
- Upload
- List
- Slips
- Invoices
- Docs
- Manifest
- Closed
One breach is cheap. The habit of breaching is not.
Take an illustrative ₹450 order. The direct penalty at settlement might be a few tens of rupees — annoying, survivable. But if the order sits long enough to be cancelled, the whole ₹450 goes with it. And the third cost is the one that compounds: dispatch metrics feed account health, and account health feeds visibility. A seller breaching a handful of orders every week is quietly bidding against their own future orders. Ten breaches a month on a 15-order-a-day store can cost more in lost ranking than in every penalty combined — you just never see that number on any statement.
The countermeasure is a daily loop, run at the same time every day: accept new orders, generate every label immediately, pack against the deadline list rather than the arrival list, confirm the pickup scan happened, and sweep the panel once more before evening. Sellers who run this loop describe the same result — breaches stop being events and become a metric stuck at zero.
Breaches are a routine problem. Robnu is the routine.
Everything in this guide is a discipline a two-person team can keep up on a good week. Robnu exists for the other weeks. It runs the order-to-manifest pipeline on AJIO and Meesho end to end: new orders picked up the moment they land, labels generated and fetched automatically with retries when the marketplace glitches, packing lists ordered by dispatch deadline instead of arrival time, and a watchdog on every order's SLA clock so drift shows up as an alert this morning, not a breach flag next week.
And because every step is logged with timestamps, the rare breach that was never your fault arrives with its waiver evidence already assembled — the failed-generation log, the pickup gap, the ticket trail — instead of a screenshot hunt three days after the fact.
Order breaches, answered
A breach is Meesho's term for an order that missed its dispatch promise — the deadline by which the parcel had to be packed, labelled and handed to the courier. Every order carries this deadline from the moment it is placed, and it is visible in the supplier panel. When the deadline passes without a valid handover scan, the order is flagged as breached. That flag follows the order to settlement, where a penalty can be deducted, and it feeds your account-level dispatch metrics, which influence how often Meesho shows your catalogs to buyers.
Meesho does not publish one fixed number, and the policy has changed over time, so treat any specific figure you see in seller groups as dated. In practice sellers report deductions that scale with order value and repeat behaviour, applied at settlement rather than at the moment of breach. The bigger costs are usually indirect: a breached order can be auto-cancelled, which takes the whole order value, and repeated breaches drag account health and visibility down. Check the current penalty policy on your supplier panel — that is the only version that counts.
Often yes, and usually you should. A breach flag does not automatically cancel the order — until Meesho or the buyer cancels it, dispatching late is almost always better than not dispatching at all, because a delivered order still pays out while a cancellation takes the entire order value and adds a cancellation mark on top of the breach. Move the breached order to the front of your next pickup, and if the delay was caused by something outside your control, capture the evidence before it disappears from the panel.
Sellers do get breach penalties reversed, but only with evidence that the cause was not theirs: a label that failed to generate, a courier pickup that never arrived, a panel outage on dispatch day. The pattern that works is screenshots with visible timestamps, ticket numbers raised on the same day, and pickup logs showing the parcel was ready. Waivers are decided case by case, so nothing is guaranteed — but sellers who can prove the timeline win far more of these than sellers who describe it from memory a week later.
Structurally, not heroically. Breaches come from gaps in routine: the panel checked once every two days, labels printed in a panic, pickups assumed rather than confirmed. The fix is a fixed daily loop — accept new orders every morning, generate labels immediately, pack against a checklist, confirm the pickup actually happened, and check the panel again before end of day for stragglers. A 15-minute loop run every single day beats a three-hour catch-up run twice a week, because the SLA clock never waits for your schedule.
Robnu runs the daily loop for you on AJIO and Meesho: it picks up new orders as they land, generates and fetches labels the moment they are available, retries failed documents automatically, and watches every order against its dispatch deadline. Orders drifting toward the cut-off surface as alerts ranked by urgency, so the one order that needs you today is impossible to miss. And because Robnu logs every step with timestamps, the evidence for a waiver request is already captured when a breach genuinely was not your fault.
Where this comes from
- Meesho supplier documentation on dispatch SLAs, order states and penalty policy: supplier.meesho.com learning hub — always check the current policy on your panel.
- Recurring seller reports of breach penalties, waiver outcomes and sale-day dispatch failures: public seller community threads (Reddit r/IndiaBusiness, seller Facebook and Telegram groups), 2025–2026.