It is 7:40 AM and you are already behind. Eleven new orders across AJIO and Meesho, four labels to download, a manifest that closes this evening, one return photo to judge, and a settlement statement from Tuesday you still have not opened. You are the founder of a one person ecommerce business — which means you are also the packer, the accountant, the claims department, and the only person who notices when ₹312 goes missing.
This post is the field guide we wish someone had handed us: where the hours actually go in a one person ecommerce business, the single rule that decides what to automate first, what you should keep manual on purpose, and a weekly rhythm that holds at 5–25 orders/day without eating your evenings.
Where the hours go in a one person ecommerce business
Sellers we have sat with at 10–15 orders/day report a weekly operations load of roughly 38 hours — illustrative, but consistent enough across stores to treat as a planning number. The surprise is the split. Packing and courier handover, the part everyone pictures, is about 7 hours. The screen work around it is nearly three times that: panel checks and order processing (~9 hours), labels, slips, and manifests (~6 hours), returns triage and claim evidence (~5 hours), payment checks (~4 hours), catalog upkeep (~4 hours), and buyer or support messages (~3 hours).
Notice what is missing from that list: anything that grows the business. New SKU research, better photos, a second marketplace, price experiments — all of it happens after hour 38, which in practice means it happens rarely and badly. The cost of manual operations is not the hours themselves. It is everything those hours crowd out.
The two-panel problem nobody warns you about
Most advice treats “a marketplace seller” as someone on one marketplace. The reality for a growing one-person operation is AJIO plus Meesho — and the second marketplace does not add its hours politely. The panels are different. The processing sequences are different. The document formats, the manifest mechanics, the settlement statement layouts, the claim portals: all different. Worse than the duplicated clicks is the context-switching tax — every jump between systems costs you a few minutes of re-orientation, and the mental ledger of “which SLA is closer right now” runs all day in the background.
The second marketplace is also where errors concentrate. By the time you open panel two, your attention is spent on panel one's problems. Sellers we have sat with consistently describe the same pattern: the missed order, the late manifest, the slipped claim window — it is almost always on whichever marketplace they check second. This is not a discipline failure. It is what happens when one person carries two operating systems in their head.
The fix is structural, not motivational: both marketplaces have to flow through one system, one schedule, one report. When the AJIO orders and the Meesho orders arrive in the same processed batch with the same document naming, the two-panel problem simply stops existing — there is one queue, and it is already done by the time you look at it.
The automate-first rule: high frequency, low judgment
Every task in your week sits somewhere on two axes: how often it recurs, and how much judgment it needs. The rule that has never failed us: automate the top-left quadrant first — high frequency, low judgment. That is the work a machine does identically every day and a tired human does worse every day.
- The daily order run. Accept, process, generate labels and slips, prepare the manifest. Same steps, same order, every single morning. This is the first thing to hand to an agentic OMS — see how Robnu's scheduled run works.
- Documents. Labels, packing slips, manifests, invoices. Generated, named, and stored against the order — never hunted for in a downloads folder.
- Settlement matching. Order amount vs settled amount vs deduction lines, for every order, not a monthly eyeball of one lump sum. This is exactly the work that gets skipped when you are exhausted — and skipping it is how money leaks.
- Deadline tracking. Claim windows, SLA cutoffs, manifest times. A calendar in your head fails precisely on the busy days when it matters most.
The top-right quadrant — high frequency but high judgment, like dispute approvals and return-fraud calls — is where software assists and you decide. The bottom-right — low frequency, high judgment, like supplier negotiation and pricing — stays fully yours.
What to keep manual — on purpose
Some work should stay human even when software offers to take it. Packing quality is one: at solo scale, the founder's hands on every parcel is a genuine advantage — your mis-pick rate and your presentation are better than any warehouse you could rent. Supplier relationships are another; no tool negotiates fabric prices in Surat for you.
And final calls on claims. Robnu's claim filing is moving toward fully autonomous, but even now it keeps a deliberate one-click human approval on filings — because a claim is a statement of fact made in your name, and the rare ambiguous case deserves your eyes for three seconds. Honest automation knows where to stop.
Budget energy, not just hours
Here is the part the hour-budget chart cannot show: not all hours are equal. The first two hours of your morning are the only time most founders can do real judgment work — pricing, catalog decisions, a hard claim. If those hours go to clicking through two marketplace panels and downloading PDFs, the business is spending its best fuel on its dumbest work.
This is the real argument for scheduled processing over even fast manual processing. It is not that 45 minutes becomes 5. It is that the 45 minutes stops being the first 45 minutes. The run finishes before you sit down; you read a report instead of performing a ritual; your peak energy goes to decisions instead of downloads.
Consider a real Tuesday. Version one: you spend 8:00–8:50 on panels, pack until 1 PM, spend the afternoon on a courier dispute, and at 9 PM remember the Meesho claim that expires tomorrow — so you build the evidence half-asleep and file something weaker than the case deserved. Version two: the run finished at 7:30, the claim deadline was flagged in Monday's report, you approved the pre-assembled filing with one click over breakfast, and the 8:00–9:00 slot went to deciding whether the ₹499 kurta line can carry a ₹50 price increase. Same business, same orders, same person — entirely different quality of decisions. That is the energy budget at work.
A weekly rhythm that holds at 5–25 orders/day
Solo operations survive on rhythm, not heroics. The structure below is the one we have seen hold for months at a stretch: the repeatable work runs itself daily, the physical work gets one fixed block, and each weekday owns exactly one category of thinking work.
- Every day: scheduled order run in the morning (before you are at the desk), packing block 11 AM–1 PM, courier handover by 4 PM. One block, no trickle-packing through the day.
- Monday — money. Settlement review and reconciliation: every line, every deduction, 60 minutes maximum when the matching is automated.
- Tuesday — returns. Triage the week's returns, review claim evidence, approve filings.
- Wednesday — stock. Thursday — catalog. Reorder decisions one day, photos and listings the next. Never both at once.
- Friday — the 30-minute audit. SLA headroom, open claim deadlines, outstanding amounts. If something is drifting, you find out on Friday, not in next month's settlement.
Where Robnu fits
Robnu is an agentic OMS built for exactly this seller: it runs the daily AJIO and Meesho order processing on a schedule, generates and stores every document, matches every settlement line to its order, tracks every claim window, and surfaces the rare exception for your one-click approval. The week above stops being aspirational and becomes the default. One honest note: Robnu is independent software built for AJIO and Meesho sellers — not affiliated with or endorsed by either marketplace.
What it does not do is also worth saying plainly. It will not pack your parcels, talk to your fabric supplier, or set your prices — the bottom-right quadrant of Figure 2 stays yours, on purpose. And it will not pretend every flagged exception can be handled without you: the one-click approvals exist because some calls genuinely need a founder. The goal is not a zero-touch business. It is a business where your touches are the ones that matter.
If you are running everything from panels and a notebook today, start with the comparison on Robnu vs spreadsheets — it maps each hour in Figure 1 to what changes. Then connect your store and let tomorrow's run happen without you. It is free while we figure out pricing, and if you stay under 25 orders/day it stays free forever — so the decision costs you nothing except the ritual you were hoping to lose anyway.