A WooCommerce pre-launch checklist should cover the complete customer and administrator journey, not only the payment form. Before a store goes live, test how visitors find products, select variations, use coupons, complete checkout, receive order information and access their accounts. The same review should include shipping, taxes, digital delivery, emails, forms, links, the active theme and installed extensions.
Treat this as a practical, store-specific QA workflow rather than an official certification or universal pass/fail test. The exact scenarios depend on the products, countries, tax configuration, payment gateway, shipping setup, theme and extensions used by the store. Use staging or the payment provider’s documented test mode where available, avoid real customer data and record the expected result, observed result and follow-up action for every important test.
Plan the WooCommerce pre-launch test workflow
Start by mapping the customer journey from the product page to the order-received page. Then include the administrator’s view: order creation, payment status, inventory changes, customer access and notification handling. Testing these parts together helps reveal problems that a payment-only check will miss.
Define representative test scenarios
Choose scenarios that reflect the store’s actual configuration. Include representative product types, customer-account states, delivery locations and payment outcomes. If the store offers physical, virtual or downloadable products, test each relevant workflow separately. The same applies to variations, coupons, cross-sells, upsells and business-critical extensions.
- Use a staging site or the payment provider’s documented test mode where available.
- Use controlled test accounts, addresses, orders, coupons and email addresses.
- Record the configuration, expected result, observed result and any corrective action.
- Keep gateway-specific sandbox procedures aligned with that gateway’s documentation.
Do not use real customer personal or payment data during QA. Also, do not treat a successful test order as proof of security, accessibility, payment compliance or legal tax compliance.
Check product data, inventory, coupons and variations
Catalog errors can affect both buying decisions and order processing. Review product names, descriptions, prices, images, visibility and stock states in the shop, on the product page, in the cart and at checkout. Compare the displayed information with the intended store configuration rather than relying on the editor view alone.
Product and variation matrix
Create a small matrix of representative products from the types configured in the store. For variable products, confirm that shoppers can select the intended attributes and that each relevant combination shows the correct price, availability and stock behavior.
- Check product titles, descriptions, images, prices and visibility.
- Confirm that selectable variation attributes work as intended.
- Compare variation-specific pricing and availability with the configured data.
- Test stock states and the inventory result after the relevant purchase workflow.
- Review the product in the shop, cart and checkout presentation.
Do not assume that one successful product test proves that every product type, variation or extension workflow works correctly.
Coupon and merchandising scenarios
Test only the coupon rules configured for the store. Where applicable, use controlled cases for valid, invalid, expired or restricted coupons. Apply and remove a coupon in the cart, then verify that totals change as expected and that the customer receives an understandable result.
- Check configured coupon eligibility and rejection behavior.
- Verify cart totals after applying and removing a coupon.
- Review configured cross-sells and upsells in the relevant customer journey.
- Remove or clearly identify test coupons and test orders before launch.
Run checkout, payment and order-confirmation tests
Checkout testing should include both the storefront presentation and the resulting order workflow. Check billing, shipping, additional information, order details and the payment methods shown to customers. Confirm that a successful order contains the expected information and reaches the order-received page correctly.
Guest and account checkout
Run a controlled guest scenario and a registered-customer scenario when accounts are enabled. A guest test cannot confirm account-specific behavior, so test login or account creation separately. Review the fields customers must complete and how the active theme presents them.
- Test guest checkout and registered-customer checkout separately.
- Check login or account-creation behavior where enabled.
- Verify billing, shipping and additional-information fields.
- Review order details and the order-received page.
- Confirm that the checkout presentation remains understandable in the active theme.
Payment outcomes and order status
Use the payment provider’s documented sandbox or test mode where available. Test a successful payment and the documented failure behavior for the configured gateway. Check the customer-facing error message, order creation, order status and relevant notifications. Payment status can affect whether follow-up emails are sent, so connect the gateway result with the complete order workflow.
Never place unapproved live test transactions or expose test orders to real customers. A successful checkout demonstrates only that the tested scenario worked; it does not prove payment compliance or the security of the entire website.
Test shipping zones, delivery rates, taxes and currency
Location-dependent behavior needs controlled address tests. WooCommerce shipping zones determine which shipping options and rates customers see on cart and checkout pages. A customer matches only one zone, and zones are evaluated from the top downward, using the first matching zone. This makes both address coverage and zone order important.
Shipping-zone and address cases
Test addresses in each important configured zone and, where relevant, an address outside the intended service area. Compare the methods shown on the cart and checkout pages with the expected zone and configuration.
- Confirm that each representative address matches the intended shipping zone.
- Check zone priority and possible unintended matching caused by the order of zones.
- Verify enabled delivery methods such as free shipping, flat rate, local pickup or configured third-party methods.
- Test relevant product types because delivery behavior may depend on the contents of the cart.
Tax calculation and display
Check tax calculation and tax presentation as separate parts of the test. WooCommerce can calculate tax from the customer shipping address, billing address or shop base address. Display settings separately affect how prices and tax appear in the catalog, cart and checkout, including inclusive or exclusive presentation where configured.
- Use representative addresses and compare results with the intended tax basis.
- Review tax presentation in the catalog, cart and checkout.
- Check total calculations for the relevant products, variations, coupons and shipping cases.
- Validate legal tax obligations with a qualified tax professional.
Testing WooCommerce tax configuration is not the same as determining what a business must charge. Avoid treating this workflow as jurisdiction-specific tax advice.
Verify digital delivery, customer accounts and transactional emails
Downloadable products require a delivery and permission test, not only an order test. Place controlled orders for the important digital-product workflows and review what the customer can access after the configured payment or order status.
Download access and permissions
Check the order-received page, confirmation email and My Account > Downloads access where applicable. Verify login restrictions and whether access is intentionally granted after payment or after the configured order status. Also review download permissions and the chosen file-delivery behavior.
- Confirm that applicable email download links are present.
- Verify My Account > Downloads access for customers with accounts.
- Check login restrictions and the intended access timing.
- Review direct-file exposure and access permissions for each important workflow.
WooCommerce documents Redirect only as insecure because anyone with the URL may access the file. Remove or clearly identify test files, orders and customer data before launch.
Email verification and troubleshooting
Check that the relevant notification is enabled, then inspect the transactional-emails log under WooCommerce > Status > Logs. Review the order status as well: pending-payment orders may not trigger the expected messages. Distinguish a failed or skipped send from a message that was sent but filtered or not delivered.
Email problems can involve hosting mail delivery, spam filtering, payment-status updates or theme and plugin conflicts. Use controlled addresses during testing, and do not assume that a logged send guarantees inbox placement.
Complete the site, theme and extension QA pass
The final pass extends beyond purchasing. Test internal links, search, contact and other forms, visible contact information and the 404 page. Review the product, cart, checkout and account areas in the active theme, including mobile rendering where it matters to the planned customer journey.
Final sign-off checklist
Test each business-critical payment, shipping, tax, membership, subscription, automation or form extension according to its documented configuration and supported workflow. If a problem appears, investigate the theme or extension in an isolated configuration rather than assuming generic compatibility.
- Review every failed, incomplete or unclear scenario.
- Document whether unresolved items are fixed, deferred or explicitly accepted.
- Repeat critical checkout, order and email scenarios after final changes.
- Record tested configurations, versions and scenarios separately for each store.
One successful order does not prove that a plugin, theme or extension is compatible with every configured workflow.
Post-test cleanup
Before launch, remove or clearly identify test artifacts. Check that controlled content cannot enter the live customer journey and that test access is no longer exposed.
- Remove test orders, credentials, coupons and customer data where appropriate.
- Remove or clearly identify downloadable test files.
- Confirm that test messages, products and account information are not visible to customers.
- Repeat the most important customer journeys after cleanup if configuration changed.
A repeatable WooCommerce pre-launch checklist helps store owners and agencies validate product data, variations, coupons, checkout outcomes, payment statuses, shipping zones, tax settings, digital access, accounts, emails, links, forms, themes and extensions. The supplied checklist framework is broad and educational, not a universal certification or pass/fail matrix. Gateway procedures, extension behavior and tax obligations require store- and provider-specific validation. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.