Smart Notification Manager – Design, Customize & Automate WordPress & WooCommerce Emails

By Seventh Sky

0+ active installationsVersion 1.0.2

Take full control of your WordPress and WooCommerce emails. Disable unwanted notifications, set custom templates, and automate your email workflow.

Description

By default, WordPress automatically sends system emails for actions like user registration, password reset, email change, and comment moderation. Most of these messages are plain text, unbranded, or unnecessary.

Smart Notification Manager gives you complete control over those emails so you can create a more polished, branded, and professional experience for your users.

✨ Key Features

  • Disable unwanted notifications – Stop WordPress from sending redundant admin or system emails.
  • Create custom email templates – Use the built-in WordPress editor to design personalized emails with placeholders like {username}, {email}, {sitename}, {password_reset_link}, and more.
  • Role-based rules – Control which user roles receive which notifications.
  • WooCommerce integration – Automatically discover registered WooCommerce emails, edit subjects, and choose Default, Custom text, Advanced body or Disabled. Classic core email bodies support custom introductions, headings, closings, footers and dynamic transactional blocks. Unsupported extension/block emails clearly show subject/control-only capability. Routing overrides remain limited to administrator alerts.
  • Notification decision logging – Optional indexed decision logs with configurable retention from 1–365 days (30 by default). Allowed/customized entries do not confirm mail transport or delivery; logs can be cleared.
  • Subjects, branding and plain text – Customize subjects, apply optional shared WordPress branding and retain URL-preserving plain alternatives. WooCommerce custom messages keep their native layout.
  • Revisions and configuration tools – Load previous template versions into drafts, preview fictional samples, send administrator samples, transfer validated configuration and explain saved sending policies.
  • Administrator and network policies – Route administrator alerts, control update-result categories and enforce network-wide notification blocks.
  • Modern dashboard interface – A clean, card-based settings page consistent with the Smart plugin suite, featuring intuitive toggles and sections.

Whether you want to brand your welcome emails, disable unnecessary notifications, or manage email delivery for specific user roles, Smart Notification Manager makes it simple and flexible.

Built for everyday site and store administration

Smart Notification Manager brings the settings for supported transactional notifications into one place. Site owners can write a recognizable welcome message, store administrators can adjust order communication, and administrators can review which sending rules affected a message. Changes are made in WordPress administration without editing PHP template files for the supported editor workflows.

Use it to keep customer communication consistent, reduce selected administrative alerts, preserve account-access links in custom messages, and understand notification decisions. Each notification can be configured independently, so you can start with one message and expand your setup as you verify the results.

Three places to manage your notifications

  • Notifications → Settings contains general sending switches, role rules, branding and policies, configuration tools, logging settings and decision logs.
  • Notifications → Custom Emails contains the supported WordPress subject and body editors, placeholder guidance, previews and previous template versions.
  • Notifications → WooCommerce Emails contains the detected WooCommerce email library, individual sending/editing modes, subjects and supported classic body editors.

The WordPress and WooCommerce editors are dedicated submenus rather than tabs inside Settings. Previously bookmarked editor tab URLs remain available for existing workflows.

Content management and email delivery

The plugin changes supported notification policies and content within the existing WordPress and WooCommerce email workflows. It does not provide an SMTP server, replace your transactional mail provider, create a marketing mailing list, or schedule email campaigns. The notification still needs its normal application event and a working mail transport.

For example, writing a processing-order template does not create a new order-status trigger. Allowing an email in this plugin does not enable an email that WooCommerce or another plugin has disabled. A successful sample also does not prove that every real notification will be permitted by its saved rules.

Getting Started

  1. Open Notifications → Settings and review the General sending switches before changing templates. Keep the notifications you need enabled.
  2. If you need role restrictions, configure only the relevant supported events in Role Based. Leave the selection empty when all roles should qualify.
  3. Open Notifications → Custom Emails, expand one notification and enter its subject and body. Leave either field blank when you want the corresponding native value.
  4. Use the placeholder guidance for that particular editor. Preview your draft with fictional data and send an administrator sample if your mail transport is configured.
  5. Choose Save Changes to apply the draft. Loading a revision, clearing a body, or restoring defaults in an editor does not apply the change until it is saved.
  6. Trigger the real event on staging and inspect both its message and its decision log. Test account-access links with a staging user rather than relying on a sample link.
  7. For a store, repeat the process under Notifications → WooCommerce Emails. Start with Custom text for one supported classic email, verify it, and then configure other types.

