Skip to content
Robnu

Meesho Ready to Ship: what it means and the steps.

Ready to Ship (RTS) is the status that says an order is accepted, packed, labelled and manifested, waiting for the courier. Here is what it means, how to get there, the dispatch SLA clock, and what missing it costs.

Free during early access · Forever free under 25 orders/day
The dispatch pipelineReady to Ship sits between accepted and handed overAcceptedReady to ShipHanded overIn transit
Quick answer

On Meesho, Ready to Ship (RTS) means an order is accepted, packed, labelled and added to a manifest, so the courier can collect it. To reach RTS: accept the order, pack it, print the shipping label, generate the manifest, then hand the parcel over within the dispatch SLA.

Last updated: September 2026

TL;DR
  • Ready to Ship (RTS) means the parcel is packed, labelled and manifested, waiting for courier pickup.
  • The path is accepted, then RTS, then handed over, then in transit; each is a distinct status.
  • A dispatch SLA clock runs on every order; the Supplier Panel timer is the source of truth.
  • Missing the RTS or dispatch SLA risks auto cancellation, penalties and lower listing visibility.
  • Robnu keeps orders moving to RTS on time, flags SLA risk, and reconciles every payout to the rupee.
Key facts (as of September 2026)
  • Ready to Ship (RTS) is a seller side order status in the Meesho Supplier Panel, confirming a parcel is packed, labelled and manifest ready for pickup.
  • RTS is reached after acceptance and before handover; handed over is a separate, later status where the courier has collected the parcel.
  • Each order carries a dispatch SLA shown in the panel; it can vary by category, region and account, so always confirm the live figure on supplier.meesho.com.
  • Missing the dispatch SLA can lead to auto cancellation, cancellation penalties and reduced product visibility.
  • RTS is an operational milestone, not a payment event; settlement follows delivery and the payout cycle, net of charges.

Ready to Ship is one of the most important words in a Meesho seller’s day. It is the moment an order stops being a promise and becomes a prepared parcel, and it is the checkpoint the dispatch SLA is measured against. Understand it well and your operations run smoothly; miss it repeatedly and your metrics, visibility and income all suffer.

What exactly does Ready to Ship mean on Meesho?

Ready to Ship, shown as RTS, is the Meesho order status confirming that a seller has accepted the order, packed the item, printed the shipping label and generated the manifest, so the parcel is prepared and queued for courier pickup. It does not mean the parcel has physically left your premises. It means everything under your control is done and the order is now waiting for the logistics partner to collect it. Think of RTS as the handshake between your packing table and the courier network: you have finished your part, and the baton is about to pass. For a broader view of the whole fulfilment flow, see our Meesho order processing checklist.

The reason RTS matters so much is that Meesho measures your dispatch performance against it. Every order has a dispatch SLA, a window inside which the order must reach Ready to Ship and be handed to the courier. Hitting that window keeps your on time metric healthy, which in turn keeps your listings visible. Missing it does the opposite. So RTS is not just an operational label; it is the metric that quietly governs how often buyers see your products at all.

How is Ready to Ship different from accepted and handed over?

Accepted means you have agreed to fulfil the order but have not packed it; Ready to Ship means the parcel is packed, labelled and manifested; handed over means the courier has physically collected it and it is scanned into the network. These three are distinct milestones, and confusing them is a common source of missed SLAs. Acceptance is a commitment. RTS is a prepared parcel sitting at your pickup point. Handover is the transfer of custody, after which tracking begins to move and the order usually shows as shipped or in transit. The dispatch SLA spans from order placement through to handover, so both reaching RTS and completing pickup matter.

A useful way to hold the sequence in your head is: an order is placed, you accept it, you prepare it to Ready to Ship, and then it is handed over. Each arrow is an action you or the courier must take, and each has a time cost. The sellers who never breach an SLA are the ones who compress the first three arrows, accept, prepare, RTS, into the same short session, then keep a single reliable pickup window for the handover. The full label and handover mechanics are covered in our Meesho manifest and handover guide.

The SLA clock

How does the dispatch SLA clock run down?

The line below shows the time left on a dispatch SLA as an order moves from placement to handover. The faster you clear the early steps, the more buffer you keep for pickup.

