Short answer
The Meesho supplier panel dispatch workflow runs: order received, order accepted, labels downloaded as one PDF, labels printed, items picked and packed, then handover to the courier before the pickup cut-off. Labels download as a single file covering many orders.
Key takeaways
- The panel is built around one order at a time. Your job is to batch what it hands you one by one.
- Label download is the natural batching point. Everything before it is per order, everything after can be grouped.
- Most lost time sits between downloading the label and sealing the parcel, not inside the panel.
- Handover is where penalties come from. Keep courier stacks physically separate from the printer onwards.
- Missing the pickup cut-off is worse than packing slightly slower, so work backwards from the cut-off time.
New Meesho sellers usually learn the supplier panel by clicking through it until orders ship. That works, but it hides which steps are actually costing time and which are just clicks.
This walks the whole dispatch workflow in order, says what each step is really doing, and flags where small sellers lose their morning. It assumes you already have a live catalogue and are receiving orders.
Scope: dispatch only. Catalogue upload, pricing, ads, returns processing and payment reconciliation are not covered. Panel screens change from time to time, so treat the stage names as the shape of the flow rather than exact button labels. I build the free sorting tool mentioned at stage three.
On this page
Stage 1: the order arrives
An order appears in the Meesho supplier panel and starts a clock. If you are still setting up, Meesho's seller onboarding pages cover registration and catalogue upload, which this guide assumes you have already done. You confirm you can fulfil it, and it moves toward ready-to-ship.
The thing to internalise here is that the panel is designed around one order at a time, because that is what it is tracking. Every screen, every status and every button is per order. Your entire operational job from this point is to batch what the panel hands you individually.
Practical rule: do not act on orders as they trickle in. Let them accumulate to a batch, then process the batch. Reacting to each notification is the single most common way to lose a morning.
Stage 2: download the labels
When you download shipping labels, the panel produces one PDF containing a page per sub-order. That file is the real handoff point between the panel's world and yours.
Two things about that PDF matter:
- The page order is order-arrival sequence, not anything useful for picking. The same product will be scattered across the file.
- Each page carries structured data in text: the SKU ID, size, quantity and delivery partner, plus the customer address block and a tax invoice.
Because that data is text rather than a flat image, the file can be reorganised before printing. That is the leverage point, and almost nobody uses it.
Stage 3: the gap nobody optimises
Between downloading the PDF and pressing print, there is a step most sellers do not know exists: reordering the pages so identical items sit together, and stamping a readable product name onto each one.
Skipping it means you do the same work later, by hand, on paper, in a worse format. Sorting forty printed pages into piles takes roughly ten to fifteen minutes. Sorting the PDF takes seconds and produces a better result, because it can also split the file per courier.
This is covered properly in the label sorting guide.
Stage 4: print
Print settings that matter more than people expect:
| Setting | Use | Why |
|---|---|---|
| Scale | 100%, actual size | Fit-to-page shrinks the barcode and scanners start failing at pickup. |
| Colour | Black and white | Nothing on the label needs colour. Saves ink on high volume. |
| Duplex | Off | Each label is one page and gets torn or stuck individually. |
| Quality | Normal, not draft | Draft mode degrades barcode edges, which is what scanners read. |
If a courier ever tells you a barcode will not scan, check scale first. It is the cause far more often than the printer.
Stage 5: pick and pack
With a sorted stack, work one product at a time. Pull the full run for a product in a single shelf trip, lay the labels out, pack the batch, then move on.
Two checks worth building into the motion:
- Quantity before sealing. Multi-quantity orders are where shortfalls happen, and reopening a sealed bag is slow.
- Size against the label, not against memory. M and L feel similar in the hand at speed.
Stage 6: handover
Handover is where penalties come from, and it is almost entirely a physical-organisation problem rather than a systems problem.
If you ship with more than one delivery partner, the two stacks should never have shared a pile. Producing a separate PDF per courier at stage 3 means they were separate from the printer onwards, and a parcel physically cannot end up in the wrong handover.
Keep the courier's manifest or scan confirmation. When something goes missing weeks later, that record is the whole argument.
Working backwards from the cut-off
Every pickup has a cut-off time. Missing it costs more than packing slowly, because the parcel sits an extra day and the delivery clock keeps running.
Plan backwards instead of forwards. If pickup is at 4pm and you can pack roughly 40 parcels an hour, then 80 orders means you start at 2pm at the latest, with 30 minutes of buffer for the things that always go wrong. Write the start time on a whiteboard, not in your head.
Five mistakes that cost the most
- Processing orders as they arrive. Batch them. Every context switch has a cost.
- Printing before sorting. Once it is paper, sorting is manual forever.
- Mixing couriers in one pile. Separate at the file level, not at the table.
- Handling returns mid-dispatch. They break rhythm and they are never urgent enough to justify it.
- Fit-to-page printing. Silently shrinks barcodes and creates scan failures you will blame on the courier.
The one change to make first
If you take one thing from this: the gap at stage 3 is where the free time is. Sort the label PDF before you print it. Free, no account, runs in your browser.