WooCommerce Order Emails Not Sending? How to Fix It

Last updated 16 November 2026.

An order goes through, the payment clears, and then nothing arrives in the inbox. The customer writes to ask whether the order worked at all, and the store owner is left unsure whether the problem is in WooCommerce, in WordPress, or in the mail system behind them. This is a confusing fault because WooCommerce can look perfectly healthy while the email quietly fails somewhere else.

The good news is that WooCommerce order emails not sending usually have a small number of causes, and they can be checked in a sensible order. Start with the email itself and the order status, then move to settings, then to delivery. Changing several things at once makes the real cause harder to find, so work through one check at a time and test after each change that could fix it.

First, work out which email is missing

WooCommerce sends different emails for different events, and they go to different people. Knowing exactly which one is missing narrows the search a great deal.

EmailGoes toWhen it sends
New orderThe store adminWhen the order moves from Pending payment to Processing, On hold or Completed
Processing orderThe customerWhen payment clears and the order moves to Processing
Completed orderThe customerWhen the order is marked Completed
On-hold orderThe customerWhen the order moves into On hold, for example when a bank transfer order is placed and payment is still to come

Two moves catch store owners out. Moving a paid order from Processing back to On hold sends no email to anyone, because WooCommerce has no email for that move. If you park a paid order on hold while you check stock, tell the customer yourself, or they will hear nothing at the moment they most want news. Cancelling is nearly as lopsided: the admin is told, but the customer version of the Cancelled order email ships switched off. Switch it on at WooCommerce, then Settings, then Emails, then Cancelled order, and the gap closes. WooCommerce ships eleven email notifications in all; the table above covers the four order emails most stores check first.

Ask these questions before changing anything. Is the admin email missing, the customer email missing, or both? Is it one order or every order? Did it work before and stop, or has it never worked? If only the customer email is missing, the admin copy arriving is useful evidence: the store is creating orders and sending mail of some kind, so the problem is more likely in one email setting, one address, or one spam filter than in the whole mail system.

Check the order status before anything else

Open the order in WooCommerce and look at its status. The customer confirmation, the Processing order email, only sends when the order reaches Processing. An order still marked Pending payment has not triggered that email yet, because payment has not been confirmed. That is normal behaviour, not a broken email, and the right fix is to sort out the payment, not the mail settings.

Also check for a Failed status. A failed payment will not produce a normal confirmation either. If the gateway is slow to confirm a payment, the email may simply be delayed until the gateway responds. Give a slow gateway time to settle, then check the order again before assuming the email system is at fault.

Read the order notes before you change anything

Open the order that failed and read its notes before you touch any setting. Since WooCommerce 10.9, released 23 June 2026, every email attempt leaves a private note on the order it belongs to. A note reading Email “New order” sent means WooCommerce built the message and handed it over; if the inbox is still empty, your problem lives past WooCommerce, in spam filtering, DNS records, or your host. A note reading Email “New order” failed to send, followed by a reason, means the mail service refused it, and the reason names the real problem.

A different line matters more. If a plugin throws while the order changes status, WooCommerce writes Error during status transition, followed by the reason, and the emails are never built at all. The same failure also stops the stock reduction and the sales counters, while the order still reads Processing in the list, so the order can look perfectly healthy when it is not. The wording after the full stop names the plugin that threw, which is usually something that reaches outward during checkout: a shipping label service, an accounting sync, an ERP bridge, a stock feed. Switch that one plugin off on staging, place a test order, and watch the notes again. If the checkout itself breaks after an update, the cause is often the same kind of conflict.

Two cases stay out of the notes on purpose. An email that is switched off, and an email skipped because there is no recipient, appear in the log only, not on the order. If the notes carry no email line at all and no error line either, check the log next, then check whether the move you made has an email at all.

Check spam, the address, and the inbox

Store owner checking her email inbox on a laptop

Many missing emails are not missing at all. They are sitting in a spam, junk, or promotions folder, or they went to a mistyped address. Ask the customer to search their whole mailbox for the store name or the order number, including spam and junk, and to check any tabs their mail service uses to sort mail.

Then check the address itself. Open the order and compare the billing email with the address the customer actually uses. A single mistyped letter sends the confirmation to the wrong inbox, and no mail setting can fix that. If the address is wrong, correct it on the order where possible, and ask the customer to check the corrected address carefully at checkout next time.

