1. Identify the missing email
Write down the exact notification and its intended recipient. A store-owner New order alert and a customer Processing order email are different investigations. In a dummy Harbor Goods example, the admin alert goes to orders@harborgoods.test and the customer message goes to the order's billing address. These are illustrative staging addresses, not delivery destinations.
Record the order reference, expected event and time, recipient role, and whether the problem affects one message or every message. Keep this record beside your test results.
2. Check order status and payment evidence
Inspect the status and order notes. Pending payment can explain why a paid-order notification was not triggered. If the gateway reports payment but the order did not update, investigate its callbacks or webhooks and reconcile the payment evidence. Check fatal-error logs if processing stopped unexpectedly.
Compare the expected order journey with the actual sequence. Do not mark a real order paid merely to force an email: the underlying payment or status issue still needs resolution.
3. Check the notification and recipient
Open WooCommerce → Settings → Emails and select the relevant notification. Check that it is enabled. Inspect the recipient setting for an admin notification and the billing email for a customer notification.
On staging, use a capture mailbox or approved test inbox. Reproduce the same notification rather than treating success from an unrelated email as proof that this one works. Record the setting before changing it so the result remains explainable.
4. Inspect the sending evidence
WooCommerce 10.9 introduced transactional email logging. On supported versions, open WooCommerce → Status → Logs and inspect transactional-emails. Match the entry to your test event. Sent means successful handoff, not inbox delivery. Failed identifies a sending failure; Disabled means the notification is off; Skipped indicates an unmet condition.
Order-related sent and failed attempts also appear in private order notes. If entries are absent, check the installed version, logging configuration and threshold; then inspect mailer or provider records. An empty log alone does not identify the cause.
The companion tutorial demonstrates a beta staging environment. Treat its screens as an example, and compare them with your installed release. No store-specific test result is implied by this guide.
5. Check delivery and sender authentication
Search junk folders and provider bounce or rejection records. Use a From address on your own verified store domain. Follow your host or mail provider's instructions for authenticated SMTP or API sending and SPF, DKIM and DMARC.
Do not invent DNS values or expose mail credentials in screenshots. Installing a mail plugin does not prove the order event fired, and authentication cannot guarantee inbox placement. Keep evidence from the sending service separate from evidence that the recipient actually received the message.
6. Retest the same order journey on staging
Use dummy customer details, sandbox payment and mail capture. Repeat the event that should produce the missing notification, including its expected status transition. A generic test email is a useful transport check, but it does not exercise the complete order journey.
- Save the baseline: notification, order status, recipient and versions.
- Run the order journey and record trigger, log and mailbox evidence.
- Change one relevant setting and repeat the same journey.
- Compare results and restore temporary test changes.
If it still fails, inspect fatal errors and isolate theme or extension conflicts on staging while retaining the dependencies needed for the test. Avoid casual plugin deactivation on a live store.
What to capture for support
Prepare a redacted record of the expected notification, actual order sequence, gateway evidence, settings, installed versions, mailer, timestamp and timezone. Include the relevant log outcome and whether the test mailbox received anything. Give a reproducible failing case and, if available, a working comparison. Exclude personal addresses, order contents and credentials from public reports.
Final checklist
- Expected notification and recipient identified
- Status transition and payment evidence compared
- Notification and recipient settings checked
- Sending evidence matched to the test event
- Delivery and authentication investigated
- Same order journey retested after each change