app.robnu.com/meesho/rts-sla-clockTime left on the dispatch SLAFrom order placed to handover (illustrative)fullhalfgonePlacedAcceptPackLabelRTSHandedRTS reachedIllustrative. Clearing accept, pack and label early leaves the most buffer for pickup.app.robnu.com/meesho/rts-time-costWhere dispatch time is spentTypical small seller day (illustrative)Waiting to acceptorders sitting in the new queueriskPacking the itempick, protect, sealhighLabel and manifestprint, paste, generatemedWaiting for pickupcourier collection windowhighStatus confirmationshipped, tracking moveslowIllustrative. The biggest risk is slow acceptance; that is time you can never get back.
Step by step

How do you move a Meesho order to Ready to Ship?

To move an order to RTS: accept it, pack it, print the label, generate the manifest, then hand it to the courier. Each step below is generic and safe; confirm the exact panel wording on supplier.meesho.com, since screens change over time.

Open the Meesho Supplier Panel and go to your new or pending orders as soon as they arrive. Accept the order to confirm you will fulfil it. Accepting early is the single biggest lever on hitting the SLA, because every hour you delay acceptance is an hour eaten from the dispatch window. Check stock is genuinely available before you accept.

Pick the exact item, variant and quantity the order specifies, then pack it in appropriate protective packaging so it survives the courier network. A mismatched or poorly packed parcel leads to returns, RTO and complaints later. Keep packing material and a printer ready at your dispatch point so this step never becomes the bottleneck that pushes you past the SLA.

Generate the shipping label from the Supplier Panel and print it clearly on the correct size stationery, thermal or A4 as your setup requires. Paste it firmly on the parcel so the barcode is flat, clean and scannable. If the label will not download or generate, resolve that first, because no order can reach Ready to Ship without a valid, scannable label attached.

Add the packed, labelled parcels to a manifest and generate it in the panel. The manifest is the handover document that lists the parcels the courier will collect. Generating the manifest is the action that typically flips the order to Ready to Ship, signalling the parcel is prepared and queued for pickup. Batch several orders into one manifest to save time.

Keep the manifested parcels ready at your pickup point for the scheduled courier collection. When the courier scans and collects them, the status moves from Ready to Ship to handed over, then to in transit as the parcel enters the network. If pickup is missed, follow up promptly so the order does not stall and breach the delivery expectation.

After handover, confirm in the panel that the order has left Ready to Ship and is showing as shipped or in transit with live tracking. This closes the dispatch loop. Watch for any order that lingers at RTS past its pickup window, since that usually means a pickup or manifest issue that needs a quick fix before it turns into a late dispatch.

If the label will not generate, work our guide on the Ready to Ship label not generating first, and use bulk label download to print many orders at once.

Status compared

Accepted vs Ready to Ship vs handed over: what changes?

Each status marks a different point of control and a different risk. Read across to see who holds the parcel and what the SLA cares about at each stage.

StatusWhat it meansWho holds the parcelSLA relevance
AcceptedYou agreed to fulfil the order; nothing is packed yetSeller, unpackedSLA clock is running; risk is highest if you delay
Ready to Ship (RTS)Packed, labelled and manifested; waiting for pickupSeller, prepared parcelYou have done your part; pickup must still happen in time
Handed overCourier collected and scanned the parcel into the networkCourier / logistics partnerDispatch SLA is satisfied at handover; tracking begins
In transitParcel is moving through the network toward the buyerLogistics partnerDelivery expectation now applies, not the dispatch SLA

What happens if you miss the Ready to Ship deadline?

Missing the RTS or dispatch SLA on Meesho can trigger auto cancellation of the order, a cancellation counted against your account, reduced listing visibility, and, if it repeats, account level warnings or holds. The immediate cost is the lost order. The lasting cost is what it does to your metrics. Meesho tracks your on time dispatch rate, and a pattern of late or cancelled orders drags it down. A weaker metric means the algorithm shows your products to fewer buyers, so a missed SLA today can quietly reduce your orders for weeks. That compounding effect is why experienced sellers treat the dispatch clock as sacred.

There is also a buyer trust cost. An order that is cancelled or dispatched late leaves a shopper waiting, and that shopper is less likely to buy from you again and more likely to leave a poor experience behind. Because Meesho is a value led, high frequency marketplace, the sellers who win are the ones buyers can rely on. Reliability starts with hitting Ready to Ship on time, every time. If penalties or deductions look wrong on your statement, our guide on Meesho seller charges explains what is legitimate and what to challenge, and support escalation covers how to raise it.

Why does an order get stuck at Ready to Ship?

