Learn / Platforms
Salesforce Commerce Cloud agent readiness
On Salesforce Commerce Cloud the catalogue is rarely the problem and the storefront usually is, because it is custom and was built for people looking at screens. The second and less technical problem is ownership: agent readiness spans catalogue, storefront, checkout and edge security, which in an enterprise are four teams, so the work stalls on who is accountable rather than on difficulty.
The join between catalogue and page
Custom storefronts are built for people looking at screens, and the fields an agent needs frequently do not survive the trip into the served markup. Rich data in the platform and an empty page are entirely compatible.
Fetch a product URL and read what an anonymous cold request receives. See headless storefronts and AI agents.
The governance problem
This is the part that is specific to enterprise rather than to the platform. Agent readiness spans four areas that in a large organisation are four teams: catalogue, storefront, checkout, and edge security. Each change is small and none of them is anybody’s job.
The result is that well resourced stores are often further behind than much smaller ones. Naming an owner is usually the intervention that unblocks it. See how to explain agent readiness to your leadership team.
Check every regional storefront
Locale sites differ in template, currency handling, policy pages and edge rules. Agent readiness is a property of a storefront rather than of a programme, so one region passing tells you very little about the others.
The checkout, cold
Enterprise checkouts carry the most customisation and therefore the most required fields, account gates and third party steps. Walk it signed out, on a narrow viewport, in a fresh session, and stop at the payment step.
See custom checkouts and AI agents and how to test checkout in an in-app browser.
Questions
Who should own this internally?
Whoever owns conversion, with a named contributor from each of catalogue, storefront and infrastructure. Spread across four teams with no owner it becomes nobody’s, which is the usual reason enterprise stores are further behind than their resources suggest.
Is this a replatform question?
Almost never. The changes are structured data in the served markup, published terms, a current feed and a checkout that survives a cold session. None of that requires changing platform.
What about locale and regional storefronts?
Check each one. Sites differ in template, currency handling, policy pages and edge rules, so a passing result in one region says very little about another.