1. Why a workspace
Prompts work best when they contain real facts: your business country, shipping regions, checkout type, active gateways, currencies, order values and the exact error text. Typing those into every prompt is slow and error-prone. The Command Center asks for each detail once and reuses it wherever the same detail is needed, so you can move from one category to the next without starting over.
2. How it works
- Choose your stage. Pick the stage closest to your situation: choose, connect, diagnose, recover or protect.
- Open a category. Each category groups ten or eleven prompts around one problem, such as failed and declined transactions.
- Fill in your details. Highlighted variables become input fields. Enter them once.
- Copy the prompt. One click copies the personalized prompt for your AI assistant.
- Review the answer. Compare it with your dashboards and the provider's current documentation before acting.
3. What to enter, and what never to enter
Good entries are plain facts: a country, a currency, a plugin name and version, a checkout type, an anonymised error message, a payout schedule. Never enter API keys, secret keys, webhook signing secrets, passwords, full card numbers, bank account numbers or government ID numbers. If a prompt needs an order or transaction reference, use a masked form such as the last four characters. The book's usage checklist repeats this rule, and your details are saved in your own browser.
4. Examples of shared details
Some details are used across many categories. Your business country and shipping regions matter for gateway availability, strong customer authentication and currency limits. Your checkout type matters for Checkout block conflicts and for any gateway comparison. Your list of active gateways matters for reconciliation, fallback planning and migration. Because they are entered once, improving one answer immediately improves the next. The workflow in the gateway failure recovery workflow uses exactly these shared details.
A suggested first session
In your first session, enter only the essentials: business country, shipping regions, checkout type, the gateways currently active and your main currencies. Then open one category that matches today's problem and run two or three prompts. Review the answers against your dashboards, note anything the assistant could not know, and add those facts to the workspace. A small, accurate set of details beats a long one with guesses in it. After the first session you will know which details your store needs most, and the later categories will feel much quicker.
If several people manage payments, agree who owns the workspace details and update them whenever a gateway, currency or checkout setting changes.
5. Revisiting your work
Return to a category any time. Change a detail, such as adding a second gateway or a new currency, and the affected prompts update. This makes the workspace useful long after the first problem is solved: you can re-run the fee audit when volumes change, repeat the sandbox test plan before a major WooCommerce update, or refresh your failover runbook each quarter.
6. Requesting the PDF
The same purchase includes the complete digital book. If you prefer a document you can read offline, request the PDF by email from your account. The book, the prompts and the workspace share the same edition, so what you read matches what you use. To see how a gateway's differences feed into the choices in the workspace, read how WooCommerce payment gateways differ. For the full overview see the book research page, or go to the complete book.
7. Keeping the workspace accurate
The workspace is only as good as the details in it. Review them whenever you change a gateway, add a currency, switch checkout type, upgrade WooCommerce to a new major version or move hosting. Keep the entries factual and dated, and remove anything that is no longer true. Treat every AI answer as a draft that you verify against the provider's current documentation and your own dashboards, and keep your own sign-off on anything you send to a provider, a customer or a colleague.
Sources and verification
WooCommerce, its extensions, WordPress and payment providers change their features, countries, fees and screens from release to release. The statements in this guide reflect what WooCommerce and the providers published when it was last reviewed on 4 October 2026, against the WooCommerce 11.1 series, and may change. Check the current pages below before you act, and never test changes on a live store without a backup.
Educational guide only. Not legal, tax, security-audit or financial advice. The Prompt Powerhouse is independent of, and not affiliated with or endorsed by, WooCommerce, Automattic or WordPress. No payment, approval, fee or dispute outcome is guaranteed.