For a missing admin email, check the recipient address in the email settings and the admin inbox with the same care. An admin address that forwards to another mailbox, or a mailbox with strict filtering, can quietly swallow store mail while personal mail arrives normally.

Check the WooCommerce email settings

Go to WooCommerce, then Settings, then Emails. Find the email that is missing and open its settings. First, confirm that the notification is enabled. An email that is switched off will never send, however good the rest of the setup is, and this is an easy setting to miss after an update or a round of changes.

A WooCommerce new order email not working while customer emails arrive usually means the recipient address on the New order email is the first place to look.

Next, check the recipient for admin emails and the sender details for all store emails. The From address should use your own domain, for example an address at your store domain, rather than a free mailbox address. Mail from a free mailbox address sent through your own site often fails authentication checks at the receiving end, and some providers reject it outright. If the From address and the recipient address are the same mailbox, try a different recipient address for testing, because some mail setups handle same-domain mail in unexpected ways.

Keep a note of what each setting was before you change it. If a change makes things worse, you will want to return to the previous setup without guessing.

Find out whether WordPress can send any email at all

WooCommerce does not send mail by itself. It hands each email to the WordPress mail system, which by default uses the hosting server mail function. If that underlying system is not working, no WooCommerce email will arrive, and WooCommerce itself may show no clear error.

A simple test helps separate a WooCommerce problem from a mail problem. Try a WordPress password reset email to an address you control. If that email also fails to arrive, the problem is in the mail system or the hosting setup, not in one WooCommerce setting. If the password reset arrives but order emails do not, the problem is more likely in the WooCommerce email settings, the order status, or a plugin affecting WooCommerce emails.

The WooCommerce transactional email log records every attempt it makes. Go to WooCommerce, then Status, then Logs, and open the log source named transactional-emails. Each attempt is one line, and it records one of four outcomes.

OutcomeWhat it meansWhat to do next
SentWooCommerce built the email and passed it to the site mail system without an error. This does not prove the email reached an inbox.Treat it as a delivery problem: spam, authentication, or the receiving provider.
FailedWooCommerce tried, and the mail process returned an error. The log usually includes the reason.Read the reason, then fix the host mail setup, the SMTP connection, or the authentication.
DisabledThat email type is switched off in WooCommerce, then Settings, then Emails.Switch it on and test again.
SkippedA required condition was missing, most often no recipient.Fix the missing condition, then test again.

Sent and failed attempts also appear as private notes on the order. Disabled and skipped ones live in the log only. Two limits are worth knowing. The log is kept for 30 days unless you change the logging settings, and it names the recipient by username, or guest for a customer without an account, not by address. It also covers WooCommerce transactional mail only: WordPress password resets and other admin mail do not appear there, so check your SMTP provider log or a mail logging plugin for those.

One trap in that log: successful sends record at INFO level. A store set to errors only shows you the failures and hides every success, which makes a working store look silent. If you expect entries and see none, check WooCommerce, then Status, then Logs, then Settings, and confirm logging is switched on and the level is not hiding routine entries.

There is also a built-in test that needs no extra plugin. Open any email under WooCommerce, then Settings, then Emails. Below its settings is Email preview, with a Send a test email button, and the attempt is logged under transactional-emails as a test. Use it, but do not trust it alone: a test email calls the mail layer directly, with no order and no status change involved, so it can arrive while real orders send nothing. Always finish with a real test order and check both inboxes, the order notes, and the log.

Fix delivery with authenticated mail

Two colleagues working on email delivery at their laptops

When WordPress mail itself is unreliable, the usual fix is to send through an authenticated mail service instead of the hosting server default. This is done with an SMTP plugin, which connects WordPress to a real mail provider using login details or an API key from that provider. Widely used SMTP plugins include WP Mail SMTP and FluentSMTP. Choose one, not several at once, because two mail plugins can interfere with each other.

Installing a WooCommerce SMTP plugin alone changes nothing until you configure a mailer inside it. Until then it uses the same default PHP mailer as before, which does not improve anything. Run the plugin setup, choose your mail provider, enter the connection details exactly as the provider gives them, and only then send the test email.

