What is a batch order on AJIO and Meesho?
“Batch,” “batch day,” “open batch,” “closed batch” — the words are everywhere in the seller panel and rarely explained. A batch is simply the group of orders you dispatch together in one cycle, and the cut-off that closes it is one of the sharpest deadlines you face. This guide explains all of it, and how to close every batch before the clock runs out.
- A batch is a group of orders bundled for one dispatch cycle — labelled and manifested together, handed to the courier as one unit. It is the daily unit of order processing.
- An open batch still accepts orders until the cut-off (commonly 17:30); a closed batch has passed the cut-off and is finalised. Miss the cut-off and every order in the batch is late.
- Because a whole batch is penalised together, one missed cut-off can trigger SLA penalties across dozens of orders. Robnu tracks batch headroom so nothing slips.
Batch orders on AJIO and Meesho — processing many orders together rather than one at a time — is the difference between a dispatch operation that scales and one that breaches SLAs daily. This guide covers why batching matters, how to run it, and where it saves the most time.
Why batching beats reacting
Handling orders as they arrive feels responsive but means switching contexts dozens of times a day, doing each step badly, and giving your latest orders the least runway. Batching means downloading all labels once, packing in one pass, and handing over as a single consignment. The decisive argument is runway: an order processed early has hours of buffer before its window closes; the same order handled late may have almost none. See the daily processing routine for the full sequence.
Running a batch across two marketplaces
The complication with AJIO and Meesho together is that each imposes its own dispatch windows on the same physical operation. A batch that satisfies Meesho’s deadlines may miss AJIO’s, so you cannot run one blind queue — you have to sequence by true urgency across both, working the shortest countdown first regardless of which platform it belongs to. Sort by time remaining, triage blockers like stock-outs and label failures separately, and confirm every handover scan. See selling on multiple marketplaces.
When batching outgrows manual tracking
Batching works until volume outpaces the state a human can hold across two marketplaces’ deadlines at once. At that point the failures are not carelessness but orders that fell out of attention. Holding the combined queue sorted by urgency, tracking the dispatch clock on every open order across both AJIO and Meesho, and flagging blockers before they stall a batch is exactly what our agentic dispatch tracking does — so one physical dispatch run cleanly satisfies two independent sets of deadlines. See the two-person team playbook.
The bigger picture for your catalogue
Whatever the specific status, charge or process, the underlying reality of selling on Indian marketplaces is the same. The platforms are built to move enormous volume, their interfaces speak in operational shorthand rather than plain language, and the money at stake hides in charges that arrive as silent settlement deductions requiring no approval from you. The sellers who stay profitable are not the ones who avoid every problem — that is impossible at scale — but the ones who understand what each event means, know which charges are genuinely owed, and reconcile every settlement so the wrong ones are caught and reclaimed while the claim window is still open.
That discipline is simple to describe and hard to sustain by hand, because it is precise, repetitive work layered on top of actually running the business. It is exactly the kind of task that a two-person team does inconsistently under volume and that software does reliably every cycle. Robnu exists to close that gap: it runs the daily operations these guides describe, reconciles the charges they represent against what you actually shipped and sold, and files the claims you are entitled to — so the vocabulary becomes something handled rather than something you have to master and police yourself. You sell; Robnu runs the rest, and makes sure every rupee is paid correctly.
Sources & further reading
Charges, policies and processes vary by marketplace and category and change over time. The details here are drawn from official documentation and reputable industry sources; always confirm current specifics against your own seller panel and settlement reports:
A batch is your daily dispatch group
A batch is a set of orders that a marketplace groups together for a single dispatch cycle. Rather than treating every order as an island, the platform collects the orders due for dispatch, lets you confirm and label them together, generates one manifest for the group, and expects the whole batch to be handed to the courier as a unit.
This is why the panel talks about batches instead of individual orders. Your morning job is not “process order 7781, then 7782” — it is “close today's batch.” The batch is the container that carries the day's work through labelling, manifesting and handover.
On Meesho the flow runs through states like Pending and Ready to Ship, with labels becoming available once orders move to Ready to Ship. On AJIO the batch is tied to the 11-stage order-to-manifest flow and closes at the manifest cut-off. Different words, same idea: a group of orders that lives or dies together against one deadline.
Open, closed, and what each means for you
Meaning: Still accepting orders for this dispatch cycle. The cut-off has not passed.
What to do: Keep confirming and labelling orders as they arrive — this is your window to act.
Meaning: Order accepted into the batch; the shipping label is available to download.
What to do: Download labels, pack, and prepare for the courier handover before the cut-off.
Meaning: Cut-off passed. The manifest is finalised; no more orders can be added.
What to do: Hand the whole batch to the courier. Orders not in it have rolled to the next batch.
Meaning: The batch has been picked up by the courier and is on the forward leg.
What to do: No action needed. Track for delivery; the settlement clock starts on delivery.
- Connect
- Sync
- Batch
- Confirm
- Upload
- List
- Slips
- Invoices
- Docs
- Manifest
- Closed
Why the batch cut-off is so unforgiving
The cut-off — commonly 17:30 on the batch day — is binary. Confirm and hand over before it and the batch is on time; miss it by a minute and the entire batch rolls to the next cycle. There is no partial credit and no per-order grace: the batch is judged as a whole.
That is what makes batches high-stakes. A single missed cut-off does not penalise one order — it penalises every order in the batch at once. Twenty orders in a missed batch is twenty SLA breaches, twenty unhappy buyers, and a visible dent in your seller performance score.
Marketplaces have also tightened dispatch expectations over time, with next-day dispatch policies pushing the window even shorter. The less slack the platform gives you, the more a clean batch-closing routine is worth.
How to close every batch on time
- 01
Open the batch first thing
Start the day by checking today's open batch and its order count, before packing starts. Knowing the number early removes the end-of-day scramble.
- 02
Confirm and label in one pass
Move orders to Ready to Ship and download labels in a single sitting rather than trickling through the day. Batching the admin work mirrors how the batch itself works.
- 03
Pre-pack standard SKUs the night before
For predictable products, pack and label the evening before so only the courier scan remains in the morning. This halves the pressure on the cut-off window.
- 04
Book courier pickup with a buffer
Schedule pickup for early-to-mid afternoon, not 16:30. If the courier is late, you still have room to re-book before the 17:30 cut-off.
- 05
Watch batch headroom, not the clock
Track how much time is left on the batch as a percentage, so you know when a batch is at risk before it is too late to act.
- 06
Automate batch closing with Robnu
Let Robnu prioritise orders approaching their batch deadline, prepare the manifest, and surface any batch at risk — so the batch closes cleanly without you watching a clock.
How Robnu closes your batches for you
Robnu reads your open batch continuously and calculates the remaining time before the cut-off, showing SLA headroom per batch so you always know how much slack is left. The same watchdog handles the AJIO manifest cut-off and the Meesho dispatch window.
Run the autonomous pipeline and Robnu front-loads the orders closest to their deadline, labels them, and assembles the manifest so the batch is ready to hand over well before 17:30. A batch at risk is surfaced early — while you can still act — not after it has already rolled.
The rare step that still needs a human is flagged clearly. Everything else — the repetitive confirm, label, manifest loop — runs itself.
Batches, answered
A batch is a group of orders bundled together for a single dispatch cycle. Instead of processing each order in isolation, the marketplace groups the orders due for dispatch into a batch, generates labels and a manifest for the whole group, and expects you to hand the entire batch to the courier together. It is the unit of daily order processing.
An open batch is still accepting orders — new orders due for the same dispatch cycle keep dropping into it until the cut-off. A closed batch has passed its cut-off time: no more orders are added, the manifest is finalised, and it is ready to hand to the courier. Once a batch closes, orders that were not in it roll into the next batch.
Batch day is the day on which a batch is due to be dispatched. Every order in a batch shares the same batch day and therefore the same dispatch deadline, regardless of when each individual order was placed. Two orders placed days apart can share one batch day.
The cut-off is the time by which the batch must be confirmed, labelled and handed to the courier — commonly 17:30 on the batch day. On AJIO this is tied to manifest closure. Confirming even a minute after the cut-off means the batch, and every order in it, is treated as late.
If you miss the cut-off, the batch rolls to the next dispatch cycle and every order inside it is late. That triggers SLA penalties per order, hurts your seller performance score, and delays the buyer's delivery — which risks cancellations and negative reviews. A single missed batch can penalise dozens of orders at once.
A single order is one buyer's purchase. A batch is the operational container that groups many orders due for the same dispatch so they can be labelled, manifested and handed over as one unit. You manage orders at the batch level because that is how the marketplace's cut-off and manifest work — miss the batch, miss every order in it.
Robnu reads your open batch continuously, calculates how much time is left before the cut-off, and shows the SLA headroom per batch so nothing slips. When you run the autonomous pipeline, orders approaching their batch deadline are prioritised for processing and labelling, and the manifest is prepared so the whole batch closes cleanly before the clock runs out.
Where this is drawn from
- Meesho order flow (Pending, Ready to Ship, label availability): Meesho Supplier app order-processing documentation and courier-integration guides, supplier.meesho.com.
- Meesho next-day dispatch expectations tightening the dispatch window: Meesho seller policy communications.
- AJIO batch and manifest cut-off tied to the order-to-manifest flow: AJIO Commerce Seller Central, seller.ajio.com, and Robnu's own process documentation.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
Meesho manifest and handover mistakes that trigger penalties
Closing the manifest, the handover scan, and the gap between them is where Meesho penalties hide. The mistakes that trigger them — manifested-but-not-handed-over, missing scans, wrong counts — and how to close cleanly.
The 10-minute Meesho order processing routine
Most missed dispatch windows come from reacting to orders all day instead of clearing one early batch. The six-step sequence, in the order that matters.
AJIO seller models decoded: outright, marketplace, JIT
What each AJIO arrangement means for cash flow, price control, and returns exposure — outright/B2B, marketplace, JIT, consignment-style — plus the questions to ask before signing.
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.
Meesho cancellation penalties: what they cost and how to avoid them
A cancelled order costs the penalty, the lost sale, and a compounding account-health hit. What triggers seller vs auto-cancellations, and how to catch orders before they reach that point.
Meesho bulk label download: 100 orders labelled in minutes
Downloading Meesho labels one order at a time does not scale. Here is the batch dispatch workflow — bulk-select ready-to-ship orders, generate labels and invoices as one merged PDF, print, and manifest without touching each order.
Meesho invoice printing and the GST mistakes sellers make
The Meesho invoice carries your GST details, and the mistakes on it are the ones that come back to bite. How invoices generate, the GST fields that matter, the common errors, and how to print them cleanly at volume.
Meesho OMS: The Honest Buyer's Guide for Sellers
What an order management system for Meesho actually is, what to look for before you commit, the questions that separate real tools from dashboards, and where Robnu fits in as one honest option.