1
Describe the product
Expose name, variant, price, availability, dimensions, compatibility, and policy links in readable content and structured data.
Commerce and checkout
Help agents compare, cart, and review—before payment.
Make product facts, variants, inventory, cart state, shipping, returns, and checkout boundaries explicit for shopping agents.
Commerce agents need more than product markup. They must distinguish variants, price and availability, shipping constraints, returns, taxes, cart state, and the exact point where a purchase becomes consequential. Provide a read-only path to compare and configure items, make totals and policies visible, and keep payment and order placement behind deliberate user approval.
2
Keep cart state explicit
Show item, quantity, variant, price, discounts, shipping, taxes, and total after every change.
3
Make the stop point safe
Let an agent reach a review cart without payment credentials and require fresh approval for order placement.
4
Protect retries
Use idempotency, clear pending states, and an order receipt so delayed responses do not create duplicates.
Product truth
A browser agent can identify the selected SKU, variant, price, and current availability.
Full cost
Shipping, tax, delivery estimate, returns, and exclusions are visible before payment.
Safe action
Payment and order placement have explicit target review, approval, and receipt states.
Evidence loop
Find the first failure. Fix the task. Verify the same task again.
A score is a summary. The useful artifact is the URL, control, state, assertion, and safe stopping point your team can hand to a coding agent. Scan a public URL to create that baseline, then rerun the journey after each fix.
Create your baselineQuestions teams ask first
Does product schema make a store agent-ready?
It helps discovery and extraction, but it does not prove that variants, cart state, policies, and checkout controls can be used safely.
Where should an agent stop?
For a public diagnostic, stop at a review cart with synthetic or no payment data. A real order requires an authorized user decision at the exact target and total.
How can I test duplicate protection?
Use a sandbox and intentionally delay or retry the request, then assert that one idempotent order or cart mutation and one durable receipt exist.