WooCommerce
Manage WooCommerce catalog, inventory, orders, refunds, customers, coupons, and reports
Connect WooCommerce when a project needs to read or change data in an existing WooCommerce store. Swarmz keeps the store URL, consumer key, and consumer secret in the shared connection. The AI can request that connection while it builds, and the published app can call the same supported operations through the connector gateway.
A Swarmz administrator must make WooCommerce visible before workspaces can connect it. WooCommerce doesn't need an OAuth application in Swarmz. Each workspace enters credentials created in its own WordPress admin.
Before you connect
Your store needs:
- HTTPS on its public store URL
- a WordPress permalink setting other than Plain
- WooCommerce REST API credentials
In WordPress admin, open WooCommerce > Settings > Advanced > REST API, then create a key for the WordPress user whose permissions should apply. Choose Read for dashboards and lookup tools. Choose Read/Write if the project will change products, stock, orders, customers, coupons, or refunds.
Copy the consumer key and secret when WooCommerce shows them. The key starts with ck_. The secret starts with cs_. Keep both out of chat, project files, browser code, and client-side environment variables.
See WooCommerce REST API authentication for the provider setup.
Available operations
| Area | Read operations | Write operations | Limit per minute |
|---|---|---|---|
| Products | list_products, get_product | create_product, update_product | 30 read, 10 write |
| Variations | list_variations | create_variation, update_variation | 30 read, 10 write |
| Categories | list_categories | create_category, update_category | 30 read, 10 write |
| Orders | list_orders, get_order | update_order | 30 read, 10 write |
| Refunds | list_refunds | create_refund | 30 read, 10 write |
| Customers | list_customers, get_customer | create_customer, update_customer | 30 read, 10 write |
| Coupons | list_coupons, get_coupon | create_coupon, update_coupon | 30 read, 10 write |
| Reports | get_sales_report, get_top_sellers_report | None | 30 |
Product and variation updates can change manage_stock, stock_quantity, and other fields accepted by WooCommerce. List operations support bounded WooCommerce query filters. Swarmz limits per_page to 100, request bodies to 128 KB, and provider responses to 2 MB.
The connector sends requests only to the connected store's /wp-json/wc/v3 path. Its server fetch pins the store's public DNS result and rejects local, private-network, link-local, and metadata addresses.
Connect WooCommerce
- In Settings > Integrations, select WooCommerce, then select Connect new.
- Enter a name that identifies the store or environment.
- Enter the public HTTPS Store URL. Include the WordPress subdirectory if the installation uses one.
- Enter the Consumer key and Consumer secret in the secure form.
- Link the connection to the project when the AI requests it.
Credential validation reads one product from /wp-json/wc/v3/products. A route error usually means the URL, WooCommerce plugin, or WordPress permalink setting is wrong. An authentication error means the key and secret don't match the store.
Build with WooCommerce
Name both the store workflow and the records the app should use. These prompts map to supported operations:
- “Use WooCommerce to build an inventory screen that lists products and variations, flags low stock, and updates stock quantities.”
- “Build a support console that searches customers, shows their orders, and lets an approved agent issue a refund.”
- “Create a coupon manager that lists active codes and can create or update a campaign.”
- “Build a sales dashboard from WooCommerce orders, sales reports, and top-seller reports.”
The AI will request a WooCommerce connection when it reaches the first store operation. Write operations require approval during the build. The WooCommerce key still decides whether the provider accepts the request.
Test WooCommerce
Use a staging store or disposable records for write tests.
- List products with
per_pageset to1, then open the returned product in WordPress admin. - Create a draft product, update its price and stock quantity, and confirm both changes in WooCommerce.
- Create a variation on a test variable product and update its stock.
- Create a coupon with a short expiry date, then confirm it appears in WooCommerce.
- Open a test order, change its status, and confirm the order timeline records the change.
- If refund handling is in scope, use a test payment and a small disposable order. Confirm the refund in both WooCommerce and the payment provider before deleting the test data.
- Read the sales and top-seller reports for a period that contains the test order.
If reads work and writes fail, replace the key with one created using Read/Write permission. If credentials may have leaked, revoke the key in WordPress admin first, create a replacement, then reconnect WooCommerce in Swarmz.