Meesho pickup not happening? Here's how to escalate before it costs you.
Your parcels are packed, the panel says Ready to Ship, and the courier simply doesn't come — or worse, a “pickup attempted” scan appears for a visit that never happened. Meanwhile the dispatch clock keeps running. This guide covers how pickups actually work, how to tell a real miss from a fake scan, the escalation ladder that gets parcels moving, and what a no-show week does to your payout.
- A Meesho pickup exists once the order is Ready to Ship and a courier + AWB is assigned; the courier should collect within the pickup window. The dispatch SLA clock does not pause for a no-show — the deadline was set when the buyer ordered.
- Separate a genuinely missed pickup from a false 'pickup attempted' scan. The fake scan says you were unavailable; your timestamped photos of packed parcels say otherwise. That difference decides who eats the penalty.
- Escalate on a ladder, same day: reschedule from the panel, then a ticket with sub-order numbers, then daily follow-ups citing the ticket, then an escalation email. Never hand parcels to an unverified courier person, and never self-drop without written instruction from support.
Real miss or fake scan? Read the trail, not the panel
When your order reaches Ready to Ship, Meesho assigns a courier partner and issues an AWB, and your pickup location lands on a field executive's route. The executive is expected to collect within the pickup SLA window — usually the same or next working day. You do not choose the courier, and you cannot see the route; all you see is whether a person with a scanner arrived. That opacity is exactly why the scan trail matters more than the panel status.
A genuinely missed pickup leaves a clean absence: no visit, no scan, status quietly rolling to the next day. Annoying, but honest — and usually a capacity or route problem that a reschedule fixes. The false-attempt scan is the dangerous cousin: the tracking shows “pickup attempted — seller unavailable” or “pickup rescheduled” at 6:40pm when nobody came all day. A route executive under pressure closed your stop without reaching it. The record now blames you, and if a breach penalty follows, that scan is the story Meesho's system believes.
So the first diagnostic is never “why no pickup?” but “what does the scan trail claim happened?” A no-scan day and a false-attempt day look identical at your doorstep and completely different in a dispute. Note the scan time against reality, every time.
Climb one rung a day, and document every rung
The ladder works because each rung creates a record the next rung can cite. Skip rungs and you arrive at escalation with nothing in hand.
- 01
Verify your side first
Before blaming the courier, confirm the basics: the order is genuinely Ready to Ship with an AWB assigned, your pickup address and phone number in the panel are current, and someone was reachable at the location during the window. A wrong phone number is the one no-show cause that really is on your side of the fence.
- 02
Reschedule from the panel, same day
Use the supplier panel's reschedule option the day the pickup fails. It routes your pincode back into the next day's run and creates the first timestamped record that you flagged the miss. One reschedule is routine; the value is in the paper trail it starts.
- 03
Second miss: raise a ticket with sub-order numbers
If the rescheduled pickup also fails, open a support ticket and list every affected sub-order number. Specific IDs get actioned; 'pickup not happening' in general terms gets a template reply. State the dates, the number of parcels ready, and attach your photos. Note the ticket number — it is your reference for every later step.
- 04
Follow up daily, citing the ticket
One follow-up per day on the same ticket, each adding the new day's non-pickup to the record. Daily, polite, specific persistence signals an operational failure being documented — and builds the exact timeline you will need if penalties land at settlement anyway.
- 05
Contest false-attempt scans immediately
The moment a 'pickup attempted' or 'rescheduled' scan appears for a visit that never happened, reply on the ticket with the scan time versus reality, attach your timestamped photos of packed parcels, and CCTV if you have it. Contest it the same day — a false scan left unchallenged becomes the official version.
- 06
Escalate in writing past the first line
If parcels are still sitting after several documented days, send an escalation email referencing the ticket number, the full day-by-day timeline, and the total order value now at SLA risk. A written escalation with a clean evidence trail moves differently through support than a fresh complaint — because it shows you can prove the whole story.
- 07
Know what never to do
Never hand parcels to any courier person unless the panel shows a pickup in progress and their scanner reflects your AWBs — parcels handed over without a pickup scan are parcels that officially never left you. And never self-drop at a hub unless Meesho support instructs it in writing inside the ticket. Both shortcuts convert a delay into a dispute.
A no-show week, priced in rupees
Run the numbers for a seller doing 10 orders a day at a ₹350 average. Two days of no-shows is 20 packed parcels going stale — no cash cost yet, but every one of them carries a live SLA clock. By day three the earliest orders cross their dispatch deadlines and breach penalties start queueing for settlement; call it ₹40–₹60 per breached order and the meter reads over a thousand rupees before the week is half done. By day five the oldest orders start auto-cancelling: order value gone, stock stranded at home, and buyers who ordered elsewhere. Seventy orders into the week, the compounding stops being abstract — penalties on one layer, cancelled order value on another, and an account-health hit shrinking next month's order flow on top.
Now price the alternative: a reschedule on day one, a ticket on day two, photos taken in thirty seconds each evening. The escalation ladder costs you minutes. The no-show week costs you the margin of a good month — and the difference between the two is almost entirely whether you started documenting on the first quiet afternoon or the fourth.
Escalate before the penalty, not after it
The whole playbook above depends on one thing sellers are worst at during a busy week: noticing early. A no-show on a normal Tuesday is invisible — the parcels sit in the corner, the panel looks fine, and the problem surfaces two weeks later as a deduction on the settlement sheet. Robnu's SLA watchdog exists for exactly this gap: it tracks every AJIO and Meesho order against its dispatch deadline from the moment it lands, and flags orders drifting toward breach while there is still time to climb the ladder.
And because Robnu runs the whole order pipeline, the evidence timeline you need is already captured — when the order went Ready to Ship, when the AWB was assigned, what scans appeared and when. When you raise the ticket, the day-by-day story is a record you already have, not a memory you reconstruct. That is the difference between contesting a penalty and eating one.
Meesho pickup problems, answered
Once an order is Ready to Ship, Meesho assigns a courier partner and an AWB, and the courier is supposed to collect within the pickup window. No-shows usually come down to route-level problems on the courier's side: an overloaded pickup executive, your pincode sitting at the end of a route, a route reassignment, or sale-week volume swamping capacity. Occasionally the address or phone number on your pickup location is wrong in the panel. None of these pause your dispatch SLA, which is why a quiet no-show day is never actually quiet.
It means the courier's system recorded an attempt that did not physically happen — a scan marked 'pickup attempted, seller unavailable' or 'pickup rescheduled' while you were standing next to packed parcels all day. Field executives under route pressure sometimes close out stops they never reached. The scan matters because it shifts the story: the record now says you were the problem. That is why noting the scan time against what actually happened, with timestamped photos of the parcels ready, is the single most useful habit in this entire guide.
No. The dispatch deadline was set when the order was placed, and it keeps running whether or not the courier turned up. If a breach happens because of courier no-shows, the penalty can be contested — but only if you can show the parcels were ready and the failure was on the pickup side. Tickets raised on the day, with sub-order numbers and photos, are what get penalties waived. Silence followed by an appeal a week later, with no evidence trail, almost never works.
Not on your own initiative. Self-drop outside the process means parcels entering the network without a proper pickup scan, and if anything goes wrong in transit you have no protected handover to point to. The exception is when Meesho support explicitly instructs a self-drop — get that instruction in writing inside the ticket, note who authorised it, and keep the hub receipt. If it is not in writing from support, treat self-drop as a way to convert a delayed order into a disputed one.
There is no published magic number, but the pattern is consistent: orders that sit undispatched past their SLA window accumulate breach penalties, and orders that stay stuck long enough get auto-cancelled — taking the full order value with them, plus a hit to account health that reduces your visibility. A week of no-shows on 10 orders a day is not ten small problems; it is up to seventy orders drifting toward penalties and cancellation together. Escalate on day one, not day four.
Robnu runs your AJIO and Meesho operations end to end, and its SLA watchdog tracks every order against its dispatch deadline from the moment it lands. When pickups stall, you are not discovering it from a settlement deduction two weeks later — orders drifting toward breach get flagged while there is still time to escalate, with the timeline already captured: when the order went Ready to Ship, when the AWB was assigned, what scans appeared and when. You escalate before the penalty with the evidence in hand, instead of appealing after it.
Where this comes from
- Meesho supplier documentation on pickup scheduling, dispatch SLAs and support tickets: supplier.meesho.com learning hub.
- Recurring seller reports of pickup no-shows, false “pickup attempted” scans and escalation experiences: public seller community threads (Reddit r/IndiaBusiness, seller Facebook and Telegram groups), 2025–2026.