The setup follows the same pattern whichever plugin you use. Install and activate the plugin, choose your mail provider in its settings, enter the connection details exactly as the provider gives them, and set the From address to an address on your own domain. Then use the plugin test email tool to send a test message to an inbox you control. Only when the test message arrives in the inbox, not in spam, should you place a real test order and check that the order emails arrive as well.

One more thing the address has to survive. If your SMTP plugin has Force From Email switched on, the address that leaves may not be the one you set in WooCommerce. The store name can come from WooCommerce while the address comes from the plugin, and you will see your store name in the From line and reasonably assume the address is yours too. That setting is not a fault, and keeping one consistent sender address is what your SPF and DKIM records rest on. Set the same address in both places, in WooCommerce and in the plugin, and the question goes away.

Keep the provider details private. Connection details and API keys belong in the plugin settings only, never in a post, a screenshot shared in public, or a support thread where others can read them.

Add domain authentication so mail reaches the inbox

Even with authenticated sending, mail can still land in spam if the sending domain is not properly authenticated. Three records work together here, and each has a plain job. SPF lists which servers are allowed to send mail for your domain. DKIM adds a signature that shows the message was not changed on its way. DMARC tells receiving providers what to do when a message fails those checks, and helps protect your domain from being spoofed.

Your mail provider will give you the exact records to add, and you add them in the DNS settings where your domain is managed, usually at your domain registrar or your hosting account. Copy the records exactly, and allow time for them to spread across the internet before judging the result. Copying records from another site, or from a guide for a different provider, will not work, because the records must match your own domain and your own provider.

Three details catch people out. First, a domain can have only one SPF record, so edit the one you have rather than adding a second, because two SPF records invalidate both. Second, start DMARC at p=none, which is monitoring only, and tighten it only once your reports look clean. Third, alignment matters: for DMARC to pass, the domain that passes SPF or DKIM has to match the domain in the From address, which is why the From address must sit on the domain you verified with your provider.

The large providers have also tightened the rules for bulk senders. Since February 2024, Gmail and Yahoo require senders of more than 5,000 emails a day to authenticate with SPF, DKIM and DMARC, and Google requires every sender to Gmail to have at least SPF or DKIM. Since 5 May 2025, Microsoft requires the same of domains sending more than 5,000 emails a day to Outlook.com, Hotmail, Live or MSN addresses: SPF and DKIM must pass, and a DMARC record of at least p=none must align with one of them, or the mail is rejected. A small store sending a few dozen order emails a day is under those thresholds, but the same three records are what keep its mail out of spam, so set them up the same way.

If your store sends through a Microsoft 365 mailbox with a password, plan the move now. Microsoft is switching basic username-and-password SMTP sign-in off by default for existing organisations at the end of December 2026, though administrators can switch it back on, and a final removal date will be announced in the second half of 2027. Pick the plugin option that signs in with OAuth, the sign in with Microsoft or Google style of login, rather than a stored password, or move the store mail to a transactional email service.

If DNS records feel unfamiliar, this is a sensible point to ask for help rather than guessing. A wrong DNS change can affect more than email, so change one record at a time and keep a note of what was there before.

Check for a plugin or theme conflict, safely

A plugin that changes emails, a security plugin that blocks outgoing mail, or a recent update can stop order emails without any obvious error. Email customiser plugins are a common suspect, because they take over how WooCommerce emails are built, but any recently changed plugin is worth considering.

Test for a conflict on a staging copy of the site first, not on the live store during a busy period. On staging, switch off the suspected plugins one at a time and place a test order after each change. When the emails start arriving, you have found the likely cause. Then decide whether to keep that plugin off, look for a replacement, or ask its support team about the conflict. Making a backup before changing plugins on a live site is good practice, and it gives you a safe way back if a change causes a new problem.

Also check that WooCommerce, WordPress, and the theme are up to date, and test again after updates. An outdated template or an old plugin version can break an email that used to work, and an update can quietly fix it. Keeping updates, backups, and routine checks on a regular schedule is the core of our WordPress maintenance plans.

Check whether your emails are waiting in a queue

