Agentic Commerce for WooCommerce -- WordPress 插件

开发者	xpaysh
更新时间	2026年7月14日 22:28
PHP版本:	7.4 及以上
WordPress版本:	7.0
版权:	GPLv2 or later
版权网址:	版权信息

Your next customer is asking ChatGPT, not Google. They're shopping by typing "find me a cordless drill under $80 that ships in 2 days" into a chat box — and quietly walking away from any store the AI can't see. Right now, that's most WooCommerce stores. Agentic Commerce for WooCommerce (by xpay) makes your store visible to ChatGPT, Claude, Gemini and Perplexity in five minutes flat — no theme changes, no replatforming, no new payment processor. Your existing checkout stays exactly as it is; xpay just makes sure you're the answer the AI gives. 📘 Full setup guide with screenshots: docs.xpay.sh/merchants/woocommerce 🌐 Plugin home: www.xpay.sh/merchants/woocommerce/ 🔓 Source on GitHub: github.com/xpaysh/agentic-commerce-for-woocommerce What it does

Publishes a public, agent-readable product feed — your full catalog with live prices and stock, hosted on xpay's CDN (no extra load on your origin).
Adds AI-shopping JSON-LD — Product, Offer, AggregateOffer, BuyAction and ItemList schemas on product pages, shop archive and home page. Detects existing schema from Yoast / Rank Math / WooCommerce core and only fills the gaps.
Serves the real AI shopping standards on your own domain — /llms.txt (llmstxt.org), schema.org Product/Offer/BuyAction JSON-LD on every product page, and an explicit robots.txt allowlist for AI user-agents. Optional watchlist emitters for /.well-known/oauth-protected-resource (RFC 9728, when UCP OAuth identity linking is on) and /.well-known/agent-card.json (A2A 1.0, off by default). The discovery layer is registry-based so new standards plug in cleanly.
Allows the right bots — GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot, Perplexity-User, Google-Extended, Applebot-Extended and CCBot. Never overrides your existing robots.txt rules.
Cart deep-link — AI agents create a one-click "Buy" link that pre-fills your existing WooCommerce cart and lands the buyer on your existing checkout. Orders are tagged with _xpay_agent_attribution so you can attribute AI-driven revenue in your existing reporting.
Live inventory — webhook-driven catalog refresh on every product / stock change (debounced 30s), plus an hourly safety-net poll.
Product FAQs and return policy — for products you approve in your xpay dashboard, the plugin publishes FAQPage and MerchantReturnPolicy JSON-LD answering the commerce questions AI shoppers ask (delivery, returns, variants). Optionally it can also show those answers to your shoppers as a block on the product page — off on new installs, enabled for your store from your xpay account on request. Placement is a WooCommerce product tab, the classic product-summary hook, or an [xpay-faq] shortcode you place yourself.

What it doesn't do

It doesn't touch your checkout. Stripe / WooPayments / PayPal / Square / whatever you already use — payment runs through them, unchanged. Your payout schedule is unchanged.
It doesn't see your customers. No buyer names, emails, addresses, IPs, payment cards, order line items, refunds, or PII of any kind passes through xpay. Ever. The plugin is non-custodial.
It doesn't require a new account or contract to start. Free to install and get going — paid plans available as you grow. See pricing.
It doesn't slow down your site. The JSON-LD block is tiny and cached; the catalog feed is served from xpay's CDN, not your origin.

Five-minute install flow

Install the plugin from this directory or upload the zip. (detailed walk-through)
Activate. You'll be taken to Settings → xpay.
Click Connect store. You're redirected to app.xpay.sh, where you grant a read-only WooCommerce REST API key. (how to generate one)
Your catalog goes live on AI surfaces within about 10 minutes. The plugin's built-in audit-readiness checklist (what each row means) turns green as each piece confirms.

Stuck on any step? Troubleshooting guide. Compatibility

