LO
E-commerce operations specialist — how we know
The page itself gives the judgements. This one gives what they rest on: which technologies bear on the work, how the estimate moved since language models reached the public, and the method behind both.
Which technologies matter here#
Four separate signals. They are deliberately not added together — a job exposed to two technologies is not twice as exposed.
How it got here#
The index is not a static number. This is where it would have sat at each capability checkpoint since ChatGPT — reconstructed, and labelled as such.
—— this stretch contains a verified event- - - no event in this stretch — reconstruction only0 = no task exposed, 100 = every task exposed
● 2 verified events for this occupation, plotted at the date it happened — the parts of the line near a marker are anchored to something checkable.
A steep early climb and then an unusually hard flat, and the shape is set by who did the automating rather than by what became possible. Listing generation and automatic bidding are platform features, so adoption was not a merchant's decision — the curve moves when the platform ships, not when the operator chooses. It flattens at the two tasks the platform's tools deliberately do not perform: explaining why a number moved, which needs information outside the dashboard, and working out what a rule change means, which needs a memory of the last three. Note the thing this curve cannot show, which decides more than its height: cheaper listings and automated bidding raise how many storefronts one operator holds, cutting operators per store without removing a task from any store.
A flat line is not a forecast of safety. It says which tasks automation has reached so far — the occupations that moved least here are the ones where the constraint is physical or regulatory, and both of those can change.
Method and sources#
- Assessment date
- 2026-09-14
- Basis of the task judgements
- 2 evidence-backed · 2 platform inference · 0 not enough evidence
- Verified events
- 2