{"id":408118,"date":"2026-11-20T18:24:22","date_gmt":"2026-11-20T18:24:22","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/extonify-order-emails-for-woocommerce\/"},"modified":"2026-11-20T18:23:51","modified_gmt":"2026-11-20T18:23:51","slug":"extonify-order-emails-for-woocommerce","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/extonify-order-emails-for-woocommerce\/","author":23551089,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.0","stable_tag":"1.0.0","tested":"7.1.5","requires":"6.6","requires_php":"8.0","requires_plugins":null,"header_name":"Extonify Order Emails for WooCommerce","header_author":"Extonify","header_description":"A per-order email panel on the WooCommerce order screen: see each order email's audience and exact resolved recipients, preview it as it would be sent, send one isolated test to an address you type, or resend it to the recipients you confirmed. Previewing cannot transmit, and no resend happens without an explicit confirmation of the exact recipient list.","last_updated":"2026-11-20 18:23:51","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/extonify.com\/product\/order-emails-for-woocommerce\/","header_author_uri":"https:\/\/extonify.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":35,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"extonify","date":"2026-11-20 18:23:51","revision":3814301}},"upgrade_notice":{"1.0.0":"<p>First public release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3814299,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3814299,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3814299,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3814299,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3814299,"resolution":"1","location":"assets","locale":"","width":1600,"height":2236},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3814299,"resolution":"2","location":"assets","locale":"","width":1600,"height":1017},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3814299,"resolution":"3","location":"assets","locale":"","width":1600,"height":381},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3814299,"resolution":"4","location":"assets","locale":"","width":1600,"height":733},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3814299,"resolution":"5","location":"assets","locale":"","width":1600,"height":392},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3814299,"resolution":"6","location":"assets","locale":"","width":1600,"height":635}},"screenshots":{"1":"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.","2":"The preview, rendered through the same pipeline a send uses, in HTML and plain text at desktop and narrow widths \u2014 and reporting that it transmitted nothing and wrote nothing.","3":"The isolated test send form: one address you type, with the order's own addresses refused on the way out.","4":"The live resend confirmation: every address the message would reach, shown before anything is sent, on a screen that cannot transmit.","5":"A completed resend result, naming which checks ran and reporting the site's mail system as having accepted the message \u2014 never as having delivered it.","6":"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."}},"plugin_section":[],"plugin_tags":[260545,149139,21473,144677,286],"plugin_category":[45],"plugin_contributors":[287253],"plugin_business_model":[],"class_list":["post-408118","plugin","type-plugin","status-publish","hentry","plugin_tags-email-preview","plugin_tags-order-emails","plugin_tags-order-management","plugin_tags-resend-email","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_contributors-extonify","plugin_committers-extonify"],"banners":{"banner":"https:\/\/ps.w.org\/extonify-order-emails-for-woocommerce\/assets\/banner-772x250.png?rev=3814299","banner_2x":"https:\/\/ps.w.org\/extonify-order-emails-for-woocommerce\/assets\/banner-1544x500.png?rev=3814299","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/extonify-order-emails-for-woocommerce\/assets\/icon-128x128.png?rev=3814299","icon_2x":"https:\/\/ps.w.org\/extonify-order-emails-for-woocommerce\/assets\/icon-256x256.png?rev=3814299","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/extonify-order-emails-for-woocommerce\/assets\/screenshot-1.png?rev=3814299","caption":"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."},{"src":"https:\/\/ps.w.org\/extonify-order-emails-for-woocommerce\/assets\/screenshot-2.png?rev=3814299","caption":"The preview, rendered through the same pipeline a send uses, in HTML and plain text at desktop and narrow widths \u2014 and reporting that it transmitted nothing and wrote nothing."},{"src":"https:\/\/ps.w.org\/extonify-order-emails-for-woocommerce\/assets\/screenshot-3.png?rev=3814299","caption":"The isolated test send form: one address you type, with the order's own addresses refused on the way out."},{"src":"https:\/\/ps.w.org\/extonify-order-emails-for-woocommerce\/assets\/screenshot-4.png?rev=3814299","caption":"The live resend confirmation: every address the message would reach, shown before anything is sent, on a screen that cannot transmit."},{"src":"https:\/\/ps.w.org\/extonify-order-emails-for-woocommerce\/assets\/screenshot-5.png?rev=3814299","caption":"A completed resend result, naming which checks ran and reporting the site's mail system as having accepted the message \u2014 never as having delivered it."},{"src":"https:\/\/ps.w.org\/extonify-order-emails-for-woocommerce\/assets\/screenshot-6.png?rev=3814299","caption":"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."}],"raw_content":"<!--section=description-->\n<p>Extonify Order Emails adds an <strong>Order emails<\/strong> panel to the WooCommerce order edit\nscreen, on the classic order screen and on High-Performance Order Storage alike.<\/p>\n\n<h4>A per-order email operations tool, not another template previewer<\/h4>\n\n<p>WooCommerce core provides template preview and test sending at <strong>Settings \u2192 Emails<\/strong>\nusing dummy data, plus two manual order actions. Existing directory plugins provide\norder-selected preview and test sending from a separate admin page.<\/p>\n\n<p>This plugin performs a different function: a <strong>per-order operations panel on the order\nedit screen<\/strong>. It resolves and displays each supported email's audience and currently\nresolved recipients <em>before<\/em> any send; performs confirmed live resends across the\nsupported email set <strong>without mutating order status<\/strong>; guards against accidental\nrepeated submissions; records an audit note on the order; and reports the per-email\ntemplate source.<\/p>\n\n<p>It does not design email templates, replace SMTP, automate order statuses, create\nemail rules, or duplicate WooCommerce's email logging.<\/p>\n\n<h4>The panel<\/h4>\n\n<p>For each supported email it resolves \u2014 for the order you are looking at, right now \u2014\nand displays:<\/p>\n\n<ul>\n<li><strong>Audience<\/strong> \u2014 whether the email goes to the <strong>store admin<\/strong> or to the <strong>customer<\/strong>.\nThis is the question WooCommerce's own settings screen answers least clearly, and\nit is the first column on the panel for that reason.<\/li>\n<li><strong>Recipients<\/strong> \u2014 the exact resolved To address, plus Cc and Bcc where the store has\nthem configured. Addresses WooCommerce silently discards as invalid are listed\nrather than quietly dropped.<\/li>\n<li><strong>Subject<\/strong> \u2014 the resolved subject for this order, not the template string from the\nsettings screen.<\/li>\n<li><strong>Headers<\/strong> \u2014 From and Reply-To, read-only.<\/li>\n<li><strong>Enabled<\/strong> \u2014 the live state, including any filter the store has applied.<\/li>\n<li><strong>Template source<\/strong> \u2014 whether the email renders from WooCommerce's own file, a theme\noverride, another plugin's template, or a published block template. A source that\ncannot be attributed with certainty is reported as unknown rather than guessed.<\/li>\n<li><strong>Matches current status<\/strong> \u2014 a statement of fact about the order's status, not a\nrecommendation about whether to resend.<\/li>\n<\/ul>\n\n<h4>Preview<\/h4>\n\n<p><strong>Preview<\/strong> renders the email through the same pipeline a real send uses, so what you\nsee is what would be transmitted \u2014 in HTML and plain text, at a desktop and a narrow\nviewport.<\/p>\n\n<p><strong>Previewing cannot send anything at all.<\/strong> Preview, test send and live resend are\nthree separate operations with three separate guards, not one operation with a\nswitch: the preview path blocks the mail transport unconditionally as its first\naction, and no input to it can reach a sending path. Preview writes nothing to the\norder, invokes the mail system zero times, and leaves WooCommerce's shared email\nobject exactly as it found it \u2014 the panel reports that measurement on every preview.<\/p>\n\n<h4>Isolated test send<\/h4>\n\n<p><strong>One email, to one address you type.<\/strong> Not to the customer, not to the store admin\naddress, not to anything the order or your email settings name. The Cc and Bcc are\ncleared, no Reply-To is set, and the message is checked against the order's own\naddresses on its way out \u2014 and if any of them is on it, the message is stopped and\nnothing goes out.<\/p>\n\n<p>One thing to know before you use it: the ENVELOPE is isolated, the CONTENT is the\nreal email. The body contains this order's real details, which for most order emails\nincludes the customer's name and email address, because that is what WooCommerce's\ntemplate puts there. Send it to a mailbox you control.<\/p>\n\n<h4>Confirmed live resend<\/h4>\n\n<p><strong>The resend goes to the order's real recipients, and only after you confirm the\nexact list.<\/strong> It is one operation in two steps, and they are two different code paths:<\/p>\n\n<ol>\n<li><strong>Confirm.<\/strong> The panel resolves the recipients again and shows you the audience and\nevery address the message would reach. This step is part of the preview pipeline and\ncannot transmit \u2014 it physically cannot name the sending code.<\/li>\n<li><strong>Dispatch.<\/strong> What crosses between the two steps is not the address list but a\none-time digest of it. The dispatch re-resolves everything from scratch and aborts,\nhaving sent nothing, if anything changed in between \u2014 and tells you what changed.<\/li>\n<\/ol>\n\n<p><strong>The envelope must equal what you confirmed.<\/strong> It is checked at three points on the\nway out, including on the mail object itself at the last moment before transmission.\nAnything <em>added<\/em> and anything <em>missing<\/em> both stop the send: a message reaching three\nof four confirmed addresses carries no forbidden address at all and is still not the\nmessage you authorised.<\/p>\n\n<p><strong>A result is only \"accepted\" when every one of those checks actually ran.<\/strong> If your\nsite sends mail through SendGrid, Mailgun, Postmark or an SMTP plugin, or removes\nother plugins' mail hooks, a check can be taken out of the path \u2014 and then the result\nis reported as <strong>not verified<\/strong> rather than accepted, with the plain statement that\nthe recipients may have received a message this plugin could not fully see. A site\nwhose mail system replaces <code>wp_mail()<\/code> outright cannot be checked at all, and the\nsend is refused there rather than performed unwatched.<\/p>\n\n<p><strong>Nothing is ever reported as \"delivered.\"<\/strong> The outcomes are <em>accepted by your site's\nmail system<\/em>, <em>refused before transport<\/em>, <em>reported as failed<\/em>, or <em>not verified<\/em> \u2014\nand the first of those is not proof of arrival. Your mail provider's own log is the\nauthority on what left the building.<\/p>\n\n<p><strong>Concurrent resends of the same email are refused while the lease is live.<\/strong> A\ndispatch takes a five-minute lease on that order-and-email pair; a second dispatch\narriving while that lease is live is refused and told why, not queued. <strong>A send that\noutlives its lease can be overlapped<\/strong> \u2014 nothing bounds how long a mail server may\ntake, so this is a real bound and not a guarantee. Every send is recorded on the\norder, so a duplicate is visible after the fact in the order's own notes.<\/p>\n\n<p><strong>Every send is recorded on the order<\/strong> as a private note: who did it, when, whether\nthe email was enabled at the time, how it ended, and which checks ran. The\ndestination is recorded as a non-reversible shape \u2014 lengths only, never the address\nitself \u2014 because order notes get pasted into support tickets.<\/p>\n\n<h4>What this plugin will never do<\/h4>\n\n<p>It does not design email templates, replace SMTP, automate order statuses, create\nemail rules, or duplicate WooCommerce's own email logging. There is no bulk resend,\nno queue and no schedule in this release. Product- and category-based routing belongs\nto a different plugin and is deliberately out of scope here.<\/p>\n\n<p>There are no Pro labels, no locked controls, no teaser-disabled features, no licence\nchecks and no upgrade nags. Everything shipped is fully functional.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the plugin to <code>\/wp-content\/plugins\/<\/code>, or install it through the Plugins\nscreen.<\/li>\n<li>Activate it.<\/li>\n<li>Open any order. The <strong>Order emails<\/strong> panel appears below the order details.<\/li>\n<\/ol>\n\n<p>WooCommerce 9.8 or newer is required. With an older WooCommerce \u2014 or none \u2014 the\nplugin stays inactive and explains what is missing in an admin notice rather than\nfailing.<\/p>\n\n<p>Resending requires the same capability WooCommerce requires to edit the order you are\nlooking at, so shop managers and administrators can resend and customers and\nsubscribers cannot.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"does%20resending%20an%20email%20change%20the%20order%27s%20status%3F\"><h3>Does resending an email change the order's status?<\/h3><\/dt>\n<dd><p>No. Nothing in this plugin changes an order's status, triggers a status transition, or\nwrites an \"email sent\" flag \u2014 not on preview, not on a test send, not on a live\nresend. The only thing a send writes to the order is one private note recording that\nit happened. The plugin measures writes to the order while the operation runs and\nreports what it measured.<\/p><\/dd>\n<dt id=\"can%20it%20send%20to%20a%20customer%20without%20my%20confirmation%3F\"><h3>Can it send to a customer without my confirmation?<\/h3><\/dt>\n<dd><p>No. A live resend cannot happen in one request. The screen that shows you the\nrecipients is in the preview pipeline and cannot transmit at all; dispatch is a\nseparate request that requires your capability, a nonce, and a one-time consent token\ntied to the exact recipient list you were shown. If the recipients change between the\ntwo steps, the dispatch aborts without sending and tells you what changed.<\/p><\/dd>\n<dt id=\"which%20emails%20are%20supported%3F\"><h3>Which emails are supported?<\/h3><\/dt>\n<dd><p>The core order email set \u2014 seven emails, each with an explicitly verified adapter:<\/p>\n\n<ul>\n<li><strong>To the store admin:<\/strong> New order, Cancelled order, Failed order.<\/li>\n<li><strong>To the customer:<\/strong> Order on-hold, Processing order, Completed order, Customer\ninvoice.<\/li>\n<\/ul><\/dd>\n<dt id=\"why%20is%20one%20of%20my%20emails%20listed%20as%20%22not%20offered%22%3F\"><h3>Why is one of my emails listed as \"not offered\"?<\/h3><\/dt>\n<dd><p>This plugin acts only on emails whose audience, required context and preparation have\nbeen explicitly verified. It never prepares an unknown email generically, because\nguessing the audience wrong would send a store notification to a customer. Emails\nwithout an adapter \u2014 including those added by other plugins \u2014 are listed with the\nreason instead of being handled on a guess.<\/p><\/dd>\n<dt id=\"does%20previewing%20an%20email%20send%20anything%2C%20or%20change%20the%20order%3F\"><h3>Does previewing an email send anything, or change the order?<\/h3><\/dt>\n<dd><p>No. Preview renders the message and nothing else: no mail is handed to the mail\nsystem, no order status, note, meta value or \"email sent\" flag is written, and\nWooCommerce's shared email object is restored afterwards. The panel asserts all\nthree on every preview and tells you the result.<\/p>\n\n<p>That is enforced rather than intended. The preview path installs the transport block\nas the first thing it does, with no condition attached, and the build fails if that\nstops being true or if the preview path so much as references the sending code.<\/p><\/dd>\n<dt id=\"can%20i%20resend%20in%20bulk%2C%20or%20on%20a%20schedule%3F\"><h3>Can I resend in bulk, or on a schedule?<\/h3><\/dt>\n<dd><p>No. There is no bulk resend, no queue, no schedule and no cron. A resend is one\noperator, one order, one email, one confirmation. Bulk resend is deliberately out of\nscope for this release.<\/p><\/dd>\n<dt id=\"which%20woocommerce%20and%20wordpress%20versions%20are%20supported%3F\"><h3>Which WooCommerce and WordPress versions are supported?<\/h3><\/dt>\n<dd><p>WooCommerce 9.8 and newer. The full test suite \u2014 197 tests, 9,114 assertions \u2014 runs\ngreen on both ends of that range: WooCommerce 9.8.7 on WordPress 6.8.8, and\nWooCommerce 11.0.1 on WordPress 7.1. WooCommerce 8.9.5 is exercised separately to\nconfirm the below-minimum behaviour: the plugin declines to load and says why.<\/p>\n\n<p>9.8 matters more than a floor usually does. It is the version that introduced\n    get_cc_recipient() and <code>get_bcc_recipient()<\/code>, and it gates the Cc\/Bcc header block\nbehind the <code>email_improvements<\/code> feature, which defaults OFF there. So it is the one\nsupported version where a Cc can be configured and still not be transmitted \u2014 and the\npanel is measured saying exactly that, with the feature both on and off.<\/p><\/dd>\n<dt id=\"which%20php%20versions%20has%20this%20been%20run%20on%3F\"><h3>Which PHP versions has this been run on?<\/h3><\/dt>\n<dd><p><strong>PHP 8.0.30 and PHP 8.3.6.<\/strong> The <code>Requires PHP: 8.0<\/code> floor is tested, not merely\ndeclared: the full suite \u2014 197 tests, 9,114 assertions \u2014 runs green on <strong>PHP 8.0.30<\/strong>\nagainst both ends of the supported WooCommerce range, WooCommerce 9.8.7 and 11.0.1,\nand every PHP file this plugin ships parses under 8.0. The same suite runs green on\nPHP 8.3.6.<\/p>\n\n<p>PHP 8.1, 8.2 and 8.4 are not executed here, so nothing is claimed about them. The\nfloor is the version the plugin is measured on, and it is real.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>First public release: the <strong>Order emails<\/strong> panel on the classic and HPOS order\nscreens.<\/li>\n<li>Resolves audience, recipients, subject, headers, enabled state and template source\nper supported email, per order.<\/li>\n<li>Preview in HTML and plain text, rendered through the pipeline a send uses, at\ndesktop and narrow viewport widths. Preview cannot transmit: the mail transport is\nblocked unconditionally, and a <code>wp_mail()<\/code> call made by a template or another plugin\nduring a preview is stopped, counted and reported.<\/li>\n<li>Isolated test send: one email, to one address you type, with the Cc and Bcc cleared,\nno Reply-To, and the envelope checked against the order's own addresses on the way\nout.<\/li>\n<li>Confirmed live resend to the order's own recipients: a two-step confirmation across\ntwo code paths, a one-time consent digest of the exact confirmed list, re-resolution\nat dispatch with an abort on any change, envelope equality asserted at three points\nincluding the mail object itself, and refusal of a concurrent dispatch of the same\nemail on the same order while its five-minute lease is live \u2014 a send that outlives\nits lease can be overlapped, which is the bound this release claims and no more.<\/li>\n<li>A result is reported as accepted only when every one of those checks actually ran;\notherwise it is reported as not verified. Nothing is ever reported as delivered.<\/li>\n<li>Supports the core order email set: New order, Cancelled order, Failed order, Order\non-hold, Processing order, Completed order and Customer invoice.<\/li>\n<li>Every send writes one private order note \u2014 operator, time, enabled state, outcome,\nwhich checks ran, and the destination as a non-reversible shape rather than an\naddress.<\/li>\n<li>No order status is ever changed, on any path. No bulk resend, no queue, no schedule.<\/li>\n<\/ul>","raw_excerpt":"Resend WooCommerce order emails from the order screen, to recipients you confirm first, with preview, an isolated test send and an audit note.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/408118","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=408118"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/extonify"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=408118"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=408118"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=408118"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=408118"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=408118"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=408118"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}