Measurement before optimization
Why agent readiness should be measured before it is optimized: a plain method for testing whether a machine can find, compare and buy from your store.

There is a familiar order of operations in online retail: ship the change, watch the conversion rate, repeat. It works when the customer is a person whose behavior shows up in your analytics. It breaks when the customer is a machine that leaves no trace except an abandoned task somewhere else.
You cannot optimize what you cannot see
If an agent fails to buy from your store, there may be no session, no cart and no bounce. It simply never recommends you. The first job is therefore not optimization. It is visibility: a way to see what an agent sees and where it gives up.
A simple method
- Pick a small set of real tasks, such as find this product, compare it to two others and complete a test purchase.
- Run them against your store with an agent, the same way each time.
- Record where each run succeeds, stalls or fails, and why.
- Score the store on the tasks it completes, not on how it looks.
The scores matter less than the repeatability. A benchmark that gives the same answer for the same store tomorrow is a benchmark you can improve against.
Where the runs end
Readiness score
Same store, five runs
Score across benchmark runs
What to record in a run
A run is useful only if it is recorded in enough detail to compare with the next one. Four things are enough.
The task
What the agent was asked to do, in a sentence.
The path
Each page and action, in order.
The outcome
Succeeded, stalled or failed.
The reason
Where it stopped and what state the page was in.
With those four, a result can be explained to the store owner and repeated by someone else. Without them it is an anecdote.
Change one thing at a time
The method only works if a change can be tied to a result. If a store fixes the price display, simplifies the form and changes the checkout in the same week, a better score tells it nothing about which one helped. Change one thing, re-run the same tasks, and read the difference.
When a score goes down
A score that drops is as useful as one that rises. It means something changed: a price field was renamed, a script now blocks a step, a new banner covers a button. A benchmark that is rerun on a schedule turns those regressions into alerts instead of surprises.
Then optimize
Once you can measure, optimization is ordinary engineering. Fix the page where price is missing. Simplify the form that traps agents. Re-run the tasks. Each change either moves the result or it does not.
Measured, not marketed
Plenty of vendors will say a store is agent-ready. A readiness claim without a test behind it is marketing. We publish open research, conformance tooling and public benchmarks so the claim can be checked by anyone, including the merchant.
Get the next one.
New writing from Machine Commerce, by email.
The machine customer.
Commerce has a new reader. What changes when that reader can buy?
Read the manifesto