Platforms · Salesforce Commerce Cloud
Can AI agents buy from a Salesforce Commerce Cloud store?
Salesforce Commerce Cloud, still Demandware underneath, serves storefronts an agent can read page by page and publishes no anonymous catalogue endpoint. Its Shopper API exists but needs a client credential, so an AI agent arriving cold sees the storefront and nothing else. On SFCC the buy path is usually the harder half: the checkout is long, often multi-step, and frequently sits behind bot protection.
How Ottom reads a Salesforce Commerce Cloud catalogue
Source: product pages, read one at a time. No anonymous feed, so Ottom uses the sitemap and reads schema.org JSON-LD from the product pages it lists, the same way an agent would. SFCC storefront URLs are recognisable (/on/demandware.store/), which is how a scan knows to stop asking Shopify and Woo questions and go straight to the pages.
What works in your favour
- Sitemaps are usually complete and well maintained, so an agent can find products without guessing URLs.
- Product markup is generally present on the standard cartridges, which gives an agent price and availability.
Where agents tend to stop
- Bot protection is common on enterprise storefronts, and an agent challenged at the door cannot report anything about the store behind it.
- Multi-step checkouts with client-side validation stop an agent well before payment.
- Locale and site selectors can send an agent to a page that is not the one a shopper would land on.
Read about these first
- Bot protection blocks the agent before the storefront loads
- Agent could not reach the payment step
- Checkout returned an error
How often this happens on Salesforce Commerce Cloud: 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
Our WAF blocks bots. Does that mean we score badly?
It means the scan reports that it was blocked rather than guessing at what is behind the block. Ottom does not score a stage it could not measure. Our agents publish a user agent and arrive from a fixed set of static addresses, so you can allowlist a scan and measure your store rather than your bot protection.
Does the Shopper API make us readable?
Not to an agent that has no credential. It is the right tool for a partner you have onboarded and the wrong assumption about a shopping agent arriving from a chat window. What that agent reads is the storefront.
See this on your own Salesforce Commerce Cloud 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.