{"id":394,"date":"2026-09-10T12:34:33","date_gmt":"2026-09-10T18:04:33","guid":{"rendered":"https:\/\/photonconsole.com\/blog\/?p=394"},"modified":"2026-09-14T07:24:34","modified_gmt":"2026-09-14T12:54:34","slug":"woocommerce-order-emails-not-sending-diagnosis-and-fix","status":"publish","type":"post","link":"https:\/\/photonconsole.com\/blog\/woocommerce-order-emails-not-sending-diagnosis-and-fix\/","title":{"rendered":"WooCommerce Order Emails Not Sending: Diagnosis and Fix"},"content":{"rendered":"\n

A customer places an order. Payment goes through. The order appears in your dashboard. And no confirmation email arrives \u2014 not for the customer, and sometimes not for you either.<\/p>\n\n\n\n

Support tickets follow within hours. Customers assume the order failed and place it again, or request a refund. For a store, this is not a minor annoyance: order confirmations are the receipt customers rely on, and missing them costs real revenue.<\/p>\n\n\n\n

The frustrating part is that WooCommerce almost never tells you anything is wrong. This guide works through the diagnosis in the order that finds the cause fastest, then covers the fixes for each.<\/p>\n\n\n\n

Quick Answer: Why Are WooCommerce Emails Not Sending?<\/h2>\n\n\n\n

There are four independent reasons, and they fail in sequence. An order email only arrives if all four pass:<\/p>\n\n\n\n

    \n
  1. The email type is enabled<\/strong> in WooCommerce, then Settings, then Emails<\/li>\n\n\n\n
  2. The order status changed<\/strong> to one that triggers that email<\/li>\n\n\n\n
  3. WordPress can send mail at all<\/strong> \u2014 wp_mail()<\/code> is working<\/li>\n\n\n\n
  4. The receiving server accepted it<\/strong> \u2014 your domain passes authentication<\/li>\n<\/ol>\n\n\n\n

    Most store owners start at step three and never check steps one and two, which is where the problem usually is. Work through them in order. If step three turns out to be the failure, routing mail through an authenticated relay such as PhotonConsole<\/a> resolves it.<\/p>\n\n\n\n

    Which Emails WooCommerce Sends, and What Triggers Them<\/h2>\n\n\n\n
    \"\tMap
    Each notification is tied to a specific order status. Pending payment triggers no customer email.<\/figcaption><\/figure>\n\n\n\n

    WooCommerce does not send one “order email”. It sends a set of separate notifications, each tied to a specific order status. If the status never reaches the trigger, the email is never queued.<\/p>\n\n\n\n

    Email<\/th>Sent to<\/th>Triggered when the order becomes<\/th><\/tr><\/thead>
    New order<\/td>Admin<\/td>Processing, Completed or On-hold<\/td><\/tr>
    Processing order<\/td>Customer<\/td>Processing<\/td><\/tr>
    Completed order<\/td>Customer<\/td>Completed<\/td><\/tr>
    Order on-hold<\/td>Customer<\/td>On-hold<\/td><\/tr>
    Cancelled order<\/td>Admin<\/td>Cancelled<\/td><\/tr>
    Failed order<\/td>Admin<\/td>Failed<\/td><\/tr>
    Refunded order<\/td>Customer<\/td>Refunded<\/td><\/tr>
    Invoice \/ order details<\/td>Customer<\/td>Sent manually from the order screen<\/td><\/tr>
    New account<\/td>Customer<\/td>Account created at checkout<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Notice what is absent: there is no customer email for Pending payment<\/strong>. An order stuck at that status is the single most common reason a customer receives nothing, and the order still appears in your dashboard, which is why it looks like an email fault rather than a payment one.<\/p>\n\n\n\n

    Match the Symptom to the Cause<\/h2>\n\n\n\n

    The pattern of what fails usually points straight at the cause.<\/p>\n\n\n\n

    Symptom<\/th>Most likely cause<\/th>Check first<\/th><\/tr><\/thead>
    No emails at all, site-wide<\/td>WordPress cannot send mail<\/td>SMTP plugin test email<\/td><\/tr>
    Admin emails arrive, customer ones do not<\/td>Order status never triggered it<\/td>Order status on a test order<\/td><\/tr>
    Manual resend works, automatic does not<\/td>Trigger condition, not delivery<\/td>Email enabled setting and status<\/td><\/tr>
    Emails arrive hours late<\/td>WP-Cron not running<\/td>Replace with a server cron job<\/td><\/tr>
    Works normally, fails during sales<\/td>Hosting hourly send limit<\/td>Host mail limit in the control panel<\/td><\/tr>
    Emails send but land in spam<\/td>Missing SPF or DKIM<\/td>Deliverability checker on your domain<\/td><\/tr>
    Stopped after an update<\/td>Template override or plugin conflict<\/td>WooCommerce, Status for overrides<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Step-by-Step Diagnosis<\/h2>\n\n\n\n
    \"\tFour
    Four checkpoints an order email must pass before it reaches the customer.<\/figcaption><\/figure>\n\n\n\n

    Work through these in order. Each step rules out a whole category of cause, so skipping ahead usually wastes time.<\/p>\n\n\n\n

    Step 1: Check Whether the Email Type Is Enabled<\/h3>\n\n\n\n

    Go to WooCommerce, then Settings, then Emails. Each notification has its own enabled toggle, its own recipient, and its own subject line. Confirm the specific email you expect is switched on.<\/p>\n\n\n\n

    Pay attention to the recipient field on admin emails<\/strong>. It defaults to the site admin address, which on many installs is an address nobody monitors, or one that no longer exists.<\/p>\n\n\n\n

    Step 2: Check the Order Status<\/h3>\n\n\n\n

    Open the order and look at its status. If it reads Pending payment<\/strong>, no customer email was triggered and nothing is broken in your mail configuration.<\/p>\n\n\n\n

    Orders sit at pending payment when the payment gateway never confirmed the transaction. Common causes are a failed gateway callback, a webhook that could not reach your site, or a customer abandoning the payment page after the order was created.<\/p>\n\n\n\n

    Common Mistake<\/p>\n\n\n\n

    Debugging SMTP settings for hours when the real problem is that orders never leave Pending payment. Before touching any mail configuration, place a test order and watch whether the status moves to Processing. If it does not, the issue is the payment gateway callback, not email. Fixing SMTP will change nothing.<\/p>\n\n\n\n

    Step 3: Test Whether WordPress Can Send Any Mail<\/h3>\n\n\n\n

    Install an SMTP plugin and send its built-in test email, or trigger a password reset for a test account. If neither arrives, the problem is WordPress-wide rather than WooCommerce-specific.<\/p>\n\n\n\n

    By default WordPress uses the PHP wp_mail()<\/code><\/a> function, which sends unauthenticated mail directly from your web server. Most hosts block it and most mailbox providers filter it. Our guide to SMTP not working<\/a> covers the full set of failure modes.<\/p>\n\n\n\n

    Step 4: Resend the Email Manually<\/h3>\n\n\n\n

    Open the order, find the Order actions<\/strong> box in the sidebar, choose an email from the dropdown, and click the arrow to send.<\/p>\n\n\n\n

    This is a useful diagnostic. If the manual resend arrives but the automatic one never did, the mail connection is fine and the problem is the trigger \u2014 meaning step two is where to look. If the manual resend also fails, the problem is delivery.<\/p>\n\n\n\n

    Step 5: Check the WooCommerce Logs<\/h3>\n\n\n\n

    Go to WooCommerce, then Status, then Logs. Fatal errors during checkout can stop execution before the email hook runs, which produces an order that saved correctly with no notification sent.<\/p>\n\n\n\n

    Also check WooCommerce, then Status, and look at the system report for a flagged template override, covered in step seven.<\/p>\n\n\n\n

    Step 6: Test for a Plugin Conflict<\/h3>\n\n\n\n

    Other plugins hook into the same email actions. A booking plugin, an invoice generator or a marketing tool can unhook WooCommerce’s own notifications, replace them, or throw an error that halts them.<\/p>\n\n\n\n

    Deactivate plugins in batches on a staging site, testing an order after each batch. Do not do this on a live store during trading hours.<\/p>\n\n\n\n

    Step 7: Check for Outdated Template Overrides<\/h3>\n\n\n\n

    If your theme contains a woocommerce\/emails\/<\/code> folder, those files override WooCommerce’s own templates. When WooCommerce updates its template structure, an outdated override can break rendering or stop the email entirely.<\/p>\n\n\n\n

    WooCommerce, then Status shows any overrides that are out of date. The fix is to update the override to match the new template version, or remove it if the customisation is no longer needed.<\/p>\n\n\n\n

    Quick Fix<\/p>\n\n\n\n

    No Order Emails At All<\/p>\n\n\n\n