'I want to deprioritize my courier partner': what the Meesho option actually does.
You cannot pick a courier per order on Meesho. What you can do is ask Meesho to allocate fewer of your pickups to one partner that keeps failing you. Here is when that request is worth raising, what to attach, and how to tell whether it worked.
“I want to deprioritize my courier partner” is an option in the Meesho Supplier Panel’s support flow that asks Meesho to allocate fewer of your orders to one named courier for your pickup pincode. It is not a per-order courier choice and not a guarantee. Use it when one courier shows repeated missed pickups, false scans or a high RTO share over several weeks, and attach order-level evidence.
- Meesho allocates the courier for every order; sellers never choose one per shipment.
- Deprioritisation asks Meesho to lower one courier's share of your pickups, typically over days, not instantly.
- Raise it only on a sustained pattern: missed pickups, false scans, RTO share or weight disputes clustering on one partner.
- Attach sub-order IDs, dates, AWBs, scans versus reality, and photos. A ledger beats a complaint.
- Judge success by pickup success and RTO share per courier over the next 30 days, not by a confirmation message.
What a deprioritisation request changes
Your orders still flow into Meesho’s allocation. One lane gets thinner. The others carry more. Nothing is switched off.
Sellers type the exact phrase “I want to deprioritize my courier partner” into search because it is what the Meesho panel shows them, and nobody explains what clicking it does. This guide does: what the request asks for, when it is worth raising, what to attach so it is taken seriously, and how to know afterwards whether anything changed.
Meesho picks the courier, not you
Every Meesho order is allocated to a courier partner by Meesho at the moment it moves to ready to ship. The panel assigns the AWB, the courier is decided, and the label carries that courier’s name. You never choose it per shipment. The allocation considers which partners serve the buyer’s pincode and yours, what each costs on that lane, and how much capacity each has that day. A large share of shipments now move through Valmo, Meesho’s own logistics network, alongside partners such as Delhivery, Shadowfax, Xpressbees and Ecom Express, and which one you get on a given order can change from day to day. Our courier partners guide covers who these partners are and how the forward and reverse legs are charged.
That design is efficient for Meesho and mostly fine for you, right up until one partner starts failing at your pickup location. Then the lack of choice becomes the whole problem. Parcels sit packed, the executive never comes, a scan says “seller unavailable” while you were standing next to the bags, and the SLA clock runs through all of it. The support flow’s deprioritisation option exists for exactly this: a way to tell Meesho, with evidence, that a specific courier should carry less of your volume.
What the deprioritisation request actually asks for
In plain words, the request says: for orders picked up from this location, please lower this courier’s priority in your allocation. Typically, if Meesho’s logistics team accepts it, the allocation logic starts favouring the other partners serving your pincode, and the named courier’s share of your new AWBs falls over the following days. It is a nudge to the allocation, not a switch. Three things it does not do are worth stating plainly, because sellers raise the request expecting them.
- It does not give you a per-order courier choice. You still cannot pick a partner when you process an order. Allocation stays with Meesho.
- It does not guarantee the courier disappears. If that partner is the only one serving a buyer’s pincode, or the others are at capacity, it will still be assigned. You will usually see its share fall, not reach zero.
- It does not fix a bad route by itself. If your pincode sits at the end of every courier’s route, shifting volume from one partner to another moves the symptom rather than the cause.
Read it as a lever that changes probabilities. Fewer allocations to a failing courier means fewer missed pickups, fewer false scans and fewer RTOs from that source. That is valuable, but only if the failure really is concentrated in one partner, which is why the evidence step comes before the request, never after.
Symptom, likely cause, and whether to deprioritise
Deprioritisation only helps when the failure is concentrated in one courier. Match your symptom before you raise anything.
| Symptom | Likely cause | Deprioritise or not |
|---|---|---|
| Missed pickups, always the same courier, other couriers collect fine | That partner's route or executive at your pincode | Yes. Classic case. Attach the missed-pickup dates and photos. |
| 'Pickup attempted, seller unavailable' scans while parcels were ready | False scans closing out stops the executive never reached | Yes, and raise each false scan as its own pickup ticket too. |
| RTO share on one courier far above the others over 30 days | Weak last-mile delivery or fake delivery attempts on that partner | Yes, if the gap holds across similar pincodes and products. |
| Weight discrepancy disputes clustering on one courier | That partner's hub re-weighing or dimension capture | Maybe. Dispute the charges first; deprioritise if the pattern continues. |
| Missed pickups across every courier | Your pickup address, phone, timings, or a hard-to-reach location | No. Fix the pickup address setup and contact details first. |
| High RTO everywhere, not one courier | Product, price, address quality or buyer profile, not logistics | No. Work the RTO causes; deprioritising moves nothing. |
| One bad week during a sale event | Volume swamping every courier's capacity | Not yet. Wait for two to four normal weeks of data before deciding. |
The two numbers that justify the request and prove the result
Pickup success and RTO share, per courier, over a rolling 30 days. Before the request they are your evidence. After it they are your verdict.
When it is worth raising, and when it is not
The request is worth raising when one courier is measurably worse than the others serving your pincode over a sustained window. Four patterns qualify. The first is repeated missed pickups from the same partner while other couriers collect from the same door without trouble; our guide on pickups not happening covers the day-one escalation you should already be doing for each of those. The second is false “pickup attempted” scans, which are worse than a plain no-show because the record now says you were the problem. The third is an RTO share on one partner that sits far above the rest across the same kinds of pincodes and products; our courier RTO rates guide explains how to compare partners fairly. The fourth is fake delivery attempts on the forward leg, where the buyer never got a call and the parcel came back as RTO anyway.
It is not worth raising when the problem is everywhere. Missed pickups across every courier usually point at your pickup address, contact number, timings or a location the executives struggle to find. High RTO across every courier points at product, price, address quality or buyer profile. And one terrible week during a festive sale is not a pattern, it is volume swamping every partner at once. In each of those cases the request may still be accepted, but nothing improves, because the courier was never the cause.
Evidence to gather before you raise it
Meesho’s logistics team is being asked to override its own allocation for your location, so the request has to make the case in numbers. Start with a courier-level table for the last 30 days: orders allocated per courier, pickups on time, missed pickups, false scans, RTOs. If you already track every AWB against its courier and outcome, this takes minutes. If you do not, the panel’s order and shipment views will usually let you export enough to build it once.
Then go order-level for the worst cases. For each, record the sub-order ID, the AWB, the date, the scan the courier recorded and what actually happened. Timestamped photos of packed parcels ready on a missed-pickup day are the strongest single item you can attach, because they answer the “seller unavailable” scan directly. If weight disputes are part of the pattern, include the booked weight, the charged slab and your own weighing photos; our guide on disputing weight discrepancies shows what a winnable dispute looks like. If a return went missing in that courier’s reverse leg, the lost return guide covers the separate claim you should file for it.
How the request typically flows
You raise it from the Supplier Panel’s help or support section, typically under the pickup or courier problem categories, where “I want to deprioritize my courier partner” appears as an option. You name the courier, select the pickup location if asked, describe the pattern and attach the evidence. A ticket is created. Typically it is reviewed within a few working days and, if accepted, the allocation for your location is adjusted over the days that follow. You will usually not receive a message saying “done”; the change shows up as a falling share of new AWBs going to that courier. If the ticket is closed with a template answer and nothing changes, reply on the same ticket with updated numbers rather than opening a new one, and follow the escalation ladder in our Meesho seller support escalation guide.
Keep dispatching normally while you wait. The request changes future allocation; it does nothing for orders already assigned, and the dispatch SLA on each of those keeps running regardless of which courier is supposed to collect. A pickup that does happen still needs a packed parcel at the door.
Raising the request properly, in seven steps
Export or list every order from the last 30 days with its AWB, courier partner, ready-to-ship date, pickup scan date, delivery outcome and RTO status. Group by courier. You are looking for one partner whose pickup success or RTO share is clearly worse than the rest. Without this table the request has no weight.
For the worst 10 to 20 orders, note the sub-order ID, the date, the scan the courier recorded (for example 'pickup attempted, seller unavailable') and what actually happened. Timestamped photos of packed parcels ready on those days are the strongest single piece of evidence you can attach.
In the panel, go to the help or support section and look for the shipping and pickup issue categories. 'I want to deprioritize my courier partner' typically sits under pickup or courier problems. Pick it, name the courier, and select your pickup location if asked. Labels move around from time to time, so search the help section if you do not see it at first.
State the courier, the pickup pincode, the window, and the numbers: orders allocated, pickups on time, missed pickups, false scans, RTO share. Then attach the order list and photos. Keep it factual and short; the reviewer needs to see a pattern in under a minute.
Do not change your dispatch routine while you wait. Orders keep arriving and the SLA clock keeps running on each one, so any pickup that does happen still needs the parcel packed and ready. Note the ticket number in your own records with the date raised.
Count new AWBs by courier for the two weeks after the ticket and compare with the two weeks before. If the deprioritised courier's share has fallen and your pickup success has risen, it worked. If nothing moved, reply on the same ticket with the updated numbers rather than opening a new one.
The real test is not the allocation mix but the outcomes. Watch RTO share and on-time pickup by courier for a further month. If the remaining couriers perform well, the request paid for itself. If a different courier now shows the same pattern, the problem may be your pincode or route, not one partner.
The problems that usually sit next to this one
Pickup not happening
The day-one routine for a no-show: ticket, photos, sub-order IDs, and why the SLA clock does not wait.
Fake delivery attempts
How to prove a delivery attempt never happened and what to attach so the RTO charge is reversed.
Courier RTO rates
How to compare partners fairly by lane and product before you blame one of them.
How to measure whether it helped
The verdict is not the ticket status. It is two numbers, per courier, over the 30 days after the request compared with the 30 days before. The first is pickup success: of the orders allocated to each courier, how many were collected on the first scheduled day. The second is RTO share: of the orders each courier delivered on the forward leg, how many came back. If the deprioritised courier’s share of new AWBs has fallen and your overall pickup success and RTO share have improved, the request paid for itself. If its share fell but the outcomes did not move, the problem was never that partner. If nothing moved at all, the request was not applied, and you reply on the ticket with the new numbers.
Watch one more thing. Occasionally a different courier starts showing the same pattern a few weeks later. That usually means the underlying issue is your pincode or route, not any single partner, and the fix lies in your pickup setup rather than in another deprioritisation request.
The money behind a bad courier
A failing courier costs more than the annoyance. Missed pickups become SLA breaches, and breaches become penalties and auto-cancellations. RTOs cost forward freight and often reverse freight, on a sale that never happened. Weight disputes that go unchallenged bill you a heavier slab on every parcel. All of it lands on your settlement as deductions that need no approval from you. That is why the courier-level record matters beyond this one request: it is the same record that lets you check every shipping charge against the shipment it actually was, and reclaim the ones that are wrong.
Sources & further reading
Support flow labels, courier partners and allocation behaviour are set by Meesho and change from time to time. Confirm the current option names in your own Supplier Panel.
The courier record that makes the request, and checks the result
Robnu does not talk to couriers and does not raise Meesho tickets for you. It is the agentic OMS for Meesho, AJIO and Amazon sellers: it runs the daily order operations, sync, processing, returns and claims, and reconciles every settlement so each rupee the marketplace pays is correct. Along the way it keeps the record this request needs: which AWB went to which courier, when the pickup scan landed, which orders came back as RTO, and what each leg was charged. That is your evidence before the ticket and your verdict after it.
Free for every seller right now, and forever free under 25 orders a day when paid pricing launches. See how it runs Meesho operations or the full order management system overview.
Deprioritising a courier on Meesho, answered
It is an option inside the Meesho Supplier Panel's support flow. Choosing it raises a request asking Meesho to reduce how often a named courier partner is allocated to orders from your pickup location. It does not let you pick a courier per order and it does not remove that courier entirely. It asks Meesho's logistics team to shift more of your pickups to the other couriers serving your pincode.
No. Meesho allocates the courier for every order based on serviceability, cost and capacity at the buyer's pincode and yours. The seller never selects a courier at the shipment level. Deprioritisation is the closest thing to control you have: it nudges the allocation away from a courier that is failing you, without giving you a per-order choice.
When one courier is measurably worse than the others serving your pincode over a sustained window. Repeated missed pickups, false 'pickup attempted' scans, an RTO share far above your other couriers, fake delivery attempts on the forward leg, or weight discrepancy disputes that all cluster on one partner. A single bad week is not enough. Two to four weeks of order-level evidence is.
Typically the ticket is reviewed within a few working days and, if accepted, the allocation shifts gradually over the days that follow rather than switching off overnight. You will usually see the change as a falling share of new AWBs assigned to that courier, not as a confirmation message. Keep the ticket number and check the allocation mix after two weeks.
Usually yes. If that courier is the only one serving a particular buyer pincode, or the others are at capacity, Meesho will still allocate it. Deprioritisation lowers priority; it is not a block. Treat any remaining allocations to that courier as expected, and keep tracking their outcomes so you can escalate again if the problem persists.
Not directly. Your dispatch SLA is still measured from order placement to the handover scan, whichever courier collects. What changes is the likelihood of a no-show, and fewer no-shows mean fewer breaches. If a breach was caused by the courier you have asked to deprioritise, raise the penalty waiver separately with the same evidence.
Sub-order numbers and AWBs for every affected order, dates, the scan that was recorded versus what actually happened, timestamped photos of packed parcels on missed-pickup days, and a simple count: orders allocated to that courier, how many were picked up on time, how many became RTO. A ticket that reads like a ledger gets acted on. A ticket that reads like a complaint gets a template reply.
No. Robnu does not talk to couriers and does not raise Meesho support tickets on your behalf. What it does is keep the per-courier record you need: which AWB went to which partner, when the pickup scan landed, which orders came back as RTO, and what the settlement charged for each leg. That record is the evidence for the request, and the proof afterwards of whether it worked.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
Meesho Courier Bag Size Guide: Which Packaging Bag to Use for Each Product
Meesho courier bag sizes in inches, what fits in each, how the bag changes your weight slab, the barcoded packaging rule, where to buy bags and what they cost.
Staggered Delivery Meaning in Courier Tracking (Meesho, DTDC, Delhivery)
Staggered delivery means the courier is delivering a shipment in more than one stage or attempt. How it shows on Meesho, DTDC and Delhivery, and when to act.
Valmo Courier and Meesho: Tracking, Pickups and Problems
Valmo is the logistics network Meesho launched in 2024. How allocation works, how to track a Valmo shipment, pickup problems, and fake customer care numbers.
Shipment lost in transit: claiming from the marketplace vs the courier
A vanished parcel loses stock, sale and freight at once, and a loss is an absence that never announces itself. Who to claim from, what proves a loss, and how to catch it in time.
Courier hidden fees: the stack beyond base freight
Fuel surcharge, COD collection, ODA, RTO legs, peak-season and handling fees, what each is, where it hides in settlements, and which are disputable versus plain shipping cost.
“Courier return” on Meesho: who pays and how to claim
The delivery partner failed and the freight lands on your settlement. What the status means, when the charge is fair, and the four charges worth challenging.
Meesho Low Shipping Image Generator: Why It Cannot Cut Charges
Meesho shipping charge image generators only resize a picture. The fee follows the packed parcel's weight slab and zone, so here is what actually reduces it.
Meesho Packaging Weight Slab: Cut Your Shipping Tier 2026
Your product weight and box dimensions decide the Meesho shipping weight slab and cost. Here is how volumetric weight works, how slabs are billed, and how to pack to land in a lower, cheaper tier.