See which AI assistants read your store and which orders they drive \u2014 now without connecting anything. New xpay Commerce menu, catalog health scoring, ChatGPT Ads eligibility and pixel checking. Your existing settings are unchanged.<\/p>","0.6.3":"
The AI Storefront Assistant now loads reliably alongside caching\/optimization plugins (WP Rocket, LiteSpeed, Autoptimize, SiteGround) with no manual exclusion, and shows your store's name correctly on multilingual stores.<\/p>","0.6.2":"
Product-FAQ sync is safer: a single product's FAQ can update on its own, and a partial or interrupted sync can no longer wipe FAQs you've already approved.<\/p>","0.6.1":"
Turning the AI Storefront Assistant on now takes effect immediately on cached stores, instead of waiting for the cache to expire. Fixes the full-page shopper returning 404 after you enable it. Adds support for opening a side-cart drawer from an off-site link.<\/p>","0.6.0":"
Control over the on-page product-FAQ block, which previously had no off switch. It now also renders on page-builder themes, as a product tab or an [xpay-faq] shortcode, with headings in your own language. Page caches are cleared when FAQs change.<\/p>","0.4.4":"
GDPR-aware attribution defaults for EU\/UK stores, asynchronous order-attribution dispatch off the shopper's thank-you page, a resilient widget consent gate with a 60-second failure breaker, and GTIN schema validation for non-numeric identifiers.<\/p>","0.4.3":"
AI-attributed orders: shoppers referred by ChatGPT, Perplexity, Claude, Gemini, Copilot and 10+ more assistants now surface in your xpay dashboard with revenue split by source. Strictly non-PII. Bundles the 0.4.2 capabilities.<\/p>","0.4.2":"
Explicit-consent gate on the AI Storefront Assistant \u2014 chat surfaces only after you turn it on. GTIN in Product JSON-LD. Variable-product carts. Defensive out-of-stock guard at the deeplink. Seconds-fast dashboard propagation.<\/p>","0.4.1":"
Optional Content Engine add-on: when enabled for your store, xpay can publish answer-first comparison\/buying-guide pages to your site. Off unless you're subscribed.<\/p>","0.3.7":"
Maintenance and reliability polish, plus optional agency\/referral attribution for stores set up by a partner.<\/p>","0.3.6":"
AI-bot crawl analytics: see which AI crawlers (GPTBot, ClaudeBot, Perplexity, etc.) discover your store and whether they reach your discovery files, on your xpay dashboard. Opt-in, off by default, shares the telemetry consent. Known AI bots only \u2014 no human or customer data.<\/p>","0.3.5":"
New \/agents.md skill tells AI shopping agents exactly how to browse your live catalog and build a cart. Hardened \/llms.txt merge that ignores non-text pages from headless storefronts. Optional shopping-bot routing to your structured catalog, off until you enable it.<\/p>","0.3.4":"
Outcome-first Connect screen: plain-language value, no jargon, and an upfront promise that it's safe to try \u2014 the plugin writes no files to your site and fully reverts on deactivate. New panel lists every external service the plugin contacts.<\/p>","0.3.3":"
New Tools \u2192 Run site diagnostics button verifies that AI agents and xpay can reach your store (Permalinks, REST API, \/.well-known\/ discovery files) and tells you exactly what to do if a layer needs attention.<\/p>","0.3.2":"
Good-neighbour discovery: if your site already publishes its own Second WP.org review pass: REST endpoints constructed via Privacy hardening: Settings \u2192 xpay is pure markup \u2014 outbound requests fire only after you click Connect store<\/strong>. Declares WC dependency via the WP 6.5 Settings \u2192 xpay reorganised into five tabs (General, Capabilities, Payments, Links, Tools). Toggle UCP shopping capabilities, map your gateways to Tighter alignment between what \/llms.txt advertises and what's actually serving \u2014 the Commerce protocols section is now backend-driven. See Changelog for the full backend-side changes.<\/p>","0.2.0":" Aligned with ACP \/ UCP \/ AP2 commerce standards and the real discovery conventions (llms.txt, schema.org JSON-LD, robots.txt allowlist). Serves Plugin RENAMED to "Agentic Commerce for WooCommerce" (slug Plugin Check (PCP) follow-up: cleared the four remaining PrefixAllGlobals warnings. No functional changes. See Changelog for full details.<\/p>","0.1.10":" Plugin Check (PCP) submission-readiness pass: tested up to WP 6.9, short description trimmed to \u2264150 chars, removed the deprecated load_plugin_textdomain() call (WP auto-loads WP.org-hosted translations since 4.6), and excluded non-canonical markdown from the zip.<\/p>","0.1.9":" Docs moved from docs.xpay.sh\/products\/woocommerce \u2192 docs.xpay.sh\/merchants\/woocommerce so the path matches the audience. Future Shopify \/ BigCommerce integrations will live as siblings under \/merchants\/. URL-only; no code changes.<\/p>","0.1.8":" Pricing link updated. Punchier Description hero. Full setup walkthroughs with screenshots published at docs.xpay.sh\/merchants\/woocommerce \u2014 readme now backlinks them at the right moments (install \/ REST API keys \/ connect \/ audit \/ troubleshooting \/ privacy).<\/p>","0.1.7":" Source repo at github.com\/xpaysh\/agentic-commerce-for-woocommerce is now public. Restored repo link references in readme.txt FAQ and source-code section so reviewers and merchants can browse the source directly.<\/p>","0.1.6":" GitHub link references in readme.txt held back until the source repo flips public (currently private). Plugin remains GPLv2-or-later \u2014 the installed zip is the canonical unminified source.<\/p>","0.1.5":" Adds the Something is already sending you customers, and your analytics can't see it.<\/strong><\/p>\n\n When a shopper asks ChatGPT \"find me a cordless drill under $80 that ships in 2 days\" and buys from the store it names, that order lands in WooCommerce looking like ordinary direct traffic. Google Analytics shows you nothing. Your reports show you nothing. You cannot tell whether AI assistants are worth your attention, because you cannot see them at all.<\/p>\n\n This plugin makes the AI channel visible, then makes you the answer it gives \u2014 and lets you buy more of it.<\/strong><\/p>\n\n Three jobs, in that order:<\/p>\n\n No theme changes. No replatforming. No new payment processor. Your existing gateway and your payout schedule are untouched.<\/p>\n\n We show you the match rate.<\/strong> Every AI-attributed number in this plugin comes with the percentage of your real orders it accounts for. When tracking misses something, you'll see that too \u2014 because a revenue figure you can't check isn't worth having.<\/p>\n\n \ud83c\udf10 Plugin home:<\/strong> www.xpay.sh\/merchants\/woocommerce\/<\/a>\n\ud83e\udd16 New to this?<\/strong> What agentic commerce actually means for a store owner<\/a><\/p>\n\n Not sure what these are? ChatGPT Ads, explained for store owners<\/a> \u2014 what they are, what they cost, and who's eligible.<\/em><\/p>\n\n Built to cooperate, not compete. If another plugin already does a job, this one stands down rather than duplicating:<\/p>\n\n Stuck on any step? Email merchants@xpay.sh or post in the support forum on this page \u2014 we aim to reply within one business day.<\/p>\n\n The plugin is GPLv2-or-later and ships as readable PHP \u2014 the complete source is in This plugin connects to the following xpay-operated services to deliver its core function. Every endpoint and its purpose is documented; full payload disclosure is in the Privacy<\/a> section.<\/p>\n\n agent-feed.xpay.sh<\/strong> \u2014 Public CDN that hosts your AI-readable catalog feed at agent-commerce.xpay.sh<\/strong> \u2014 The agent-side API that AI shopping agents call to surface and buy from your products. The plugin contacts this host at the following paths: (a) app.xpay.sh\/onboard\/woocommerce<\/strong> \u2014 The merchant-side onboarding page. When you click Connect store<\/strong>, the plugin redirects your browser here with three query-string parameters: your site URL, your administrator email address, and a one-time random nonce generated locally. No data is sent to xpay before you click the button. You sign in or sign up on xpay and grant the WooCommerce REST API permission there.<\/p><\/li>\n agent-commerce.xpay.sh\/v1\/events<\/strong> \u2014 Optional anonymous lifecycle telemetry. Disabled by default; only contacted if you explicitly opt in via the first-activation admin notice or xpay\u2726 Commerce \u2192 Settings \u2192 Privacy<\/strong>. Full payload disclosure in the Privacy section.<\/p><\/li>\n agent-commerce.xpay.sh\/v1\/merchants\/{slug}\/orders<\/strong> \u2014 Agent-attributed order reporting for connected stores (non-PII order summary + attribution source; no customer, payment, or personal data). Off via the agent-commerce.xpay.sh\/v1\/agent-analytics<\/strong> \u2014 Optional anonymous AI-bot crawl analytics. Disabled by default; shares the same opt-in as item 4 (and respects a separate audit.xpay.sh<\/strong> \u2014 Merchant-facing audit dashboard. The plugin emits a link to Your own website.<\/strong> The Tracking screen fetches your store's own home page (a request from your server to itself, never to a third party) to check whether an advertising pixel is present in the markup. Nothing is sent anywhere as a result, and the outcome is cached for several hours. This is not a third-party service and no data leaves your site.<\/p>\n\n Terms of use: install.xpay.sh\/woocommerce\/terms.html<\/a>\nPrivacy policy: install.xpay.sh\/woocommerce\/privacy.html<\/a><\/p>\n\n We never see your customers, your orders, or any payment data.<\/strong> The plugin is non-custodial by design.<\/p>\n\n Every byte, itemised: install.xpay.sh\/woocommerce\/privacy.html<\/a> \u00b7 Terms<\/a><\/p>\n\n\n No. What we add to your pages is a few lines of invisible data. Your catalog is served from our CDN, so AI shoppers reading it never touch your server at all.<\/p><\/dd>\n No \u2014 never. Payment runs through your existing gateway exactly as it does today. No buyer names, emails, addresses, cards or order contents ever reach us.<\/p><\/dd>\nllms.txt<\/code>, this update appends our agent-shopping sections at the end and leaves your content untouched. Backend-callable admin\/refresh endpoint and a smoother connect handshake round it out.<\/p>","0.3.1":"rest_url()<\/code> to respect custom REST prefixes, raw-Markdown \/llms.txt<\/code> output, i18n-wrapped readiness strings, and an expanded External Services disclosure. See Changelog for full details.<\/p>","0.3.0":"Requires Plugins<\/code> header. See Changelog for full details.<\/p>","0.2.4":"payment_handlers[]<\/code>, and override the URLs in ucp.links<\/code>. See Changelog for full details.<\/p>","0.2.1":"\/.well-known\/ucp<\/code> for capability negotiation. See Changelog for full details.<\/p>","0.1.12":"agentic-commerce-for-woocommerce<\/code>). Same product, same code \u2014 the previous name overlapped with the existing Nexi XPay plugin in the directory. See Changelog for full details.<\/p>","0.1.11":"\/?xpay_route=acp<\/code> query-arg fallback for the discovery file on hosts that intercept \/.well-known\/<\/code>. Post-activation redirect now also fires for upgrades where the store hasn't connected yet. WC HPOS compatibility declared. Privacy + terms pages live.<\/p>"},"ratings":{"1":1,"2":0,"3":0,"4":0,"5":4},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3559287,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3559287,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3633242,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3633245,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":{"xpay\/buy-in-ai-chat":{"name":"xpay\/buy-in-ai-chat","title":"Xpay Buy In Ai Chat"}},"tagged_versions":["0.3.1","0.3.2","0.3.4","0.3.5","0.3.6","0.3.7","0.4.0","0.4.3","0.4.4","0.5.0","0.5.1","0.5.3","0.6.0","0.6.1","0.6.2","0.6.3","0.7.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3633242,"resolution":"1","location":"assets","locale":"","width":1600,"height":900},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3633242,"resolution":"2","location":"assets","locale":"","width":1920,"height":1080},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3633242,"resolution":"3","location":"assets","locale":"","width":1600,"height":900},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3633242,"resolution":"4","location":"assets","locale":"","width":1600,"height":900},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3633242,"resolution":"5","location":"assets","locale":"","width":1600,"height":900},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3633242,"resolution":"6","location":"assets","locale":"","width":1600,"height":900},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3633242,"resolution":"7","location":"assets","locale":"","width":1600,"height":900},"screenshot-8.png":{"filename":"screenshot-8.png","revision":3633242,"resolution":"8","location":"assets","locale":"","width":1600,"height":900}},"screenshots":{"1":"From agent-averse to agent-ready \u2014 your score across eight weighted commerce dimensions, and the exact fix for each one that's failing.","2":"Someone is asking an AI about your products right now \u2014 live shopper visits separated from the crawls building your future visibility, and which engines found you.","3":"Your WooCommerce catalog delivered to ChatGPT in one click \u2014 validated against the current standards. No spreadsheets, no SFTP, no developer.","4":"Getting listed is easy; getting chosen is the hard part \u2014 a completeness score on every SKU, with titles and attributes written the way AI reads them.","5":"Every product, every field, every delivery checked before it reaches OpenAI \u2014 and a broken feed stopped before it gets there.","6":"Edit a product and the feed re-syncs on its own, with a full snapshot every day, so ChatGPT never has a half-updated catalog.","7":"ChatGPT Ads numbers you can actually trust \u2014 reconciled against real orders, sent server-side, with live health so you know it's firing.","8":"Can agents reach your products quickly? Your page speed against Google's targets, from Lighthouse and real Chrome user data."}},"plugin_section":[],"plugin_tags":[2353,232,216196,5418,286],"plugin_category":[45],"plugin_contributors":[265642],"plugin_business_model":[],"class_list":["post-314035","plugin","type-plugin","status-publish","hentry","plugin_tags-ai","plugin_tags-analytics","plugin_tags-chatgpt","plugin_tags-product-feed","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_contributors-xpaysh","plugin_committers-xpaysh"],"banners":{"banner":"https:\/\/ps.w.org\/agentic-commerce-for-woocommerce\/assets\/banner-772x250.png?rev=3633245","banner_2x":"https:\/\/ps.w.org\/agentic-commerce-for-woocommerce\/assets\/banner-1544x500.png?rev=3633242","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/agentic-commerce-for-woocommerce\/assets\/icon-128x128.png?rev=3559287","icon_2x":"https:\/\/ps.w.org\/agentic-commerce-for-woocommerce\/assets\/icon-256x256.png?rev=3559287","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/agentic-commerce-for-woocommerce\/assets\/screenshot-1.png?rev=3633242","caption":"From agent-averse to agent-ready \u2014 your score across eight weighted commerce dimensions, and the exact fix for each one that's failing."},{"src":"https:\/\/ps.w.org\/agentic-commerce-for-woocommerce\/assets\/screenshot-2.png?rev=3633242","caption":"Someone is asking an AI about your products right now \u2014 live shopper visits separated from the crawls building your future visibility, and which engines found you."},{"src":"https:\/\/ps.w.org\/agentic-commerce-for-woocommerce\/assets\/screenshot-3.png?rev=3633242","caption":"Your WooCommerce catalog delivered to ChatGPT in one click \u2014 validated against the current standards. No spreadsheets, no SFTP, no developer."},{"src":"https:\/\/ps.w.org\/agentic-commerce-for-woocommerce\/assets\/screenshot-4.png?rev=3633242","caption":"Getting listed is easy; getting chosen is the hard part \u2014 a completeness score on every SKU, with titles and attributes written the way AI reads them."},{"src":"https:\/\/ps.w.org\/agentic-commerce-for-woocommerce\/assets\/screenshot-5.png?rev=3633242","caption":"Every product, every field, every delivery checked before it reaches OpenAI \u2014 and a broken feed stopped before it gets there."},{"src":"https:\/\/ps.w.org\/agentic-commerce-for-woocommerce\/assets\/screenshot-6.png?rev=3633242","caption":"Edit a product and the feed re-syncs on its own, with a full snapshot every day, so ChatGPT never has a half-updated catalog."},{"src":"https:\/\/ps.w.org\/agentic-commerce-for-woocommerce\/assets\/screenshot-7.png?rev=3633242","caption":"ChatGPT Ads numbers you can actually trust \u2014 reconciled against real orders, sent server-side, with live health so you know it's firing."},{"src":"https:\/\/ps.w.org\/agentic-commerce-for-woocommerce\/assets\/screenshot-8.png?rev=3633242","caption":"Can agents reach your products quickly? Your page speed against Google's targets, from Lighthouse and real Chrome user data."}],"raw_content":"\nAI Traffic & Sales Tracking for WooCommerce \u2014 ChatGPT Ads, Product Feed & AI Visibility<\/h4>\n\n
\n
See the AI channel<\/h4>\n\n
\n
\/llms.txt<\/code> and product pages answer when requested by the AI crawlers themselves<\/em>, and what to do when one is too slow. A diagnostic \u2014 it won't fight your caching plugin.<\/li>\n<\/ul>\n\nWin the AI channel<\/h4>\n\n
\n
Product<\/code>, Offer<\/code>, AggregateOffer<\/code>, BuyAction<\/code> and ItemList<\/code> JSON-LD on product pages, shop archive and home page. Detects Yoast, Rank Math and WooCommerce core schema and fills only the gaps<\/strong> \u2014 never a duplicate.<\/li>\n\/llms.txt<\/code> (llmstxt.org<\/a>) and an explicit robots.txt<\/code> allowlist for AI user-agents. If you already publish your own \/llms.txt<\/code>, this appends to it and leaves your content untouched.<\/li>\nFAQPage<\/code> and MerchantReturnPolicy<\/code> structured data answering the delivery, returns and variant questions AI shoppers ask, for products you approve. Optionally shown to your shoppers too, as a product tab, a summary block, or an [xpay-faq]<\/code> shortcode \u2014 off on new installs<\/strong>.<\/li>\nRun ChatGPT Ads<\/h4>\n\n
\n
Works alongside what you already run<\/h4>\n\n
\n
What it doesn't do<\/h4>\n\n
\n
Five-minute install flow<\/h4>\n\n
\n
Compatibility<\/h4>\n\n
\n
Privacy and consent<\/h4>\n\n
\n
define( 'XPAY_WC_TELEMETRY', false );<\/code> in wp-config.php<\/code>.<\/li>\nMore from xpay<\/h4>\n\n
\n
Source code<\/h4>\n\n
wp-content\/plugins\/agentic-commerce-for-woocommerce\/<\/code> on your own server the moment you install it. You can read it, fork it, modify it, redistribute it and self-host it without paying anything. Full technical changelog: install.xpay.sh\/woocommerce\/CHANGELOG.md<\/a>. Questions or bug reports: merchants@xpay.sh, or the support forum on this page.<\/p>\n\nExternal services<\/h3>\n\n
\n
https:\/\/agent-feed.xpay.sh\/catalog\/{your-slug}.json<\/code>. The plugin does not contact this URL directly; the xpay backend writes it from your WooCommerce REST API after you click Connect store<\/strong>.<\/p><\/li>\nPOST \/v1\/onboard\/woocommerce\/wc-auth-callback<\/code> is the WooCommerce OAuth callback target (WordPress itself calls this on your behalf, server-to-server, after you approve the one-click connect prompt); (b) GET \/v1\/onboard\/woocommerce\/status?nonce=\u2026<\/code> is polled by the xpay onboarding page while the handshake finishes; (c) POST \/v1\/merchants\/{slug}\/resync<\/code> triggers a fresh catalog ingest after a product or stock change; (d) GET \/v1\/merchants\/{slug}<\/code> is called when xpay\u2726 Commerce \u2192 Settings<\/strong> verifies the current connection state; (e) PATCH \/v1\/merchants\/{slug}\/products\/{sku}<\/code> pushes a single-product delta when a WooCommerce product\/stock webhook fires; (f) DELETE \/v1\/merchants\/{slug}<\/code> is sent (non-blocking) when you click Disconnect<\/strong> so xpay marks your account as disconnected and archives the cached catalog. The hostname is also the publicly advertised target for POST \/mcp\/{slug}<\/code> (the JSON-RPC commerce MCP endpoint AI agents talk to) \u2014 the plugin itself does not call this URL but lists it in the \/.well-known\/ucp<\/code> manifest.<\/p><\/li>\nxpay_wc_order_events_enabled<\/code> option. Full payload disclosure in the Privacy section.<\/p><\/li>\ndefine( 'XPAY_WC_AGENT_ANALYTICS', false )<\/code> hard-off). When enabled, the plugin counts requests from known AI bots only<\/em> (e.g. GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended) \u2014 recording the bot name, a coarse page type (home\/product\/category\/discovery-file\/sitemap\/other), the HTTP status, and whether we routed the bot to your structured catalog. It also sends an aggregate daily count of human pageviews (a number only \u2014 no user-agent, no URLs, no per-visit data) as the AI-vs-human denominator. Since 0.5.3 a bot event also carries a salted, one-way hash of the connecting IP address (a bot's \u2014 behind a proxy or CDN this is the connecting edge address), so two hits from the same crawler can be counted as one visitor. The salt is unique to your store and is regenerated every day, so the hash cannot be linked across days or across stores, and the address itself is never stored or transmitted. This applies to AI bots only \u2014 a human visitor's IP is never read, hashed or sent. Events are buffered locally and sent in the background by WP-Cron, never on a page load. Cart, checkout, account, admin and REST paths are never recorded. No per-visit human data, no customer, order, or personal data.<\/p><\/li>\naudit.xpay.sh\/{your-slug}<\/code> on the Settings page so you can review the live agent-readiness score xpay computed from your catalog; the plugin itself does not fetch from this host. Opening the link from your browser sends standard browser headers to xpay.<\/p><\/li>\nauth.xpay.sh<\/code> as the authorization_servers[0]<\/code> entry in \/.well-known\/oauth-protected-resource<\/code> (an RFC 9728 metadata document AI agents fetch to learn where to obtain a token). The plugin does not contact this host server-to-server; it is referenced for agent-side discovery only.<\/li>\nPrivacy<\/h3>\n\n
\n
wp-config.php<\/code> with define( 'XPAY_WC_TELEMETRY', false );<\/code> (or XPAY_WC_AGENT_ANALYTICS<\/code> for bot counts alone). The constant overrides any UI choice.<\/li>\nFrom the WordPress.org plugin directory<\/h4>\n\n
\n
System requirements<\/h4>\n\n
\n
https:\/\/<\/code>) on the store domain \u2014 required for the agent discovery files to be honored by AI surfaces<\/li>\n<\/ul>\n\n\n\n
Will this slow down my store?<\/h3><\/dt>\n
Does xpay see my customers or their payment details?<\/h3><\/dt>\n
Will it change how my product pages look?<\/h3><\/dt>\n