Check your store before you buy.
Choose a workspace and review the setup it needs. Download the open questions to discuss with your developer before purchase.
Review the requirements
These answers describe your plans. They do not test your store or certify compatibility.
Testing and questions to take to your developer
Use PHP 8.1 or later with WordPress and WooCommerce. The recorded verification environment is WordPress 7.1.1 and WooCommerce 11.1.2. It does not certify every theme, gateway or host.
Preorder: ordinary staging/development installations block checkout and outgoing customer messages. Ask for the supported payment-testing procedure before buying. Changing an environment label is not a compatibility test.
Vendor: PayPal Sandbox activation is available on a merchant staging site. Live payouts require account eligibility, deployment checks and separate activation. A recorded manual ledger payment is not a bank transfer.
Check outcomes after an update
On an isolated store with fictional data, record versions and expected results before changing the ZIP. Ask your developer to check these outcomes:
- Order storage: reload the order and its item values through WooCommerce APIs. Review HPOS with compatibility synchronization both on and off where supported; do not bypass synchronization guards.
- Checkout: test the store's actual classic or block checkout and confirm the expected order data. An editor block preview alone does not verify checkout.
- Theme and messages: check WooCommerce > Status > System Status > Templates for outdated overrides. Check the expected message in a controlled test inbox; a preview alone does not confirm delivery.
- Refunds and access: compare full and partial refund amounts, commission records and each account's permitted actions. Keep payout requests separate from confirmed transfers.
These are checks to agree with your developer, not completed checks of your store. Official HPOS testing guidance · System Status guidance. Guidance checked October 12, 2026.
Keep backups and verify deployment-specific permissions, theme pages, scheduled jobs and mail delivery. Share product and gateway versions with support. Keep passwords, payment tokens, API secrets and customer exports private.