WooCommerce has a deferred transactional emails feature under Settings, then Advanced, then Features. With it on, order emails move into a scheduled queue instead of sending during checkout, which makes checkout faster but means your emails now depend on that queue running. If WordPress cron is broken, or switched off without a real server cron job behind it, nothing sends and there is no visible error.

Check it in one place. Go to WooCommerce, then Status, then Scheduled Actions, and look at the Pending and Failed tabs. Email jobs sitting there untouched for minutes mean your queue has stopped, which is a scheduling problem, not a mail one. Fix the cron setup first; changing mail providers will not help while the queue is stalled. The same check applies if a plugin or custom setup defers transactional emails or queues them some other way.

When the problem is with the host or the gateway

Some causes sit outside WooCommerce entirely. A host may block the default server mail function to fight spam, in which case authenticated sending through an SMTP provider is the practical answer. A payment gateway that is slow to confirm payments will delay the Processing email until it responds. A mail server with a poor reputation may have its mail filtered by large providers even when everything on the site is set up correctly.

Some hosts block the mail ports outright. DigitalOcean, for example, blocks ports 25, 465 and 587 on its Droplets. If your host blocks the port your provider uses, ask the host which outgoing ports it allows, or use your plugin API option for the service instead, which runs over a normal secure web connection and is not affected by blocked mail ports. Some services also accept port 2525. The error message usually tells you which case you are in: a connection timeout points at a blocked port, while an authentication error points at wrong credentials.

When you contact your host, give them useful detail: which email is missing, one order number, the time the order was placed, and what the transactional email log shows. That helps them check their own logs instead of starting from scratch. If the host confirms a block or a reputation problem, authenticated sending and proper domain authentication are still the steps that help store mail reach the inbox.

A checklist to run in order

  1. Identify which email is missing, and whether it affects the admin, the customer, or both.
  2. Check the order status. Pending payment and Failed orders do not trigger a normal confirmation.
  3. Check spam, junk, and promotions folders, and confirm the billing and admin addresses are correct.
  4. Confirm the email is enabled in WooCommerce, then Settings, then Emails, and check the From address.
  5. Test whether WordPress mail works at all with a password reset email.
  6. Check the WooCommerce transactional email log to see whether WooCommerce tried to send.
  7. Set up authenticated sending with one SMTP plugin and one mail provider, then send a test email.
  8. Add the SPF, DKIM, and DMARC records your provider gives you, exactly as given.
  9. Test for a plugin conflict on staging, one plugin at a time, with a test order after each change.
  10. Place a real test order and confirm the admin and customer emails arrive in the inbox.
  11. After you fix the cause, resend any missed emails from the Order actions box on the order: Send order details to customer, or Resend new order notification for the admin email.

Frequently asked questions

Why does the admin get the new order email but the customer gets nothing?

These are separate emails with separate settings. Start by checking the order status, because the customer confirmation only sends when the order reaches Processing, then check that the Processing order notification is enabled and that the customer address is correct. If the admin email arrives, the mail system is working at some level, so the cause is more likely one of those settings than a total mail failure.

Why does the customer get an email but the admin does not?

Check the recipient address on the New order email in WooCommerce, then Settings, then Emails. An admin address that is mistyped, that forwards elsewhere, or that sits behind strict filtering will miss store mail while customer mail arrives normally. Try a different recipient address for testing to separate an address problem from a sending problem.

The order is Processing but no email arrived. What now?

A WooCommerce Processing order email not sending usually means one of three things: the notification is off, the log shows a failure, or delivery is being filtered. Check spam and the billing address first, then confirm the Processing order notification is enabled. Then open the order and read its notes: since WooCommerce 10.9, every email attempt leaves a note there. If the notes carry no email line at all, WooCommerce never built the message, and an SMTP plugin cannot help; look for an error line naming the plugin that threw during the status change, or check whether the email is switched off. If the notes say the email was sent, the problem is in delivery or filtering, and authenticated sending with domain authentication is the next step. If there is no log entry either, check that logging is switched on and the log level is not hiding routine entries, under WooCommerce, then Status, then Logs, then Settings.

Why do order emails always land in spam?

WooCommerce order emails going to spam usually point to authentication or sender reputation, not to WooCommerce itself. Use a From address on your own domain, send through an authenticated provider, and add the SPF, DKIM, and DMARC records your provider gives you. Also ask customers to mark a genuine order email as not spam, which helps their own mailbox learn to trust future mail from your store.

