WooCommerce email template overrides can keep working for years, then break after a WooCommerce update, theme update, or HPOS-related plugin change. The symptom may affect only one order status email.
Use this for stores where customer processing emails, completed emails, refund emails, failed order emails, or admin new-order emails are missing or malformed.
Quick answer
WooCommerce Order Status Email Template Override Audit should be handled with a narrow evidence-first workflow: list overrides, compare versions, test statuses, then verify the result before making broader changes.
What to check first
- List all WooCommerce email template overrides in the active theme and child theme.
- Compare override versions against current WooCommerce templates and note stale files.
- Test each affected order status with a real order, not only the WooCommerce email preview.
- Check custom hooks, conditional snippets, and plugin email builders that alter the same email.
- Confirm HPOS compatibility when order data is read directly from posts or post meta.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|---|---|
| List overrides | List all WooCommerce email template overrides in the active theme and child theme. | Each order status sends the correct customer or admin email. |
| Compare versions | Compare override versions against current WooCommerce templates and note stale files. | Stale overrides are removed, updated, or documented with a reason. |
| Test statuses | Test each affected order status with a real order, not only the WooCommerce email preview. | Email logs and SMTP logs agree for the tested order IDs. |
| Review snippets | Check custom hooks, conditional snippets, and plugin email builders that alter the same email. | Custom branding remains intact after template cleanup. |
Why this usually happens
- A child theme can override an email file long after the original WooCommerce template changed.
- Email previews do not always execute the same order-status path as production orders.
- Custom snippets often check old post meta keys that no longer match HPOS behavior.
- A template can render in admin while missing customer-facing sections or order items.
Field notes
- Keep a matrix of email type, order status, template file, override version, and test order ID.
- When removing an override, preserve a copy first so custom branding can be re-applied intentionally.
- Check both plain-text and HTML versions if the store sends both.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
find wp-content/themes -path '*woocommerce/emails*' -type f -print
wp theme list
wp plugin list | grep -Ei 'woocommerce|email|smtp|hpos'
# Test order statuses: pending, processing, completed, failed, refunded, cancelled.
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- List overrides
- Compare versions
- Test statuses
- Review snippets
- Rebuild safely
What to tell the client or owner
Report which email templates were overridden, which were stale, which order statuses were tested, and which files were changed or left in place.
Production verification checklist
- Each order status sends the correct customer or admin email.
- Stale overrides are removed, updated, or documented with a reason.
- Email logs and SMTP logs agree for the tested order IDs.
- Custom branding remains intact after template cleanup.
Mistakes to avoid
- Do not judge the fix by one browser or the homepage only.
- Do not delete evidence before recording usernames, file paths, timestamps, and response headers.
- Do not add a cache, security, or tracking plugin while the original problem is still unclear.
- Do not leave test users, temporary debug logs, or broad API keys active after verification.
When HandL WP should help
Bring in help when this affects leads, checkout, search visibility, malware risk, paid media reporting, or a client production site. HandL WP can trace the issue through WordPress, hosting, cache, tracking, and Search Console, then verify the workflow after the technical fix.
If this is active on a production site, fix WooCommerce email templates.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.