Half the day goes into judgement
Someone I know runs five home goods stores.
She says her day has two completely different halves. One is deciding what to push, how to price it, and how to schedule the promotion. The other is getting those decisions into five back ends.
The first half is where her value sits. The second, in her words: “I could do it with my eyes closed — but not for five stores.”
This article takes apart the second half: which parts of a day need no judgement at all, and which should be handed over first.
Listing: the most assembly-line-like part
Listing is the most standardised action in the job, because it naturally divides in two.
The first half is deciding: which product, what price, how to write the selling points, which hero image. That differs every time and is the real work.
The second half is entering: open the back end, create a product, put name, price and specification into the right fields, upload images, pick a category, submit. That is nearly identical every time; only the content changes.
The second half has a very recognisable profile: fixed steps, fixed fields, fixed order. That is the kind of work most easily handed over.
With iEasyRun you can describe it directly:
Open the product back end and create a new listing. Read the name, price, specification and description from this sheet, take the images from this folder on the desktop, and upload them in order. Stop before submitting so I can look at it.
That last sentence matters. Listing publishes externally, so the machine stops before submitting and a person makes the final check. You save the entry time without handing over the risk.
Repricing and data collection: two very different things
These often get lumped together as “daily maintenance”, but they deserve different treatment.
- Repricing belongs to the “modifies things” category. A misplaced zero can lose a month of margin overnight, so it should not be the first thing automated. It belongs after patrol and fixed-field entry are steady.
- Data collection belongs to the “reads only” category. Open a few back ends and transcribe sales, stock and review counts into a sheet. Getting it wrong means inaccurate data, not a loss.
The order should be: do the read-only work first, and touch modifications once it runs steadily. That is not caution for its own sake — the read-only work is what teaches you the workflow, and those lessons get used later. Which screen is slow, which back end is down in the morning, which device hesitates: you learn all of it doing collection first.
Reviews and messages: standard questions dominate
Answering reviews and answering messages are two ends of one job.
- Reviews are public, and the consideration is wording and reach.
- Messages are one-to-one, and the consideration is speed.
Both share a line: standard questions can be handed over; anything with emotion or a commitment cannot.
A standard question is one with a fixed answer and no judgement: when will this ship, is it returnable, is there a discount. That category is the bulk of the volume.
What must reach a person? Complaints, handling negative reviews, and anything committing you to compensation. Those conversations are not about accuracy; they are about being taken seriously, which a machine cannot provide.
Reporting: what it saves is not the ten minutes
Assembling the figures and sending the daily report looks like a ten-minute job.
But it carries a hidden cost: switching out of working mode into assembling mode, and back. That switch costs far more than the ten minutes.
So the right handling is not to drop the report but to hand over the assembling: have a machine collect the figures at a fixed time into a sheet, so opening it shows you something already assembled. You only make the judgement — which store fell off, whether to adjust something.
This is really the “how do you use the result” question. Most tools only solve how to operate, and rarely how the data becomes readable. The second is often where the relief actually is.
What to hand over first
In order:
- First, data collection. Least risk since it only reads, highest frequency, verifiable. Two weeks of it also gets you familiar with the hardware and network.
- Second, fixed-field entry. The back half of listing, batch profile updates. Fixed steps, reversible mistakes.
- Third, standard question replies. High volume, simple, clear boundary.
- Last, repricing and delisting. Anything touching money, and with a human check before submitting.
The only criterion in that order: start where a mistake costs nothing.
A test you can reuse
For any operation, ask two questions.
- Does this step need judgement? If so it stays with people; if not, hand it over.
- If it goes wrong, what is the cost? If the cost is redoing it, hand it over. If the cost is money or account standing, not yet.
Those two answers tell you both whether to hand an action over and where it belongs in the queue.
The software is completely free and runs on your own computer. For a related breakdown, read how many messages a support agent answers a day; for the full bulk listing flow, see bulk e-commerce listing.
Frequently asked questions
- Which part takes the most time?
- It depends on volume. Listing and repricing take longest per action, but data collection and review replies happen most often. Taken together, what actually eats the day is whatever is high-frequency, short, and needs no judgement.
- Can listing be fully automated?
- The back half can. Filling fixed fields, uploading images and applying a template are all mechanical. Choosing products, pricing and writing selling points are judgement calls. The sensible split is the machine enters and uploads, a person decides what goes in.
- Can repricing, which touches money, be handed over?
- Put it last. Repricing, delisting and refunds cost real money when they go wrong. The right order for any automation is patrol first, then fixed-field entry, and modifications last.
- Why hand data collection to a machine?
- Because a person will not get it wrong, but will get tired of it. Manual transcription starts drifting around the sixth page. And this is the most regular category of work there is, which makes it the best automation candidate.
- How is answering reviews different from support?
- Two ends of the same job. Reviews are public and about wording and impact; private messages are about response speed. Both share the same line: standard questions can go, anything with emotion or a commitment cannot.
- Can the daily reporting be skipped?
- The report itself cannot, but the assembling can. Have a machine collect the figures at a fixed time into a sheet and you only make the judgement. What that saves is not the few minutes but the switch into and out of a different mode.
- Which part pays back first?
- Data collection. It carries the least risk because it only reads, it happens most often, and the result is verifiable. Two weeks of it also teaches you how each back end loads, which pays off later.
- How many stores can one person run?
- It depends how much has been handed over. Purely manual, three to five stores is the limit. With patrol and fixed-field entry automated, a dozen is common.
How many times a day?
Hand over the half that needs no thought
Software is completely free and runs on your own computer. Start with the most repetitive part.