Description
Extonify Order Emails adds an Order emails panel to the WooCommerce order edit
screen, on the classic order screen and on High-Performance Order Storage alike.
A per-order email operations tool, not another template previewer
WooCommerce core provides template preview and test sending at Settings → Emails
using dummy data, plus two manual order actions. Existing directory plugins provide
order-selected preview and test sending from a separate admin page.
This plugin performs a different function: a per-order operations panel on the order
edit screen. It resolves and displays each supported email’s audience and currently
resolved recipients before any send; performs confirmed live resends across the
supported email set without mutating order status; guards against accidental
repeated submissions; records an audit note on the order; and reports the per-email
template source.
It does not design email templates, replace SMTP, automate order statuses, create
email rules, or duplicate WooCommerce’s email logging.
The panel
For each supported email it resolves — for the order you are looking at, right now —
and displays:
- Audience — whether the email goes to the store admin or to the customer.
This is the question WooCommerce’s own settings screen answers least clearly, and
it is the first column on the panel for that reason. - Recipients — the exact resolved To address, plus Cc and Bcc where the store has
them configured. Addresses WooCommerce silently discards as invalid are listed
rather than quietly dropped. - Subject — the resolved subject for this order, not the template string from the
settings screen. - Headers — From and Reply-To, read-only.
- Enabled — the live state, including any filter the store has applied.
- Template source — whether the email renders from WooCommerce’s own file, a theme
override, another plugin’s template, or a published block template. A source that
cannot be attributed with certainty is reported as unknown rather than guessed. - Matches current status — a statement of fact about the order’s status, not a
recommendation about whether to resend.
Preview
Preview renders the email through the same pipeline a real send uses, so what you
see is what would be transmitted — in HTML and plain text, at a desktop and a narrow
viewport.
Previewing cannot send anything at all. Preview, test send and live resend are
three separate operations with three separate guards, not one operation with a
switch: the preview path blocks the mail transport unconditionally as its first
action, and no input to it can reach a sending path. Preview writes nothing to the
order, invokes the mail system zero times, and leaves WooCommerce’s shared email
object exactly as it found it — the panel reports that measurement on every preview.
Isolated test send
One email, to one address you type. Not to the customer, not to the store admin
address, not to anything the order or your email settings name. The Cc and Bcc are
cleared, no Reply-To is set, and the message is checked against the order’s own
addresses on its way out — and if any of them is on it, the message is stopped and
nothing goes out.
One thing to know before you use it: the ENVELOPE is isolated, the CONTENT is the
real email. The body contains this order’s real details, which for most order emails
includes the customer’s name and email address, because that is what WooCommerce’s
template puts there. Send it to a mailbox you control.
Confirmed live resend
The resend goes to the order’s real recipients, and only after you confirm the
exact list. It is one operation in two steps, and they are two different code paths:
- Confirm. The panel resolves the recipients again and shows you the audience and
every address the message would reach. This step is part of the preview pipeline and
cannot transmit — it physically cannot name the sending code. - Dispatch. What crosses between the two steps is not the address list but a
one-time digest of it. The dispatch re-resolves everything from scratch and aborts,
having sent nothing, if anything changed in between — and tells you what changed.
The envelope must equal what you confirmed. It is checked at three points on the
way out, including on the mail object itself at the last moment before transmission.
Anything added and anything missing both stop the send: a message reaching three
of four confirmed addresses carries no forbidden address at all and is still not the
message you authorised.
A result is only “accepted” when every one of those checks actually ran. If your
site sends mail through SendGrid, Mailgun, Postmark or an SMTP plugin, or removes
other plugins’ mail hooks, a check can be taken out of the path — and then the result
is reported as not verified rather than accepted, with the plain statement that
the recipients may have received a message this plugin could not fully see. A site
whose mail system replaces wp_mail() outright cannot be checked at all, and the
send is refused there rather than performed unwatched.
Nothing is ever reported as “delivered.” The outcomes are accepted by your site’s
mail system, refused before transport, reported as failed, or not verified —
and the first of those is not proof of arrival. Your mail provider’s own log is the
authority on what left the building.
Concurrent resends of the same email are refused while the lease is live. A
dispatch takes a five-minute lease on that order-and-email pair; a second dispatch
arriving while that lease is live is refused and told why, not queued. A send that
outlives its lease can be overlapped — nothing bounds how long a mail server may
take, so this is a real bound and not a guarantee. Every send is recorded on the
order, so a duplicate is visible after the fact in the order’s own notes.
Every send is recorded on the order as a private note: who did it, when, whether
the email was enabled at the time, how it ended, and which checks ran. The
destination is recorded as a non-reversible shape — lengths only, never the address
itself — because order notes get pasted into support tickets.
What this plugin will never do
It does not design email templates, replace SMTP, automate order statuses, create
email rules, or duplicate WooCommerce’s own email logging. There is no bulk resend,
no queue and no schedule in this release. Product- and category-based routing belongs
to a different plugin and is deliberately out of scope here.
There are no Pro labels, no locked controls, no teaser-disabled features, no licence
checks and no upgrade nags. Everything shipped is fully functional.
Installation
- Upload the plugin to
/wp-content/plugins/, or install it through the Plugins
screen. - Activate it.
- Open any order. The Order emails panel appears below the order details.
WooCommerce 9.8 or newer is required. With an older WooCommerce — or none — the
plugin stays inactive and explains what is missing in an admin notice rather than
failing.
Resending requires the same capability WooCommerce requires to edit the order you are
looking at, so shop managers and administrators can resend and customers and
subscribers cannot.
FAQ
Does resending an email change the order’s status?
No. Nothing in this plugin changes an order’s status, triggers a status transition, or
writes an “email sent” flag — not on preview, not on a test send, not on a live
resend. The only thing a send writes to the order is one private note recording that
it happened. The plugin measures writes to the order while the operation runs and
reports what it measured.
Can it send to a customer without my confirmation?
No. A live resend cannot happen in one request. The screen that shows you the
recipients is in the preview pipeline and cannot transmit at all; dispatch is a
separate request that requires your capability, a nonce, and a one-time consent token
tied to the exact recipient list you were shown. If the recipients change between the
two steps, the dispatch aborts without sending and tells you what changed.
Which emails are supported?
The core order email set — seven emails, each with an explicitly verified adapter:
- To the store admin: New order, Cancelled order, Failed order.
- To the customer: Order on-hold, Processing order, Completed order, Customer
invoice.
Why is one of my emails listed as “not offered”?
This plugin acts only on emails whose audience, required context and preparation have
been explicitly verified. It never prepares an unknown email generically, because
guessing the audience wrong would send a store notification to a customer. Emails
without an adapter — including those added by other plugins — are listed with the
reason instead of being handled on a guess.
Does previewing an email send anything, or change the order?
No. Preview renders the message and nothing else: no mail is handed to the mail
system, no order status, note, meta value or “email sent” flag is written, and
WooCommerce’s shared email object is restored afterwards. The panel asserts all
three on every preview and tells you the result.
That is enforced rather than intended. The preview path installs the transport block
as the first thing it does, with no condition attached, and the build fails if that
stops being true or if the preview path so much as references the sending code.
Can I resend in bulk, or on a schedule?
No. There is no bulk resend, no queue, no schedule and no cron. A resend is one
operator, one order, one email, one confirmation. Bulk resend is deliberately out of
scope for this release.
Which WooCommerce and WordPress versions are supported?
WooCommerce 9.8 and newer. The full test suite — 197 tests, 9,114 assertions — runs
green on both ends of that range: WooCommerce 9.8.7 on WordPress 6.8.8, and
WooCommerce 11.0.1 on WordPress 7.1. WooCommerce 8.9.5 is exercised separately to
confirm the below-minimum behaviour: the plugin declines to load and says why.
9.8 matters more than a floor usually does. It is the version that introduced
get_cc_recipient() and get_bcc_recipient(), and it gates the Cc/Bcc header block
behind the email_improvements feature, which defaults OFF there. So it is the one
supported version where a Cc can be configured and still not be transmitted — and the
panel is measured saying exactly that, with the feature both on and off.
Which PHP versions has this been run on?
PHP 8.0.30 and PHP 8.3.6. The Requires PHP: 8.0 floor is tested, not merely
declared: the full suite — 197 tests, 9,114 assertions — runs green on PHP 8.0.30
against both ends of the supported WooCommerce range, WooCommerce 9.8.7 and 11.0.1,
and every PHP file this plugin ships parses under 8.0. The same suite runs green on
PHP 8.3.6.
PHP 8.1, 8.2 and 8.4 are not executed here, so nothing is claimed about them. The
floor is the version the plugin is measured on, and it is real.
Screenshots






