Meesho Ready to Ship (RTS) — What It Means & What to Do Next

Ready to Ship (RTS) in Meesho means an order has crossed its paperwork stage — accepted, label generated — and now waits for exactly one thing: the physical parcel entering courier custody. It reads like a resting state; it's actually a countdown. The SLA judges you at handover, and every hour an order sits in RTS is runway burning. Understanding RTS — including its priority and non-priority flavours — is understanding dispatch itself.

Key Takeaways

RTS = accepted + label ready, awaiting handover — the SLA clock runs.
Priority RTS = due now; non-priority = buffer left, still ship daily.
RTS is a to-do state, not a done state.
Exit RTS via: pack → verify → manifest → handover.
Orders aging in RTS are the #1 source of avoidable penalties.

Where RTS Sits in the Order's Life

Stage	Status	Whose move
Order placed	New/pending	Yours — accept it
Accepted, label made	Ready to Ship	Yours — pack & hand over
Courier has parcel	Handed over / in transit	Courier's
Delivered	Delivered	Settlement clock starts

RTS is the last stage that's entirely in your hands — which is precisely why the SLA measures it. Everything after handover has shared custody; everything in RTS is on you alone.

Priority vs Non-Priority RTS

Meesho splits the RTS queue by urgency: priority orders are at or near their dispatch deadline — pack these first, always; non-priority orders have buffer days left. The label is a sorting aid, not a permission slip: the winning habit is shipping everything ready in each daily batch, because today's non-priority is tomorrow's priority, and a single courier hiccup converts a comfortable queue into a breach list overnight. The nuances — including what "RTS non-priority" implies — are in the non-priority explainer.

Exiting RTS Cleanly, Every Day

The exit path is the dispatch workflow: print labels in batch (crop them clean), pick against the label, verify item vs label before sealing — the ten-second step that prevents wrong-product penalties — manifest everything, and hand over same-day (the full SOP). If the courier fails the pickup, your manifested-and-ready proof keeps the late-dispatch penalty off your account. RTS handled this way is a state orders pass through in hours — never a place they live. A tool like TrackEcom does this automatically — it reconciles every order, flags each deduction, and shows your real per-order profit so nothing slips through.

FAQs

What does Ready to Ship mean in Meesho?

The order is accepted and its label generated — the parcel now awaits packing and courier handover, with the dispatch SLA clock running.

What is the difference between priority and non-priority RTS?

Priority RTS orders are at or near their dispatch deadline; non-priority ones have buffer days — but the best practice is dispatching everything ready, daily.

What should I do when an order shows RTS?

Pack it, verify the item against the label, add it to the manifest, and hand it to the courier the same day — RTS is a countdown, not a resting state.

Can RTS orders cause penalties?

Yes — orders aging in RTS past their SLA trigger late-dispatch penalties. Daily batch dispatch, with courier failures documented, eliminates the category.