指南
AI support assistant for your WooCommerce store
Create a read key in your store admin, let your mate learn the catalogue and policies, and give a signed-in customer answers about their own orders.
Loading…
指南
Create a read key in your store admin, let your mate learn the catalogue and policies, and give a signed-in customer answers about their own orders.
Busymate AI reaches a WooCommerce store through the store's own REST API: the catalogue, categories, shipping zones and policy pages become content your mate answers from, and a signed-in customer can ask where their order is. Nothing is installed inside WooCommerce for that — the connection is a read key you create in the store admin.
Every step below is proven against a real WooCommerce store, end to end, by a shopper in the widget.
/wp-json/wc/v3/, and plain permalinks do not serve them.ck_…) and consumer secret (cs_…) are shown once — copy both before leaving that page.Read is enough for everything here: a write key would let the assistant change orders and move money, so the connection does not ask for one.
Open Console → Connections and add the store with three values: the store address, the consumer key and the consumer secret. The secret is stored value-blind — afterwards the Console shows a hint, never the value.
It is verified before anything is saved: one call to GET /wp-json/wc/v3/system_status proves the site really runs WooCommerce, the credential authenticates, and the key reads more than a public resource. A failure is reported as a sentence, never saved as a row claiming to be connected.
Over MCP: connect_commerce, get_commerce_status and sync_commerce, each taking a kind of woocommerce.
Four corpora, and you pick the set:
Products are bounded by a page limit you set, 1 to 50, default 20. It is the same knowledge pipeline as a website source or pasted text — see Teach your assistant your own content.
The store is re-synced on a schedule you set — daily by default, hourly at most. A sync compares the newest edit time across products and pages against the last one seen; when nothing changed it is skipped and not one memory is rewritten. Sync now in the Console, or sync_commerce, forces a pass.
Order lookup is identity-gated: it answers only with the signed-in customer's own orders, and has no anonymous arm.
The match is made on your store's own customer id. The plugin signs the WordPress user id into the proof — exactly the customer a WooCommerce order carries — so the store filters on it directly, and no email or phone number crosses the browser. A storefront that signs customers in another way falls back to a verified email.
Ownership is checked again on every order returned: a filter you asked for is not a filter that was applied. An order number alone is a guessable integer, never sufficient.
What comes back: order number, status, the dates placed, paid and completed, the total, the shipping method, the items, and a tracking number when the store recorded one.
One WordPress plugin does both jobs: it loads the chat on every storefront page and signs a short-lived proof of who is logged in, so order lookup needs no second sign-in. Your customer database is never shared.
Without the plugin the chat still works — add the embed script to your theme — but the storefront must then sign identity itself: Recognize signed-in customers.
The connection deliberately offers no start_return action. WooCommerce core has no customer-initiated return resource in its REST API, and POST /orders/<id>/refunds is an admin refund that moves a merchant's money — not something to run on a visitor's say-so. Returns are a plugin choice that differs per store.
So the assistant answers the returns policy from your own returns page, with a citation, and hands the conversation to a person for the rest.
Every step above is available from any MCP client on your own account:
claude mcp add --transport http busymate-ai https://busymate.ai/mcpNo. Read covers the catalogue, the policies and order lookup. Write access is never asked for, because everything it would unlock moves a merchant's money.
No. The lookup runs only for a signed-in customer, is scoped to that customer's own key, and re-checks ownership on every row before showing it. There is no search-all-orders path.
On the schedule you set — daily by default, hourly at most. An unchanged store is skipped, so re-syncing a quiet catalogue costs nothing.
Only to hand over who is signed in. The chat can go on the site with the embed script; the plugin saves you signing the proof by hand.