{"id":23053,"date":"2026-08-31T06:30:46","date_gmt":"2026-08-31T04:30:46","guid":{"rendered":"https:\/\/www.curiaweb.ch\/?post_type=docs&p=23053"},"modified":"2026-08-31T06:30:47","modified_gmt":"2026-08-31T04:30:47","password":"","slug":"woocommerce-emails-are-not-being-sent","status":"publish","type":"docs","link":"https:\/\/www.curiaweb.ch\/en\/hilfe\/cms-online-shops\/woocommerce-emails-werden-nicht-versendet\/","title":{"rendered":"WooCommerce is not sending emails: Systematically checking causes"},"content":{"rendered":"

An order exists in the WooCommerce backend, but the customer is not receiving an order confirmation? Or you yourself are not receiving a notification about new orders?<\/p>\n\n\n\n

Then you shouldn't install plugins right away or change settings on a whim. With WooCommerce emails, there are several places where a problem can arise.<\/p>\n\n\n\n

Simplified, a message takes this path:<\/p>\n\n\n\n

WooCommerce \u2192 WordPress \u2192 Mail system \u2192 Receiving mail server \u2192 Inbox<\/strong><\/p>\n\n\n\n

Therefore, the most important question is first: Did WooCommerce trigger the expected email at all?<\/strong><\/p>\n\n\n\n

Important:<\/strong> \u201eWooCommerce has sent the email and the customer has received the email are not the same thing. A message can successfully leave WooCommerce and still be rejected or classified as spam later.<\/p>\n\n\n\n

Start with the affected order<\/h2>\n\n\n\n

If a certain order confirmation email is missing, first open the respective order under WooCommerce \u2192 Orders<\/strong>.<\/p>\n\n\n\n

Check the order status and the customer's saved email address. Also check the order notes, as WooCommerce and payment extensions store important information there regarding status changes and sometimes also email delivery.<\/p>\n\n\n\n

An incorrectly entered customer address cannot be fixed by changes to the mail server. Likewise, not every WooCommerce email is triggered for every order status.<\/p>\n\n\n\n

For example, if an order still stands on Payment pending<\/strong>, even though you are expecting an email that is only triggered after successful payment, you must first find out why the payment or the status change did not occur.<\/p>\n\n\n\n

We explain the individual statuses in the article WooCommerce Order Status Simply Explained<\/a>.<\/p>\n\n\n\n

Check if the email in question is activated<\/h2>\n\n\n\n

Open:<\/p>\n\n\n\n

WooCommerce \u2192 Settings \u2192 Emails<\/strong><\/p>\n\n\n\n

Select the notification there that is not working.<\/p>\n\n\n\n

Check if this notification is enabled. For emails to the store owner, you should also check whether the correct recipient address has been entered.<\/p>\n\n\n\n

In customer emails, the recipient address usually comes from the order or the customer account. Therefore, check there for typos as well.<\/p>\n\n\n\n

We explain in detail how to set up the individual notifications in the article Set up WooCommerce emails and order notifications<\/a>.<\/p>\n\n\n\n

The WooCommerce email log is the most important next step<\/h2>\n\n\n\n

Current WooCommerce versions log the sending of their transactional emails. This allows you to determine much more precisely what actually happened.<\/p>\n\n\n\n

Open:<\/p>\n\n\n\n

WooCommerce \u2192 Status \u2192 Logs<\/strong><\/p>\n\n\n\n

Search or filter there by source:<\/p>\n\n\n\n

transactional emails<\/strong><\/p>\n\n\n\n

If necessary, trigger the exact email you want to examine with a test order and check the corresponding entry.<\/p>\n\n\n\n

WooCommerce distinguishes four particularly helpful results:<\/p>\n\n\n\n

Entry<\/th>Meaning<\/th><\/tr><\/thead>
Sent<\/strong><\/td>WooCommerce has successfully passed the email to the downstream mail system.<\/td><\/tr>
Failed<\/strong><\/td>WooCommerce attempted to send, but the mail function has returned an error.<\/td><\/tr>
Disabled<\/strong><\/td>The WooCommerce email in question is disabled.<\/td><\/tr>
Skipped<\/strong><\/td>WooCommerce didn't send the message because a required prerequisite was missing, such as a recipient.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

For order-related emails, successful and failed shipping attempts are additionally saved as private order notes. Disabled or skipped emails, on the other hand, can only be found in the email log.<\/p>\n\n\n\n

Privacy Policy:<\/strong> WooCommerce does not simply write complete customer email addresses into the log. Recipients are displayed there as an associated WordPress user or as a guest, for example; email addresses in error messages are redacted.<\/p>\n\n\n\n

If it says \u201eDisabled\u201c in the log<\/h2>\n\n\n\n

This case is relatively simple: WooCommerce has determined that the notification in question is disabled.<\/p>\n\n\n\n

Open WooCommerce \u2192 Settings \u2192 Emails<\/strong>, select the message in question and activate it if it is actually to be sent.<\/p>\n\n\n\n

Then perform a new controlled test.<\/p>\n\n\n\n

If \u201eSkipped\u201c appears in the log<\/h2>\n\n\n\n

At Skipped<\/strong> the message was not sent because a required prerequisite was missing.<\/p>\n\n\n\n

One possible example is a missing recipient address.<\/p>\n\n\n\n

Therefore, check the information in the log as well as the relevant order and email configuration. Fix the cause identifiable there before searching on the mail server or in the DNS settings.<\/p>\n\n\n\n

If the log says \u201eFailed\u201c<\/h2>\n\n\n\n

Failed<\/strong> means that WooCommerce attempted to send the message, but the sending process returned an error.<\/p>\n\n\n\n

The log entry usually contains additional information on the reported cause. This error message is significantly more helpful for further diagnosis than the general statement \u201eWooCommerce is not sending emails\u201c.<\/p>\n\n\n\n

In this case, you should investigate the technical email delivery of the WordPress installation. Depending on the configuration, this can involve the web server's email delivery, an SMTP connection, or an external transactional email service.<\/p>\n\n\n\n

Also check under WooCommerce \u2192 Status \u2192 Logs<\/strong>, whether additional errors or serious PHP errors were logged at the same time.<\/p>\n\n\n\n

Do not change settings at random:<\/strong> If WooCommerce already provides a specific error message, it should be investigated first. Making multiple changes at the same time often makes the cause harder to trace later.<\/p>\n\n\n\n

If the log says \u201eSent\u201c, the problem is likely further along the delivery path<\/h2>\n\n\n\n

Sent<\/strong> means that WooCommerce has successfully handed over the message to the mail system.<\/p>\n\n\n\n

It does not mean that the receiving mail server will accept the message or that the customer has seen it in their inbox.<\/p>\n\n\n\n

From this point on, you should therefore no longer primarily look for an incorrect WooCommerce order status, but instead investigate the actual email sending and delivery.<\/p>\n\n\n\n

First, check the recipient's spam or junk folder. If you are sending via SMTP or an external mail service, check its delivery log. Depending on the provider, you can use it to determine whether the message was accepted, forwarded, rejected, or otherwise handled.<\/p>\n\n\n\n

\n

Note:<\/strong> WooCommerce can confirm that it has passed a message to the mail system. The final delivery can only be confirmed by the further mail infrastructure.<\/p>\n<\/blockquote>\n\n\n\n

If there is no entry at all<\/h2>\n\n\n\n

If a WooCommerce email should have been triggered, but no corresponding entry appears in the log, the problem lies earlier in the processing.<\/p>\n\n\n\n

Check again whether the expected event has actually occurred. In the case of an order, this means in particular: Was the payment successfully processed and has the order reached the expected status?<\/p>\n\n\n\n

Check the WooCommerce logs for fatal errors afterwards. Conflicts with plugins, extensions, the theme, or custom code can also affect normal operation.<\/p>\n\n\n\n

During an online payment, you should also check whether the payment provider has correctly reported the payment back to WooCommerce. You can find out more at Setting up and managing payment methods in WooCommerce<\/a>.<\/p>\n\n\n\n

Check the sender address<\/h2>\n\n\n\n

WooCommerce recommends using an address on your website's domain for the sender address.<\/p>\n\n\n\n

For a store at:<\/p>\n\n\n\n

www.meinshop.ch<\/strong><\/p>\n\n\n\n

would be, for example, a sender address like:<\/p>\n\n\n\n

shop@meinshop.ch<\/strong><\/p>\n\n\n\n

technically much more sensible than a third-party public sender address like a Gmail or Yahoo address.<\/p>\n\n\n\n

The reason: If your web server claims to be sending on behalf of a third-party domain even though it is not authorized to do so, receiving mail servers may classify the message as suspicious or reject it.<\/p>\n\n\n\n

You can find the WooCommerce sender address under WooCommerce \u2192 Settings \u2192 Emails<\/strong>.<\/p>\n\n\n\n

Check SPF, DKIM and DMARC<\/h2>\n\n\n\n

For reliable email delivery, WooCommerce is not the only relevant factor. The sender domain must also match the sending method used.<\/p>\n\n\n\n

Three methods play a particularly important role in this context:<\/p>\n\n\n\n

Procedure<\/th>Task explained simply<\/th><\/tr><\/thead>
SPF<\/strong><\/td>Define which systems are allowed to send emails for a domain.<\/td><\/tr>
DKIM<\/strong><\/td>Signs messages with a cryptographic signature that the recipient can verify using DNS.<\/td><\/tr>
DMARC<\/strong><\/td>Links, among other things, the sender domain with SPF\/DKIM checks and enables policies for incorrectly authenticated messages.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Incorrect or missing authentication does not necessarily mean that an email cannot be sent at all. However, it can have a significant impact on whether a receiving mail server trusts the message.<\/p>\n\n\n\n

Important:<\/strong> SPF, DKIM, and DMARC are not configured in the regular WooCommerce email settings. They belong to the domain and mail server configuration or the mail service being used.<\/p>\n\n\n\n

SMTP can make sending more reliable and traceable<\/h2>\n\n\n\n

WordPress uses the function by default wp_mail()<\/strong>. WooCommerce passes its emails to this WordPress mail function.<\/p>\n\n\n\n

Depending on the hosting and mail configuration, messages are then forwarded via the server's mail infrastructure.<\/p>\n\n\n\n

For an online shop, an authenticated SMTP or transactional mail service may be useful instead. In this process, WordPress is connected to a dedicated mail system designed for this purpose.<\/p>\n\n\n\n

The process then looks something like this in simplified form:<\/p>\n\n\n\n

WooCommerce \u2192 WordPress \u2192 authenticated mail service \u2192 recipient<\/strong><\/p>\n\n\n\n

Such a service can often also provide more detailed information on the further processing of a message, in addition to the actual sending.<\/p>\n\n\n\n

SMTP is not a repair button for every email problem.<\/strong> If WooCommerce does not trigger an email at all, another transport method will not fix this problem. Therefore, first check the WooCommerce log to find out where the error occurs.<\/p>\n\n\n\n

If only individual recipients do not receive emails<\/h2>\n\n\n\n

If some customers receive the WooCommerce emails without any issues while messages to a specific address or a specific mail provider are missing, this rather speaks against a complete failure of the WooCommerce mail dispatch.<\/p>\n\n\n\n

In this case, check the affected email address, the WooCommerce log, and \u2013 if available \u2013 the sending log of your mail service in particular.<\/p>\n\n\n\n

The spam filter or receiving mail server's acceptance rules can also play a role.<\/p>\n\n\n\n

When troubleshooting, test with another external email address if possible. This makes it easier to determine whether the issue is general or occurs only with a specific recipient.<\/p>\n\n\n\n

If only the shop owner receives no notifications<\/h2>\n\n\n\n

If customers receive their order emails, but you yourself do not receive a notification about new orders, for example, you should first check the recipient address of the WooCommerce admin email.<\/p>\n\n\n\n

Open WooCommerce \u2192 Settings \u2192 Emails \u2192 New order<\/strong> and check the recipients entered there.<\/p>\n\n\n\n

Then you check that again transactional emails<\/strong>-Log. This is how you can determine whether the administrator notification was triggered independently of the customer email.<\/p>\n\n\n\n

A working customer email does not automatically prove that every administrator notification is also configured correctly.<\/p>\n\n\n\n

If only certain WooCommerce emails are missing<\/h2>\n\n\n\n

If, for example, emails for completed orders work, but another notification is missing, the basic email transmission has obviously not failed completely.<\/p>\n\n\n\n

Then focus on the notification in question:<\/p>\n\n\n\n

Is it activated? Is a recipient available? Has the required order status been reached? What does the transactional emails<\/strong>-Protocol specifically for this type of email?<\/p>\n\n\n\n

How to avoid reconfiguring a working mail server when the actual problem lies in a single WooCommerce setting.<\/p>\n\n\n\n

Check plugins and themes as a cause<\/h2>\n\n\n\n

WooCommerce emails can be influenced by additional plugins or custom code. This particularly affects payment extensions, email customizations, checkout extensions, and plugins that modify order statuses or order processes.<\/p>\n\n\n\n

A technical error in a plugin or theme can also interrupt the processing.<\/p>\n\n\n\n

If the logs indicate a conflict and the cause cannot be identified otherwise, a controlled conflict test can be useful. This checks whether the problem still occurs with WooCommerce and a standard environment.<\/p>\n\n\n\n

Do not disable uncontrolled in the live shop:<\/strong> On a live WooCommerce store, disabled payment, shipping, or checkout plugins can affect order processing. You should therefore perform an extensive conflict test in a safe test or staging environment whenever possible.<\/p>\n\n\n\n

Check scheduled actions when messages are delayed<\/h2>\n\n\n\n

Not every extension processes all emails immediately. WooCommerce and numerous extensions use the so-called background tasks for Action Scheduler<\/strong>.<\/p>\n\n\n\n

You can find the planned actions at:<\/p>\n\n\n\n

WooCommerce \u2192 Status \u2192 Scheduled Actions<\/strong><\/p>\n\n\n\n

There you can see, among other things, whether tasks are pending or have failed.<\/p>\n\n\n\n

By default, Action Scheduler uses WordPress WP-Cron to execute its tasks. If WP-Cron does not function reliably or if background tasks pile up, features processed via such scheduled actions may also be affected.<\/p>\n\n\n\n

This point is particularly relevant when an extension sends emails with a time delay or in the background. For a normal WooCommerce core order email, however, you should first the transactional emails<\/strong>- Check the log and do not automatically assume a cron problem.<\/p>\n\n\n\n

The right order saves a lot of time<\/h2>\n\n\n\n

If a WooCommerce email is missing, you can narrow down the troubleshooting to this sequence:<\/p>\n\n\n\n

Exam<\/th>Question<\/th><\/tr><\/thead>
1. Order<\/strong><\/td>Does the order exist and does it have the expected status?<\/td><\/tr>
2. Recipient<\/strong><\/td>Is the email address correct?<\/td><\/tr>
3. WooCommerce Setting<\/strong><\/td>Is the notification in question enabled?<\/td><\/tr>
4. WooCommerce Log<\/strong><\/td>Does it say Sent, Failed, Disabled, Skipped, or is the attempt missing entirely?<\/td><\/tr>
5. Mail System<\/strong><\/td>Did WordPress or the mail service used process the message further?<\/td><\/tr>
6. Authentication<\/strong><\/td>Do sender domain, SPF, DKIM, and DMARC match the transmission path?<\/td><\/tr>
7. Recipient<\/strong><\/td>Was the message accepted by the destination server or filtered, for example?<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

With this sequence, you can narrow down the problem step by step instead of changing settings on a whim.<\/p>\n\n\n\n

A practical example<\/h2>\n\n\n\n

A customer reports that they have not received an order confirmation.<\/p>\n\n\n\n

First, you open his order and determine that it has been paid correctly and has the expected status. The email address is also correct.<\/p>\n\n\n\n

Under WooCommerce \u2192 Settings \u2192 Emails<\/strong> the corresponding customer notification is enabled.<\/p>\n\n\n\n

Then you open WooCommerce \u2192 Status \u2192 Logs \u2192 transactional-emails<\/strong>.<\/p>\n\n\n\n

Can you find that there for this message Sent<\/strong>, You know: WooCommerce has done its job and passed the message to the mail system. Now you are investigating the further delivery path.<\/p>\n\n\n\n

It stands in contrast to that Failed<\/strong>, you investigate the logged error message.<\/p>\n\n\n\n

At Disabled<\/strong> Are you correcting the WooCommerce setting? At Skipped<\/strong> are you looking for the missing prerequisite.<\/p>\n\n\n\n

With that, you have already turned \u201eThe customer does not receive an email\u201c into a much more precise technical diagnosis.<\/p>\n\n\n\n

Always retest after a correction<\/h2>\n\n\n\n

Once you have found and fixed a cause, run a new test order or a controlled new email dispatch.<\/p>\n\n\n\n

Afterwards, check not only whether the message was received, but also:<\/p>\n\n\n\n