WooCommerce Order Emails Not Sending

Identify the missing email and its trigger

Start with the message type: new-order notification to staff, processing-order email to the customer, refund notice or something else. Check which event should trigger it and whether the relevant order reached that state. A payment accepted by the provider may not yet have updated the WooCommerce order.

Use one safe test order and an agreed recipient. If the trigger never happened, investigate the order or payment path first. Resending a message may help the immediate customer request, but it does not explain why future orders would miss the same trigger. WordPress password resets and admin emails also have a different path from WooCommerce transactional messages.

Review the email settings in WooCommerce

Open WooCommerce → Settings → Emails and select the notification being checked. Confirm it is enabled and, for staff notifications, that the intended recipients are configured. Review the sender details and any extension that adds or replaces that email type.

Use a From address on the business’s own domain with the mail provider’s supported configuration. A public mailbox address used as the sender can conflict with the way the website sends mail. Check custom templates when content is wrong, but do not start by redesigning the template if the store never tried to send the message.

Check the transactional-email attempt

Current WooCommerce documentation describes a transactional-emails source under WooCommerce → Status → Logs. For the installed version, review the entry for the controlled test and the relevant order notes. A Sent result indicates a successful handoff to the site’s mail system. Failed, Disabled and Skipped results point to different next checks.

If the expected entry is absent, check the installed version, log settings and any fatal error affecting the order transition. Logging may hide lower-level entries. Keep detailed diagnostics private and limited to the relevant attempt. An empty view is a reason to inspect the trigger and configuration, rather than proof that nothing happened anywhere in the mail system.

Follow the message through the mail provider

Once the website has handed off the message, trace it in the mail provider’s logs. Check whether it was accepted, queued, rejected or reported as delivered. Then confirm the controlled inbox, including spam or filtering. Provider delivery can mean acceptance by the recipient’s server rather than placement in the inbox.

Check domain authentication and sending setup against the mail provider’s instructions. Installing an SMTP plugin can change transport, but it does not fix a disabled notification, a missing order event or every recipient filter. Use the result from the specific message to decide whether the next action belongs to the store, host, mail service or recipient-side system.

Verify the message as well as the send

With the sending path working, inspect the test email’s subject, sender, recipient, totals and useful links. Account and order links should lead to the intended store. After a migration or staging test, check that the message does not contain a staging host or expose order information through an incorrect link.

Test any template or extension change on an isolated copy with controlled recipients. Keep staging from emailing real customers or triggering fulfilment. Record the cause, change and delivery evidence, with temporary logging cleaned up afterwards. That gives the next missing-email report a clear starting point and avoids promising inbox placement that the store cannot control.

Useful documentation

• WooCommerce email settings and troubleshooting (opens in a new tab) ↗