For Magento 2 and Adobe Commerce developers
Agentic commerce on Magento is a developer's job. Here is what it involves.
AI shopping agents in ChatGPT, Gemini and Google AI Mode read a store's data, not its theme. Shopify switched this on for its merchants. On Magento, somebody has to configure it, verify it against real agents and keep it working. That somebody is usually the developer who already looks after the store.
# two of the first things an agent looks for $ curl -sI https://store.example/.well-known/ucp HTTP/2 404 $ curl -s https://store.example/robots.txt \ | grep -A1 OAI-SearchBot User-agent: OAI-SearchBot Disallow: /
Illustration. No commerce manifest, and the search agent that would recommend the store is blocked.
The work, layer by layer
Where agent readiness lives in a Magento codebase.
The same five layers the readiness audit scores, mapped to the parts of Magento you already know.
FoundAccess
robots.txt rules that separate search agents (OAI-SearchBot, Googlebot, PerplexityBot) from training crawlers, XML sitemaps, and a product feed that stays fresh.
a blanket bot block, or a feed cron that stopped months ago.
UnderstoodComprehension
schema.org Product and Offer JSON-LD from your templates, configurable products exposed as real variants, and GTIN, MPN and brand mapped from attribute sets.
variants collapse into one offer, or key attributes exist only in descriptions.
TrustedIdentity
Organization data, MerchantReturnPolicy and OfferShippingDetails in machine-readable form, and a signed UCP manifest at /.well-known/ucp.
policies live only in CMS pages, or signing keys drift from the manifest.
BuyableTransactability
UCP capability endpoints that return live price and stock, and a clean cart handoff into the Magento checkout.
full-page cache or Varnish serves agents a stale price, or a plugin rewrites the response.
Kept readyReliability
Scheduled re-scans after deploys, extension upgrades, cache changes and spec releases, with drift caught before a merchant notices.
a routine deploy or setup:upgrade quietly undoes last month's work.
Why modules are the start, not the finish
A valid manifest and a broken runtime.
Free and commercial Magento modules for UCP, ACP and MCP exist, and they are a sensible starting point. A validator confirms the manifest is well formed. It cannot tell you what an agent receives from a real Magento stack.
- Caching. Full-page cache and Varnish rules written for browsers can hand agents yesterday's price or stock.
- Plugins and observers. Third-party extensions that rewrite product or checkout responses change what agents see.
- Store views. Multi-store, multi-currency and B2B setups need the right scope in every response.
- Performance. Agents time out on slow endpoints; uncached GraphQL and REST calls need budgets.
- Change. The standards move month to month. Adobe committed to UCP and ACP in February 2026 without a date for native support.
Where this goes
The developer who does this work is an Agentic Commerce Orchestrator™.
Goofre™ trains and certifies Magento developers and agencies to own agent readiness for the stores they look after, and gives them the audit engine, the storefront toolkit and the console to run it. Membership is free, and you certify by readying a real store.
The path to ACO™
- Live cohort, from basics to the protocols in practice
- Audit engine, toolkit and console
- Certification on a real store
Is your Magento store invisible to AI shoppers?
- The markup, feeds, identity and checkout signals agents read
- The gaps most Magento stores miss
Magento questions
What Magento developers ask first.
Does Magento support UCP natively?
Not yet. Adobe committed to UCP and ACP in February 2026 without publishing a date for native support, so today a Magento store reaches UCP through a module plus configuration, and has to be verified store by store.
Open Source or Adobe Commerce?
Both. The work and the audit apply to Magento 2 Open Source and Adobe Commerce, self-hosted or on Cloud.
Does the theme matter, Luma or Hyvä?
It changes where structured data is emitted, not what agents need. The audit reads the rendered output a crawler receives, so it scores Luma, Hyvä and headless storefronts the same way.
Which UCP module should I use?
Whichever fits the store: an open-source module, a commercial extension, or the Goofre storefront toolkit. The readiness engine scores conformance, whichever module produced it.
Why does a store pass a validator and still fail agents?
Validators check that a manifest is well formed. On Magento, full-page cache, Varnish rules, plugins and store-view scoping can still serve agents stale prices, wrong stock or broken endpoints at runtime.
Free · a store you maintain
See what agents see on a store you look after.
Send the URL. We run the readiness engine and a person emails you the graded report, every gap with its fix and its owner. Then decide whether to apply.