An order usually sticks at Ready to Ship when the courier pickup did not happen, the manifest was not generated or handed over, or a label failed to scan at collection. The parcel is prepared, but the handover step never completed, so the status cannot advance to handed over. The fix is methodical: confirm the manifest exists and is closed, check the parcel is physically at the pickup point with a clean scannable label, and then follow up on the pickup itself. A missed pickup is the most common culprit, and it is fully recoverable if you catch it the same day. Our dedicated guide on Meesho pickup not happening walks through each cause and its remedy in order.

Prevention beats cure here. Keep one predictable daily pickup window, generate a single manifest for the day’s orders, and keep manifested parcels together and ready so the courier never leaves empty handed. When pickup is a routine rather than a scramble, orders stop stalling at RTS, and your handed over timestamps stay comfortably inside the SLA. For the wider mechanics of scanning and manifesting, see our guide on scan, label and apply manifest.

How do you move more orders to Ready to Ship on time?

The reliable way to hit RTS on time is to batch the work: accept new orders promptly, print labels in bulk, pack against a fixed checklist, generate one manifest, and keep a single daily pickup window. Dispatch fails when it is treated as a series of interruptions scattered through the day. It succeeds when it is a routine. Set a rhythm where you clear new orders to Ready to Ship in one or two focused sessions, so nothing sits unaccepted and no SLA quietly runs down while you are busy elsewhere. The tighter and more predictable your routine, the fewer orders ever get close to their deadline.

This is exactly the kind of repetitive, deadline sensitive work an agentic order management system is built to carry. Robnu watches your Meesho orders, keeps them moving toward Ready to Ship, and flags any order whose dispatch SLA is at risk before it lapses, so a missed clock never surprises you. It does not print your labels or generate tax invoices, and it never touches buyer personal data; it orchestrates the operation and protects the money behind it. As your volume grows from a handful of orders a day toward hundreds or thousands, the same routine holds, because the system does the watching for you. If you are still deciding whether the category pays, our guide on whether Meesho is profitable for sellers sets realistic expectations, and how to sell on Meesho covers the full starting path.

Does Ready to Ship affect when and how much you get paid?

Reaching Ready to Ship does not itself release payment; it is an operational milestone. Payment follows delivery and the Meesho settlement cycle, net of commission, shipping and any return or RTO charges. What RTS does is keep the order flowing so it can eventually be delivered and settled, and it protects the metrics that keep your listings visible. But between dispatch and payout sits the settlement statement, and that is where money quietly leaks: a wrong deduction, a return charge that should not apply, an RTO fee on an order that was actually delivered. Hitting RTS on time earns the order; reconciling the settlement makes sure you are paid correctly for it. Our guide on Meesho seller charges breaks down every line so you know what to expect.

The two jobs behind every dispatched order
Getting an order to Ready to Ship on time is the operations job. Making sure the eventual payout for that order is correct to the rupee is the money job. Robnu runs both so a fast dispatch is not undone by a wrong deduction later.
app.robnu.com/meesho/rts-robnuWhere Robnu carries the loadKeeping orders moving and payouts correct100%of your ordersOrders moved to RTS on time70%SLA at risk, flagged early18%Payout lines to reconcile12%Robnu keeps the pipeline moving; you keep control of your stock and packing.
Where Robnu fits

You pack and dispatch; Robnu keeps the clock and the money honest

You style the store and run the sales; Robnu runs the daily order operations and makes sure every rupee Meesho pays you is correct. It is an agentic OMS for AJIO, Meesho and Amazon sellers: it keeps orders moving toward Ready to Ship, flags any order whose dispatch SLA is at risk before it lapses, and reconciles every settlement so a wrong deduction never eats the profit a dispatched order earned. It scales the same way whether you ship one order a day or fifty thousand.

Free for every seller right now, and forever free under 25 orders a day when paid pricing launches. See the plan on pricing, read more about Robnu for Meesho, or browse the full guide library.

Sources & further reading

Order statuses, SLA windows and penalty rules change over time and can differ by category and account. Always confirm the current details against your live Meesho Supplier Panel and Meesho’s own material before you rely on a specific figure.

FAQ

Meesho Ready to Ship, answered

Ready to Ship, usually shown as RTS, is the Meesho order status that says you have accepted the order, packed the item, and generated the shipping label and manifest so the courier can collect it. The parcel is prepared and waiting for pickup. RTS is the seller confirming the order is dispatch ready, not that the parcel has left your premises yet.

In the Meesho Supplier Panel, open the new or pending order, accept it, download and print the shipping label, paste the label on a securely packed parcel, then generate or add the order to a manifest. Once the label and manifest exist and the order is confirmed for pickup, the panel marks the order Ready to Ship and it enters the courier pickup queue.

