Pingverablog ← Blog
Home › Blog › WooCommerce Not Sending Order Emails: Find the Cause Before Black Friday

WooCommerce Not Sending Order Emails: Find the Cause Before Black Friday

November 9, 2026 · 13 min read

WooCommerce Not Sending Order Emails: Find the Cause Before Black Friday

When WooCommerce is not sending order emails, the fault sits in one of three places. The email may never be triggered, because the order status did not change or the notification is switched off. WordPress may fail to hand it to a mail server. Or the mail server sends it and Gmail or Outlook rejects it or files it as spam. WooCommerce's own troubleshooting page puts it plainly: "Often, email issues are deliverability issues, where your server is sending the email, but it's not being received."

You can tell the three apart in about thirty minutes. Open the WooCommerce email log under WooCommerce > Status > Logs, check the order notes on a recent order, send a test email from the email settings screen, and confirm that your sending domain passes SPF, DKIM and DMARC. Do it before Black Friday (27 November 2026). If your store sends through a Microsoft 365 mailbox with a username and password, add one more check to the list: Microsoft plans to disable that method by default at the end of December 2026.

At a glance

  • WooCommerce sends mail through WordPress's wp_mail() function. Orders left in Pending payment trigger no email at all, so a payment callback problem can look like an email problem.
  • Recent WooCommerce versions write each transactional email attempt to a log with the source transactional-emails, marked Sent, Failed, Disabled or Skipped. Failed attempts also appear as order notes.
  • Since November 2025, Gmail has been "ramping up its enforcement on non-compliant traffic", including temporary and permanent rejections of messages that miss its sender requirements.
  • Outlook.com requires SPF, DKIM and DMARC from domains sending more than 5,000 messages a day, and Microsoft documents the rejection code 550 5.7.515.
  • Microsoft says SMTP AUTH basic authentication will be disabled by default for existing Exchange Online tenants at the end of December 2026. Store mail sent through smtp.office365.com with a plain password will need OAuth or another sending route.

Why it matters now

Order confirmations do more work at peak than in any other month. A customer who gets no confirmation writes to support or places a second order to be safe. Shop staff who rely on the admin "New order" email may not see orders until someone opens the dashboard. None of this shows up on an uptime monitor, because the store loads and checkout completes.

Three changes make this year's check different from last year's.

Gmail's sender rules apply to transactional mail. Google's sender guidelines have required, since 1 February 2024, that anyone sending to personal Gmail accounts set up SPF or DKIM, keep valid forward and reverse DNS (PTR) records, use TLS, and keep the spam rate in Postmaster Tools below 0.3%. Senders of roughly 5,000 or more messages a day to Gmail must also publish DMARC and align the From: domain with SPF or DKIM. The one-click unsubscribe rule excludes transactional messages; the authentication rules do not. Google's FAQ states that from November 2025 "messages that fail to meet the email sender requirements will experience disruptions, including temporary and permanent rejections." A store that has run on a half-configured SMTP setup for years may only now be losing mail.

Outlook.com set its own bar. Microsoft's April 2025 announcement for Outlook.com (hotmail.com, live.com and outlook.com addresses) requires domains sending more than 5,000 emails a day to pass SPF and DKIM and to publish DMARC of at least p=none, aligned with SPF or DKIM. The post gives 5 May 2025 as the start date and lists the rejection response 550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level. A store that sends 300 order emails a day may sit below that threshold, but the newsletter tool on the same domain often does not. Your order emails share the domain's reputation either way.

Microsoft 365 SMTP basic auth has a date. Many small stores send WooCommerce mail through an SMTP plugin that logs in to a Microsoft 365 mailbox at smtp.office365.com with a username and password. Microsoft's updated timeline, published 27 January 2026, says SMTP AUTH basic authentication behaviour "remains unchanged" until December 2026. At the end of December 2026 it will be "disabled by default for existing tenants", though administrators can re-enable it. Microsoft will announce the final removal date in the second half of 2027. Its earlier post gives the error clients see once basic auth is off: 550 5.7.30 Basic authentication is not supported for Client Submission. For a store, that lands in the January returns period, when refund and exchange emails matter.

Step-by-step: find where order emails stop

