Your first 25 orders a day: the operations playbook
Getting orders is a catalog problem. Surviving them is an operations problem — and it is the one that actually kills growing sellers. Here is the 1-to-25 orders/day playbook: the three phases, what breaks at each jump, and how to make 25 a day feel like 5.
- There are three phases: 1–5 orders/day (manual is fine — use it to learn every screen), 5–15 (routines or chaos: fixed dispatch windows, a packing bench, evidence habits), and 15–25 (systems: stock discipline, claim tracking, weekly reconciliation).
- Each jump breaks something different: first your time, then your accuracy, then your cash-flow visibility. The failures look sudden but the causes build for weeks — the playbook is about fixing each one before its phase arrives.
- A 2-person team hits a wall near 25/day doing everything manually. The wall is made of repetitive screen-work, not of decisions — which is why a pipeline that runs the repetitive layer moves the wall instead of you hiring your way to it.
Volume doesn't grow smoothly. It jumps.
Sellers describe growth as if it were a slope, but operationally it is a staircase. At 1–5 orders a day, everything is manageable by hand and mistakes are rare because every order gets your full attention. Then a catalog starts ranking, a festival week hits, and you are suddenly doing 12 a day with a routine built for 3. Nothing about your process changed — the volume simply outgrew it overnight. That is the first jump, and it is where the first SLA breaches, the first mispacks, and the first missed return windows appear.
The second jump, into the 15–25 band, is quieter and more expensive. By then dispatch usually works — you have routines. What breaks is everything you stopped looking at: stock accuracy, deduction correctness, claim deadlines. The money side of the business goes dark precisely when the money gets meaningful. The playbook below is organised around those two jumps: build the habit before the phase that punishes its absence.
- Connect
- Sync
- Batch
- Confirm
- Upload
- List
- Slips
- Invoices
- Docs
- Manifest
- Closed
Seven moves, matched to the phase that needs them
Each move is cheap to adopt in the phase before it becomes urgent, and expensive to adopt during the phase that punishes its absence.
- 01
Phase 1 (1–5/day): learn every screen
Manual is not a weakness here — it is the apprenticeship. Download your own labels, close your own manifests, open every report on the panel including the ones that look boring. The seller who understands the payments report at 3 orders a day catches the wrong deduction at 20 a day.
- 02
Phase 1: build a perfect dispatch record
At low volume there is no excuse for a breach, and early breaches hurt a young account's visibility disproportionately. Track one metric — dispatch-on-time rate — and keep it at 100%. This is also when you set your packing standard: every parcel packed to survive a round trip, because some will make one.
- 03
Phase 2 (5–15/day): fix dispatch windows
The chaos cure is a timetable. Orders accepted and labels pulled at fixed times, packing in one block, handover before the courier cut-off — every day, same slots. Ad-hoc dispatch dies somewhere around 8 orders a day; a fixed window scales to 25 without drama.
- 04
Phase 2: set up a real packing bench
A dedicated surface with stock bins, packaging material, a scale, and the printer within arm's reach. Weigh and photograph parcels as you pack — the weight note kills future weight-discrepancy disputes, and the photo habit costs seconds now versus hours of arguing later.
- 05
Phase 2: start the evidence habit
Every return opened on camera, every damaged or wrong item photographed, every panel error screenshotted with a timestamp. Evidence gathered in the moment is nearly free; evidence reconstructed for a claim two weeks later is usually impossible. This habit is worth more than most ads budgets.
- 06
Phase 3 (15–25/day): reconcile weekly
Settlements now arrive for orders you no longer remember. Block a weekly hour to tie every payout line to its order: price, deductions, returns, penalties. Expect to find a few wrong lines every month — small amounts, high frequency — and file claims within the window instead of donating them.
- 07
Phase 3: stock discipline and claim tracking
Overselling at 20 a day means cancellation penalties and account-health damage, so inventory counts become sacred. And claims now need a tracker with deadlines — a claim is not filed-and-forgotten, it is a receivable you chase like any other. A spreadsheet works; a system that never forgets works better.
Where a two-person team runs out of day
Do the illustrative arithmetic for 25 manual orders a day: pulling labels and paperwork order by order, packing, manifest and handover, returns inspection with evidence, support tickets, and a reconciliation pass — it stacks to roughly a full working day of pure operations. That is one entire person consumed by screen-work and tape, before anyone touches the catalog, pricing, or growth that got you here. The business starts eating its own founders.
The revealing part is what those hours contain. Almost none of it is judgement — it is downloading, clicking, copying, checking, the same loop 25 times. Sellers usually respond by hiring, and a third pair of hands does help. But hiring to run a manual loop just moves the wall to 40 a day and adds a salary. Removing the loop moves the wall out of sight.
Make 25 a day feel like 5
Robnu exists for exactly this staircase. It runs the repetitive layer on AJIO and Meesho end to end: new orders picked up the moment they land, labels and documents fetched as soon as they exist, dispatch paperwork batched, every SLA deadline watched, returns logged with evidence, and every settlement reconciled line by line against what each order should have paid. The seven-hour ops day collapses into an exceptions list — the handful of orders that genuinely need a human decision.
The money side scales with you instead of going dark: wrong deductions become claims filed for you — fully autonomous filing is rolling out, and the rare claim still asks for one approval click. Phase-3 discipline, running from whatever phase you are in today.
- Connect
- Sync
- Batch
- Confirm
- Upload
- List
- Slips
- Invoices
- Docs
- Manifest
- Closed
Scaling questions, answered
There is no standard timeline — sellers with the right product in a value-priced niche have done it in a couple of months, and plenty of good businesses sit at 5–10 a day for a year. The honest answer is that demand growth is mostly a catalog and pricing question, while surviving the growth is an operations question. This guide is about the second part: sellers usually fail the jump not because orders stopped coming, but because dispatch, returns, and reconciliation collapsed under volume they were not structured for.
Time. At 1–5 orders a day, everything fits in an hour and mistakes are rare because each order gets full attention. Somewhere between 5 and 15, the manual routine stops fitting: labels, packing, manifests, and returns eat the afternoon, and the first SLA breaches appear — not from laziness but from queue overflow. After time, accuracy breaks: wrong products in right boxes, missed return windows. Last is cash-flow visibility: settlements arrive for orders you no longer remember, and nobody is checking whether the amounts are right.
Per phase. At 1–5 a day: dispatch-on-time rate and little else — build the habit of a perfect record. At 5–15: add return rate and RTO rate by product, because one bad SKU can quietly eat the margin of five good ones. At 15–25: add settlement variance — the gap between what each order should have paid and what actually landed — plus claim recovery. The pattern: early on you manage effort, then you manage quality, then you manage money. Sellers who track money metrics from day one are rare and noticeably richer.
Done fully manually, 25 orders a day is genuinely hard for two people: labels, packing, handover, returns inspection, evidence, tickets, and reconciliation stack up to a full working day of pure operations before anyone touches catalog or growth. That is why many sellers hire their first helper around this volume. But the wall is a manual-work wall, not a headcount wall — most of those hours are repetitive screen-work a pipeline can run. Automate the repetitive layer and a two-person team handles 25 a day with room to breathe.
Deliberately slowing demand because ops cannot keep up is sometimes the right emergency brake — an SLA breach spiral hurts account health in ways that take months to repair, and a week of controlled volume is cheaper than a visibility penalty. But treat it as a tourniquet, not a strategy. The moment you throttle growth to protect a manual routine, the routine has become the ceiling on your business. Fix the routine: fixed dispatch windows, a real packing bench, and automation for the screen-work, then open demand back up.
Robnu is the pipeline this guide keeps pointing at. It picks up every new order on AJIO and Meesho, fetches labels and documents as soon as they exist, batches dispatch paperwork, watches every SLA deadline, logs returns with evidence, and reconciles every settlement line against what the order should have paid. Wrong deductions turn into claims filed for you — fully autonomous filing is rolling out, and the rare claim still asks for one approval click. The repetitive layer that eats seven hours at 25 a day drops to an exceptions list you clear over coffee.
Where this comes from
- AJIO and Meesho seller documentation on dispatch SLAs, manifests, returns windows and settlement reports: seller/supplier panel learning hubs.
- Recurring scaling stories and breaking-point reports from growing Indian marketplace sellers: public seller community threads (Reddit r/IndiaBusiness, seller Facebook and Telegram groups), 2024–2026.