Learn / Assistants

Can Claude buy from your store?

What any assistant needs from your store is the same: permission to fetch, a catalogue it can enumerate, and product data that answers a shopper’s constraints. Where a purchase completes varies by assistant and changes, so that part belongs in vendor documentation rather than in an article, while the readiness work is identical and can be verified today.

What an assistant needs from your store does not depend on which assistant it is. Permission to fetch, a catalogue it can enumerate, and product data that answers a shopper’s constraints: those three decide the outcome, and all three are things you can check today without knowing anything about a particular vendor.

The readiness work is shared

It is worth resisting the instinct to optimise per assistant. The failures are almost never assistant specific: a price that only exists after scripts run is missing for all of them, a blocked agent category blocks all of them, and a checkout that demands an account defeats all of them.

See what happens when an AI agent visits your store for the mechanics that apply in every case.

Admit by identity, not by lowering the wall

The question behind this one is often whether allowing an assistant means allowing scrapers. It does not have to. Agents worth admitting declare themselves in a stable user agent, come from address ranges their operator publishes, and read your robots rules.

Verifying a declared identity against published addresses is a narrow opening and the opposite of what abusive traffic does. See how to let honest agents through bot protection.

Where the purchase completes belongs in vendor documentation

This is the part that genuinely varies, and it is also the part that has moved most during 2026. Retail Dive reported on 25 March 2026 that OpenAI had announced the previous day that it was retiring the first version of Instant Checkout, with checkout moving back to merchant sites. A detail like that invalidates any article that stated it confidently a month earlier.

So check the vendor, and design for both possibilities: data good enough to win a comparison with no page involved, and a checkout that survives a cold session in a narrow in-app browser.

Questions

Is there anything Claude specific I should do?

Nothing that is not already on the general list. A store that is fetchable, enumerable and correctly published is in the same position with every assistant, and assistant specific tactics are usually a way of avoiding unfinished fundamentals.

How do I allow it without allowing everything?

Admit by verified identity rather than by relaxing your protection. Agents worth admitting declare themselves, come from published address ranges and respect robots rules, which is a much narrower opening than turning bot protection down.

Where does the purchase complete?

Read the current vendor documentation. This detail has changed more than once during 2026 across the market, and a summary in an article is a snapshot that starts decaying the day it is written.

Scan your store