Agentomise for WooCommerce

Description

Agentomise your shop. Connect your shop to AI buyers. Learn more at https://agentomise.com/.

Includes public MCP connection metadata, HTML/HTTP discovery links and a merchant-controlled registry export. Agents choose whether to discover and connect. Exporting connection metadata does not publish a registry listing.

Provides a WordPress-hosted MCP endpoint at /wp-json/wacc/v1/mcp. Customer agents can use native WooCommerce private carts, addresses, shipping rates, coupons and checkout through the store’s installed gateways. No separate Stripe keys or processor integration is added. Select Shopping enabled under WooCommerce > Agentomise.

Native purchase tools require WooCommerce 11.1+ with expected_total checkout support, PHP OpenSSL, production HTTPS and working REST loopback requests with multiple concurrent PHP workers. Agents need authorised gateway-specific tokenised payment data. Gateway scripts, authentication or redirects can still require customer action; every installed plugin/chat host is not automatically headless-compatible. No administrator credentials should be given to customer agents.

One native cart permits one checkout submission. Agentomise checks the approved quote and uses WooCommerce’s total-mismatch guard; identical retries replay an encrypted recorded result instead of invoking the gateway again. Uncertain attempts require merchant reconciliation. Paid status is read from the WooCommerce order, not inferred from a gateway success message. Checkout results may contain addresses and private gateway URLs; encrypted results expire after 30 days. No request/payment payload is retained, only a request hash. Auth salt rotation makes old results unreadable and fails closed.

A shopper page and custom agent REST API that work with WooCommerce alone. Customers and external agents can search products, select exact variants, prepare private cart snapshots and request a short-lived checkout link. The customer reviews and confirms cart replacement, then pays through normal WooCommerce checkout.

Also includes a shortcode [agent_commerce_shop], a standalone shopper page, public capabilities and a browser-handoff OpenAPI schema, exact-variant validation, private snapshot carts, revision checks, single-use handoff, merchant pause, catalogue audit and readiness diagnostics. No AI model or paid model API key is needed. External agents use MCP for native purchases, or HTTP/OpenAPI for the separate handoff flow. The plugin does not implement UCP or automatically distribute products to shopping platforms.

The shopper interface is off by default. Enable it under WooCommerce > Agentomise. Production requires HTTPS. WooCommerce AI is optional and no longer required for the built-in shopping interface. Optional upstream UCP diagnostics/guarding remain unverified against the WooCommerce AI runtime.

For the optional browser-handoff flow, shipping, tax, discounts and payment are confirmed on the normal checkout page. For native MCP purchases, WooCommerce calculates the quote and its installed gateway handles payment/order creation. Agentomise does not grant spending authority or mark orders paid itself. A customer-confirmed browser handoff replaces existing cart items and coupons; opening its link alone does not modify the cart.

Supports simple products and exact variations. Wildcard variations, custom types and product-form add-ons require normal product pages or further integration. Test your gateway, shipping, pricing and product extensions before production.

Independent project; not an official WooCommerce or Automattic product. All functionality included in this plugin is available without a licence key, subscription or paid upgrade.

Privacy and security

Snapshot carts: the plugin stores exact product IDs, quantities, state, revisions, expiry and hashed credentials. These snapshots do not store addresses or payment details. They expire after one hour; handoff links expire within ten minutes and require explicit customer confirmation.

Native checkout records: a separate plugin table stores a hashed cart identity, operation ID, request hash, state, WooCommerce order ID and encrypted checkout result for up to 30 days. Results may contain customer addresses and private gateway URLs. Request/payment bodies are not retained by Agentomise. Encryption uses WordPress authentication salts; rotating those salts makes old results unreadable. WooCommerce separately retains its normal sessions, customer and order data.

Rate limits: the plugin stores salted hashes of server-observed IP addresses and request counts, not raw IP addresses. Expired carts, rate-limit records and checkout records are removed by the hourly WordPress cron task when cron runs; physical deletion can be delayed on inactive sites.