Changes to sending policies and templates affect future events. Saving a template does not resend earlier messages or retrospectively deliver a notification that was previously blocked.

Supported Notifications

WordPress notifications

  • Administrator registration alert: the site administrator notification about a newly registered user. Its role rule refers to the new user.
  • User welcome email: the new user’s registration message, including the existing account setup link when applicable.
  • Password reset: the recovery message requested for an existing account. Customization reuses the key produced by the native reset workflow.
  • Password changed: the notification sent after the user’s password changes.
  • Email address changed: the notification to the old email address after a change. Verification of the new address remains a separate WordPress workflow.
  • Comment moderation: moderator notifications for comments awaiting review, with comment-specific placeholders.
  • Automatic update results: supported core, plugin and theme result messages, with separate success, failure/partial failure and critical-result preferences.

Role restrictions are available for the registration and account events that expose a role selector. Comment moderation and automatic-update result emails do not use those user-role rules. Network signup/activation messages and notices requiring manual update action are outside the corresponding suppression policy.

WooCommerce notifications

The library detects emails from WooCommerce’s registered email objects, including emails supplied by active extensions. Detection does not imply that every detected type has an editable body: the capability notice identifies which editing operations are supported.

Classic body customization covers these core email IDs:

  • new_order, cancelled_order, failed_order.
  • customer_on_hold_order, customer_processing_order, customer_completed_order.
  • customer_refunded_order, including the native full/partial refund context.
  • customer_invoice, used for customer order details and payment requests.
  • customer_note, customer_reset_password, customer_new_account.

Registered types outside this supported set, WooCommerce block-editor bodies and unadapted extension bodies retain their native content and show subject/control-only capability. Their available controls do not turn them into classic body templates.

Writing Email Templates

WordPress placeholder reference

Use only the placeholders listed beside the selected notification. Account-oriented WordPress templates expose {username}, {user_login}, {display_name}, {email}, {first_name}, {last_name}, {sitename}, {siteurl}, {user_role}, {date} and {time}. A value can be empty when the event has no corresponding data, such as a user without a saved first name.

Additional values depend on the event:

  • Welcome and password-reset bodies: {password_reset_link}.
  • Email-change notifications: {old_email} and {new_email}.
  • Comment moderation: {original_message}, {comment_id}, {comment_author}, {comment_content}, {post_title} and {moderation_link}, alongside site/date/time values.
  • Automatic updates: {original_message}, {update_type} and {update_status}, alongside site/date/time values.

Placeholders are case insensitive. Unsupported names are not a way to execute PHP or fetch arbitrary account fields. Keep the editor’s token list as the reference for that notification, and review warnings before saving.

Example: a WordPress welcome message

Subject:

Welcome to {sitename}, {username}

Body:

<p>Hello {display_name},</p>
<p>Your account at {sitename} is ready.</p>
<p><a href="{password_reset_link}">Set your password</a></p>
<p>Thank you for joining us.</p>

The link placeholder above supplies a URL in a WordPress body. If it is omitted from a custom welcome/reset body, the plugin appends the available setup/reset link. Review the final message on staging to make sure the link appears where you want it.

Example: retaining automatic-update information

<p>An automatic update finished on {sitename}.</p>
<p>Update category: {update_type}. Result: {update_status}.</p>
<div>{original_message}</div>

Keep {original_message} when you need the detailed update result and native instructions. The custom introduction can provide your own wording without relying on a short status value to explain an entire failure.

Subjects, HTML and links

Subject fields are for plain text and supported text placeholders. Put account links and dynamic message sections in the body. Use simple email-friendly HTML, clear link labels and readable paragraphs; do not rely on JavaScript or interactive website components in email content. Template HTML is sanitized when saved.

Preview both short and long values, including customer names and order numbers. A fictional preview shows your wording, while a real staging notification verifies the event’s actual data, native layout and mail transport.

WooCommerce Editing Guide