Work through these in order. Each step rules out one layer.

  1. Check the order status. Open three recent orders. WooCommerce's documentation says "if your new orders have a Pending Payment status, no email will be sent", while orders that move to Processing "should generate an email if the email notification is enabled". If paid orders sit in Pending payment, fix the payment callback first. Our guide on orders marked as paid without payment covers the webhook side.
  2. Check the notification settings. Go to WooCommerce > Settings > Emails. Open "New order" and confirm the box "Enable this email notification" is ticked and the recipient list holds an address someone reads. WooCommerce defaults it to the site administrator email from Settings > General, which is often a developer's old address. Then open "Processing order", "Completed order" and "Refunded order", the customer-facing ones.
  3. Read the email log. Go to WooCommerce > Status > Logs and choose the source transactional-emails. Each entry carries a status. Disabled or Skipped points back to step 2. Failed means WordPress could not hand the message to a mail server, and you should look for a matching note on the order. WooCommerce does not write raw customer email addresses to this log, so match entries by order number and time.
  4. Send a test email. On the same Emails screen, use the preview's "Send a test email" option and send to a personal Gmail address and an Outlook.com address. If the test arrives and real orders do not, a plugin or custom code is changing the order flow. If the test does not arrive either, continue to step 5.
  5. Identify the sending route. Find out which plugin or service sends mail: an SMTP plugin, a transactional email provider's plugin, or the host's PHP mail. With no SMTP plugin at all, mail leaves through the web server, usually from an IP address that has no aligned SPF or DKIM for your domain. WooCommerce's guide recommends a dedicated SMTP provider.
  6. Check the From address. WooCommerce warns that using a @gmail.com or @yahoo.com address as the sender "is likely to cause emails to land in spam folders" and recommends an address on your own domain. Set the "From" address under the email sender options to something like orders@yourstore.example.
  7. Check DNS authentication. Look up the SPF, DKIM and DMARC records for the sending domain and confirm that the provider you found in step 5 is included in SPF and signs with DKIM on your domain. Send a test to a Gmail account and use "Show original" to confirm SPF, DKIM and DMARC each show PASS. Our article on how SPF, DKIM and DMARC break goes through the common failures.
  8. Read the provider's bounce log. Your SMTP provider or mailbox shows rejections with codes. Gmail's FAQ lists temporary codes such as 4.7.27 (SPF) and 4.7.30 (DKIM) with permanent 5.7.x equivalents. Outlook.com uses 5.7.515. Microsoft 365 basic auth failures show 5.7.30.
  9. Check Microsoft 365 authentication. If step 5 found smtp.office365.com with a password, ask the Microsoft 365 administrator to check the SMTP AUTH clients report in the Exchange admin center. Plan a move to OAuth (if your SMTP plugin supports it) or to a transactional email provider before the end of December.

Who checks what, and how often

Risk Owner Check Frequency
Notification switched off or sent to a dead inbox Store owner WooCommerce > Settings > Emails, recipients for "New order" Monthly and after staff changes
Email fails at hand-off Developer or agency transactional-emails log, order notes with failures Weekly; daily during peak
Authentication breaks after a DNS or provider change Agency or whoever manages DNS SPF, DKIM and DMARC PASS in a Gmail "Show original" After every DNS change, and monthly
Rejections at Gmail or Outlook.com Developer or agency Provider bounce log for 4.7.x, 5.7.x and 5.7.515 codes Weekly; daily during peak
Microsoft 365 SMTP basic auth disabled Microsoft 365 admin SMTP AUTH clients report; plugin authentication method Once before December 2026
Paid orders stay in Pending payment Developer Order status vs. payment provider records Daily during peak

Copyable test plan

Paste this into your ticket or maintenance checklist and fill in the results.

WooCommerce order email test plan (run before 20 Nov and after any mail or DNS change)

Store: ____________   Tester: ____________   Date: ____________

[ ] 1. Sending route recorded: plugin ______  provider/host ______  auth: password / OAuth / API key
[ ] 2. From address on own domain: ______________________
[ ] 3. WooCommerce > Settings > Emails: New order, Processing, Completed, Refunded all enabled
[ ] 4. New order recipients reach a monitored inbox: ______________________
[ ] 5. "Send a test email" delivered to Gmail inbox (not spam)       Y / N
[ ] 6. "Send a test email" delivered to Outlook.com inbox (not junk) Y / N
[ ] 7. Gmail "Show original": SPF ____  DKIM ____  DMARC ____ (expect PASS x3)
[ ] 8. Place one real low-value order with a live payment method
       - Order status after payment: ____________ (expect Processing)
       - Customer email received in ___ minutes
       - Admin "New order" email received in ___ minutes
[ ] 9. WooCommerce > Status > Logs > transactional-emails: entries show Sent for steps 5-8
[ ] 10. Provider bounce log checked for the last 7 days: ___ rejections, codes: ______
[ ] 11. If smtp.office365.com with password: migration plan and date: ______
[ ] 12. Refund the test order and confirm the Refunded order email arrives

Worked scenario (illustrative)

A homeware store on WooCommerce takes around 120 orders a day in November. The numbers here are illustrative. Its agency set up an SMTP plugin in 2023 that logs in to orders@ on the shop's Microsoft 365 tenant with a password.