Accepted means you have agreed to fulfil the order but have not yet packed or labelled it. Ready to Ship means the parcel is packed, the label is printed, and the manifest is generated so the courier can collect it. Accepted is a promise; Ready to Ship is a prepared parcel. An order must move from accepted to RTS within the dispatch SLA to avoid penalties.

Meesho sets a dispatch SLA, usually a short window measured in a small number of days from when the order is placed, by which the order must reach Ready to Ship and be handed to the courier. The exact clock is shown against each order in the Supplier Panel. Treat the panel timer as the source of truth, because SLAs can differ by category, region and account, and always confirm on supplier.meesho.com.

Missing the RTS or dispatch SLA can trigger penalties. Common consequences include the order being auto cancelled, a cancellation being counted against your account, reduced product visibility or search ranking, and in repeated cases account level warnings or holds. Late dispatch also hurts your on time metric, which quietly lowers how often Meesho shows your listings to buyers.

No. Ready to Ship means the parcel is packed and labelled and waiting for the courier. Handed over means the courier has physically collected the parcel and it is scanned into the network, often reflected as shipped or in transit. RTS is your responsibility; handover is the moment control passes to the logistics partner and the tracking begins moving.

You can, but seller initiated cancellations after acceptance count against your account and hurt your metrics, so avoid them unless a genuine stock or quality issue forces it. If you cannot fulfil, cancel as early as possible rather than letting the SLA lapse. Repeated cancellations reduce visibility and can lead to account penalties, so keep accurate inventory to prevent the situation.

An order can sit at RTS when the courier pickup did not happen, the manifest was not handed over, a label failed to scan, or the pickup was missed on the courier side. Check the manifest is generated and the parcel is ready at the pickup point, then follow up on the pickup. Our guide on Meesho pickup not happening walks through the fixes step by step.

No. RTS is an operational milestone, not a payment event. Payment follows delivery and the settlement cycle, minus commission, shipping and any return or RTO charges. Moving orders to RTS on time protects your metrics and keeps orders flowing, but you still have to reconcile each settlement to confirm every rupee Meesho pays is correct, which is exactly what Robnu does for you.

Batch your work: accept orders promptly, print labels in bulk, pack against a checklist, generate one manifest, and keep a single pickup window each day. The biggest wins are catching new orders early and never letting the SLA clock run down. An agentic OMS like Robnu keeps orders moving toward RTS and flags any order whose dispatch SLA is at risk before it lapses.

Keep reading

Related seller guides

More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.

Meesho Order Processing: From Order to Handover (2026)

Meesho order processing explained end to end: new order, accept, label and invoice, pack, ready to ship, manifest, courier pickup, delivery or RTO, and settlement. Learn each SLA stage and where sellers lose time and money.

Every Meesho SLA status decoded (and what each one costs)

Within SLA, Breaching Soon, Breached, dispatch vs delivery SLA — every state explained, what it costs, and the one moment that actually stops the clock.

Scan, label, manifest: the Meesho dispatch chain end to end

Dispatch is not four separate jobs, it is one chain: scan, label, pack, manifest, hand over. Run as a routine, it flows; broken up, it leaks time and triggers penalties. The full chain, in order, and where each link fails.

Meesho orders stuck in pending: what it means and how to clear them

Blocked does not mean paused — the dispatch clock usually keeps running. The four causes, which two you can fix yourself, and what to document when you cannot.

SLA in Meesho: full form, dispatch deadlines & penalties

SLA stands for Service Level Agreement, your Meesho dispatch promise. Every status type, the 17:30 cut-off, what a miss costs, and how to never miss one again.

Meesho Manifest: How to Generate and Hand Over (2026)

A Meesho manifest is the handover list that proves you gave your packed parcels to the courier. Learn how to generate it after labels are ready, scan parcels onto it, hand it over, and use it to protect disputes.

Order Management for Meesho Sellers: A Practical Guide (2026)

What order management means for a Meesho seller: the full accept, label, dispatch, track, return and reconcile workflow, doing it in the panel versus with an OMS, and when you actually need a system.

Meesho SKU ID Explained: How to Structure Seller SKUs 2026

A Seller SKU ID is your internal code for each product variation on Meesho. Here is what SKU ID means, why it matters for variations and inventory, and how to structure SKUs so they scale across marketplaces.

build fcb09af3e7173aa4445201c8c1c1b9d2f27dbf0f · 2026-09-06T11:33:03+05:30