E-commerce operations specialist — tasks, one by one
The unit of analysis is the task, not the job title. Each one below carries its direction, whether the judgement rests on evidence or on platform inference, the reasoning, and what it does not establish.
Every task on this page#
Writing the listing
Automating✓ Evidence-backedTitles, keywords, descriptions, the detail images and the variant table — for hundreds or thousands of items.
This is high-volume templated writing against a known format with a measurable outcome — the listing ranks and converts or it does not — which is the combination that lets a system iterate without supervision. It is also the task that has always consumed most of the hours, and platforms themselves now ship generation tools, so the adoption does not even require the merchant to choose it.
Cheap listings do not create advantage, they remove one: when everybody's copy improves at once the ranking returns to what it was and the work still has to be done. This is the clearest case on the site of automation that is compulsory rather than optional — a merchant who does not adopt it falls behind, and one who does gains nothing durable.
Buying the traffic
Automating✓ Evidence-backedBidding, budgets and the daily decision about how much to pay for a customer this platform will rent you.
Bid optimisation is a closed loop with a fast, numeric outcome, and the platforms have automated it deliberately — automatic bidding is the default and often the only well-supported mode. Note who did the automating: the party selling the traffic now also sets the price paid for it.
This automation was not adopted, it was imposed, and that distinction matters more here than anywhere else on the site: the operator's judgement did not lose to a better algorithm, it lost to a change in what the platform exposes. What is left is choosing what to sell and when to stop — decisions the platform's tools do not make because they are not in the platform's interest to make.
Reading what the numbers mean
Still human-led≈ Platform inferenceNoticing that conversion fell because of a review, a competitor's price, a rule change or a picture that stopped loading — from a dashboard that says none of those things.
Detecting the drop is trivially automated and already is. Explaining it requires going outside the data — reading the reviews, checking a competitor, knowing that the platform ran a campaign yesterday — and the explanation determines the action. This is the analysis-versus-attribution split that recurs across this site, and it is unusually sharp here because the environment changes weekly.
This task holding does not mean the headcount does, because the same person can now cover several stores: cheaper listings and automated bidding raise the number of storefronts one operator can hold, which reduces the operators per store without removing a single task from any of them.
The platform changed the rules again
Still human-led≈ Platform inferenceWorking out what a new policy, fee or ranking change actually means for this shop, and what to do about it before competitors do.
The input is an announcement written to be vague plus knowledge of how this platform has behaved before, and the output is a bet made before anyone has data. No model has the second input because it is not published anywhere — it exists as the operator's memory of the last three rule changes.
This is the most durable task and the least transferable: it is knowledge of one platform, and it becomes worthless the day the merchant moves to another. An occupation whose defensible skill is specific to a single company's rulebook has a different kind of fragility from the automation this page otherwise describes.