Platforms · BigCommerce

Can AI agents buy from a BigCommerce store?

BigCommerce publishes no anonymous catalogue endpoint: its APIs need a token, so an agent arriving cold reads the storefront the way a shopper does, page by page. What it gets is therefore whatever the theme puts in the markup, which on the stock themes is usually complete and on heavily customised ones often is not.

How Ottom reads a BigCommerce catalogue

Source: product pages, read one at a time. Ottom uses the sitemap and reads the schema.org JSON-LD on the product pages it lists. We deliberately do not path-guess for a feed: a URL that happens to answer is not a catalogue a store has published, and treating it as one would report a capability the merchant never offered.

What works in your favour

Where agents tend to stop

Read about these first

How often this happens on BigCommerce: not stated here. Ottom publishes frequency by retail category rather than by platform, so there is no per-platform figure to quote. The benchmark pages carry the category view, and publish one only once enough of its stores have been measured at every stage.

Questions

Can we give Ottom API access to read more?

We would not use it. The scan measures what an AI shopping agent can do arriving cold at your storefront, and that agent has no credential. Reading your catalogue through a key would produce a better score and a worse answer.

Does a Google Merchant feed help?

It helps if you advertise it where something can find it, in your page markup or in robots.txt. A feed nobody is told about is a file on a server. Ottom looks for an advertised feed before falling back to reading pages.

See this on your own BigCommerce store

We run the four stages above against your storefront and tell you which of these it actually hits. One free scan per store, per email address, every 30 days.

By scanning you agree to the Terms of Service

Free, and no card. We email you a link, and the scan starts the moment you click it.