Network communication: native MCP operations send cart credentials and relevant cart, customer and tokenised payment data to this store’s own WooCommerce Store API using server-side REST loopbacks. Running readiness checks can request this site’s domain-root /.well-known/ucp URL. These requests do not send data to Agentomise. Browser JavaScript and styles are bundled locally. No telemetry is sent to the author.

External agents and services: enabling Browse only exposes the public catalogue and connection metadata; Shopping enabled also permits private cart and checkout operations using the relevant cart credentials. Connected agents receive the responses to their requests, including private cart or checkout information when authorised by those credentials. The merchant should review the chosen agent provider’s privacy terms and customer authorisation flow. Installed payment gateways handle payment processing and may contact their own services under their own settings and policies. This plugin does not require an Agentomise account, automatically contact an AI provider, or automatically publish a registry listing. Registry publication is a separate merchant action using an external publisher.

The checkout review sets a ten-minute HttpOnly, SameSite=Lax confirmation cookie named __Host-wacc_review on HTTPS (wacc_review on isolated HTTP staging). It binds the confirmation nonce to that browser and is not used for analytics. Native MCP cart creation also has a separate ten-creations-per-minute throttle.

Cart credentials and checkout links are secrets. The plugin does not log them. Redact wacc_checkout query values in reverse-proxy/access logs and exclude the API and confirmation pages from CDN caching. HTTPS is required in production.

Diagnostics are optional, off by default, limited to 50 events/seven days and contain only fixed codes and numeric counts. Settings/readiness/staging-attestation snapshots remain local until replaced, cleared or uninstalled. Uninstall deletes this site’s Agentomise options and shopping tables, never WooCommerce products/orders. Product exclusion metadata is retained to preserve merchant policy on reinstall. Deactivation retains data but removes Agentomise shopping routes and pause controls. Existing transferred browser carts remain.

Installation

  1. Upload the plugin ZIP through Plugins > Add New Plugin > Upload Plugin.
  2. Activate on an individual site. Network activation is unsupported.
  3. Configure WooCommerce checkout, shipping and a payment gateway.
  4. Open WooCommerce > Agentomise and select an Agent shopping status.
  5. Use the shopper-page link or add [agent_commerce_shop] to a page.
  6. Configure external agents using the capabilities and OpenAPI links on the dashboard.
  7. Complete gateway-test-mode acceptance testing on isolated staging before production.

FAQ

Do I need WooCommerce AI?

No. The shopper and native MCP purchase tools work with WooCommerce alone. Optional WooCommerce AI/UCP features remain separate and require access to that upstream package.

Is this a chatbot?

No. The browser page demonstrates shopping operations. An external AI agent can use the documented HTTP/OpenAPI interface with its own intelligence.

Can an agent submit a purchase?

Yes, when the merchant enables native agent checkout and the agent supplies customer-authorised payment data accepted by the installed WooCommerce gateway. Gateway authentication/redirects may require customer action. The browser-handoff flow remains available as a separate option.

What does pause do?

It blocks private cart creation/updates and checkout handoff, and guards documented optional UCP mutations. Product reads and ordinary checkout remain available. It does not reverse payments or stop carts already transferred.

Why are there request, cart and expiry limits?

The browser-handoff API paginates products in groups of 20 and accepts snapshot carts with at most 20 unique lines and quantities of 1-99 per line. These bounds limit validation and storage work per request. Snapshot carts expire after one hour and handoff links within ten minutes to reduce stale selections and credential exposure. IP-based throttles allow ten snapshot-cart creations per minute and ninety other handoff API requests per minute; MCP dispatches have a separate ninety-request-per-minute throttle. These are fixed operational and anti-abuse controls, with no paid bypass or upgrade. Native WooCommerce carts are separate from snapshot carts and use their own validation.