In the second week of January, support tickets rise: customers say their refund was promised but no email came. The agency opens WooCommerce > Status > Logs, filters transactional-emails and sees Failed entries starting on one day, with matching notes on each refunded order. The SMTP plugin's debug output shows 550 5.7.30 Basic authentication is not supported for Client Submission. The tenant's administrator confirms Microsoft disabled SMTP basic auth by default. The administrator re-enables it as a stopgap, which Microsoft's timeline still allows. The agency then moves sending to OAuth in the same plugin and resends the missed refund emails from each order's actions menu.

Run in November, step 5 of the test plan would have flagged the password login. The fix could then have gone in during a quiet week, after the code freeze lifted.

Common mistakes

  • Treating every missing email as a spam problem. If the order is in Pending payment, WooCommerce sent nothing, and changing SMTP settings will not help.
  • Testing only with the agency's own Google Workspace inbox. Google's sender guidelines cover personal Gmail accounts, so test with a personal @gmail.com address and an Outlook.com address too.
  • Keeping a free-mail address as the sender because "it worked before". It worked before enforcement tightened.
  • Testing with a 100% discount code instead of a real low-value payment, which skips the payment callback that moves the order to Processing.
  • Checking once and assuming it stays fixed. A DNS migration, a new marketing tool or an expired API key can break sending months later.

Limitations: this guide covers WooCommerce's built-in emails. Plugins that replace order emails (some subscription, booking or email-customiser plugins) may log elsewhere. Passing SPF, DKIM and DMARC improves delivery but does not guarantee inbox placement, since mailbox providers also weigh spam complaints and sending history. Microsoft's dates may change; check its Exchange blog before you plan.

FAQ

Why does WooCommerce send the admin "New order" email but not the customer email?

They are separate notifications with separate switches and triggers. "New order" goes to the recipients you set; "Processing order" goes to the customer after payment. Check that the customer email is enabled and that the order reached Processing. If both are fine, look in the transactional-emails log for a Failed entry.

Do Gmail's bulk sender rules apply if my store sends fewer than 5,000 emails a day?

The bulk rules (DMARC and From alignment) apply at roughly 5,000 messages a day to personal Gmail accounts. Every sender must still meet the baseline: SPF or DKIM, valid PTR records, TLS and a low spam rate. Google counts mail per sending domain, so newsletters on the same domain count.

Can I resend an order email that failed?

Usually, yes, from the order actions menu on the order screen in the admin. Fix the cause first, or the resend will fail the same way, and confirm that a new Sent entry appears in the transactional-emails log.

Monitoring order emails after peak

The log and the test plan tell you whether email works today. They do not tell you when it stops. Pingvera's WordPress connector records WooCommerce order.created and order.failed events and alerts when order flow drops below its hourly baseline, which covers the Pending payment case from step 1. For contact and enquiry forms, Pingvera's end-to-end form checks submit a test lead and confirm through IMAP that the email reached the inbox. For a wider look at delivery, see our guides on transactional message deliverability and catching a store that stopped selling.

Sources

  • WooCommerce, Email troubleshooting: https://woocommerce.com/document/email-faq/
  • WooCommerce, Email settings: https://woocommerce.com/document/configuring-woocommerce-settings/emails/
  • Google Workspace Admin Help, Email sender guidelines: https://support.google.com/a/answer/81126
  • Google Workspace Admin Help, Email sender guidelines FAQ: https://support.google.com/a/answer/14229414
  • Microsoft Defender for Office 365 blog, Outlook's new requirements for high-volume senders (2 April 2025, updated 30 April 2025): https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/strengthening-email-ecosystem-outlook%E2%80%99s-new-requirements-for-high%E2%80%90volume-senders/4399730
  • Microsoft Exchange Team blog, Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline (27 January 2026): https://techcommunity.microsoft.com/blog/exchange/updated-exchange-online-smtp-auth-basic-authentication-deprecation-timeline/4489835
  • Microsoft Exchange Team blog, Exchange Online to retire Basic auth for Client Submission (SMTP AUTH): https://techcommunity.microsoft.com/blog/exchange/exchange-online-to-retire-basic-auth-for-client-submission-smtp-auth/4114750
  • Microsoft Learn, Deprecation of Basic authentication in Exchange Online: https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online

Last reviewed: 2026-11-09

Know about problems before your customers do

Pingvera watches whether an online business actually works — uptime, checkout, orders, domain, SSL and server — and alerts you in Telegram, email or a webhook before a customer has to tell you.

Start free

Read next: Merchant Center Misrepresentation: Fix It Before Peak · PayPal IPN Not Working: Fix Stuck Orders Before Peak · How to Update WooCommerce Safely Before Black Friday · SPF, DKIM, DMARC: why emails go to spam · Run a free site check.

Read next: Update PHP on WordPress: WooCommerce Plan Before 11.6 · WooCommerce Add to Cart Not Working: Pre-Peak Fix Guide · Merchant Center Misrepresentation: Fix It Before Peak · SPF, DKIM, DMARC: why emails go to spam · Run a free site check.

← All articles · Privacy policy · pingvera.com