Not much work, but a lot of variety
Someone I know runs a pet supplies business: one physical shop and two online stores.
He summed it up well: “Not much work, but a lot of variety.”
Messages on two platforms in the morning, a stock update at midday, content in the afternoon, a look at the figures in the evening. Individually none of it is a big deal. Together, the day is gone.
And there is nobody to share it with. A team can assign review replies to a fixed person. He cannot; everything lands on one head.
So the problem is not efficiency. It is priority: what must happen now, what can wait and be batched, and what does not need doing at all.
Four buckets
Pour the day out and sort by “what happens if this waits”.
- Do it now: conversations where a customer is waiting, transactions in progress, anything with a time window such as a flash sale going live.
- Batch it: public review replies, product detail updates, data assembly, routine posting.
- Schedule it: stock counts, reconciliation, monthly reports.
- Skip it: the vague “while I was there” activities.
Of the four, the third and fourth are worth attacking first, because they get squeezed out by the first two — and once squeezed, the day feels like nothing got done.
How to batch the second bucket
The method is to pull these out of the day and put them in a fixed slot.
Three shops’ public reviews can be answered in one pass at eight in the evening. You enter “reply mode” once instead of three times.
Batching has one precondition: these tasks need no immediate judgement. Review replies, product updates and posting all qualify — two hours earlier or later changes nothing.
Messages do not qualify. A customer is waiting; batch it to eight in the evening and they are gone.
So the test is one line: is someone waiting? If yes, it cannot be batched. If no, it can.
The scheduled bucket is the one you forget
The third bucket is where things go wrong, because while nothing is wrong you never think about it.
If stock is not updated you cannot know without a count. If accounts are not reconciled you cannot know without doing the sums. If the report is not assembled, you find out at month end.
The only reliable answer is to give it to something that does not forget. People forget; it is not a matter of attitude.
The method is straightforward: have a machine walk the key pages of all three shops at a fixed time — stock, orders, figures — and save screenshots for you to review once in the morning. Read-only, so the risk is zero, but you stop forgetting.
That is the category worth handing over first for someone running several shops alone. Not because it saves much time (it does not), but because it turns “will I forget” into “were there screenshots”.
There is a second benefit that is less obvious: the records accumulate into data. Which platform turns stock faster, when review scores dipped, what hours orders cluster in. No single day shows a trend; a month of days does. And that retrospective view is exactly what a solo operator lacks.
The bucket to skip
This is the hardest one, because it means going against what everyone else is doing.
The test: if I skip this, what changes in a week?
Posting identical content to every platform — skip it, and in a week little changes, possibly for the better, since duplicated content hurts the accounts.
Chasing every trend — skip it, and in a week little changes, while the time goes into the products that matter.
Trying every feature on every platform — skip it, and in a week little changes.
The first time you apply that test it feels wasteful. After a few rounds you notice something: the things that genuinely cost you if skipped are fewer than you assumed.
A working sequence for three shops
Laid on a clock:
- Before work: overnight patrol results and overnight messages, together, fifteen minutes.
- Morning: the do-it-now bucket — waiting conversations and anything that must move today.
- Afternoon: one pass on the batch bucket. Reviews, details, content.
- Evening: the machine handles the scheduled bucket; you read the result.
The core of that arrangement is reducing the number of mode switches in a day. A lot of the exhaustion in running several shops alone is not volume; it is jumping between a dozen mental states.
Where the accounts live
One practical point to finish: keep each shop’s accounts on separate devices.
Not for any defensive reason, but because cycling logins on one device is itself unnatural. Two or three devices is enough with a few shops — get the workflow running on what you own before deciding whether to add more.
The software is completely free and runs on your own computer. For a related small-team scenario, read how many messages a support agent answers a day; for device grouping, see managing 20 phones solo.
Frequently asked questions
- How is running shops alone different from being on a team?
- Not volume but coordination. A team can assign a category to a fixed person; alone, everything lands on one head. That makes priority more important than efficiency.
- What has to be done on the spot?
- Conversations where a customer is waiting, transactions in progress, and anything with a time window. The test is simple: does an hour of delay cost you something?
- What can be batched?
- Replying to public reviews, updating product details, assembling reports, posting routine content. Two hours earlier or later makes no difference, and batching them avoids repeated switching.
- What can simply be dropped?
- More than you would expect. A lot of daily activity is done because others do it: posting identical content to every platform, chasing every trend. Ask what changes in a week if you skip it.
- How many shops can one person run?
- Depends on category and platforms. If a shop generates more than twenty customer conversations a day, three is already tight. Once the batchable work is handed over, five or six is realistic.
- How many devices do I need?
- Each shop's accounts on separate devices is the floor. Not out of fear, but because cycling logins on one device is unnatural. With a few shops, two or three devices is enough.
- What should be handed over first?
- Status checks — the read-only kind. Have a machine walk the key pages of all three shops at a fixed time and save screenshots, and you review them once in the morning. Zero risk, immediate relief.
- Will I become dependent on the tooling?
- Yes, and that is fine, provided you know what you are depending on. The real danger is handing over judgement without noticing, so decisions stay with you.
How many shops?
Let the computer watch what needs no judgement
Software is completely free and runs on your own computer. Start with one device.