WooCommerce emails not sending? Find the break in the chain.
Order confirmations can disappear for several very different reasons: WooCommerce never generated the message, WordPress could not hand it off, SMTP authentication failed, the sender domain was rejected, or the recipient accepted the mail and filtered it. Debug those layers in order instead of changing random settings.
The fast split
If password resets and SMTP tests fail too, debug the shared WordPress mail path. If those work and only one WooCommerce email type fails, debug the WooCommerce trigger first. If WordPress reports a successful handoff but the recipient never sees the message, move outward to the sending service, bounce/rejection data, authentication, and mailbox placement.
1. Confirm WooCommerce actually tried to send the email
Start with the application, not DNS. Check that the relevant WooCommerce email is enabled, the order reached the status that should trigger it, and the recipient address is correct. If only one message type is missing while other WordPress mail works, the problem may be inside the WooCommerce workflow rather than your mail transport.
2. Check whether the problem affects all WordPress mail
Trigger a password reset or use the test-email feature in your current SMTP plugin. If every WordPress message fails, investigate the shared mail path. If generic WordPress mail works but a WooCommerce message does not, stay focused on the plugin, template, hook, or order-state path that creates that message.
3. Look at the mailer's result, not only the inbox
An empty inbox does not tell you where the failure occurred. A useful SMTP plugin or sending service should tell you whether WordPress handed off the message successfully, whether the SMTP connection failed, or whether the destination later rejected it. Preserve the exact error before changing settings.
4. Stop depending on the web server's default mail setup
WordPress can call PHP mail through wp_mail(), but that does not give a store a reliable authenticated transport by itself. Configure a real transactional-email service through SMTP or a supported provider integration so the sending path is explicit and testable.
5. Verify the From address and sending domain
Use a From address on a domain you control and have configured for the sending service. A connection can authenticate successfully while a message is still rejected because the sender identity is not authorized. Avoid quietly switching between unrelated From domains while debugging.
6. Check SPF, DKIM, DMARC, and any custom return path
SPF and DKIM help mailbox providers authenticate the message, while DMARC defines policy and alignment for the visible From domain. A passing authentication setup improves trust and makes failures easier to reason about, but it does not guarantee inbox placement. Compare the DNS records your provider expects with the records actually visible in public DNS.
7. Rule out conflicting mail plugins
Running multiple plugins that all modify wp_mail() or PHPMailer can make the active route hard to predict. Keep one component responsible for the final transport while debugging. After changing plugins, send a fresh test rather than assuming the previous connection state still applies.
8. Separate a bounce from spam-folder placement
A rejected or bounced message is different from a message that the recipient accepted and placed in spam. For a rejection, use the SMTP or bounce reason. For spam placement, review authentication, sender reputation, message content, recipient engagement, and sending behavior. No SMTP plugin can guarantee inbox placement by itself.
9. Test the real store workflow before declaring it fixed
After the generic test passes, place a safe test order or trigger the exact customer/account event that was failing. That final check proves WooCommerce, WordPress, the mail transport, the sender domain, and the recipient path are working together.
A simpler WordPress mail path with Parcel Wing
Parcel Wing can provide the authenticated SMTP transport behind WordPress and WooCommerce. Add your sending domain, configure its DNS, create SMTP credentials, connect them through a WordPress SMTP plugin, and then test the actual WooCommerce message that matters. You do not need to replace WooCommerce or your existing email templates.
Need a quick DNS check first? Look up your domain's SPF and DMARC records for free, then return to the real WooCommerce send to confirm the result.