Changelog
1.0.0
- First public release: the Order emails panel on the classic and HPOS order
screens. - Resolves audience, recipients, subject, headers, enabled state and template source
per supported email, per order. - Preview in HTML and plain text, rendered through the pipeline a send uses, at
desktop and narrow viewport widths. Preview cannot transmit: the mail transport is
blocked unconditionally, and awp_mail()call made by a template or another plugin
during a preview is stopped, counted and reported. - Isolated test send: one email, to one address you type, with the Cc and Bcc cleared,
no Reply-To, and the envelope checked against the order’s own addresses on the way
out. - Confirmed live resend to the order’s own recipients: a two-step confirmation across
two code paths, a one-time consent digest of the exact confirmed list, re-resolution
at dispatch with an abort on any change, envelope equality asserted at three points
including the mail object itself, and refusal of a concurrent dispatch of the same
email on the same order while its five-minute lease is live — a send that outlives
its lease can be overlapped, which is the bound this release claims and no more. - A result is reported as accepted only when every one of those checks actually ran;
otherwise it is reported as not verified. Nothing is ever reported as delivered. - Supports the core order email set: New order, Cancelled order, Failed order, Order
on-hold, Processing order, Completed order and Customer invoice. - Every send writes one private order note — operator, time, enabled state, outcome,
which checks ran, and the destination as a non-reversible shape rather than an
address. - No order status is ever changed, on any path. No bulk resend, no queue, no schedule.
