The Agent-Ready Checkout Checklist
Shopping agents will buy from you if they can fill the form, read the total, and trust the button. Here is the exact checklist.
Agent-driven commerce is already real: assistants compare prices, fill carts, and check out on behalf of users. Whether the purchase happens depends almost entirely on how legible your checkout is. This checklist is the same set of checks our audit runs — expressed as a build-time review.
Form fields with real names
Each field must be identifiable by name, type, and purpose. An unlabeled <input> is a guess; a labeled one is a contract. Add autocomplete attributes so agents (and browsers) can fill from a profile.
<label for="card-name">Name on card</label> <input id="card-name" name="cardName" type="text" autocomplete="cc-name" placeholder="Jordan Vale" />
A visible, honest total
The order total must exist as real text in the rendered DOM. If the total is painted into a canvas or an image, agents see an empty rectangle where the price should be — and a cautious assistant will stop the purchase there.
Buttons that say what they do
The submit control needs an accessible name that matches its action. “Place order” beats “Submit”; “Pay $49.00” beats both. Text like this also reduces hallucinated confirmation steps.
| Check | Pass if | Common failure |
|---|---|---|
| Fields named | Every input has a label or aria-label | placeholder-only fields |
| Types correct | email, tel, cc-number used properly | everything type="text" |
| Total in tree | Price is text, not canvas or image | canvas subtotal |
| Button named | Submit reads as an action | icon-only arrow button |
| Errors in text | Validation appears as text near the field | toast that disappears |
Run the checklist
Audit the checkout URL directly — the capability list will tell you exactly which of these checks fail, with a copy-pasteable fix for each.
See what agents read on your own site.
Run a free scan of any page and get a 0–100 readiness score with copy-pasteable fixes.