Step-by-step WooCommerce troubleshooting guides.

Identify the exact step that fails, note the time and affected order, then review WooCommerce status, order notes, logs and recent changes. Check whether the issue affects every customer, one payment method or one product before changing settings.

Use an isolated staging copy with the payment provider's sandbox credentials and outgoing customer messages contained. Follow the checkout guide to verify the order as well as the screen. Before any retry, check whether the earlier attempt created a charge or authorisation.

No. A bank decline, authentication failure or gateway outage can fail without a WordPress fault. Compare the WooCommerce order notes with the gateway transaction record and logs before changing checkout code or credentials.

The payment provider can have a charge or authorisation that WooCommerce has not recorded correctly. Compare its transaction with the order notes and notification delivery before requesting payment again. For recurring orders, follow the subscription renewal guide before triggering a manual retry.

First check whether WooCommerce generated the email and whether the order reached the status that triggers it. Then inspect email logs, recipient settings, SMTP delivery and spam filtering rather than repeatedly resending without a delivery record.

The customer's address, shipping zone, product class, package weight or cart conditions may not match any enabled rate. Recreate the same basket and address, then trace which zone and method WooCommerce selects.

Check its expiry, usage limits, minimum spend, allowed products, customer email restrictions and whether other coupons can be combined. Also confirm that tax and shipping are not being mistaken for the discountable subtotal.

Check that each intended combination exists, has a price and meets the store's stock rules. The variation guide separates product settings from a broken selector. Test a theme or plugin conflict on staging only after the product data is confirmed.

Contain customer email, payments and scheduled jobs on a staging copy before testing. Follow the conflict guide, retaining WooCommerce and the extensions needed to reproduce the fault. Change one component at a time and repeat the same basket and action.

Get help when payments, order data, customer information or live revenue are at risk, or when safe testing requires code or server access. Preserve order notes and logs and avoid repeated payment attempts while the transaction state is unclear.