The daily routine for a 2-person marketplace team.
Two people, three marketplaces, one day. Here is a realistic morning-to-evening operating rhythm for a lean team running AJIO, Meesho and Amazon together — hour-by-hour blocks, a clean division of labour, and the SLA cutoffs you can never afford to miss.
- A two-person team can run AJIO, Meesho and Amazon well if the day has a fixed shape and the two people split by function, not by marketplace.
- The spine of the day is the dispatch SLA cutoff on each platform — batch the earliest-cutoff marketplace first, every morning.
- Person A owns the flow-out: intake, accept, label, manifest, dispatch. Person B owns the flow-back and the money: returns, inventory sync, ads, reconciliation, claims.
- The real tax of multi-marketplace selling is context-switching between three sets of rules — not the order volume itself.
- Robnu is an agentic OMS: it runs the repeatable operations itself, so the same two people hold the quality bar without adding hours. Free while we figure out pricing.
Running one marketplace with two people is calm. Running three is a juggling act — three seller panels, three SLA clocks, three label formats, three settlement files, all moving at once. The teams that make it look easy are not working harder; they are working to a routine. This guide lays out that routine hour by hour, then shows which parts a lean team should do by hand and which parts are better handed to something that never forgets a cutoff.
The difference between a two-person team that thrives across AJIO, Meesho and Amazon and one that quietly burns out is not talent, capital, or even order volume. It is rhythm. A day with a fixed shape — the same blocks in the same order, the same person owning the same work — absorbs three marketplaces without drama. A day without one turns every SLA cutoff into a scramble and every settlement file into a weekend you never take. This guide gives you the shape.
Why the day needs a shape at all
Selling on a single marketplace is forgiving. You learn one panel, one cutoff, one label format, one return window, and the work settles into muscle memory within a few weeks. The moment you add a second and third marketplace, that muscle memory stops helping, because almost nothing transfers cleanly. AJIO’s manifest procedure is not Meesho’s. Amazon’s dispatch cutoff is not AJIO’s. Each platform has its own return logic, its own settlement layout, its own deduction categories. The cost of running three is not three times the packing — it is the constant switching between three sets of rules, and switching is where a two-person team bleeds hours it cannot spare.
A routine fixes this by grouping like work together. Instead of hopping between marketplaces order by order, you do all the intake at once, all the labelling at once, all the manifesting at once, and you do the earliest-cutoff platform first so no clock ever catches you out. The routine is not bureaucracy; it is the thing that lets two people behave like a larger team. For the deeper case on when this pressure justifies a proper system, see our guide on order management software in India.
The morning: intake and the race against the first cutoff
The day starts with a single question: which marketplace’s dispatch cutoff is earliest today, and how many orders are sitting against it? Order intake is the first block because everything downstream depends on it — you cannot label what you have not accepted, and you cannot accept what you have not seen. The first thirty to forty minutes are spent pulling new orders from all three panels, accepting them, and sorting them by cutoff so the tightest deadline is handled first. This is the most decisive block of the day: an order accepted late is already halfway to a missed SLA.
The trap here is doing intake marketplace by marketplace in the order you happen to log in, rather than in cutoff order. If Amazon’s cutoff is 11am and you spend the morning on Meesho because you opened it first, you will find yourself sprinting at 10:45 with a stack of unlabelled Amazon orders. The discipline is simple: sort by deadline, not by habit. A clear view of every open order across platforms — the kind an order management software gives you — turns this from a memory test into a glance.
Mid-morning: batch, label, manifest, dispatch
Once orders are accepted and sorted, the middle of the morning is a production line: print labels in a batch, pack against those labels, generate the manifest for each marketplace, and hand the parcels to the courier before each platform’s cutoff. Batching is what makes this fast — you do not want to print one label, pack one parcel, print the next label, pack the next. You want to print every label for a cutoff window at once, pack the whole batch, and manifest once. The rhythm of batch, then act is the single biggest efficiency lever a small team has, and it is why the day is drawn as blocks rather than a trickle.
The friction in this block comes from format differences. Each marketplace hands you a label in its own layout and a manifest in its own procedure, so a manual team spends real time downloading, printing and re-checking three different documents. Grouping the work by task rather than by platform — all labels first, then all packing, then all manifests — keeps the switching cost down. When intake, labelling and manifesting are automated, this block shrinks to a fraction of its manual length, because the fixed per-order overhead is what an order management system is built to remove.
Midday: returns inbound, inventory sync, and a short ads check
By midday the outbound rush has eased and the flow reverses. Returned and RTO parcels arrive back, and each one needs scanning against the order it belongs to, checking that the SKU and condition are right, and re-inducting into saleable stock if it passes. This is not glamorous work, but it is where recoverable money hides: a parcel marked returned that never physically arrived, a wrong SKU sent back, a return to origin billed for freight that should not apply. Skipping the scan is how stock and money quietly go missing. Our guide on RTO recovery covers the claim side in depth.
Midday is also the natural moment to reconcile inventory across the three marketplaces, because both the morning’s dispatches and the returns intake have now moved stock. Manually, this means updating a master stock sheet and pushing adjusted quantities into each panel — a slow job with a dangerous lag window, because a unit can sell on two platforms within the same hour and oversell before the sheet catches up. Finally, a fixed ten-minute ads check belongs here: pace the spend, pause the losers, note the bids to adjust, and close the dashboard. A short, fixed slot keeps ads honest without letting them eat the afternoon.
End of day: reconciliation and the claims queue
The last block of the day is the one most teams skip, and it is the one that decides whether the whole operation is actually profitable. Reconciliation means pulling each marketplace’s settlement report, matching every payout line against what the order should have paid, and flagging the deductions that look wrong: a weight that does not match, a duplicate charge, a commission off its slab, an RTO billed for a parcel that never came back. Every flagged line is a claim, and every claim has a window that expires. Review settlements the day they land, not in a monthly pile, because the pile is where claim windows go to die. This is the money spine of the day, and it is covered in full in our payment reconciliation guide.
Sources & further reading
Marketplace procedures, cutoff times and settlement layouts change over time and vary by category, so always confirm against your own seller panels and the official documentation. These are useful starting points for the operational details behind the routine above:
The two-person day, block by block
A realistic shape for a day running AJIO, Meesho and Amazon together. Times are illustrative — the principle is the order of the blocks and who owns each one, not the exact clock.
Order intake & triage
Pull new orders from all three panels, accept them, and sort by dispatch cutoff so the tightest deadline is first. This block sets the whole day — an order accepted late is already losing the race. Owned by Person A.
Batch label, pack, manifest, dispatch
The production line. Print labels in a batch, pack against them, manifest per marketplace, hand off to the courier before each cutoff. Earliest-cutoff platform first, always. Owned by Person A.
Returns inbound & inventory sync
Scan returned and RTO parcels against their orders, check SKU and condition, re-induct good stock, and reconcile inventory across all three marketplaces before the oversell window opens. Owned by Person B.
Ads checkpoint
A fixed ten-minute slot: pace the spend, pause anything bleeding on a non-converting term, note bids to adjust, close the dashboard. Short and disciplined, not constant. Owned by Person B.
Second dispatch wave & replies
Late-cutoff orders and any afternoon intake go out; customer queries across the three platforms get cleared. Person A drives the dispatch, Person B clears the inbox.
Reconciliation & claims queue
Pull each settlement report, match payouts against what orders should have paid, flag wrong deductions, and queue the claims before their windows expire. The money spine of the day. Owned by Person B.
Split by function, not by marketplace
The instinct is to give each person a marketplace. Resist it. Splitting by function lets each person build deep fluency in one type of work, keeps the handoffs clean, and maps neatly onto the two halves of the money story — getting orders out on time, and making sure every rupee comes back correctly.
- Person A — the flow-out. Intake, accept, batch-label, pack, manifest, dispatch. One person owns the SLA clock across all three platforms.
- Person B — the flow-back. Returns intake, inventory sync, ads checkpoint, customer replies, reconciliation and claims. One person owns the money.
- Shared — the master stock view. Both people read and write the same inventory picture, so a dispatch and a return never fight over the same unit.
This split also survives a sick day far better than the marketplace split: cross-cover is easier when the tasks are grouped by type. For the growth decision that sits behind all of this, read when to expand to a new marketplace.
The real cost is context-switching
When a two-person team feels stretched, they usually blame the order count. It is almost never the count. It is the switching — the mental and manual cost of moving between three seller panels, three cutoff clocks, three label formats and three settlement layouts, all day long.
- Three logins, three habits. Every platform has its own quirks; every switch resets your focus.
- Three clocks that never align. Miss one cutoff on a busy day and account health takes the hit.
- Three settlement files. Different layouts, different deduction names, easy for a wrong charge to hide.
- One oversell window. Stock that is not synced fast enough sells twice and cancels once.
Comparing how two fashion marketplaces differ makes the point concrete — see Myntra vs AJIO for fashion sellers. Robnu supports AJIO, Meesho and Amazon today, with Flipkart and Myntra coming soon.
Let the routine run itself
A routine makes two people behave like a larger team. An agentic OMS goes one step further: it runs the repeatable parts of that routine itself, so the two people spend their hours on the judgement calls instead of the button-clicking.
Robnu accepts, labels and manifests your orders on schedule across AJIO, Meesho and Amazon — the whole mid-morning production line, handled without a person driving it. It keeps stock synced across every platform the moment a unit moves, so the oversell window simply closes. It reads each marketplace’s settlement, flags the wrong deductions, and prepares the claims, with a rare approval click while fully-autonomous filing rolls out. Ads run to your pacing between checkpoints. And the AI Catalog Studio produces listing images and video on credits, with credits included to start.
That is the spine of the whole product: you sell, Robnu runs the rest — and makes sure every rupee is paid correctly. Free while we figure out pricing, no card, no caps.
The two-person day, answered
With a disciplined routine, two people can comfortably run somewhere in the region of 50 to 150 orders a day across three marketplaces — the exact number depends far more on how much of the work is manual than on the order count itself. The bottleneck is almost never packing; it is the switching cost of logging into three seller panels, learning three sets of SLA cutoffs, downloading three label formats, and reconciling three settlement files. Teams that automate order intake, label generation and manifesting can push the same two people well past that range without adding hours, because the fixed per-order overhead collapses. Teams doing it all by hand tend to hit a wall around 40 to 60 orders because the day simply runs out of usable minutes.
The dispatch SLA cutoff on each marketplace — the deadline by which an accepted order must be handed to the courier. Missing it is the fastest way to damage account health, because a late dispatch can trigger penalties, lower search ranking, and in repeat cases suspension of specific listings. Each platform runs its own clock, and the cutoffs rarely line up, so the practical rule is to batch the earliest-cutoff marketplace first every morning and never let an accepted order sit unlabelled past mid-morning. The whole point of an hour-by-hour routine is to make sure no cutoff is ever a surprise.
For most two-person teams, splitting by function beats splitting by marketplace. If Person A owns intake, labelling, manifesting and dispatch across all three platforms while Person B owns inbound returns, inventory sync, reconciliation and customer replies, each person builds deep fluency in one type of work and the handoffs are clean. Splitting by marketplace sounds tidy but forces both people to learn every task, doubles the tooling each has to touch, and creates gaps when one person is out. Function-based ownership also maps neatly onto the two halves of the money story: getting orders out on time, and making sure every rupee is paid back correctly.
Manually, you cannot keep it perfectly in sync — you can only reduce the lag. The usual method is a shared master stock sheet that both people update after every dispatch and every returns intake, plus a once-daily manual push of adjusted quantities into each seller panel. The risk is oversell: a unit sells on Amazon and AJIO within the same hour before the sheet is updated, and now one customer gets a cancellation and an account-health ding. This is exactly the failure mode that cross-platform inventory sync removes, because stock is decremented everywhere the moment it moves anywhere, with no human in the loop and no lag window.
Reconciliation is an end-of-day or start-of-day task, never a mid-rush one, because it needs calm attention and the latest settlement files. The practical rhythm is: pull each marketplace's settlement report, match every payout line against what the order should have paid, flag deductions that look wrong — wrong weight, duplicate charges, RTO billed for a parcel that never came back, commission that does not match the slab — and queue the claims. Because claim windows expire, the discipline is to review settlements the day they land rather than saving a month of files for a painful weekend session. Two people rarely have a spare weekend, which is why this is the first task most teams want off their plate.
It is broadly the same shape of work — accept, label, manifest, dispatch, handle returns, reconcile — but the details differ enough to matter. Label formats, manifest procedures, SLA cutoff times, return windows, settlement file layouts and deduction categories all vary between AJIO, Meesho and Amazon. That variation is the real tax of multi-marketplace selling: not the volume, but the constant context-switching between three sets of rules. A routine reduces the pain by grouping like tasks together across platforms; an agentic OMS removes most of it by handling each platform's specifics itself so the two people work in one place instead of three.
Ads deserve a short, fixed daily checkpoint rather than constant fiddling. The healthy habit is a ten-minute review — usually late morning once dispatch pressure has eased — to check spend pacing, pause anything bleeding money on a term that is not converting, and note bids that need adjusting. The trap is either ignoring ads for a week (and letting spend drift) or refreshing the dashboard obsessively (and stealing time from operations). A fixed slot keeps ads honest without letting them colonise the day, and campaign automation can hold the pacing steady between checkpoints.
SLA adherence and reconciliation break first, in that order. As volume climbs, the manual per-order overhead that was merely tedious at 30 orders becomes impossible at 80: labels start printing late, one marketplace's cutoff gets missed on a busy day, and settlement files pile up unreviewed until claim windows quietly expire. The team feels busier but earns less per order because both the on-time-dispatch side and the money-recovery side are silently degrading. This is the point at which teams either hire a third person — adding cost — or move the repeatable operations onto an agentic OMS so the existing two can keep the quality bar without adding hours.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
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.
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.
AJIO Seller Panel Guide: A Walkthrough of AJIO Seller Central
A practical, screen-by-screen walkthrough of the AJIO seller panel — onboarding, catalogue, orders, dispatch SLAs, returns and payouts — plus the reports that decide whether you get paid correctly.
Festival Sale Prep: Stock, SLA and RTO Buffers
Festival demand spikes reward sellers who prepared their operations and punish the ones who did not. How to buffer stock, protect dispatch SLA and plan for the RTO wave.
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.
Order breach in Meesho: what it is and how to prevent it
What a breach flag means, the seven ways orders drift past the dispatch promise, what one costs at settlement, and the daily loop that keeps the count at zero.
AJIO seller operations: the daily workflow, end to end
The full 11-stage AJIO order-to-manifest flow, document pipeline, SLA watchdog, and how to run it all on autopilot with the Robnu Chrome extension.
The two-person team playbook for marketplace brands
How two people run a marketplace brand without burning out: the demand/supply split, the four-block daily rhythm, shared systems and runbooks, and when to hire #3.