Do I need an SMTP plugin if emails used to work?

Not always. If a setting was switched off, an address changed, or a plugin update broke something, fixing that may be enough. But if WordPress mail itself has become unreliable, or if mail keeps landing in spam, authenticated sending is the reliable fix, because it replaces an unauthenticated default with a login that receiving providers can trust.

My test email arrives but real orders send nothing. Why?

Because a test email skips the part that breaks. A test calls the mail layer directly, with no order and no status change involved. Real orders build their emails during the status change, and a plugin that throws at that moment stops them. Open the failed order and read its notes. If you see a line reading Error during status transition, followed by a reason, that reason names the plugin that threw. Switch that plugin off on staging, place a test order, and watch the notes again.

Where is the WooCommerce transactional email log, and what do Sent, Failed, Disabled and Skipped mean?

Go to WooCommerce, then Status, then Logs, and open the log source named transactional-emails. It records every WooCommerce transactional email attempt since WooCommerce 10.9. Sent means WooCommerce built the email and passed it to the site mail system without an error; it does not prove the email reached an inbox. Failed means WooCommerce tried and the mail process returned an error, and the log usually includes the reason. Disabled means that email type is switched off in WooCommerce, then Settings, then Emails. Skipped means a required condition was missing, most often no recipient. Sent and failed attempts also appear as private notes on the order; disabled and skipped ones live in the log only. If you expect entries and see none, check WooCommerce, then Status, then Logs, then Settings: logging must be switched on, and the level must not be hiding routine entries.

The customer gets nothing when I cancel an order. Is that normal?

Yes, as WooCommerce ships it. Cancelling tells the admin, but the customer version of the Cancelled order email is switched off by default, so the customer hears nothing. Switch it on at WooCommerce, then Settings, then Emails, then Cancelled order. Ten seconds, and the gap closes.

I moved a paid order to On hold and nobody got an email. Is that a fault?

No. WooCommerce has no email for that move. Moving an order from Processing back to On hold sends nothing to the customer and nothing to you. If you park a paid order on hold while you check stock, tell the customer yourself, because they will otherwise hear nothing at the moment they most want news.

Can I send store emails through my Gmail or Microsoft 365 mailbox?

You can, with two warnings. Gmail and Google Workspace need an app password, which Google only offers on accounts with 2-Step Verification switched on, and an app password stops working when the account password changes. Microsoft 365 accepts an address and password for SMTP only while your administrator allows that kind of sign-in; Microsoft is switching password sign-in off by default for existing organisations at the end of December 2026, though administrators can switch it back on. For either mailbox, pick the plugin option that signs in with OAuth, the sign in with Microsoft or Google style of login, rather than a stored password. A transactional email service is the steadier choice for a busy store, because it is built for automated mail and gives you a clear answer when it refuses a message. If your customers report WooCommerce emails not sending to Gmail, the first checks are the same: a From address on your own domain, and the SPF, DKIM and DMARC records in place.

I fixed the cause. How do I send the missed order emails again?

Use the Order actions box on the order. Choose Send order details to customer to send the customer email again, or Resend new order notification to send the admin email again. Fix the cause first and send a test, or the resend will fail the same way. If the customer typed their address wrong, correct it on the order, save, and then send again from Order actions.

Conclusion

WooCommerce order emails not sending feel alarming, but they reward a calm, ordered approach. Work out which email is missing, check the order status and the addresses, confirm the email is enabled, find out whether WordPress mail works at all, and only then move to authenticated sending and domain authentication. Test after each change that could fix the problem, and keep a note of what you changed. That way, when the next order comes through, you will know the confirmation reached the people who need it.

If email trouble keeps coming back, or if the fix involves DNS records and mail providers you would rather not touch alone, Raozan IT can help. Our team builds and looks after WooCommerce stores: new store builds are covered by our WooCommerce development work, and regular store care, including update and email checks, is part of our WooCommerce maintenance work. For a store build or a care plan, talk to us through WhatsApp on +8801735127127, through the contact page, or by email at [email protected]. For more on how store emails are meant to work, see the official WooCommerce email settings documentation and the WooCommerce email troubleshooting documentation.

Scroll to Top