Agentic Commerce for WooCommerce vs Code Engine – PHP Snippets, AI Functions & Automation for WordPress

AI Traffic & Sales Tracking for WooCommerce — ChatGPT Ads, Product Feed & AI Visibility Something is already sending you customers, and your analytics can’t see it. 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. This plugin makes the AI channel visible, then makes you the answer it gives — and lets you buy more of it. Three jobs, in that order: Measure it. See which AI crawlers reach your store, which pages they read, and which of your real WooCommerce orders came from an AI assistant — broken out by ChatGPT, Claude, Perplexity, Gemini, Copilot and a dozen more, reconciled against your actual orders so you know the number is true. Win it. Publish your catalog, prices, stock and answers in the formats AI shopping assistants actually read, so you’re the store they recommend. Buy it. Run ChatGPT Ads — campaigns, budgets, creative and results — from inside WooCommerce, measured against your real orders rather than the ad platform’s own scorecard. No theme changes. No replatforming. No new payment processor. Your existing gateway and your payout schedule are untouched. We show you the match rate. 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 — because a revenue figure you can’t check isn’t worth having. 🌐 Plugin home: www.xpay.sh/merchants/woocommerce/ 🤖 New to this? What agentic commerce actually means for a store owner See the AI channel AI crawler analytics → — which assistants visit (GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, PerplexityBot, Google-Extended and more), what page types they read, whether they reached your catalog, and how that compares against your human traffic. Opt-in, off by default, known AI bots only — never your shoppers. AI-attributed orders — real WooCommerce orders traced back to the assistant that referred the buyer, with revenue split by source. Strictly non-PII: no names, emails, addresses or payment data ever leave your store. Agent-readiness audit → — a live score for how well AI shopping assistants can read, understand and recommend your catalog, with a prioritised fix list. Agent delivery speed → — AI crawlers give up on slow pages. See how fast your catalog, /llms.txt and product pages answer when requested by the AI crawlers themselves, and what to do when one is too slow. A diagnostic — it won’t fight your caching plugin. Win the AI channel An agent-readable product feed — your full catalog with live prices and stock, hosted on xpay’s CDN, so assistants reading it never touch your origin. Refreshed within ~30 seconds of any product or stock change, with an hourly safety net. AI-shopping structured data — Product, Offer, AggregateOffer, BuyAction and ItemList JSON-LD on product pages, shop archive and home page. Detects Yoast, Rank Math and WooCommerce core schema and fills only the gaps — never a duplicate. The real AI shopping standards, on your own domain — /llms.txt (llmstxt.org) and an explicit robots.txt allowlist for AI user-agents. If you already publish your own /llms.txt, this appends to it and leaves your content untouched. Cart deep-link — an assistant can hand a shopper a one-click Buy link that pre-fills your existing WooCommerce cart and lands them on your existing checkout. Product FAQs and return policy — FAQPage and MerchantReturnPolicy 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] shortcode — off on new installs. AI storefront assistant → (optional) — an on-site shopper chat that answers from your own catalog. Never appears without your explicit say-so. Run ChatGPT Ads Not sure what these are? ChatGPT Ads, explained for store owners — what they are, what they cost, and who’s eligible. Campaign management inside WooCommerce → — create, edit, budget, activate and pause ChatGPT Ads campaigns and ad groups without switching to another tab. Results land next to the orders they produced. Your numbers, not just theirs — every campaign shows the orders we reconciled against your real WooCommerce data alongside what OpenAI reports. The gap between the two is the most useful number on the screen. A ChatGPT product feed — your catalog serialised to OpenAI’s specification and delivered on a schedule, with a per-product health score so you can see exactly which listings are incomplete and fix them inline. Eligibility, up front — ChatGPT Ads requires a minimum catalog size and is currently limited to the US, Canada, Australia and New Zealand. The plugin tells you where you stand before you invest time, and points you at the organic path if ads aren’t open to you yet. Tracking that works with what you have — already running Pixel Manager, PixelYourSite or a GTM container? This verifies their pixel is firing and reconciles it, instead of asking you to rip it out and install another one. Works alongside what you already run Built to cooperate, not compete. If another plugin already does a job, this one stands down rather than duplicating: Yoast SEO / Rank Math / SEOPress — detects existing Product and FAQ schema and fills only what’s missing. AdTribes Product Feed PRO / CTX Feed / Google Listings & Ads — separate feeds for separate channels; nothing conflicts. Pixel Manager / PixelYourSite / GTM / WooCommerce core Order Attribution — attribution here is additive and non-destructive. WP Rocket / LiteSpeed / Autoptimize / SiteGround Optimizer — automatically excluded from JS optimization so nothing breaks. HPOS and Cart/Checkout Blocks — declared compatible. Storefront / Astra / Divi / Elementor and the standard page builders. 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. Activate. You’ll land on the xpay✦ Commerce dashboard. Click Connect store. You’re redirected to app.xpay.sh, where you grant a read-only WooCommerce REST API key. Your catalog goes live on AI surfaces within about 10 minutes. The built-in readiness checklist turns green as each piece confirms, and tells you in plain English what to do about anything that doesn’t. Stuck on any step? Email [email protected] or post in the support forum on this page — we aim to reply within one business day. 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 xpay✦ Commerce → Settings → 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. More from xpay Agentic commerce, explained — what changes when AI assistants, not people, do the browsing. Plugin listing and version history — feature detail, release notes and compatibility, kept current. ChatGPT Ads for store owners — eligibility, costs and what to expect before you spend anything. Source code The plugin is GPLv2-or-later and ships as readable PHP — the complete source is in wp-content/plugins/agentic-commerce-for-woocommerce/ 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. Questions or bug reports: [email protected], or the support forum on this page. External services 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 section. agent-feed.xpay.sh — Public CDN that hosts your AI-readable catalog feed at https://agent-feed.xpay.sh/catalog/{your-slug}.json. The plugin does not contact this URL directly; the xpay backend writes it from your WooCommerce REST API after you click Connect store. agent-commerce.xpay.sh — 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) POST /v1/onboard/woocommerce/wc-auth-callback 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=… is polled by the xpay onboarding page while the handshake finishes; (c) POST /v1/merchants/{slug}/resync triggers a fresh catalog ingest after a product or stock change; (d) GET /v1/merchants/{slug} is called when xpay✦ Commerce → Settings verifies the current connection state; (e) PATCH /v1/merchants/{slug}/products/{sku} pushes a single-product delta when a WooCommerce product/stock webhook fires; (f) DELETE /v1/merchants/{slug} is sent (non-blocking) when you click Disconnect so xpay marks your account as disconnected and archives the cached catalog. The hostname is also the publicly advertised target for POST /mcp/{slug} (the JSON-RPC commerce MCP endpoint AI agents talk to) — the plugin itself does not call this URL but lists it in the /.well-known/ucp manifest. app.xpay.sh/onboard/woocommerce — The merchant-side onboarding page. When you click Connect store, 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. agent-commerce.xpay.sh/v1/events — Optional anonymous lifecycle telemetry. Disabled by default; only contacted if you explicitly opt in via the first-activation admin notice or xpay✦ Commerce → Settings → Privacy. Full payload disclosure in the Privacy section. agent-commerce.xpay.sh/v1/merchants/{slug}/orders — Agent-attributed order reporting for connected stores (non-PII order summary + attribution source; no customer, payment, or personal data). Off via the xpay_wc_order_events_enabled option. Full payload disclosure in the Privacy section. agent-commerce.xpay.sh/v1/agent-analytics — Optional anonymous AI-bot crawl analytics. Disabled by default; shares the same opt-in as item 4 (and respects a separate define( 'XPAY_WC_AGENT_ANALYTICS', false ) hard-off). When enabled, the plugin counts requests from known AI bots only (e.g. GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended) — 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 — 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 — 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 — 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. audit.xpay.sh — Merchant-facing audit dashboard. The plugin emits a link to audit.xpay.sh/{your-slug} 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. auth.xpay.sh — Public OAuth-protected-resource discovery target. The plugin publishes auth.xpay.sh as the authorization_servers[0] entry in /.well-known/oauth-protected-resource (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. install.xpay.sh/woocommerce/{terms,privacy}.html — Static legal documents linked from this readme and from the Settings privacy panel. The plugin itself does not fetch these URLs; clicking the links opens them in your browser. Your own website. 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. Terms of use: install.xpay.sh/woocommerce/terms.html Privacy policy: install.xpay.sh/woocommerce/privacy.html Privacy We never see your customers, your orders, or any payment data. The plugin is non-custodial by design. Nothing leaves your site until you click Connect store. Before that, the settings page makes no outbound request of any kind. After you connect we receive: your site URL, your admin email, a one-time nonce, a WooCommerce REST API key so we can read your catalog, and your public product fields (name, description, price, stock, images, categories). No customer data. No order data. No payment data. Anonymous diagnostics are OFF by default. You’re asked once. If you turn them on, we receive plugin lifecycle events and version numbers tagged with your site URL — and, separately, counts of known AI bots only (which bot, what kind of page, the response code) plus a daily total of human pageviews as a number, so you can see your AI-vs-human split. A human visitor’s IP address is never read, hashed or sent, and cart, checkout, account and admin pages are never recorded. Turn it off any time at xpay✦ Commerce → Settings → Privacy, or hard-disable in wp-config.php with define( 'XPAY_WC_TELEMETRY', false ); (or XPAY_WC_AGENT_ANALYTICS for bot counts alone). The constant overrides any UI choice. Delete your data: email [email protected] from your admin address with your store name. Processed within 7 business days. Every byte, itemised: install.xpay.sh/woocommerce/privacy.html · Terms

