WooCommerce store tools
Manage products and orders in Free; add catalog, coupons, customers, reviews and Store Manager with Pro.
OctoPress uses its own focused tools with native WooCommerce permissions and behavior. WooCommerce must be active. The WordPress Abilities API is not required.
Free: Products and orders#
The WooCommerce extension lets Octo list, inspect, create, update, trash and restore products and orders. It also reads paginated order notes and adds internal or explicitly customer-visible notes. New products default to draft and orders to pending. Changes need approval unless allowed by current chat permissions. See Tool access and roles.
Simple, variable, grouped and external products are supported. Variations are created explicitly under a variable parent; Octo does not generate every attribute combination automatically. Inventory reads identify whether stock belongs to the parent or a variation, so variable products do not have to be edited manually just because they are variable.
Existing brands can be assigned to products in Free or Pro when WooCommerce supports brands; creating or editing the brand vocabulary requires Pro. Product catalog details expose brand IDs. Focused merchandising details cover related upsell/cross-sell products, menu order, purchase notes and whether reviews are allowed. These settings apply to parent products, not individual variations, and relationship changes share the 20-item mutation limit.
Financial edits follow WooCommerce's current order editability rules. Native totals, stock changes, emails and integration hooks remain active. A note is internal unless you explicitly request a customer-visible note. Existing product types cannot be converted, notes cannot be edited/deleted, and refunds, gateway payment operations and permanent deletion are not supported. Restored products are not silently published.
Pro: Store Manager#
An active Pro license and enabled WooCommerce Store extension add the Store Manager agent and these resources:
| Resource | Available actions |
|---|---|
| Store configuration | Inspect store status, payment methods, shipping zones and tax settings. Read-only. |
| Catalog | List, inspect, create and update categories, tags, available brands, shipping classes, global attributes and attribute terms. No deletion. |
| Coupons | List, inspect, create, partially update, trash and safely restore. |
| Customers | Discover registered customers, inspect requested details, create a customer or update contact/address fields. No deletion. |
| Reviews | List, inspect, update content/moderation, add a store reply and trash/restore. No fabricated buyer reviews or author/rating/verified-purchase changes. |
Brands and other optional features must exist in your WooCommerce installation. Global attribute creation can be followed immediately by term creation. Generic WordPress term tools cannot change WooCommerce-owned taxonomies.
Store Manager also searches, inspects, imports and updates Media Library files for product images, then assigns attachment IDs through product management. It has no PHP runner by default and does not use database/code workarounds for missing operations. Integrations go to Builder, substantial page writing to Content Writer, SEO metadata to SEO Specialist and broader administration to Octo through confirmed handoffs.
Review replies can be listed one page at a time for a selected review, inspected individually, edited, trashed or restored. Existing replies retain their author and review/product ownership. Adding a store reply uses your account; replies cannot become fabricated buyer reviews or change ratings/verified-purchase state.
Focused reads and changes#
Lists use pages of 20, up to 50. A single-record read returns identity by default; ask for only the detail groups needed, such as inventory, items, coupon configuration or customer billing. Nested collections do not expand automatically. Large browsing requests can use live tables.
Updates change only supplied fields. Product arrays replace their supplied values; nested customer addresses merge individual keys. Native calculations remain authoritative. Compact confirmations include the affected identity and actual status rather than a full customer or order record. After a reported partial failure, inspect the affected record before trying again.
Customer lists do not include guest-order identities, addresses or payment data. Customer creation generates credentials internally and never returns them to chat. Existing accounts are not converted; staff and privileged accounts cannot be managed as customers. Requested contact/address data may remain in chat arguments and approval history. Retrieve only the personal information needed for the task.
Try it#
- "Find running shoes, inspect where their stock is managed, and change the quantity to 12."
- "Create a draft variable T-shirt with Blue and Red options, then add only a Blue medium variation."
- "Add an internal note to order 1234 saying the parcel was re-sent."
- "List my product categories and suggest a cleaner structure."
- "Inspect coupon 42's usage and update only its expiration date."
Keep Require approval enabled for sensitive store work and review possible email, stock and status effects before approving.