WooCommerce 7.0+ on WordPress 6.2+ and PHP 7.4+.
Declares compatibility with WooCommerce High-Performance Order Storage (HPOS) and Cart/Checkout Blocks.
Works alongside Yoast SEO, Rank Math, WooCommerce Blocks, WooPayments, Stripe for WooCommerce, and the standard Storefront / Astra / Divi / Elementor themes.

Privacy and consent

Anonymous lifecycle telemetry is off by default. On first activation a single admin notice asks once. Pick "No thanks" and the plugin never contacts our backend for analytics. Pick "Enable" and you can change your mind any time under Settings → xpay → Privacy. System-wide opt-out via define( 'XPAY_WC_TELEMETRY', false ); in wp-config.php.
Full data disclosure at install.xpay.sh/woocommerce/privacy.html — every byte the plugin sends, when it sends it, how to opt out, how to request deletion. Plain-English version: docs.xpay.sh/merchants/woocommerce/privacy-telemetry.

Source code and contributing The plugin source is published under GPLv2-or-later. Public repo and issue tracker: github.com/xpaysh/agentic-commerce-for-woocommerce. You can fork, modify, redistribute, and self-host without paying anything.

The full machine-readable changelog lives at install.xpay.sh/woocommerce/CHANGELOG.md (Keep-a-Changelog format). The summary below is the WP.org-required mirror. 0.6.1

Enabling the AI Storefront Assistant now works immediately on a cached store. If you run WP Rocket, LiteSpeed, WP Super Cache, W3 Total Cache, WP Fastest Cache, Cache Enabler or SiteGround, your pages were served from the cache before our code ran — so you could switch the assistant on and see nothing change, sometimes for hours, until each page's cache happened to expire. The page cache is now cleared when you turn the assistant on or off. (Cloudflare APO caches at the edge and can only be purged with your own Cloudflare credentials; those stores still wait for the edge TTL. Developers can hook xpay_wc_purge_site_cache to wire up any other stack.)
Fixed: the full-page shopper could stay a 404 after you enabled it. The page is only reconciled when someone loads wp-admin or an hourly job runs, and it refuses to publish until your account is confirmed as entitled — so if you enabled it before that confirmation landed, your own link was dead and nothing retried it. It can now be published on demand.
Your shopper page is no longer renamed behind your back. If you retitled it or changed its slug, we were silently restoring our own value every time the page was reconciled — breaking your menu link. Your edits are now left alone.
New: open a side-cart drawer from an off-site link. Stores using a side-cart plugin (such as Caddy) often retire the /cart/ page entirely, leaving any link to it a dead end. A link ending in #open-cart now opens the drawer instead. Does nothing on stores without a side cart. Developers can switch it off with add_filter( 'xpay_wc_side_cart_bridge', '__return_false' );.

0.6.0

