=== Agentomise for WooCommerce === Contributors: agentomise Tags: woocommerce, agentic-commerce, shopping, checkout Requires at least: 6.6 Tested up to: 7.1 Requires PHP: 7.4 Stable tag: 0.4.8 License: GPL-2.0-or-later License URI: https://www.gnu.org/licenses/gpl-2.0.html Customer agent purchases through native WooCommerce carts, checkout and installed payment gateways. == Description == **Let AI shoppers discover products and build carts in your WooCommerce store.** With Agentomise, they can check out through a compatible gateway or send the customer a link to finish checkout themselves. * **Native checkout via MCP.** Authorised agents can build private carts, get shipping rates, apply coupons and check out through a compatible gateway you already use. Some gateways may require customer interaction. * **Customer checkout via a link.** Shoppers and agents can find products, select exact variations and prepare a cart. The customer reviews and confirms the cart before completing payment in your regular WooCommerce checkout. * **Merchant controls.** Shopping is off by default. Enable or pause it under **WooCommerce → Agentomise**. The plugin includes a shopper page, a shortcode and readiness checks. Agentomise supports simple products and exact variations. Native MCP checkout requires WooCommerce 11.1+ and a compatible gateway. No AI model API key, licence key or subscription is required. [Learn more at agentomise.com](https://agentomise.com/) == 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. [Store administrator guide](https://agentomise.com/store-administrator-guide/) == Privacy and security == * **Private carts and checkout links.** Cart snapshots store product selections, quantities, cart state and hashed credentials, without addresses or payment details. Snapshots expire after one hour. Handoff links expire within ten minutes and require customer confirmation. A short-lived browser cookie secures that confirmation and serves no analytics purpose. * **Native checkout records.** Agentomise retains checkout identifiers, a request hash, the WooCommerce order ID, checkout state and an encrypted result for up to 30 days. The result may include customer addresses and private gateway URLs. Agentomise does not retain checkout request or payment bodies. WooCommerce retains its regular session, customer and order data. * **Agent and gateway access.** Browse only exposes the public catalogue and connection metadata. Shopping enabled lets agents with the relevant credentials access private cart and checkout information. Merchants should review their agent provider's privacy terms and customer authorisation process. Installed gateways process payments under their own settings and policies. * **Telemetry and diagnostics.** Agentomise sends no telemetry to the author and requires no Agentomise account. It does not automatically contact an AI provider or publish a registry listing. Rate limiting uses salted IP hashes and request counts. Optional diagnostics are off by default and store only fixed codes and counts. * **Deactivation and uninstall.** Deactivation removes Agentomise routes and pause controls while retaining data and any carts already transferred to WooCommerce. Uninstall removes Agentomise options and shopping tables. WooCommerce products, orders and Agentomise product exclusions are retained. == Frequently Asked Questions == = 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. == 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.