Off, Browse only and Shopping enabled are merchant permission controls. Production HTTPS, compatible WooCommerce checkout and encryption support protect purchases and private records. None is a paid feature gate.

How do I move from the old plugin folder?

This release uses the agentomise-for-woocommerce folder and retains the woo-agent-commerce-companion.php entry filename. Before switching from woo-agent-commerce-companion, back up the site and deactivate the old copy. Replace the old directory through your deployment or file-management tool, then activate the new copy. Do not use WordPress Delete on the old plugin: its uninstall handler removes shared Agentomise data. Do not activate both copies together. Settings, product exclusions, private tables, shortcodes and /wp-json/wacc/v1/ API routes retain their identifiers. Deactivation/reactivation does not erase settings or tables.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Agentomise for WooCommerce” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

0.4.8

  • Removes the optional Author URI header so it no longer duplicates the plugin homepage URI.

0.4.7

  • Prepares custom SQL table identifiers with WordPress identifier placeholders while retaining atomic cart and checkout operations.
  • Uses registered WordPress assets for standalone shopping and review pages, with only plugin handles rendered.
  • Makes request validation and sanitisation explicit and documents narrowly scoped static-analysis exceptions.
  • Preserves WooCommerce extension validation and documents intentional uninstall table cleanup.
  • Tests with WordPress 7.1.4 and WooCommerce 11.3.0; avoids an empty-body PHP 8 deprecation.

0.4.6

  • Removes the public Powered by credit and the site-wide Browse only notice; status remains available in Agentomise settings.
  • Prepares the agentomise-for-woocommerce package folder and matching text domain for directory submission.
  • Declares the WooCommerce dependency and licence URL.
  • Clarifies privacy, network communication, retention, operational limits and legacy-folder migration.

0.4.5

  • Catalogue audit skips excluded products and their variations by default.
  • Adds Include excluded products, with matching totals and pagination. Auditing exclusions does not change agent access.

0.4.4

  • Adds Exclude from agentic shopping under Product data > General; parent exclusions include all variations.
  • Filters agent discovery and blocks excluded products in carts, checkout links and native checkout preflight. Normal WooCommerce remains unaffected.

0.4.3

  • Separate Setup, Readiness checks, Catalogue audit, Purchase verification and Diagnostics tabs.
  • Actions and catalogue pagination return to their relevant tabs.

0.4.2

  • Replaces enable/pause switches with Off, Browse only and Shopping enabled.
  • Existing native purchase stores retain access; paused stores remain browse-only. Legacy handoff-only stores become browse-only until the merchant explicitly enables shopping.
  • Browse-only shopper pages disable cart actions.

0.4.1

  • Introduces Agentomise branding in the plugin listing, dashboard, shopper page and MCP server identity.
  • Preserves existing installation, settings, shortcode and API identifiers for compatible upgrades.

0.4.0

  • Adds registry-format connection metadata, HTML/HTTP discovery links, merchant registry export and guidance.
  • Adds MCP 2026-07-28 server/discover, per-request metadata/header validation and modern results; preserves 2025-06-18 clients.

0.3.0

  • Added merchant-hosted MCP shopping tools and native WooCommerce cart/checkout integration using existing payment plugins.
  • Added approved-quote validation, native total guard, one-submission ledger, encrypted result replay and current WooCommerce order-state lookup.
  • Added an isolated simulated-gateway purchase test; no real payment gateway compatibility is implied by that fixture.

0.2.0

  • Added WooCommerce-only shopper page, shortcode, public catalogue/exact-variant API, private cart snapshots, revision checks, single-use confirmation handoff and OpenAPI documentation.
  • Added merchant enable/pause controls, durable expiring storage, throttling and integration tests.
  • Removed WooCommerce AI as a requirement for the customer-facing path.

0.1.0

  • Initial readiness, catalogue audit, optional UCP pause, staging checklist and diagnostics.