Choose the mode that matches your change

  • Default: retain the native WooCommerce body. A separately configured subject override can still apply; clear the subject too when you want its native value.
  • Custom text: edit introductory and closing copy, plus optional heading/footer values. The supported adapter inserts the native transactional sections and required account/payment links automatically.
  • Advanced body: arrange custom HTML and the required dynamic blocks inside the native WooCommerce header/footer. This mode requires more careful staging checks.
  • Disabled: block the selected email through the plugin’s WooCommerce sending controls, including its applicable manual/direct-send gates.

For Custom text and Advanced body, blank headings and footers retain their native values. The custom body replaces native introductory/additional prose, so include your store’s relevant instructions in the authored copy. Keep the email enabled in WooCommerce itself when you want a custom message to send.

WooCommerce body tokens and required blocks

WooCommerce body tokens use a separate context from WordPress templates. Common body values include {customer_first_name}, {customer_name}, {username}, {store_name}, {order_number}, {order_total} and {order_status}. Availability depends on whether the message concerns an order or an account.

Order messages expose {order_details}, {order_meta} and {customer_details} for native sections. Payment-related values use {payment_link} or {payment_url}. Customer-note messages expose {customer_note}. Account messages use {account_link} / {account_url} and {set_password_link} / {set_password_url}. Reset messages use {password_reset_link} / {password_reset_url}.

In WooCommerce bodies, a _link token supplies a ready-made labeled link, while its _url partner supplies the address for your own link markup. This differs from the WordPress {password_reset_link} URL example above. Do not wrap a WooCommerce _link block inside another anchor.

Advanced order bodies require {order_details} and {customer_details}. Invoices also require a payment link/URL; notes also require {customer_note}. Account bodies require account and setup links/URLs, and reset bodies require a reset link/URL. Place native section blocks in the visible body rather than in HTML attributes. Custom text includes the appropriate sections automatically.

Sending Rules and Administration

Understanding effective sending rules

A template is used only when its event is permitted to send. Network blocks take precedence over local preferences. Applicable local switches, role restrictions and update-result preferences can also prevent a notification. WooCommerce’s own settings and other plugins can independently prevent or change delivery.

When a supported role selection is empty, all roles qualify. When one or more roles are selected, a user with several roles qualifies if any one of those roles matches. Selecting roles does not override a disabled sending switch or a network block.

Use Settings → Tools to explain the plugin’s saved policy for a notification without triggering an actual email. This evaluates plugin rules; it does not inspect the final decision of every extension or confirm that an event occurred.

Administrator alert routing

Routing is limited to the supported administrator alerts: new-user registration alerts, comment moderation, automatic-update results, and the standard WooCommerce new/cancelled/failed order administrator alerts. Enter up to ten valid addresses for each configured route. A configured route replaces the To recipients for that alert; unrelated headers remain intact.

Customer notifications and account-recovery messages are not rerouted through this feature. Leaving a route blank retains the incoming recipient list, and routing does not recreate a recipient list that was already suppressed.

Revision and configuration workflows

Loading a revision changes the editor draft so you can inspect it before saving. It is not an instant rollback. Histories are bounded, and configuration exports do not include revision history, logs or network policies.

Before importing configuration, review the source and the settings it contains. Supplied fields replace their local counterparts after validation. Importing authored templates from another store does not guarantee matching native email capabilities, theme layouts or extension availability on the destination. Preview and verify the affected messages there.

Installation

You can install the Smart Notification Manager plugin directly from the WordPress repository.

  1. From your WordPress dashboard, navigate to Plugins → Add New.
  2. In the search bar, type Smart Notification Manager.
  3. Click Install Now, and once installed, click Activate.
  4. Open Notifications → Settings for sending rules, roles, branding, tools and logs.
  5. Open Notifications → Custom Emails for WordPress templates, or Notifications → WooCommerce Emails for detected WooCommerce emails.

Manual ZIP installation

If you have a plugin ZIP, open Plugins → Add New → Upload Plugin, select the ZIP, install it and activate it. For an existing installation, back up the site before replacing the plugin files. Keep only one active copy of Smart Notification Manager to avoid loading duplicate plugin classes.

WooCommerce is optional. WordPress notification controls are available without it. The WooCommerce submenu displays registered emails when WooCommerce and the relevant email-providing extensions are active.

FAQ

Can I change email subject lines?

