Hoobert – AI Command Bar for WooCommerce
You know the click path. Orders, filter by status, find the order, scroll, Refund, line item, quantity, amount, Refund manually, confirm. Six screens to do one small thing. Hoobert is a command bar for that. Press Cmd/Ctrl-K anywhere in wp-admin to open the WordPress command palette, pick Ask Hoober
You know the click path. Orders, filter by status, find the order, scroll, Refund, line item, quantity, amount, Refund manually, confirm. Six screens to do one small thing.
Hoobert is a command bar for that. Press Cmd/Ctrl-K anywhere in wp-admin to open the WordPress command palette, pick Ask Hoobert , and type the thing you actually wanted:
- “refund order 1042”
- “mark this order completed and add a note that the replacement shipped”
- “create a coupon SUMMER20 for 20% off”
- “add a Large / Red variation to this product at 54.99”
- “which products are out of stock”
- “who were my top customers last month”
- “approve the pending review on the espresso grinder”
Hoobert reads the request, picks the matching WooCommerce action, shows you what it is about to do, and runs it. That is the whole product. No chat thread to babysit, no second dashboard to learn, no new place your data lives.
He is an owl, and he is careful
Hoobert is meant to be trusted with a live store, so the boring parts got the most attention.
- Nothing runs until you see it. Every request is resolved into a concrete action first and previewed back to you in plain English. Anything destructive – refunds, deletions, status changes, price and stock edits – needs a confirm click before it touches your data.
- Your permissions, not the plugin’s. Actions execute in-process through WooCommerce’s own REST API v3, under your logged-in admin session. Hoobert can never do something your own account could not do.
- No keys in the browser. The inference key is stored server-side and used server-side. Your browser never holds a credential, and Hoobert never creates or uses a WooCommerce consumer key/secret pair.
- Everything is written down. Every executed command is recorded in a store-wide audit log: the request, the exact REST call, the arguments, the outcome, and who ran it.