The on-page FAQ block now has an off switch. For products you approve, xpay publishes FAQ schema that AI shoppers and search engines read. Until now it also injected a visible FAQ section into your product pages, with no way to say no — that switch now exists, managed from your xpay account. New installs start with the block off. Stores already displaying it keep displaying it (this release doesn't strip it off your live pages) and can now have it turned off. Either way the schema is unaffected: approving a FAQ publishes the answers to AI shoppers; showing them to your own shoppers is a separate decision. Developers can force it off from their own code with add_filter( 'xpay_wc_faq_visible', '__return_false' );.
The FAQ block works on page-builder themes. It can now render as a WooCommerce product tab, which Elementor and similar builders display — previously it hung off a hook those themes never call, so stores built with them saw nothing at all. There's also an [xpay-faq] shortcode if you want to place it exactly where you like. Classic themes keep the original placement.
FAQ answers show in your own language. The section heading arrives with the FAQ content instead of being hardcoded English, so a French store gets a French heading. It's now called "Additional questions" rather than "Frequently asked questions" — these answer the commerce facts (delivery, returns, variants) that your own product FAQ usually doesn't.
FAQ changes appear immediately on cached stores. If you run LiteSpeed, WP Rocket, WP Super Cache or W3 Total Cache, the cached copy of a product page was served before our code ran — so an updated FAQ stayed invisible until the cache happened to expire. Product pages are now cleared from the cache whenever their FAQ changes.
Non-returnable products no longer advertise a return window. A product marked as non-returnable was still emitting a 14-day return window in its schema, contradicting its own FAQ text. The return category, method and fees you set are now used as given.
One FAQPage per page. Where xpay can see that another plugin (Rank Math, a dedicated FAQ plugin) already publishes FAQ schema on a product page, it stands down instead of adding a competing one.

0.5.3

AI referrals are now detected even when your pages are cached. If your store runs a page cache, the cached HTML is served before our code runs — so a shopper arriving from ChatGPT looked identical to someone typing your address in. Detection now also happens in the browser and reports back to a page that is never cached, which is how WooCommerce's own order-source tracking works. Referrals from AI assistants stop silently disappearing.
Works with WP Rocket out of the box. Our referral tag no longer gets swallowed by WP Rocket's cache, and it does not create a second cached copy of the page.
A "likely AI (unconfirmed)" signal, kept honest. Some AI apps (ChatGPT's iOS app, the Atlas browser) send no clue at all — Atlas even identifies itself as ordinary Chrome, so no rule can ever spot it for certain. Where an order arrives with no referrer straight onto a deep product page, we now flag it as possible AI influence and show it separately. It is never counted as confirmed AI revenue.
Fixed: Google crawls could have been mislabelled as AI traffic. Gemini's fetcher identifies itself as exactly "Google", which is also the start of "Googlebot" — we now require an exact match, so your ordinary Google search crawling is never misreported as an AI referral.
Better AI-crawler reporting. Repeat visits from the same crawler can now be grouped into sessions, using a salted daily hash of the bot's address (never a person's, and never the address itself). Added lmarena.ai and komo.ai; removed a rule that could never match anything.

0.5.2

See the orders AI agents actually place. WooCommerce's built-in Agentic Checkout records a session ID on every order an AI agent completes through it. We now read that ID, so those orders show up in your dashboard as confirmed agent orders instead of being lumped in with everything else. This applies to new orders from now on — it can't reach back and re-label past ones.
Attribution that survives page caching. If your store runs a page cache (WP Rocket, LiteSpeed and friends), the cached HTML is served before our code gets a chance to look at where the shopper came from — so referrals from ChatGPT and other assistants were being missed. We now also read WooCommerce's own order-source data, which is recorded in the shopper's browser and isn't affected by caching.
Orders paid by bank transfer, cheque or cash on delivery are no longer skipped. Previously only orders that reached "Processing" or "Completed" were reported. Stores using offline payments, or shipping plugins with their own custom statuses (La Poste, for example), were missing roughly a fifth of their orders.
Order reporting no longer depends on a visitor arriving. Order events were queued for WordPress's scheduler, which only runs when someone next loads a page — so on a quiet store an order could sit unsent for hours, or never send. Orders now dispatch straight after checkout, and a daily catch-up re-sends anything that slipped through the past week. Only runs on stores connected to xpay.

0.5.1

Help search engines find your articles. Your blog's sitemap is now reachable on your own domain (yourstore.com/blog/sitemap.xml), and its address is added to your robots.txt automatically — so Google and other search engines discover and index your xpay articles faster. Only active when the blog feature is turned on, and it adds to your robots.txt without changing anything already there.

0.5.0

Publish your xpay articles on your own domain. Your Content Agent articles can now appear at yourstore.com/blog — on your own domain instead of a separate subdomain — so the pages build your site's authority and are more likely to be cited by AI answer engines. Off until you turn it on; only the articles xpay created for you; your own content always wins if you already have a page at that address.

0.4.4

GDPR-aware attribution defaults. EU/UK stores (30-country list: all EU + EEA IS/LI/NO + UK) ship with the 30-day _xpay_ref persistence cookie OFF by default; the WC session still carries attribution through the active shopping journey (~48h). New xpay_wc_attribution_cookie_enabled option and xpay_wc_attribution_should_set_cookie filter for CMP integrations (Cookiebot, Iubenda, Complianz, etc.).
Asynchronous agentic-order attribution. Order summaries dispatch in the background via a wp_schedule_single_event cron job that fires immediately through WP-Cron loopback, keeping the shopper's thank-you page on the critical path. An in-flight sentinel collapses concurrent completion hooks into a single dispatched job.
Resilient storefront-widget consent gate. Only successful entitlement responses are cached for an hour; transient backend failures use a 60-second breaker so a brief blip clears within a minute instead of locking the widget out for the full hour.
GTIN schema validation. Numeric identifiers continue to emit as length-keyed gtin8/gtin12/gtin13/gtin14; alphanumeric values now route to the bare gtin slot per schema.org so Google Search Console accepts the markup on every PDP.

0.4.3

AI-referred orders are now attributed and reported. When a shopper completes checkout after being referred by an AI assistant — through one of our links (sidecar, MCP, chat widget) or via a Referer / utm_source from ChatGPT, Perplexity, Claude, Gemini, Copilot, Meta AI, You.com, DeepSeek, Grok, Phind, Poe, Mistral, HuggingChat, Kagi or DuckDuckGo AI — the order surfaces in your xpay dashboard's attributed-orders feed with revenue split by source. First-touch attribution carried in a first-party cookie (30 days, no third-party tracking).
Strict no-PII contract. Only order_id, placed_at, status, amount_total, amount_discount, currency, line_count, ordered SKUs and the attribution source leave your store. Never customer email, address, phone or IP. The server-side ingest enforces an allow-list on top-level keys as defence in depth. As of 0.5.2 an attributed order may also carry: the WooCommerce Agentic Checkout session and provider ID (present only on orders an AI agent completed through WooCommerce's own agentic checkout), and WooCommerce's own order-source context — the channel type (utm/organic/referral/typein/admin), the device type, and the path of the page the shopper first landed on. The landing value is the path only: the host, query string and fragment are stripped before it leaves your store, so no tokens or personal data can ride along. Still never sent: customer email, address, phone, or IP.
No re-authorization needed. Uses existing plugin permissions only — no new WooCommerce REST scope, no new merchant grant. WordPress will not surface a "permission change" prompt on auto-update.
Includes everything from 0.4.2 (consent-gated AI Storefront Assistant, GTIN in product schema, defensive out-of-stock guard at the cart deeplink, variable-product carts, faster dashboard propagation).

0.4.2

AI Storefront Assistant is consent-gated. The chat bubble surfaces on your storefront only after you explicitly turn it on — either from the Storefront Assistant page in the xpay dashboard or from the WooCommerce settings toggle. A backend subscription or design-partner grant alone never renders the widget; you stay in control of what shows on your site.
GTIN in product schema. When your products carry a global_unique_id (WC 8.6+) or a legacy GTIN/EAN/UPC value, it's emitted in the Product JSON-LD as gtin8/gtin12/gtin13/gtin14 so Google Shopping, Bing and AI shopping agents can match each PDP to the corresponding offer in your feed.
Defensive out-of-stock guard at the cart deeplink. The cart-deeplink handler refuses lines whose target product or variation is out of stock — a guard against stale agent responses or manual deeplinks arriving after a stock-out. If every line is rejected, you still get the existing "items unavailable" response.
Variable-product carts. Agent-minted carts pass the variation attribute map through to WC()->cart->add_to_cart() so variable-product lines flow into checkout correctly. Variation SKUs supplied without a separate variation id are resolved automatically.
Faster propagation. Toggle and appearance changes from the xpay dashboard take effect on your storefront within seconds.

0.4.1

New: Content Engine pages. When your store is subscribed to the Content Engine add-on, xpay can publish answer-first comparison, buying-guide and listicle pages — tuned to the questions AI assistants ask — as real Pages on your own domain (indexable, in your sitemap, human-visible, and discoverable by AI agents). Pages stay in sync automatically: published while subscribed, reverted to draft if you unsubscribe, and we only ever touch pages we created — your own content is never modified. Off by default; nothing publishes unless the add-on is active for your store.

0.3.7

Maintenance and reliability polish.
Optional agency/referral attribution: a store set up by a partner can carry that partner's referral code — captured automatically from a referral link, entered on the Connect screen, or pinned by the installer. Counts only — no product, customer or order data is shared.

0.3.5

New: /agents.md agent skill. A dedicated, machine-readable skill served at yourstore.com/agents.md that tells AI shopping agents (and skill-using assistants) exactly how to connect to your store: browse the live catalog over MCP or REST, look products up, and build a cart that hands the shopper off to your existing checkout. Purpose-written connect-and-transact instructions — not a copy of /llms.txt. Served once your store is connected; like our other discovery files it steps aside quietly if you already publish your own /agents.md.
Hardened /llms.txt merge. When appending to an existing /llms.txt, the plugin ignores non-text responses. Hybrid/headless storefronts and single-page themes that answer every URL with an HTML page have that page rejected instead of pulled in above our agent-shopping sections.
Branded catalog link. The /llms.txt catalog link now points at your store's own agent-commerce surface instead of the shared feed host (same data, your brand).
Optional AI shopping-bot routing. Realtime AI shopping assistants can be transparently routed to your structured catalog surface for cleaner, faster product data, while search/indexing crawlers stay on your store for citations. Centrally controlled and off by default — nothing changes for your site until xpay enables it for your store; never affects humans, logged-in users, your cart, or checkout.

0.3.4

Outcome-first Connect screen. The pre-connect panel leads with what you get — your products discoverable to ChatGPT, Claude, Gemini and Perplexity, with no code and no payment change — and demotes the protocol acronyms (llms.txt, schema.org, ACP/UCP/AP2/MCP) to a small footnote for technical reviewers.
Upfront safety promise. The Connect screen now states plainly what this update verified end-to-end: the plugin writes zero files to your site, doesn't touch your theme or payments, appends to any existing /llms.txt rather than replacing it, and fully reverts the moment you deactivate.
New transparency panel. Once connected, the General tab lists every external service the plugin contacts (agent-feed.xpay.sh, agent-commerce.xpay.sh, app.xpay.sh) and what each receives, alongside the Terms and Privacy links.
Value-first telemetry opt-in. The anonymous-diagnostics prompt explains the benefit to you — we can flag a silently broken AI connection (failed sync, blocked endpoint) before your products drop out of ChatGPT, Claude and Perplexity. Still off by default, still no customer or order data, still changeable any time.

0.3.3

New: Run site diagnostics (Tools tab). One click loopback-checks the three layers that gate connection at the web server before WordPress runs: the WordPress REST API (Pretty Permalinks), the plugin's own REST routes, and the /.well-known/ discovery files. Each row shows pass/fail with the HTTP status, and any failure renders the exact next step — switch Permalinks off "Plain", or (on Apache/ACME hosts that reserve /.well-known/) the query-arg fallback URL that agents can still use.
No behaviour change to the connect flow itself. Diagnostics are network-only on the explicit button click; the Settings page still makes zero outbound calls on render.

0.3.2

Good neighbour with other AI/SEO plugins. If your site already publishes its own llms.txt (e.g. via Yoast SEO AI, RankMath AI, AIOSEO, or your own setup), the plugin appends our agent-shopping sections at the end of your file. Everything you wrote is preserved exactly as you wrote it; /.well-known/* JSON emitters defer to existing handlers cleanly.
Automatic detection. A daily WP-Cron probe (and a 6-hour transient cache) detects when another tool is publishing one of the same discovery files we do. When it sees one, we step aside or append cleanly — no merchant action needed.
Smoother connect experience. A handful of polish items in the Connect flow so the handshake is quicker and an idempotent retry resolves silently.
Backend-callable admin/refresh endpoint. Once you're connected, xpay can flush local discovery caches and fine-tune small parts of your discovery setup without a plugin update. Constant-time site-token auth, local-only actions (no outbound HTTP triggered by the endpoint), forward-compatible action vocabulary.

0.3.1

REST endpoints constructed via rest_url(). The fallback UCP manifest now calls rest_url('xpay/ucp/v1') / rest_url('xpay/mcp') instead of hardcoding home_url('/wp-json/...'), so the plugin respects sites that customize the REST prefix. Per the WP.org Determining Locations guideline.
Tested against WordPress 7.0 + WooCommerce 10.8.1 on a clean sandbox with WP_DEBUG=true.

0.3.0

Privacy: no outbound calls on Settings page load. The Connect panel no longer pre-registers a nonce with the xpay backend when the page renders. The nonce is generated, the attempt is stamped, and the merchant is redirected to the xpay onboarding flow only after the Connect store button is clicked. Matches WordPress.org's no-phoning-home guideline.
Requires Plugins: woocommerce header. Declares the WooCommerce dependency via the WP 6.5 plugin-dependencies mechanism so the plugin won't activate without WooCommerce present. Existing manual activation check remains as defence-in-depth for pre-6.5 sites.
Inline admin script removed. The Connect button no longer emits an inline <script> tag; click-time telemetry is recorded server-side in the redirect handler instead.

0.2.4

Tabbed Settings → xpay UI. Five tabs replace the single-screen layout: General (status + slug + last sync + disconnect + telemetry opt-in), Capabilities (per-UCP-capability toggles), Payments (map enabled WC gateways to UCP payment_handlers[]), Links (auto-detect privacy/TOS/about/contact/shipping with per-row override), Tools (view UCP profile, view full audit, test connection, refresh catalog now, telemetry debug log toggle). URL is bookmarkable via ?tab=.
Capability toggles wired into /.well-known/ucp. Switching off any of checkout / fulfillment / discount / order removes the entry from the emitted UCP manifest. Default (no option set) = all enabled, so existing installs don't regress on upgrade.
payment_handlers[] now populated from the Payments tab. Each enabled gateway emits as {id, label, type:"merchant_gateway"} so UCP-aware agents can negotiate payment surfaces against the methods you actually accept.
ucp.links array. Privacy, TOS, About, Contact, Shipping URLs are auto-detected (WordPress privacy_policy_url + common page slugs) and overridable on the Links tab; emitted in the manifest as {rel, href} pairs.

0.2.3

MCP transport advertised in /.well-known/ucp. Native MCP-speaking agents (Claude, ChatGPT Operator, Shopify AI Toolkit) discover the endpoint at agent-commerce.xpay.sh/mcp/{slug} without further configuration. Three tools available: search_catalog (BM25-ranked over title + description), get_product (lookup by SKU or numeric product ID), create_cart (returns a signed deeplink that pre-populates checkout on your store).
One-click connect via WooCommerce's /wc-auth/v1/authorize OAuth. When you click Connect store, the xpay onboarding page opens WooCommerce's built-in approval popup. You approve there once and WordPress hands xpay read-only API credentials directly — no Settings → Advanced → REST API trip, no copy-paste. The manual paste flow remains available as a fallback.
Disconnect notifies the backend. Clicking Disconnect now fires a non-blocking DELETE /v1/merchants/{slug} so your account is marked disconnected and the cached agent-feed catalog is archived. Local cleanup happens regardless of whether the backend acks.
UCP manifest aligned with the 2026-04-08 spec. extends emitted as an array (["dev.ucp.shopping.checkout"]); capability spec URLs uniformly date-prefixed; payment_handlers: [] placeholder added for parity with the rest of the ecosystem.
Recovery guidance on incomplete Connect attempts. If you start a Connect flow but the handshake doesn't complete, the Settings → xpay page surfaces a clear "click Connect again" CTA and our ops team is notified automatically so we can assist.

0.2.2

Idempotent onboarding handshake. Plugin-side rest_finalize is idempotent on (slug, api_key) replay, so a re-click of Connect store is always safe within the nonce TTL. Initial catalog resync moved to wp_schedule_single_event + non-blocking wp_remote_post so the REST response returns in under a second on hosts whose outbound HTTPS to xpay is slow. Paired with a backend change that delivers credentials before consuming the nonce and surfaces a clear actionable error if the WP site is unreachable.

0.2.1

/llms.txt ## Commerce protocols section is now gated on the xpay_wc_protocol_endpoints wp_option (backend-pushed during Connect). Agents that follow a URL from /llms.txt reach a working service or a structured 501 — never a bare 404.
Companion: backend stubs at agent-commerce.xpay.sh/{ucp,acp,ap2,mcp}/... now return a 501 Not Implemented envelope with protocol, spec, merchant_slug, status, retry_after_seconds, and a docs link.
Filter xpay_wc_protocol_endpoints lets a mu-plugin override.

0.2.0

Aligned with the open commerce standards. Per-protocol surfaces (ACP, UCP, AP2, MCP) are now advertised in /llms.txt and hosted on xpay infrastructure. The plugin keeps the merchant's domain to what genuinely belongs there: discovery files, JSON-LD, robots.txt allowlist.
NEW: /.well-known/ucp (UCP business profile, spec 2026-04-08). This is the file Google, Shopify, Etsy, Wayfair, Target and Walmart fetch to negotiate capabilities with your store. The plugin generates a sensible default profile pointing at xpay-hosted UCP service endpoints; commercial-tier merchants can override the body + inject JWK signing keys via the xpay_wc_ucp_profile and xpay_wc_ucp_signing_keys options.
Discovery layer is an extensible emitter registry. Each standard (/llms.txt, /.well-known/ucp, RFC 9728 OAuth metadata, A2A agent-card) is a registered emitter with a default-on/default-off flag and per-merchant override. Adding a new standard means adding a new emitter — no changes elsewhere in the plugin.
Added watchlist emitters (off by default):
/.well-known/oauth-protected-resource (RFC 9728) — turns on automatically when UCP OAuth Identity Linking is enabled for the merchant on the xpay side.
/.well-known/agent-card.json (A2A 1.0, IANA-registered 2025-08-01) — opt-in via the xpay_wc_emit_agent_card option once A2A adoption matures in commerce.
/llms.txt content refresh. Now links the agent-readable catalog, the per-protocol endpoints (ACP / UCP / AP2 / MCP), the cart-deeplink template, and top product categories. Markdown structure follows the llmstxt.org convention.
Admin readiness checklist updated to reflect the standards-based architecture — the "AI assistants know where to send a buyer" row now points at the per-protocol endpoints listed in /llms.txt, not at a single discovery file.
No breaking changes for merchants. Cart deeplink, catalog feed, JSON-LD injection, robots.txt allowlist, telemetry pipe and the WC REST onboarding flow are unchanged. The audit-readiness pills continue to all turn green after Connect.

0.1.12

Plugin renamed to "Agentic Commerce for WooCommerce" (slug agentic-commerce-for-woocommerce).
Why: the previous name "xpay for WooCommerce" was rejected at WordPress.org submission as too similar to Nexi XPay (an established Italian payment-gateway plugin for WC by Nexi Payments, ~6,000 installs since 2017). WordPress.org's similarity check matches on the brand string regardless of category, and Nexi has prior art.
What changed: Plugin Name header, Text Domain (agentic-commerce-for-woocommerce), main file name (agentic-commerce-for-woocommerce.php), /languages/agentic-commerce-for-woocommerce.pot, admin page slug, plugin folder name inside the zip. User-Agent header for outbound HTTP. Settings page H1.
What didn't change: the product, the architecture, the xpay brand identity (still the author + still in admin nav as "xpay"), backend services (agent-feed.xpay.sh, agent-commerce.xpay.sh, etc.), or anything else functional.

0.1.11

Cleared 4 PCP PrefixAllGlobals warnings:
uninstall.php now runs in an anonymous-closure IIFE — no top-level $option_keys / $key globals.
class-xpay-schema.php :: render_product() uses a local $xpay_product and skips the global $product declaration entirely. Direct wc_get_product(get_the_ID()) works on PDPs without WC's template-loop side effect.
class-xpay-plugin.php :: woocommerce_active() uses raw get_option('active_plugins') + multisite merge + class_exists('WooCommerce') instead of filtering WP core's active_plugins hook. Same behavior, no false-positive.

0.1.10

Tested up to WordPress 6.9 (PCP flagged 6.7 as below current). No code changes — verified compatibility on a real WC 9.x install.
Short description trimmed to 141 chars (PCP cap is 150).
Removed load_plugin_textdomain() call. Discouraged since WP 4.6 — WordPress.org-hosted plugins get translations loaded automatically by core via the plugin slug.
Excluded non-canonical markdown files (INSTAWP_TEST_WALKTHROUGH.md, README.md) from the release zip. The plugin zip should only contain files needed at runtime; READMEs and walkthroughs are repo-only.

0.1.9

Documentation URLs migrated docs.xpay.sh/products/woocommerce/* → docs.xpay.sh/merchants/woocommerce/*. Merchants is the bucket; WooCommerce is one (of many future) integrations inside it. Future Shopify / BigCommerce docs will live as siblings.
No plugin functionality changed — readme + admin-UI links updated.

0.1.8

Punchier Description hero — leads with the buyer-side framing ("Your next customer is asking ChatGPT, not Google") instead of an abstract claim.
Pricing link updated everywhere to https://www.xpay.sh/pricing/?tab=agentic-commerce.
New documentation site at docs.xpay.sh/merchants/woocommerce — multi-page walkthrough covering install, WC REST API key generation, connect flow, privacy & telemetry, audit readiness checklist, and a troubleshooting guide. readme backlinks the docs at the right moments.
GitHub backlinks throughout the readme + FAQ (issue tracker, source browse).

0.1.7

xpaysh/xpay-for-woocommerce GitHub repo flipped public. Restored repo link references in readme.txt FAQ and "Source code" section so reviewers and merchants can browse the unminified source directly. GPLv2-or-later unchanged.

0.1.6

Removed GitHub repo link references from readme.txt to avoid a broken-link impression for reviewers (the source repo was private). Plugin is still GPLv2-or-later — the zip is the canonical, unminified source.

0.1.5

Query-arg fallback for the discovery file: hosts that intercept /.well-known/ (some shared hosts, CDN edges, ACME setups) can now serve the discovery file at /?xpay_route=acp. Discoverable via the Link header on the home page.
Post-activation redirect to Settings → xpay now fires on any activation when the store hasn't connected yet, not only on the very first activation. Skipped on bulk-activate.

0.1.4

WC HPOS + Cart/Checkout Blocks compatibility declared.
First-activation redirect to Settings → xpay.
Privacy + Terms pages at install.xpay.sh/woocommerce/{privacy,terms}.html.
Plugin URI: xpay.sh/sellers/woocommerce → www.xpay.sh/merchants/woocommerce/.

0.1.3

PHPCS WordPress-standard clean: 0 errors / 1 cosmetic warning.
phpcs.xml.dist ruleset added.
languages/xpay-for-woocommerce.pot generated.
WP.org listing assets (banner / icon / 5 screenshots).

0.1.2

Slug renamed xpay-woocommerce → xpay-for-woocommerce (Guideline 17).
Telemetry now opt-in via first-activation admin notice; default OFF (Guideline 7).
Settings → xpay → Privacy toggle.
readme.txt External services and Privacy sections added.

0.1.1

Fire-and-forget lifecycle telemetry pipe (was always-opt-out; reworked to opt-in in 0.1.2).

0.1.0

Initial release. WP plugin scaffold; /llms.txt and /.well-known/agentic-commerce.json; JSON-LD on PDP / shop / home; robots.txt allowlist; cart-deeplink handler; webhook-driven resync; admin page with connect flow and audit-readiness checklist.

Agentic Commerce for WooCommerce

标签

下载

详情介绍:

安装:

屏幕截图:

升级注意事项:

常见问题:

更新日志: