Agentic Commerce Suite — user guide
Agentic Commerce Suite — user guide
Everything the module does, written for the person who will run it. Documents release 1.3.0; the same text ships with the module.
Published copy: https://expandingweb.com/agentic-commerce-suite/manual. That page renders
resources/docs/agentic-suite-user-guide.mdin the expandingweb.com repository — a mirror of this file. Change this guide and the mirror in the same session, or the page documents a release that no longer exists.
Make your store legible and transactable to AI shopping agents, and see in your admin how much agent traffic you are winning or losing.
This module does not add a chatbot to your storefront. It makes your store readable and buyable for other people's agents — ChatGPT Shopping, Perplexity, Gemini, Claude, agent browsers — and measures what they do.
It never promises placement or ranking in any AI surface. Nobody can.
1. Install
composer require expandingweb/module-agentic-suite
bin/magento module:enable ExpandingWeb_AgenticSuite
bin/magento setup:upgrade
bin/magento setup:di:compile # production mode only
bin/magento cache:flush
Requires Magento Open Source or Adobe Commerce 2.4.6+ on PHP 8.2, 8.3 or 8.4. Make sure Magento cron is running — the daily scan, the feed refresh and data pruning are cron jobs.
Disable with bin/magento module:disable ExpandingWeb_AgenticSuite; the module's own tables (expw_agentic_*) and configuration are left in place so you do not lose history by accident. bin/magento module:uninstall ExpandingWeb_AgenticSuite removes them completely.
2. What you get for free
Open Marketing → Agentic Commerce.
- Readiness score. Nine checks run against your own storefront once a day, and on demand with Run scan now. Each one explains, in plain words, what an agent sees. The on-demand scan runs synchronously with a 60-second budget — if your PHP-FPM/webserver request timeout is lower than that, raise it for the admin or rely on the nightly cron scan.
- AI agent traffic. Requests from known AI agent user-agents (GPTBot, ClaudeBot, PerplexityBot, ChatGPT-User, Claude-User, …) counted per day, shown over 7 / 30 / 90 days.
- Every failing check links to the fix, or to a readiness review if the fix is bigger than a module.
Nothing leaves your store on the free tier — the only outbound requests are your own storefront's URLs, scanned by your own server.
The checks
| Check | Passes when |
|---|---|
| UCP-01 | /.well-known/ucp returns a manifest with a version and at least one capability |
| MCP-01 | The advertised MCP endpoint completes an initialize handshake and lists at least one tool with a description and input schema |
| BOT-01 | robots.txt lets AI crawlers reach the catalog (not just the homepage), and no noindex/noai directive contradicts it |
| LLMS-01 | /llms.txt exists, is plain text, and is a structured document rather than a placeholder |
| FEED-01 | A sampled product page carries enough agent-expected attributes, with valid values (GTIN checksum, numeric price, non-expired priceValidUntil) |
| SCHEMA-01 | Product and Offer JSON-LD are present on a product page |
| FEED-02 | Merchant feeds are configured, fresh, and free of blocking validation errors |
| WAF-01 | Your edge/CDN serves AI agent user-agents instead of blocking them |
| VAR-01 | Configurable products are exposed as ProductGroup with hasVariant/variesBy |
3. Pro
Paste your licence key under Stores → Configuration → ExpandingWeb → Agentic Commerce Suite → License.
The key is checked once a day. The request carries your key, your storefront's public domain and the module version — never catalog, order or customer data. If our service is unreachable, a valid licence keeps working for 14 days. When a licence expires, the module quietly returns to the free tier; it never breaks your store.
3.1 Merchant feeds — the highest-leverage feature
Most AI shopping surfaces buy from merchant feed programmes, not from crawling. Magento has no first-party path to those programmes — this module provides one.
Under Merchant Feeds, switch on the channels you want:
- Google Merchant Center — RSS 2.0 at a token-protected URL. Copy the feed URL from the dashboard into Merchant Center as a scheduled fetch. This is what feeds Google AI Mode and Gemini.
- Perplexity Merchant Program — same format; join the (free) programme and give them the same URL. Data completeness is a direct ranking signal there, so watch the warnings column.
- OpenAI Product Feed — gzipped JSONL, regenerated every 15 minutes. Delivery needs direct-feed access from OpenAI; until you have an endpoint and token, the file is generated but not pushed.
Set your GTIN and brand attribute codes — products without either are hard for agents to identify across catalogs, and the validation report will say so. Feeds regenerate on cron; Generate feeds now does it immediately and shows the validation report: blocking errors (the product will be rejected) and completeness warnings (it will rank worse).
3.2 Schema repair
Most themes, Luma included, ship no product JSON-LD at all — which is why a perfectly healthy store can read as empty to an agent. Under Schema Repair you can emit:
- Product + Offer on product pages, including your declared shipping and return policy. Declare them honestly: fill in the country, rate and return window only if they are true. Nothing is invented on your behalf.
- ProductGroup with variants for configurable products — sizes and colours become visible instead of hidden behind a dropdown.
- Organization + WebSite on the homepage and BreadcrumbList on product pages.
If your theme already emits Product JSON-LD, turn the first one off — two Product blocks on one page is its own kind of illegible.
3.3 Analytics
- Agent funnel — where agent sessions actually get to, and where they stop.
- Estimated revenue exposure — agent product-page requests × session factor × your conversion rate × your average order value. Every input is yours to adjust, the method is printed under the number, and it is an estimate, not a forecast.
- Readiness score over time, with a warning when a check that used to pass starts failing. A theme deploy quietly breaking your markup is the classic case.
- AI visibility — shopping questions in your category asked against a web-search AI model, answers checked for your domain. Runs on your OpenAI API key, so you control the spend: a 3-prompt sample from the button, the full set from
bin/magento agentic:visibility, and an optional monthly cron. It is a sampled estimate of citations — never a guarantee. - AI share of voice — the question that decides the sale is not "can an agent buy here" but "whose store does the assistant recommend". Buying questions are phrased from your own top-level categories and asked against the same web-search model; every answer is parsed for the store domains it names. The dashboard shows the ranking — named competitors included — your own row even at zero (zero is the finding), and the trend of your share between runs. Marketplaces you sell on can be excluded in configuration. A 3-question sample from the button, the full set from
bin/magento agentic:sov, same key and monthly cron opt-in as visibility. Sampled and non-deterministic — a trend instrument, never a ranking guarantee. - Why they win — the top stores of the latest share-of-voice run are scanned with the same public readiness checks your own score is built from, and lined up against your store check by check. The gaps (they pass, you fail) each name the module switch that closes them; the edges (you pass, every scanned rival fails) are yours to keep. Read-only public checks, blocks honoured — a rival that refuses the scanner at the edge is reported as exactly that. Costs no API credits.
3.4 Agent endpoints
Under Agent Endpoints, switch on what you want to serve:
| Path | What it is |
|---|---|
/llms.txt |
Your store described for language models, generated from the live catalog. Add your own notes — shipping regions, B2B terms — and they are appended verbatim. |
/.well-known/ucp |
Capability manifest. It advertises only what you have actually switched on. |
/agentic/feed/agent |
Your catalog as clean JSON with live price and stock. |
/agentic/mcp |
An MCP server agents can call: search products, get a product, check availability, start a checkout session. |
/agentic/acp/products, /agentic/acp/sessions |
Product discovery and guest checkout sessions. |
Checkout sessions are ordinary Magento guest quotes, so your tax rules, promotions, inventory and shipping rates all apply — the totals an agent quotes are your totals.
Letting agents place orders is off by default. When you turn it on, orders are placed with the offline payment method you nominate (Check/Money order, Purchase order). An agent cannot present card details, and this module will not pretend otherwise. With order placement off, agents can still price a full basket and send the shopper to your storefront to pay.
4. Cron jobs
| Job | Schedule | What it does |
|---|---|---|
expw_agentic_scan |
03:10 daily | Runs the readiness checks and records the score |
expw_agentic_prune |
03:40 daily | Drops traffic aggregates past your retention setting |
expw_agentic_feeds |
every 15 min | Regenerates enabled merchant feeds (Pro) |
expw_agentic_visibility |
monthly | AI visibility probe, if you switched it on (Pro) |
expw_agentic_sov |
monthly | AI share-of-voice probe, same switch as visibility (Pro) |
expw_agentic_rivals |
monthly | Competitor analysis of the share-of-voice top, same switch (Pro) |
5. Privacy
- No order or customer data leaves your store. Ever. Catalog data leaves it only as the merchant feeds you enabled, delivered to the channels you enrolled in.
- Outbound requests are limited to: your own storefront (self-scan), your licence check, the merchant feed channels you enabled, the OpenAI API on your own key if you use the visibility or share-of-voice panels, the public documents of rival stores if you use the competitor analysis (a handful of read-only GETs per domain), and (Pro) a daily plain GET refreshing the known-agent user-agent list.
- Traffic numbers are estimates by declared user-agent: agents presenting a browser user-agent are not counted, and pages served entirely from Varnish/FPC never reach the counter. The figures are a floor, not a total, and the dashboard says so.
6. Support
support@expandingweb.com · expandingweb.com
Fixes beyond the scope of a module — ERP mapping, custom checkout, B2B pricing — are what the Agentic Commerce Readiness Sprint is for.