Missing WooCommerce order emails

Match the order status to a notification that exists

Before looking for a lost message, name the email you expected and the status the order had. WooCommerce's troubleshooting guide says to confirm that an email should have been sent. A new order still in Pending payment does not trigger the email. An error that stops the status from changing also means no email is sent.

The email settings then name the messages. Processing order goes to the customer after payment. Completed order goes when the order is marked completed and usually indicates that the order has shipped. Failed order notifications go when an order is marked failed after it was pending or on hold, including a customer message about the payment. On-hold, refunded, new-order, and customer-note messages have their own triggers. A payment receipt from a payment provider, if that provider sends one, is not one of these store messages.

Write the status and the notification name on the sheet. If they do not pair, the absence is the order state or the wrong expectation. Do not open a mail-delivery investigation for a message the status does not send.

Read the store log before blaming the inbox

WooCommerce logs each transactional email. At WooCommerce, then Status, then Logs, open the source named transactional-emails. Sent means WooCommerce handed the message to the mail system. Failed means the send was attempted and the mail process returned an error. Disabled means that notification is turned off. Skipped means a required condition was missing, such as a recipient. Sent and failed attempts for order emails are also private order notes. Disabled and skipped attempts are only in the log.

The log does not store the raw customer email address. Recipients appear as a WordPress username or as guest. If the log threshold hides INFO or NOTICE entries, a sent, disabled, or skipped row can be absent even though logging exists. Check the log settings before you treat a missing row as a missing send.

Use an order that already exists. Do not put a customer's address, a card number, or a mailbox password into the Prism form. The worksheet does not submit or save entries.

A sent log is not an inbox

WooCommerce's troubleshooting guide separates a send from delivery. Often the server sends the message and it is not received. The same guide says to use a From address on the site's domain. A From address at a public mailbox provider is likely to be filtered because the declared sender and the server that sent the mail do not match.

The authentication document tells the merchant to ask the host, or the SMTP plugin that actually sends, whether SPF, DKIM, and DMARC are in place for that domain. Each host has its own process. This page does not list DNS records. If the log says failed, the failure reason in the log is the lead, and it often points at the host or mail setup rather than at the order status.

WordPress's own messages, such as a password reset, may not appear in the transactional-emails log. Those need the mail service's log. An unknown mail service stays unknown. Do not invent a sender.

What you can close, and what the provider still owns

You can turn on a notification that the log marks disabled, add a missing store recipient, and correct a From address that does not use the store domain, when you control those settings. You can stop telling a buyer that a message was sent when the log says it was not. You cannot make a receiving mailbox accept a message the log already marked sent. That question goes to the host or the named mail service, with the log outcome and the time, not with a copy of the customer's mailbox.

A missing email does not say whether the payment succeeded. Use the order status and the payment record for that question.

Prism can trace and repair a store's order emails as an agreed store-operations engagement: following the message through the order status, the notification setting, and the send attempt, and repairing the part the store controls, with email tools Prism supports. Whether your tools are supported is confirmed in the consultation, and email delivery still depends on the receiving mailbox. Confirm the email work in the agreed scope; Prism confirms scope, responsibilities, fees, and terms before work begins.

In the consultation request, include the order's actual status, the notification you expected, the log outcome (sent, failed, disabled, skipped, or no row), and the host or mail service that sends for the site, if you know it. Leave out customer email addresses, message contents, and mailbox passwords.

Order-email trace

Use one existing order and one expected notification. Write unknown where the log or the inbox was not checked. Do not enter customer email addresses or message contents. Record the notification type and the delivery result only.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.