An agent can list, create, update, and delete WooCommerce products, and list orders, add order notes, or change an order's status, all through the same REST layer as the wc/v3 API.
Moksa for WooCommerce abilities, governed through the Bridge
An agent can look up WooCommerce orders, customers, payment status, shipping and e-invoice settings, and revenue stats, and change order status, create or delete shipments, switch payment, shipping and invoice options on or off, and issue or void e-invoices.
- Abilities
- 3215 read2 write15 destructive
- Active installs
- 10+
- Rating
- 100% (1 rating)
- Version checked
- 1.21.0
- Requires
- WP 7.0+, PHP 8.2+
- Last updated
- 2026-11-07
- Abilities verified
- 10 November 2026
- Installs and rating as of
- 10 November 2026
View Moksa for WooCommerce on WordPress.org
What has to be true first
Needs WordPress 7.0 or later (the plugin's own minimum; the Abilities API itself needs 6.9), plus PHP 8.2 or later and the plugin active. The abilities check these capabilities: edit_shop_orders, manage_woocommerce.
A note on the count below
Counted from the plugin code on 10 November 2026; settings or feature flags that the count does not evaluate may hide some of these abilities.
The 32 Moksa for WooCommerce abilities
Grouped by what each one can change. Every one starts off until you enable it.
Destructive also covers abilities the plugin does not declare read-only: the Bridge treats a missing annotation as destructive until the owner reviews it, so some of them may only look things up.
Read 15
- Read
Find an order by number
Look up matching WooCommerce orders by e-invoice number, tracking number or payment transaction ID, and return the order number, customer, status and admin link. Pass an order number (such as 2855) to check that order directly. Read-only.
- Read
Get order details
Get the full details of a single order: status, customer, items, totals, payment method, shipping method, pickup store, plus the e-invoice number and whether it has been issued, the tracking number and the payment transaction ID. Use it to answer questions such as “has the invoice been issued”, “what is the tracking number” or “which store is it going to”. Accepts an order number or any of those numbers. Read-only.
- Read
Count orders by status
Return order counts: either the number of orders in every status, or the count for one status. Common status slugs: processing, pending, on-hold, completed, cancelled, refunded. Use all (or omit status) to get the breakdown across every status. For an actual list of orders use list-orders instead; to find one customer's orders use find-customer-orders. Read-only.
- Read
Find a customer's orders
Look up every order belonging to a customer by email address, phone number or name, and return the list along with the total amount paid. Read-only.
- Read
Revenue and order statistics
Order count, paid revenue, status breakdown and average order value for a period. The period is optional and defaults to this_month: today, yesterday, this_month, last_month, this_year or custom. With custom, also pass date_from and date_to in YYYY-MM-DD format. Read-only.
- Read
List shipping zones and methods
List every shipping method in the WooCommerce shipping zones, such as 7-ELEVEN pickup or T-Cat ambient and frozen delivery, along with whether each is enabled. Use it to confirm a method name before switching it. No parameters. Read-only.
- Read
Check payment status
Check the payment status of an order: payment method, whether it is paid, transaction ID, last four card digits, ATM virtual account and convenience store payment code. NewebPay orders are also queried live against NewebPay. Read-only.
- Read
Summarize plugin settings
Summarize the current non-sensitive settings: which payment, shipping and e-invoice channels are enabled, whether each module is in test or production mode, when invoices are issued, which fields order number lookup searches, and whether the AI assistant is on. No credentials are included. No parameters. Read-only.
- Read
Get tracking links
Get the shipment tracking links for an order: each carrier's public tracking page plus the tracking number. Read-only.
- Read
List invoice issuing options
List the issuing options an e-invoice service (ECPay, ezPay, SmilePay, PayNow or Amego) supports, member carrier, mobile barcode, Citizen Digital Certificate, paper, donation and tax ID, along with whether each is enabled. Read-only.
- Read
List payment methods
List every individual payment method offered by a payment service (ECPay, NewebPay, PAYUNi, SmilePay, PayNow or PChomePay) and whether each is enabled. Use it to confirm what is available before switching anything. Read-only.
- Read
Advanced order list
Return an actual list of orders, filtered by status, date range (date_from and date_to in YYYY-MM-DD format) and payment method. The list is compact and returns 20 orders by default, up to a maximum of 50. If you only need counts per status, use query-orders instead. Read-only.
- Read
List payment, shipping and e-invoice channels
List the payment, shipping and e-invoice channels with their slugs and whether each is enabled. Use all for everything, or filter with payment, shipping or invoice. Read-only.
- Read
Look the payment up at the provider
Ask the payment provider directly what happened to the transaction on an order, whether it was authorised, how much was captured and when. Use this when the order and the provider might disagree, for example when a customer says they paid but the order still shows unpaid. Works for ECPay card payments and PAYUNi. For what this site already recorded, use get-payment-status instead, which does not call the provider. Read-only.
- Read
List the shipments on an order
List the shipments already created for an order, with their shipment numbers, tracking numbers and when they were created. Use this before deleting a shipment so you know which number to give.
Write 2
- Write
Add an order note
Add an internal note to an order. It is for your own records and is not sent to the customer.
- Write
Print shipping labels
Print shipping labels for one or more orders, grouped automatically by carrier. Calling the tool only proposes it; the print page opens once the user presses Confirm. An order needs an existing shipment before it has a label to print.
Destructive 15
- Destructive
Change order status
Move an order to a new status such as processing, completed or cancelled. This is a destructive action, calling the tool only proposes the change, and nothing happens until the user presses Confirm, so there is no need to ask for confirmation yourself.
- Destructive
Create shipments in bulk
Create shipments for several orders at once and get their tracking numbers, choosing the carrier automatically from each order's shipping method. This is destructive and cannot be undone, calling the tool only proposes it, and nothing is created until the user presses Confirm, so there is no need to ask for confirmation yourself.
- Destructive
Enable or disable a shipping method
Enable or disable one shipping method in a WooCommerce shipping zone, for example “SmilePay T-Cat ambient” or “ECPay 7-ELEVEN pickup”. Pass the method name directly. This is a destructive action because it changes what customers can choose at checkout, calling the tool only proposes it, and nothing takes effect until the user presses Confirm, so there is no need to ask for confirmation yourself.
- Destructive
Resend the payment details email
Resend the payment details email, such as the ATM virtual account or convenience store payment code, to the customer. Only orders that have those details can be sent; card orders have none. This is a destructive action because it emails the customer, calling the tool only proposes it, and nothing is sent until the user presses Confirm, so there is no need to ask for confirmation yourself.
- Destructive
Enable or disable invoice issuing options
Enable or disable one or more issuing options for an e-invoice service: member carrier, mobile barcode, Citizen Digital Certificate, paper, donation or tax ID. Pass the option names directly. This is a destructive action, calling the tool only proposes it, and nothing takes effect until the user presses Confirm, so there is no need to ask for confirmation yourself.
- Destructive
Enable or disable payment methods
Enable or disable one or more individual payment methods within a payment service, such as ECPay's one-off credit card payment, Apple Pay or ATM. Pass the method names directly. This is a destructive action, calling the tool only proposes it, and nothing takes effect until the user presses Confirm, so there is no need to ask for confirmation yourself.
- Destructive
Issue an invoice allowance
Issue an allowance against an order's existing e-invoice, used for partial refunds. An amount is required. Only ECPay, ezPay and Amego support this. It is destructive and cannot be undone, calling the tool only proposes it, and nothing is issued until the user presses Confirm, so there is no need to ask for confirmation yourself.
- Destructive
Enable or disable a channel
Enable or disable a payment, shipping or e-invoice channel. Pass the channel name (such as “SmilePay shipping”) or its slug directly; there is no need to list them first. This is a destructive action, because disabling a channel changes what customers can choose at checkout and enabling one without credentials causes errors on the storefront, calling the tool only proposes it, and nothing takes effect until the user presses Confirm, so there is no need to ask for confirmation yourself. It does not touch credentials or the test and production switch.
- Destructive
Add an invoice donation charity
Add a charity, with its name and love code, to the donation list of the enabled e-invoice module so customers can choose it at checkout. A love code is 3 to 7 digits. Calling the tool only proposes it, and nothing is saved until the user presses Confirm, so there is no need to ask for confirmation yourself.
- Destructive
Create a shipment
Create a shipment with the carrier for an order and get its tracking number, choosing the carrier automatically from the order's shipping method. This is destructive and cannot be undone, because it places a real booking with the carrier, calling the tool only proposes it, and nothing is created until the user presses Confirm, so there is no need to ask for confirmation yourself. A label can only be printed once the shipment exists.
- Destructive
Delete a shipment from an order
Remove a shipment record from an order so the shipment can be created again, for example after the pickup store was changed. This only removes the record on this site; it does not cancel the booking with the carrier, so never use it for a parcel that is already on its way. This is a destructive action, calling the tool only proposes it, and nothing is deleted until the user presses Confirm, so there is no need to ask for confirmation yourself. If the order has more than one shipment you must say which shipment number to delete.
- Destructive
Change the pickup store
Change which convenience store an order is picked up at, by store number. Use this when a customer asks to collect the parcel somewhere else. This is a destructive action, calling the tool only proposes the change, and nothing happens until the user presses Confirm, so there is no need to ask for confirmation yourself. It does not re-book the shipment: if a shipment was already created it still points at the old store and has to be deleted and created again on the order screen. If the store name and address are not given they are cleared, because keeping the old ones would show the new number next to the old store name.
- Destructive
Issue an e-invoice
Issue an e-invoice for an order, using the invoice service and invoice type already set on it. This is a destructive tax operation that cannot be undone, calling the tool only proposes it, and nothing is issued until the user presses Confirm, so there is no need to ask for confirmation yourself.
- Destructive
Void an e-invoice
Void the e-invoice already issued for an order. A reason is required. This is a destructive tax operation that cannot be undone, calling the tool only proposes it, and nothing is voided until the user presses Confirm, so there is no need to ask for confirmation yourself.
- Destructive
Change order status in bulk
Move several orders to the same new status at once, such as processing, completed or cancelled. This is a destructive action, calling the tool only proposes the change, and nothing happens until the user presses Confirm, so there is no need to ask for confirmation yourself. Use this whenever the user mentions two or more orders together.
No abilities match that search.
How to switch these on
Four steps from two active plugins to a governed connection.
Install Moksa for WooCommerce and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. Moksa for WooCommerce registers its own abilities; this plugin discovers and governs them.
Open the Plugins’ own tools screen
In Agent Abilities for MCP, open the Bridge tab (labeled "Plugins’ own tools" in the admin, "Other plugins" before 1.12.0). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Enable one ability at a time
Every ability from Moksa for WooCommerce starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Connect as a least-privilege user
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Frequently asked questions
Does Moksa for WooCommerce work with the Bridge?
Yes. Moksa for WooCommerce calls wp_register_ability() for 32 abilities in its current code on wordpress.org, so the Bridge can discover them once the plugin is active.
Do Moksa for WooCommerce's abilities register automatically?
Yes, once Moksa for WooCommerce is active, as far as its code shows. This directory reads the code but does not evaluate every setting or feature flag, so check the plugin's own settings if an ability is missing on your site.
Does Moksa for WooCommerce need anything special to work with the Bridge?
Needs WordPress 7.0 or later (the plugin's own minimum; the Abilities API itself needs 6.9), plus PHP 8.2 or later and the plugin active. The abilities check these capabilities: edit_shop_orders, manage_woocommerce.
More Ecommerce plugins
WooCommerce Stripe Payment Gateway
ConditionalAn agent can pull the connected Stripe account's status and balance, and read charges, payment intents, disputes, payouts and balance transactions by ID or as lists, all read-only, once WooCommerce and the plugin's ability feature flag are both enabled.
WooCommerce PayPal Payments
ConditionalAn agent can check whether the store's PayPal account is connected, list configured payment methods, and look up a PayPal order's captures, refunds and shipment tracking, all read-only, once WooCommerce and the plugin's ability feature flag are both enabled.
Verified from Moksa for WooCommerce's own free wordpress.org code (version 1.21.0) on 10 November 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, Moksa or Moksa for WooCommerce. Back to the full directory.
Bridge Moksa for WooCommerce, keep the same control.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.