Sébastien Laframboise

Check WooCommerce order emails sent to customers and the team

Check WooCommerce order emails sent to customers and the team

WooCommerce order emails have two distinct roles: to confirm to the customer what’s happening and to notify the team that action is required. A store can receive a valid payment while sending the wrong message, to the wrong recipient, or at the wrong time.

When checking your WooCommerce order emails, don’t limit yourself to a successful order. Instead, verify the enabled notifications, the recipients, the status changes, the content, and the actual delivery of messages. That way you can tell a configuration issue from a delivery issue.

Start by taking inventory of active notifications

In the admin, open WooCommerce > Settings > Emails. WooCommerce shows the native notifications there, their recipients and their status. The official documentation on WooCommerce email settings specifies in particular which notifications are intended for the team and which are meant for customers.

Check each notification that matches your order flow. The emails New order, Order canceled and Failed order are normally used to notify the team. Conversely, the pending order, processing order, completed order and refunded messages are aimed at the customer.

Check activation and recipients

Then open each important email with the management link. Make sure the enable option is checked. For internal notices, also verify the recipients field. An incorrect, obsolete or missing address will prevent the team from receiving a useful notification.

Add multiple recipients only when it serves a clear responsibility. For example, the orders address can receive new sales while accounting can receive payment failures. Use the Cc or Bcc fields sparingly so as not to expose addresses unnecessarily or multiply messages.

Before changing recipients, take the time to understand WooCommerce order statuses. The status often triggers the email; a missing message can therefore reveal a status that never changed.

Match each email to the correct status

An effective audit links each sales event to an expected notification. WooCommerce states that a submitted order often goes from Pending payment à Processing, to Completed. However, payment method, product type and team actions can alter that progression.

The official page on order statuses reminds that Processing generally means payment is received and the order is awaiting fulfillment. A physical order does not automatically move from that status to Completed : the team usually must process it and mark it complete after shipping.

Situation to testStatus to confirmEmail to monitor
Payment accepted for an order to be shippedProcessingNew order to the team and order processing for the customer
Payment pending validationOn holdOrder pending for the customer, depending on the scenario
Payment declinedFailedNotify the team and failure message to the customer
Order shipped or fulfilledCompletedOrder completed for the customer
Partial or full refundRefunded or refund recordedRefund email to the customer

Adapt this matrix to your products. Virtual and downloadable products may follow a different flow. Also, an extension, theme or custom code can add, remove or modify emails. Record any additional notifications in your own checklist.

Check the content, sender identity and template

For each template, proofread the subject, heading, supplemental text and sending format. WooCommerce supports plain text, HTML and multipart formats. The multipart format provides both HTML and text versions; the recipient’s mail client chooses the one it can display.

Keep subjects explicit. The customer should recognize the store, the order number and the relevant stage. Also verify that the displayed information matches your actual policies: timing, processing, delivery, returns or support. An order completed email shouldn’t imply a package has been shipped if your process uses that status differently.

Under the templates, check the sender name and address. WooCommerce recommends an address tied to your site’s domain to improve deliverability. If you want to centralize replies, also configure a reply-to address Reply-to that is separate and monitored. This setting is not the same as the from address From.

Preview on desktop and mobile when your settings screen offers it. If the feature is available in your setup, also send a test message. Check rendering, links, prices, taxes, variations and the support address. A template customization deserves a trial first in a controlled environment; if needed, consult how to create a WordPress staging environment before making changes.

Test real order transitions

A template preview doesn’t confirm that a trigger works. Create test orders with a customer address you control. Repeat important scenarios: payment accepted, payment declined, order put on hold, transition to completed and refund.

After each action, note the order number, the status obtained, the expected emails, the recipients and the time of receipt. Test the gateway in the mode intended for that purpose and avoid creating unnecessary real transactions. To extend this check to payment, also follow this guide to test a WooCommerce payment gateway before going live.

Check the logs before concluding there’s an outage

A missing email does not automatically mean WooCommerce didn’t generate it. The WooCommerce email troubleshooting documentation explains that WooCommerce records transactional email attempts in the logs. After your test order, go to WooCommerce > Status > Logs, then open or filter the source transactional-emails.

A result of Sent indicates that WooCommerce handed the message off to the site’s sending system. Failed indicates a failure returned by that system. Disabled reveals the template is disabled, while Skipped signals that a required condition is missing, such as a recipient.

If the log shows a successful send, check junk folders and the destination address. Then investigate deliverability rather than the WooCommerce template. A sender address on your domain, plus SPF, DKIM and DMARC authentication, help recipient servers assess the legitimacy of your messages, as explained in the WooCommerce email authentication documentation.

Keep the check short but repeatable

Repeat this audit after changing the gateway, theme, email extension, sending provider or shipping process. Also check messages after a major update. This prevents discovering a disabled notification only after a customer order.

Finally, if the issue also affects forms or password resets, broaden the diagnosis with this article on WordPress email issues and missing messages. You’ll then know whether the cause specifically involves WooCommerce order emails or the site’s email sending as a whole.