Yes. Notifications → Custom Emails supports per-notification subjects; leave a subject blank to retain the original. WooCommerce subjects are configured under Notifications → WooCommerce Emails. Subjects support text placeholders, with order-number and total placeholders available for WooCommerce order emails. Recovery links and full message content belong in bodies.

How do I include the password reset link in my custom email?

Use {password_reset_link} in your welcome or password-reset body. A working link is appended if the placeholder is omitted. Preview and test tools use fictional links and never generate real password keys.

Is Smart Notification Manager compatible with WordPress Multisite?

Settings and log tables are isolated per site, including when another plugin switches the current site. Storage is upgraded lazily for each site, so network activation does not create all tables at once. Deactivation clears maintenance schedules and deletion removes plugin data across the network in batches. Network administrators can enforce per-notification blocks under Network Admin → Settings → Notification policies. Blocks are scoped to the current network and take precedence over local switches. Network signup/activation messages and manual-action-required core notices remain outside these blocks; full network signup compatibility is not claimed.

How do previews and test emails work?

Open a body on Custom Emails and choose Preview or Send sample to my email. These use the current editor content, including unsaved edits, and fictional account data. Blank bodies show an illustrative default rather than an exact copy of every WordPress message. Tests go only to the signed-in administrator profile address, at most once per minute. Mailer acceptance does not guarantee delivery.

What does Reset to default do?

It clears the custom body in the editor. Save Changes to persist the reset; leaving without saving retains the saved body. An empty role selection allows all roles. Sending switches take precedence over templates and role selections.

How does log retention work?

Logging settings lets you stop new decision records or retain them for 1–365 days (30 by default). Turning logging off does not immediately delete existing records. Daily WordPress cron removes expired rows in batches; low-traffic sites may run cleanup late, and sites disabling WP-Cron need a server cron job. Existing option-based logs migrate to an indexed per-site table with retry protection. The legacy option is deleted only after a successful import. Only compact event metadata is retained, not message bodies, reset keys, recipient addresses or full update results.

What versions and email integrations are supported?

Requires WordPress 6.1+ and PHP 7.4+. The minimum follows the core registration send-decision filters. The plugin preserves incoming recipients, subjects and unrelated headers unless an explicit subject or administrator-recipient override is configured. Custom SMTP/routing plugins can still alter delivery. WooCommerce Emails discovers the active email registry. Custom bodies cover the 11 classic core account/order email types; extension emails and WooCommerce block-editor emails retain native bodies unless a compatible classic-section adapter explicitly opts in. Newer core types outside that set also show subject/control-only capability. Object methods supply order context, without assuming posts-based order storage. WooCommerce-native layouts are preserved. PHP syntax and automated regression checks do not constitute certification of every WordPress, WooCommerce, SMTP, PHP or multisite combination.

How do branding, plain-text alternatives and revisions work?

Branding & policies offers an optional shared heading, accent and footer for managed WordPress emails. WooCommerce retains its native layout. Plain-text alternatives are generated for tracked HTML messages through the WordPress PHPMailer pipeline, preserve link URLs, and do not replace an existing alternative. API mail plugins may handle multipart messages themselves. The last five previous subject/body versions of each core template and five structured versions per WooCommerce email (up to 50 email types) are stored without autoloading. WooCommerce custom HTML messages receive an alternative generated from the final customized body so native multipart text cannot contradict it. Load a revision into the editor, review it, then Save Changes to apply it.

What do delivery results mean?

Allowed/customized are policy decisions. Mailer accepted means the WordPress mailer processed the send without reporting an error, not that a recipient received it. Mailer failed means the mailer reported failure. Handled by another mail plugin means an API/SMTP plugin short-circuited WordPress sending; its final delivery status is unavailable here. Only messages identified as managed notifications are tracked. Raw error text, bodies, recipient addresses and reset keys are not retained in logs. The internal per-message trace header is removed before PHPMailer transport.

Can I route alerts or transfer settings?

Branding & policies allows up to ten To addresses for each administrator alert. Blank retains existing recipients, and an empty/suppressed recipient list is not recreated. Customer and account-recovery emails cannot be rerouted. Tools exports/imports schema-validated local configuration JSON, excluding logs, revisions and network policies. Exports can contain routing addresses and authored template content; treat them as private configuration. Invalid schemas, unknown settings, field types and invalid lists/maps are rejected before settings change. Imports sanitize content and retain changed templates as revisions.

