WooCommerce not sending emails? Find the break and fix it

Start with the missing notification

1. Step 1

   Identify who is missing which email

   Separate the store owner’s New order alert from the customer’s Processing or Completed order email. Record a test order number, time and expected recipient.

2. Step 2

   Check settings and the status change

   Open WooCommerce > Settings > Emails and the affected notification. Confirm it is enabled. Compare the order notes with the trigger table below.

3. Step 3

   Follow a controlled test

   Use a test customer address you control. Match the order to the mail log, then inspect the provider record and inbox, including spam or quarantine.

4. Step 4

   Fix the layer that failed

   Investigate missing triggers or errors before changing the mailer. For a rejected send, investigate the provider connection; for accepted mail, investigate delivery and filtering.

For missing form messages or password resets as well, use our WordPress not sending email guide. It covers the shared sending route beyond WooCommerce.

Check WooCommerce > Settings > Emails

Open the affected email with Manage and check Enable this email notification where available. For store alerts, verify the Recipient(s) field. For customer emails, check the billing email on the order. Correcting the store admin address alone does not correct a customer’s order address.

Also check the From name and address. Use a sender on your business domain that your mail provider authorizes. If a mailer forces a different From address, check its settings too. Save changes before repeating your test. See WooCommerce email settings.

Which order statuses trigger WooCommerce email notifications?

Core notifications depend on events and status transitions. An order existing in the dashboard does not mean every email should fire. This table assumes the relevant notification is enabled; extensions and custom code can change the behavior.

Sources: WooCommerce notification definitions and the New order email trigger code. Check the email list in your installed version for available notifications.

An unpaid order staying at Pending payment does not trigger the normal paid-order confirmation. Orders containing only products that are both virtual and downloadable can skip Processing. Compare the actual transition with WooCommerce order statuses before treating a missing Processing email as a failure.

Payment received, but the order still says Pending payment?

Compare the gateway transaction with the order notes and payment status. A payment captured by the provider without an order update points to gateway communication. Review that gateway’s webhook or callback delivery, endpoint configuration and errors using its own documentation. SMTP does not update payment status.

This distinction comes from WooCommerce’s payment and email troubleshooting. Confirm the transaction before changing a real order’s status. Do not cycle customer orders through statuses just to force emails; other integrations may react too.

Test with an email log plugin, then check the inbox

Use WP Mail Logging or your existing mailer’s logging feature to record a controlled test. Install and activate logging before the test, then inspect the timestamp, recipient, subject and error. The plugin records the WordPress handoff; a logged message does not prove inbox delivery. Logs may contain customer data, so restrict access and remove unnecessary test records.

Your WooCommerce version may also expose a transactional-emails source under WooCommerce > Status > Logs. Check its logging settings and threshold if expected entries are hidden. The WooCommerce troubleshooting documentation explains these outcomes:

A preview or SMTP test isolates part of the path. After it works, create a controlled checkout order and verify the actual customer and store notifications. If testing on staging, route mail to test inboxes and use the gateway’s test mode.

Set up authenticated sending and verify SPF, DKIM and DMARC

WooCommerce uses WordPress’s mail interface; it is not a mail server. A provider connection changes how messages leave the site. WooCommerce’s sending-route guide explains why a dedicated service can be preferable to the web server’s default mail route.

The SMTP setup documentation illustrates provider connections and test messages. Choose settings for your actual provider instead of copying a generic port or password recipe.

Publish the records supplied for your domain and provider. WooCommerce’s authentication guide covers domain setup; Google’s sender guidelines explain alignment. Inspect a received message’s authentication results instead of assuming that saving DNS entries proves success.

If mail lands in spam, check those results and the sending provider’s bounce or suppression record. Also check mailbox rules and organizational quarantine. Authentication supports delivery but does not guarantee inbox placement. A message can be blocked before it reaches the spam folder, as explained in WooCommerce’s delivery guidance.

Check Action Scheduler and WP-Cron when emails are delayed

If the affected extension schedules emails or a related background task is stalled, open WooCommerce > Status > Scheduled Actions. Inspect relevant overdue Pending actions and Failed action logs by hook, group and time. A failed action elsewhere in the queue is not proof that it caused your missing email.

WP-Cron normally depends on page requests, so low traffic can delay scheduled work. Check whether it is disabled without a working server cron replacement, whether loopback requests fail and whether PHP errors stop the task. Do not assume every core order email is an Action Scheduler job.

Use the WooCommerce scheduled actions guide to investigate the runner. Review an action’s purpose before retrying it, especially if it involves payment. Do not bulk-run or delete the queue to make the warning disappear.

Isolate conflicts without disrupting live checkout

If the status changes correctly but no expected email is generated, inspect WooCommerce > Status > Logs for fatal errors around the test time. Look at recent mailer, email designer, gateway, theme and custom snippet changes.

Follow WooCommerce’s conflict testing procedure on a backed-up staging copy: test with a default theme and the smallest plugin set needed to reproduce the problem. Restore plugins one at a time and repeat the same test. Control staging emails and payment connections so tests cannot reach real customers or charge them.

Back up the store before testing changes. After the repair, verify checkout, order status, store notification and customer receipt together. Our WooCommerce optimization guide covers the wider store flow.