Code Engine is a snippets manager that doesn’t stop at snippets. Yes, it runs your PHP and JavaScript exactly where and when you want: frontend, backend, on a schedule, or inside your content. But its real magic is what happens after you write a function: the same little piece of code instantly becomes a tool your AI chatbots can call, a step you can drag into a visual workflow, and an endpoint the outside world can trigger. One function, three superpowers. Most “code snippets” plugins stop at a textarea and a toggle. Code Engine treats your functions as first-class building blocks for the whole Meow Apps ecosystem, and for anything that can speak REST. Think out of the box, let your creativity flow, because the possibilities really are endless! ✨ For more, check the official website and come say hi on the Discord. Quick Intro Hello! ☀️ I built Code Engine because I was tired of pasting mystery snippets into functions.php and praying. I wanted a place where small bits of code are organized, safe, AI-assisted, and reusable everywhere. Here’s the idea. You write a function (or let the AI write it for you from a plain-English description). That function immediately shows up in three places: AI Engine: your chatbots and MCP clients (Claude, ChatGPT, Claude Code) can call it as a tool, with real arguments. Ask “how many orders shipped today?” and your chatbot runs your function to answer. Workflow Engine: your function appears in the step picker as its very own block. Drag it onto the canvas, wire it between an AI step and a Slack step, done. No glue code. REST / External tools: give it a secure endpoint and a token, then trigger it from Make.com, n8n, Zapier, a cron job, or a webhook. You never wrote an “integration.” You just wrote a function. Code Engine did the rest. 🤝 Core Modules 🧩 Snippets Manager Backend, Frontend, Persistent, Scheduled, Functions, and in-content (PHP/JS) snippets, all in one clean dashboard with tags, search, scope filters, and priorities. 🪄 AI-Assisted Coding Describe what you want in plain English and let AI Engine write the snippet: code, name, arguments, and scope included. Refine existing code or implement it straight from your comments. 🤖 Functions as AI Tools Every Function snippet becomes a function-calling tool and an MCP tool, so your AI Engine chatbots (and external AI agents) can actually do things on your site, not just talk. 🔀 Functions as Workflow Steps Workflow Engine surfaces each of your functions as its own draggable step. Your custom logic becomes a first-class citizen on the automation canvas. 🌐 External Access (REST) Expose any runnable snippet through a secured REST endpoint with a bearer token. Perfect for Make.com, n8n, webhooks, and scheduled external jobs. 🛡️ Safe Mode A snippet that throws a fatal error is automatically caught and disabled before it can take your site down. Code with confidence. ⏰ Scheduling Run a snippet daily at a chosen time via WP-Cron (reports, cleanups, syncs) without touching the server crontab. 🧱 Code Blocks & Shortcodes (Pro) Drop PHP or JS straight into a post or page with a Gutenberg block or the [code-engine] shortcode, with safety guards. 🧩 Snippets, the way they should be Code Engine organizes your code by scope, so each snippet runs exactly where it belongs: Persistent: runs everywhere (frontend and backend). Your everyday “add this to functions.php” code, but managed. Frontend: runs only on the public site. Backend: runs only in the admin. Function: a named, callable function with typed arguments and defaults. This is the reusable building block (see below). Scheduled: runs on a WP-Cron schedule, at the hour and minute you pick. Content (PHP / JS): runs inside a specific post or page, via a Gutenberg Code Block or the [code-engine] shortcode (Pro). Everything is searchable, taggable, sortable by priority, and importable/exportable. The CodeMirror editor gives you proper syntax highlighting and keyboard shortcuts (Cmd+S to save, Cmd+Enter to run). A nikic/php-parser pass validates your PHP before it ever runs. 🪄 Let AI write it for you Don’t feel like writing the boilerplate? Describe the snippet in plain language and Code Engine, powered by AI Engine, generates the whole thing: the code, a sensible name, a description, the right scope, and, for functions, the argument list with names, types, and defaults. Already have code? Ask the AI to modify it from a prompt, or write a few comments describing what you want and let it fill in the implementation. It’s pair programming, right inside your dashboard. ✨ The big idea: write once, use everywhere This is what makes Code Engine different. A Function snippet is not just code you call from other code. It’s a reusable capability that the rest of your stack can plug into. The moment you save it, the same function is available in three places at once: 1. As an AI tool, for chatbots and AI agents With AI Engine active, your functions are exposed through function calling and over MCP (Model Context Protocol). Your on-site chatbot can run them mid-conversation, and external AI agents (Claude, Claude Code, ChatGPT, OpenClaw) can call them too. Want a chatbot that checks stock, looks up a booking, or kicks off a process? Write the function; the chatbot gains the skill. 2. As a workflow step, for automation With Workflow Engine, every active function shows up in the Add-step picker as its own block, named after your snippet, with one input per argument. Drag it onto the canvas and wire it between other steps: an AI step that summarizes, your function that saves, a Social Engine step that posts. There’s also a generic “Execute snippet (by ID / by name)” step when you want to call one dynamically. You never write integration code; your function is the integration. 3. As a REST endpoint, for the outside world Give a snippet a custom endpoint name and a bearer token, and it’s instantly callable from anywhere: POST /wp-json/code-engine/v1/snippets-endpoint/your-endpoint Pass arguments as JSON in the body, secure it with a token, and trigger it from Make.com, n8n, Zapier, GitHub Actions, or a humble cron job. Automation without a middleware bill. 🛡️ Safe by default Running arbitrary code is powerful, so Code Engine takes safety seriously: Safe Mode catches fatal errors and auto-disables the offending snippet, so a typo never white-screens your site. REST whitelisting means global snippets only run on trusted REST routes by default, so you choose what to open up. Per-snippet tokens secure your external endpoints. Validation with a real PHP parser before code is saved. For developers who want fewer guardrails, there’s a “Bypass REST Security” option and filters (mwcode_rest_authorized, mwcode_rest_whitelist) to tailor exactly what’s allowed. Works beautifully with the Meow Apps family Code Engine is one engine in a connected set, each one useful alone, magical together: AI Engine: chatbots, content generation, and MCP. Turns your functions into AI tools. Workflow Engine: visual automation. Turns your functions into draggable steps. SEO Engine: smart, lightweight AI SEO. Social Engine: schedule and automate social posts. Why Code Engine? Reusable, not throwaway Other snippet plugins give you a place to paste code. Code Engine gives you a place to build capabilities that your AI, your workflows, and your external tools can all use. Native to WordPress Clean, fast, and built the WordPress way. No clunky external dashboards, no bloat. AI-native Write snippets with AI, expose them to AI. The whole loop lives in your wp-admin. Developer friendly REST API, MCP tools, function calling, scheduling, import/export, and plenty of filters to hook into. Cared for Part of the Meow Apps family, with regular updates and a real human behind it. 💕