How can I explain blocked emails or adjust update alerts?

Tools evaluates saved site/network switches, role restrictions, WooCommerce controls and update-result settings without sending mail. Role checks accept any matching role for a multi-role user. Branding & policies independently controls successful, failed/partly failed, and critical core update results. Failure and critical types are enabled by default. The existing General master switch and network blocks still take precedence; manual-action-required core notices remain enabled.

How do I customize detected WooCommerce emails?

Open Notifications → WooCommerce Emails. Choose Custom text to edit the heading, introduction, closing and footer while automatically retaining native order/download/customer sections and required account/payment links. Advanced body allows HTML and dynamic blocks inside WooCommerce’s native header/footer. Required blocks are checked on save; missing native sections or account keys at send time retain the original message and record a fallback. Default keeps native content; Disabled blocks this email through the native enabled/recipient gates. Restoring defaults clears the subject and body configuration in the editor; Save Changes applies it. Selecting a mode replaces earlier local Woo sending switches for that email; network blocks still win. WooCommerce’s own disabled setting stays effective.

Body values are escaped and token substitution runs once. Order data uses object getters, including HPOS orders. Account links reuse the original generated key; customization never generates another key. Emails continue through WooCommerce’s existing trigger and mail callback, preserving recipients, headers and attachments. Theme templates must emit the standard WooCommerce header/footer and transactional section actions; otherwise the original message is retained. Custom text/body modes replace native introductory/additional prose, so include any store-specific instructions or legal text in your custom copy. They do not copy arbitrary PHP templates into an editor.

What are the storage and compatibility limits?

Up to 50 non-default WooCommerce configurations are stored in a separate non-autoloaded option. UTF-8 byte limits are heading 200, introduction/closing 5,000 each, footer 2,000 and advanced body 20,000. Configuration imports allow up to 3 MB. Histories keep five previous configurations for up to 50 recently changed Woo email types. Missing providers retain saved settings; inactive configurations are listed separately. Detection observes WooCommerce’s lazy registry, avoiding mailer initialization on ordinary frontend requests.

Extension adapters may filter senm7s_woo_body_capability with a supported profile (order, invoice, note, account, reset) only after verifying their classic section actions and required account/order context. This opt-in does not supply an arbitrary renderer: missing sections still fall back. Block-editor bodies require a dedicated future integration and remain native. Mail callback replacements, theme overrides and other email designers require staging verification. Previews are illustrative, side-effect-free samples, not exact screenshots of the final WooCommerce theme. See tests/STAGING-CHECKLIST.md before enabling custom bodies on a store.

Screenshots

Changelog

1.0.2 – 2026-11-16

  • Expand documentation with a setup walkthrough, notification coverage, separate WordPress/WooCommerce token guides and examples, sending-rule explanations, troubleshooting and data/removal guidance.
  • Consolidate the 1.0.1 development series into the next production release, including corrected registration/reset suppression, existing-key reuse, preserved recipients/attachments and safe HTML template handling.
  • Include accessible send controls, role selection, lazy editors, fictional previews, administrator samples and scoped mailer diagnostics.
  • Include indexed per-site decision logs, retry-safe legacy migration, configurable retention, bounded cron cleanup and multisite lifecycle cleanup.
  • Include subject overrides, optional WordPress branding, URL-preserving plain alternatives, bounded revisions, administrator alert routing, update-result controls, validated configuration transfer and network notification policies.
  • Include the detected WooCommerce email library with Default, Custom text, Advanced body and Disabled modes, capability notices, required transactional blocks and native-content fallback. Block-editor and unadapted extension bodies remain native.
  • Move Custom Emails and WooCommerce Emails to dedicated submenus under Notifications; retain legacy editor URLs and load the correct editor assets for each submenu.
  • Remove the email editor tabs from Settings and document the updated navigation and consolidated release features.

