Claude WooCommerce integration: what it looks like in daily work

A Claude WooCommerce integration through MCP lets Claude look up live orders, products and customers in your store while you work, and, if you allow it, change an order status, add an order note or set a stock level. This article follows a normal day in a shop: which prompts work, what Claude does with them, how read-only seats keep it safe and where the integration stops.

What does a Claude WooCommerce integration via MCP look like?

A Claude WooCommerce integration is three pieces in a row: Claude, MCP Self-hosted on your own server, and the REST API of your store. Claude Desktop or Claude Code connects to MCP Self-hosted with a seat token. MCP Self-hosted keeps the WooCommerce consumer key and secret in its .env and calls /wp-json/wc/v3 on your store. Nothing is installed inside WordPress.

Claude never sees the API keys. It sees tools with names like woocommerce_list_orders, decides which one fits your question and reads the answer. The install steps are on the connect Claude to WooCommerce page and in the WooCommerce MCP setup guide. This article is about what happens after that.

Which store questions can a Claude WooCommerce integration answer?

Claude can answer any question that a list or a detail lookup of orders, products or customers answers. In read-only mode the integration has five tools:

• woocommerce_list_orders: newest first, filtered by status, a date range (created after or before), a customer ID or a search term.
• woocommerce_get_order: one order in full, including line items.
• woocommerce_list_products: filtered by search term, category ID or stock status (in stock, out of stock, on backorder).
• woocommerce_get_product: one product with SKU, price and stock.
• woocommerce_list_customers: filtered by search term or email address.

List tools return 10 results by default and up to 100 per page. Claude pages through longer lists by itself when the question needs it. Every answer from the Claude WooCommerce integration is the state of the store at the moment you ask, not the state of the last export.

Which prompts work for a Claude WooCommerce integration in daily store work?

Plain questions work. You describe what you need, and Claude picks the tool and the filters. Four examples from a typical morning, with what the Claude WooCommerce integration does behind each one.

The on-hold queue. Orders on hold need a person to look at them, and opening each one in wp-admin takes time:

Show all orders that are on hold. Open each one and tell me what was ordered, by whom, and the order total.

Claude calls woocommerce_list_orders with status on-hold, then woocommerce_get_order for every result, and returns one summary. You decide what to do with each order.

A customer email. Someone writes in and asks where their order is:

Find the customer with email [email protected] and list her orders from the last 30 days with their status.

Here Claude chains two tools. woocommerce_list_customers with the email gives the customer ID, then woocommerce_list_orders runs with that ID and an after date. You get the answer for the reply without searching the order screen.

A stock check before a promotion:

Which products in category 12 are out of stock or on backorder?

Claude runs woocommerce_list_products once per stock status. The category filter takes the category ID, not the name, so give Claude the ID or let it look up a product in that category first.

A shipped order, on a seat with Can make changes on:

Order 4182 has shipped. Set it to completed and add a note for the customer with tracking number 3SABC123.

Claude calls woocommerce_update_order_status and then woocommerce_add_order_note. Order notes are internal by default. The customer only sees the note when Claude marks it as a customer note, which is why the prompt says “for the customer”.

How does a read-only seat keep the Claude WooCommerce integration safe?

In read-only mode the write tools are not registered at all, so Claude does not see them and cannot call them. You choose the mode per seat, when you add the seat in My Account → MCP Self-hosted → Seats. Read-only is the default for WooCommerce.

A seat is one person or device with its own token, its own tools and its own mode per tool. In a shop that maps to roles. The support colleague who answers “where is my order” gets read-only. The person who handles fulfilment gets Can make changes and can mark orders completed. If a laptop goes missing, you revoke that one token and the other seats keep working. MCP seats explains the tokens and the per-tool modes.

The store adds a second lock. You create the REST API key under WooCommerce → Settings → Advanced → REST API and pick its permissions there. A key with Read permission only makes every write call fail, even on a seat with Can make changes on. Start with a Read key and read-only seats, let the team ask questions for a week, then decide who needs write access.

What does the Claude WooCommerce integration not do?

It does exactly what its eight tools do and nothing more. Can make changes adds three actions to the five read tools: update an order status, add an order note and set the stock quantity of a product. That is the full list.

• No creating or deleting products, and no price changes.
• No creating orders, and no editing customer records.
• No refund tool, no coupons, no settings.
• Stock updates only take effect on products with “Manage stock” enabled. The tool does not switch that setting on for you; it returns a warning instead.

A Claude WooCommerce integration also does not watch your store. There is no schedule and no trigger: Claude calls a tool when a prompt asks for it, and only then. If your workflow needs a tool that does not exist yet, you can request a custom add-on.

Can one Claude WooCommerce integration cover several stores?

Yes. Instead of the three single-store variables you set WOOCOMMERCE_CONNECTIONS, a JSON array with one entry per store, each with its own id. With two or more stores, every WooCommerce tool gets a required store parameter, and Claude picks the store by that id. A prompt like this then works across shops:

Compare the number of processing orders in shop-a and shop-b today.

In My Account you add extra stores under the Tools tab of your license. On the Seats tab you then choose per seat which stores it can reach, so a colleague who only works for one brand only sees that store.

What does a Claude WooCommerce integration cost?

You need two licenses. MCP Self-hosted costs € 217,80 excl. VAT: € 180,00 per year and includes 3 seats and 1 activation. The WooCommerce add-on costs € 157,30 excl. VAT: € 130,00 per year. An extra seat is € 18,15 excl. VAT: € 15,00 per year. Payment is yearly recurring through Mollie, with EU VAT handled at checkout. The WooCommerce MCP server product page lists the tools and current terms, and MCP Self-hosted covers the server itself. If you prefer not to run Docker, the MCP Hosted seat is billed monthly with the first month free.

A Claude WooCommerce integration is most useful for the repeated lookups: the on-hold queue, the customer asking about an order, the stock check. Start with a read-only seat and a Read key, use the prompts above, and widen access only for the people who need it. The setup guide is the next step.