Extonify Order Emails For WooCommerce Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin 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.
Screenshots
The Order emails panel on the order edit screen: every supported email for this order, with its audience, exact resolved recipients, subject, headers, enabled state and template source.
The preview, rendered through the same pipeline a send uses, in HTML and plain text at desktop and narrow widths — and reporting that it transmitted nothing and wrote nothing.
The isolated test send form: one address you type, with the order’s own addresses refused on the way out.
The live resend confirmation: every address the message would reach, shown before anything is sent, on a screen that cannot transmit.
A completed resend result, naming which checks ran and reporting the site’s mail system as having accepted the message — never as having delivered it.
The private order note a send leaves behind: operator, time, enabled state, outcome, and the destination as a non-reversible shape rather than an address.