1.0.1.5 – 2026-11-15

  • Discover registered WooCommerce core/extension emails lazily and add per-email Default, Custom text, Advanced body and Disabled modes with explicit body-capability notices.
  • Customize classic core headings, introductions, closings, footers and advanced HTML using native order/download/metadata/customer blocks and existing payment/account/reset links.
  • Preserve WooCommerce triggers, mail callback, recipients, headers and attachments; capture native sections without rerunning their hooks, validate required blocks and retain original messages when context is unavailable.
  • Add sandboxed fictional previews, administrator-only samples, lazy advanced editors, draft revision loading and default restoration with unsaved-change tracking.
  • Store Woo bodies and bounded structured history without autoloading; include them in validated configuration transfer and multisite cleanup while retaining unavailable-provider preferences.
  • Extend dynamic subjects, manual-send gates, network policy retention, readable fallback logs, PHP 7.4/8.5 rendering/storage and JavaScript editor checks.

1.0.1.4 – 2026-11-15

  • Add per-notification subject overrides with placeholder rendering, UTF-8-safe limits and handling for core subject formatting.
  • Track managed-message mailer acceptance, failures and API-plugin handoff separately from policy decisions without retaining message content or raw error text.
  • Add independent success/failure/critical update-result controls while preserving existing master switches and external suppression.
  • Add optional shared WordPress email branding and URL-preserving multipart plain-text alternatives; preserve existing integration alternatives.
  • Retain the last five previous core-template subject/body revisions without autoloading and support loading them into an editor before saving.
  • Add administrator-only recipient routing, validated configuration JSON export/import and saved-policy explanations.
  • Add 11 standard WooCommerce notification switches and subject overrides using order-object context; enforce explicit blocks for manual invoice flows, cover paid invoice subjects and preserve native WooCommerce layouts.
  • Add network-admin notification blocks scoped to each network, enforce them over local settings and clean policies/revisions on uninstall.
  • Extend captured core-mail, PHP admin rendering, policy isolation and real database persistence checks.

1.0.1.3 – 2026-11-15

  • Replace serialized option logging with indexed per-site rows, prepared SQL filters and database pagination/counts.
  • Add restartable legacy log migration with import deduplication, an expiring upgrade lock and explicit non-autoloading of legacy data.
  • Add optional logging and 1–365 day retention, with scheduled cleanup in bounded batches and maintenance status warnings.
  • Retain only compact allowlisted event metadata; omit message bodies, recipient addresses, reset keys and raw update results.
  • Initialize visual editors only when their panels open; avoid loading admin classes on ordinary frontend requests.
  • Normalize settings by field type, ignore unknown keys, avoid unchanged writes and refresh cached settings after site switches.
  • Clean up per-site tables, settings and maintenance schedules across multisite networks on deletion; stop maintenance on deactivation.
  • Correct WooCommerce feature claims, qualify multisite/network email coverage, and document cron and compatibility limits.
  • Add real database migration/retention/query tests and multisite lifecycle regression coverage.

1.0.1.2 – 2026-11-15

  • Add positive send switches with explicit statuses, accessible labels and visible keyboard focus while retaining existing settings.
  • Show effective sending policies beside collapsible template editors; replace role multi-selects with searchable checkboxes.
  • Warn about unsupported placeholders, omitted setup/reset links and missing original update details, both during editing and on save.
  • Add previews and administrator-only sample emails using fictional account data, nonce protection and a one-minute test cooldown.
  • Add per-template reset-to-default actions and unsaved-change protection for text and visual editors.
  • Add readable log event names, status badges, combined type/status filtering, 20-row pagination and expandable details.
  • Load editor assets only on the Custom Emails tab and remove the admin script dependency on jQuery.

1.0.1.1 – 2026-11-15

  • Fix registration and password-reset suppression using WordPress send-decision filters, including role rules.
  • Reuse the existing WordPress welcome setup link and retain setup/reset links in custom bodies.
  • Apply comment moderation and core/plugin/theme update templates with documented event placeholders.
  • Preserve existing recipients, subjects, attachments and unrelated headers when customizing email bodies.
  • Record allowed/customized decisions instead of claiming successful sending; identify historical sent entries as unverified.
  • Correct email-change labels to distinguish old-address notifications from new-address verification.
  • Separate update hook adapters and log compact, correctly classified update metadata.
  • Preserve literal template bodies such as 1 and false during settings updates.
  • Require WordPress 6.1 for the registration send-decision filters and synchronize build version declarations.

1.0.1

  • Compatibility update with WordPress 6.9

1.0.0

  • Initial release
  • Added email disabling
  • Added custom email templates
  • Added role-based rules
  • Added WooCommerce integration
  • Added email logging and cleanup option