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 a staging site and the gateway's test mode for repeatable checks. If a live test is necessary, use a controlled low-value order, confirm whether a charge or authorisation exists before retrying, and reconcile the test order afterwards.

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 gateway may have charged or authorised the payment without successfully notifying WooCommerce. Check the transaction, webhook or callback delivery, order notes and logs before asking the customer to pay again or manually changing the order status.

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.

Missing attribute terms, invalid default selections, stock settings, theme templates or JavaScript conflicts can prevent variations from appearing. Confirm the product data first, then test the default theme and minimal plugin set on staging.

Clone the issue to staging, switch to a default compatible theme and leave only WooCommerce plus the required gateway or extension active. Re-enable other extensions one at a time while repeating the exact failing 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.