Store coverage
Start with the store question
The plugin exposes 79 canonical abilities across the WooCommerce records, reports, and settings an AI client needs to return a concrete result.
Catalog maintenance
Use 28 product, variation, taxonomy, metadata, and stock abilities to query products and variations, create, update, or delete them, manage categories, tags, attributes, and terms, query and update product metadata, duplicate a product, and bulk update stock when the intended correction is clear.
Orders
Use 9 order abilities covering orders, line items, notes, refunds, status, and transactional email. Query or create orders, update status and line items, inspect notes and refunds, create refunds, delete orders, and resend transactional email when needed.
Coupons
Use 4 coupon abilities to query a coupon before creating, updating, or deleting it, keeping a promotion change tied to the record it affects.
Customer profiles
Use 4 customer abilities to query, create, update, or delete customer records while WooCommerce remains the owner of the store data.
Reports
Use 4 currency-specific sales, product, customer, and stock report abilities to get a bounded view for a catalog, fulfillment, or customer decision.
Inspect the operating surface
Use 15 store and operational settings abilities for settings, tax, shipping, payments, webhooks, email, and system status. Query the current configuration, inspect system status, and run only explicitly allowlisted system tools; create, update, or delete webhooks when authorized.
Apply a named configuration change
Use 11 store infrastructure mutation abilities for tax, shipping, payment, and related store configuration. Update store settings; save or delete tax rates, shipping zones, and shipping classes; add, update, or delete shipping methods; and update payment gateways after inspection identifies a specific change.
Product reviews
Use 4 product review abilities to inspect customer feedback, publish a review, revise its text, or remove it when moderation calls for action.
Operation boundaries
Keep the decision inside WooCommerce controls
The result is useful because the data owner, authorization boundary, workload, and protected surfaces remain visible.
WooCommerce owns the records
Operations use WooCommerce CRUD and query APIs, including support for high performance order storage. WooCommerce remains the owner of store data.
Confirm before impact
Authorization is object-specific. High-impact operations require explicit confirmation before a consequential change is committed, so you can inspect the proposed result first.
Failures stay legible
Collection and report workloads are bounded, and failures are normalized before schema validation.
Public destinations
Persistent outbound URLs must use public HTTPS hosts, and webhook secrets are never returned. External actions can be reviewed without exposing a secret through the result.
WordPress still guards protected surfaces
Protected product metadata and system tools remain denied unless WordPress filters explicitly allowlist them. The interface does not bypass the store’s existing control point.
Dependencies
Check the runtime before the first store result
These source-owned dependencies must be present for the registered operations to run.
WordPress 6.9 or newer
WordPress Abilities APIRegisters the WooCommerce operations through the WordPress runtime.
PHP 8.0 or newer
PHP 8.0 or newerProvides the required server runtime.
Required plugin
WooCommerceOwns the products, orders, customers, reports, settings, and store data controlled by this add-on.
Stable package
Download the package for a concrete evaluation
Download the stable plugin ZIP to obtain the exact package for your next evaluation. That gives you a concrete starting point for testing whether your AI client can reach the WooCommerce records, reports, and settings your work depends on.