Before your morning coffee goes cold you can know where the store stands: how many products are actually live versus sitting in draft, how many orders are waiting on you in processing or on-hold, and what sales did over the period you care about. This is the read-only standup for your shop. It counts and summarises, and it cannot change a thing.
Give me a one-screen status of my WooCommerce store. Read only, change nothing.
I want product counts by status (published, draft, pending, trash), ordercounts by status (pending, processing, on-hold, completed, cancelled,refunded, failed), and a sales summary for [this month]: total sales, ordercount, net sales, and average order value.
Lay it out as a short briefing I can skim in under a minute, and put aone-line takeaway at the very top, like orders piling up in processing or astack of draft products that never went live.Why this is safe to run
Every ability behind this prompt is a read. Counting products is a separate ability from listing them, and none of these three can write, so the worst case is that a count you left switched off quietly returns nothing. Nothing is created, changed, or deleted.
Because it is all reads, there is no approval step and no batching to watch: it just answers. The order breakdown often surfaces the useful thing on its own, a pile of orders stuck in processing or on-hold that need a human, without you opening the orders screen at all. Every call still runs against the capability of the user you bound the agent to and lands in the Activity Log.
Already connected? Skip the paste. Ask your agent for the “see your catalog and order counts at a glance” recipe, or just ask how the store is doing, and it runs the same reads on your own install.