Requirements and responsibilities
Choose a compatible native WordPress server and confirm the selected theme, WooCommerce, extensions, payment provider and expected order volume. Native WordPress creation requires Nginx or OpenLiteSpeed rather than Docker.
xCloud WooCommerce hosting · xCloud agent capability boundaries
Gather product, price, inventory, shipping region/rates, tax configuration, policies, account behavior and notification destinations. The store operator owns these business decisions; xCloud hosting cannot configure them.
WooCommerce store setup and launch checklist · xCloud agent capability boundaries
Use an eligible isolated staging site and a payment provider’s sandbox or test mode for checkout trials. Test orders can trigger emails, integrations and analytics; keep them away from real fulfillment.
WooCommerce testing orders · xCloud agent capability boundaries
Illustrative situation
Illustrative scenario: a small retailer is opening a WooCommerce store with physical products. Before removing Coming soon mode, the owner needs proof that an in-stock item can be bought, an out-of-stock item cannot, shipping and tax are right, and the team receives an order email.
Choose the approach
Choose the gateway supported for the seller’s country and business, then validate its own sandbox and production credential switch. Do not assume one payment extension or test-card behavior for every provider.
WooCommerce store setup and launch checklist · WooCommerce testing orders
Treat stock, shipping, taxes, failed payments and customer email as separate acceptance conditions. The order-received page alone does not prove that a charge or notification succeeded.
WooCommerce store setup and launch checklist · WooCommerce testing orders
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Confirm the hosting and domain plan
- Where
- xCloud team/server/site views; connected MCP reads
- Permissions
- Authorized owner or administrator for the named team, site and application.
- Inputs
- Store domain, team, compatible server, capacity, desired WordPress site and DNS owner.
- Action
- Confirm an existing WordPress site or prepare an explicit new-site plan. For a new site, inspect compatible server and domain/DNS inputs before any approved creation.
- Expected result
- An identified site and launch address with a named DNS owner.
- Verify
- Check the returned site identity, application access and HTTPS status; compare them with the intended store domain.
- If it fails
- If the server is Docker or agentic, choose a compatible Nginx/OpenLiteSpeed server before native WordPress provisioning.
Sources: xCloud agent capability boundaries · xCloud WooCommerce hosting
Step 2 of 5
Create a safe checkout test area
- Where
- Site overview → Add Staging; staging site → Manage Staging
- Permissions
- Authorized owner or administrator for the named team, site and application.
- Inputs
- Eligible plan, staging hostname, payment sandbox, mail and fulfillment isolation.
- Action
- Create WordPress staging in the dashboard. Disable or isolate real payment, fulfillment, customer mail and webhook side effects before seeding test products and orders.
- Expected result
- A staging checkout that can be exercised without real fulfillment.
- Verify
- Check environment URL and that the payment provider is in test mode; inspect integrations before placing test orders.
- If it fails
- If safe isolation cannot be demonstrated, stop checkout testing and resolve the integration path first.
Sources: xCloud agent capability boundaries · WooCommerce testing orders
Step 3 of 5
Configure catalog and order rules
- Where
- WooCommerce → Settings and product editor in wp-admin
- Permissions
- Authorized owner or administrator for the named team, site and application.
- Inputs
- Product and stock matrix, shipping zones/rates, tax obligations, checkout fields, policies and email recipients.
- Action
- Configure the minimum sellable catalog and order rules under the store owner’s direction. Record expected totals for at least one domestic and one unsupported or edge-case address.
- Expected result
- Expected checkout totals and rules documented before testing.
- Verify
- Review settings with the business owner; compare product availability and calculation examples against approved prices and policies.
- If it fails
- If tax/shipping rules are undecided, do not call checkout ready; assign the decision to the owner.
Step 4 of 5
Run a complete staging order matrix
- Where
- Staging storefront, WooCommerce → Orders and provider sandbox
- Permissions
- Authorized owner or administrator for the named team, site and application.
- Inputs
- Test customer, safe test product, allowed and disallowed address, valid/failed payment cases, monitored mailboxes.
- Action
- Run cart to order-received flow, failed payment, stock limit, shipping/tax calculation, guest/account behavior and confirmation mail. Inspect order status and gateway record. Remove or label test data per the provider and fulfillment process.
- Expected result
- Observed outcomes match the order and payment acceptance matrix.
- Verify
- Match checkout total, order ID, payment result, stock change and messages; verify no real shipment or production charge occurred.
- If it fails
- If an order stays pending or a customer is charged unexpectedly, stop launch, reconcile provider transaction and WooCommerce order before retrying.
Sources: WooCommerce testing orders · WooCommerce store setup and launch checklist
Step 5 of 5
Approve the production switch
- Where
- Production WordPress, WooCommerce and xCloud dashboard
- Permissions
- Authorized owner or administrator for the named team, site and application.
- Inputs
- Passing staging evidence, completed backup, DNS/HTTPS check, production gateway credentials and launch approver.
- Action
- Record a fresh completed recovery point. Apply only approved files/settings to production; do not push staging orders or customer tables over newer production records. Switch the payment provider to its approved live mode and remove Coming soon only when the owner accepts the checklist.
- Expected result
- The store accepts intended orders at its final HTTPS domain.
- Verify
- Perform a tightly controlled production smoke check and reconcile any test transaction with the provider, order record and mail; confirm dynamic cart/checkout are uncached.
- If it fails
- If a live order or email fails, return to the agreed safe selling state, identify the failure and decide on a forward fix or dashboard recovery with newer orders preserved.
Sources: WooCommerce store setup and launch checklist · WooCommerce testing orders · xCloud agent capability boundaries
Maintenance
Review failed/pending orders, payment-provider reconciliation, stock, notifications and dynamic checkout pages on an agreed cadence. Re-run the test matrix after gateway, theme or WooCommerce changes.
WooCommerce testing orders · WooCommerce store setup and launch checklist
Keep backup completion and restore access visible; test whether the agreed recovery plan preserves orders placed after the backup.
Recovery decisions
If checkout breaks, stop accepting orders using the store’s agreed business procedure, reconcile any payment already captured, and preserve affected order IDs before a retry or rollback.
Any xCloud restore is a dashboard decision. A full database restore can remove newer orders; export/reconcile them and confirm the recovery point, target and acceptable loss first.
AI handoff
Connect xCloud MCP in an agent client and select the intended team. Discover the current tools, schemas and scopes. Use reads for inventory; present exact site, server, domain, cost, interruption and data impact before each approved write. Use returned dashboard_url values for manual work. The packaged REST fallback accepts GET requests only; never use it for writes.
Supported scope
- Confirm requirements and inspect resources mcp · read
Discover the connected profile and operation schema first; only teams granted to the connection are visible.
Checkpoint: Confirm exact team, server and site identity. Use dashboard_url returned by the resource; do not invent a dashboard link.
Operation identifiers and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
- Create a WordPress site mcp · write
Requires a compatible Nginx or OpenLiteSpeed server; Docker and single-site agentic servers cannot host a new WordPress site.
Checkpoint: Approve the exact server, domain, capacity, cost and creation inputs before provisioning. Verify completion and HTTPS.
Operation identifiers and scopes to discover
servers.sites.wordpress.create
Scopes: write:sites
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles
- Create and synchronize WordPress staging dashboard · manual
WordPress staging requires an eligible paid plan. The API staging-create operation is for Git sites.
Checkpoint: Use Site overview → Add Staging and staging Site → Manage Staging. Inspect push/pull scope before overwriting data.
- Configure native WordPress backup and restore dashboard · manual
Native schedule, retention and destination changes and all restores are dashboard-only.
Checkpoint: Use Site → Site Backup. Before restoring, confirm backup, target, scope and treatment of newer records.
- Configure WordPress caching dashboard · manual
Cache settings reads and purges do not allow changing cache layers or exclusions. OpenLiteSpeed page exclusions live in the LiteSpeed Cache plugin.
Checkpoint: Use Site → WordPress → Caching or the relevant plugin. Test dynamic booking, checkout and account pages in separate sessions.
- Configure and test application behavior app · manual
xCloud hosting operations do not configure WooCommerce checkout, n8n workflows, Nextcloud sharing policy or application users.
Checkpoint: An application administrator verifies each real business journey and records observed outcomes.
WooCommerce testing orders · n8n Webhook node and test/production URLs · Nextcloud file sharing administration · xCloud agent capability boundaries
Copyable agent brief
Manual checkpoints
- Configure WooCommerce and payment provider in wp-admin.
- Create and isolate WordPress staging through the dashboard.
- Approve live payment and Coming soon changes; reconcile test orders.
- Choose any restore only after preserving newer orders.
Feature coverage
- hosting (covered): Confirms compatible WordPress site and domain. Confirm the hosting and domain plan
- test-environment (covered): Isolates payment and fulfillment. Create a safe checkout test area
- commerce-rules (covered): Documents price, shipping and tax decisions. Configure catalog and order rules
- checkout-acceptance (covered): Checks payment, order, inventory and mail. Run a complete staging order matrix
- release (covered): Gates live switch on recovery and verification. Approve the production switch