Some products need to say something the rest of the order does not \u2014 licence terms for a\ndownload, or a lead time for a made-to-order item. Write that message once, choose which\nproducts it applies to, and decide when it goes out. It runs through WooCommerce's own\nemail system.<\/p>\n\n
A rule is one message plus the conditions under which it is sent, and a store can have as\nmany as it needs. Trigger, timing, recipients and subject belong to a rule sent as its own\nemail; an inserted rule takes those from the WooCommerce email it joins.<\/p>\n\n
These apply to a rule sent as its own email. An inserted rule has no trigger of its own:\nWooCommerce decides when its email sends.<\/p>\n\n
Target a rule by individual products or variations, product categories, tags or product\ntype. Each selector can include or exclude products. An item matches any selected\ninclude, while a matching exclusion always wins. Choose \"Every product in the order\"\nto start broadly and then exclude exceptions.<\/p>\n\n
Two modes, chosen per rule:<\/p>\n\n
Both of these belong to a rule sent as its own email. It can wait \u2014 seconds, minutes,\nhours or days after the trigger \u2014 queued through Action Scheduler, WooCommerce's own\nbackground queue. And when it matches several products in one order, you choose: one\nmessage for the order<\/strong>, listing the matched products, or one message per product<\/strong>.<\/p>\n\n Recipients belong to a rule sent as its own email. A line can be the word customer<\/em> for\nthe order's billing address, admin<\/em> for the site administrator, or any email address, and\na rule can carry separate To, Cc and Bcc lists. A rule with no To recipient sends nothing\nand records that as the reason. An inserted rule has none of its own: its content goes into\nthe WooCommerce email already being sent, to whoever that email is addressed to.<\/p>\n\n Body content can carry placeholders filled in from the live order: customer name, email\nand phone; order number, date, status, total and payment method; billing and shipping\naddresses; store name and sender address; the matched product's name, SKU, quantity and\nvariation attributes; list placeholders covering every matched product; and custom fields.\nA separate email takes them in its subject and heading too, and the rule editor lists each\none with a description.<\/p>\n\n Every automatic delivery is recorded \u2014 rule, order, recipient, subject line, whether it\nsucceeded and the reason if it did not \u2014 store-wide on its own screen and per-order on the\norder edit screen. Details go with a personal-data erasure request, or when you remove the\nplugin's data; nothing is cleared on a schedule in this release.<\/p>\n\n From an order you can send any eligible rule's message on demand, resend one already sent,\nand send or cancel one waiting on its delay \u2014 each behind a confirmation naming the\nrecipient.<\/p>\n\n Messages use WooCommerce's email templates. Compatibility with theme overrides and\nthird-party email customizers varies. Preview rules and verify insert mode with a real\ntest order. The plugin declares compatibility with High-Performance Order Storage (HPOS)\nand is tested with it enabled.<\/p>\n\n\n WooCommerce must be installed and active. If WordPress, PHP or WooCommerce is older than\nthis plugin requires, it stays inactive and names the unmet requirement. On multisite it\nactivates per site, not network-wide.<\/p>\n\n\n Only if you choose that. An insert<\/strong> rule puts its message inside an email WooCommerce\nis already sending, so one arrives. A separate<\/strong> rule sends its own.<\/p><\/dd>\n Both send, unless you tell one to stop the others: each rule has a priority, and can be\nmarked to stop the rest for that trigger.<\/p><\/dd>\n No. Each automatic delivery is recorded against the order, the rule and the event that\ncaused it, and that record prevents a repeat \u2014 so the same automatic message is not sent\nagain if the order changes status back and forth. Sending by hand is always possible, and\nis recorded as deliberate.<\/p><\/dd>\n It is cancelled. Queued messages are re-checked against the live rule and the live order\nat the moment they are due, so a message that no longer applies is not sent.<\/p><\/dd>\n The plugin creates its own database tables. Removing them on uninstall is opt-in, so\nuninstalling keeps your delivery history unless you ask.<\/p><\/dd>\n Yes. Delivery details are returned by WordPress's personal-data exporter and removed by\nits eraser, including where a message was addressed to someone other than the customer.<\/p><\/dd>\n Yes. The plugin ships with a translation template and its interface is translatable. One\nexception is stated rather than glossed over: some delivery diagnostics are still English\nonly. The coded reasons a scheduled email was cancelled are translated; the free-text\ndetail composed for other outcomes is not \u2014 the reason and failure lines on a delivery\nattempt, on the delivery history screen and in the order-edit panel, and the note about\nunresolved placeholders above a preview. Making them translatable is scheduled for a later\nrelease.<\/p><\/dd>\n\n<\/dl>\n\n\nWho receives it<\/h4>\n\n
Placeholders<\/h4>\n\n
Preview and test<\/h4>\n\n
\n
Delivery history<\/h4>\n\n
Sending by hand<\/h4>\n\n
Compatibility<\/h4>\n\n
\n
\n
Does the recipient get two emails?<\/h3><\/dt>\n
What happens if two rules match the same product?<\/h3><\/dt>\n
Can the same email be sent twice for the same order?<\/h3><\/dt>\n
What happens to a delayed message if I disable the rule?<\/h3><\/dt>\n
Is my data removed if I uninstall?<\/h3><\/dt>\n
Does it support personal-data export and erasure?<\/h3><\/dt>\n
Can I translate it?<\/h3><\/dt>\n
1.0.0<\/h4>\n\n
\n