What your store needs to be legible to an agent
Here is the part most owners get backwards. They assume the work is payment integration. It isn't. Most of the agentic commerce work we take on turns out to be catalog work with a better name on the invoice: fixing feeds, making price and stock honest in real time, checking that the machines reading a store are allowed to. That sits inside our AI integration work and costs a fraction of what owners brace for.
An agent recommending your product needs four things to be true. A product feed with stable identifiers, complete attributes, and prices and stock correct at the moment they're read. Product pages that render their content to a machine, not only to a browser. Returns and shipping policies published as structured, machine-readable links, because that is a required protocol field and it is what an agent checks before recommending anything. And permission to read you at all, which lives in your robots.txt: OpenAI's crawler documentation states that sites opted out of its search crawler will not be shown in ChatGPT search answers.
That last one takes an afternoon. We have opened robots.txt on stores paying an agency for AI visibility work and found the relevant crawler blocked by a rule someone added in 2023.
The catalog side is where the real gap sits. In the same April 2026 analysis, Adobe scored how much of a page a large language model can read and put the average US retail product page at 66%, leaving roughly a third of product content invisible to the models doing the recommending. That is a vendor-defined score from a company selling the fix, so treat the exact figure with suspicion. The pattern matches our audits: price and availability are the fields that have quietly drifted, and a stale stock flag is worse than a missing one.
The checklist version lives in what agent-ready actually means for a catalog.