Post Status Notifier is a WordPress plugin that sends email notifications when the status of a post, page or custom post type changes — for example when a contributor submits work for review, an editor publishes it, or a post is scheduled. It is aimed at multi-author blogs, editorial teams and membership or directory sites that need reliable, rule-based alerts rather than the single fixed email that WordPress sends by default. The plugin is sold as Post Status Notifier Utilities on CodeCanyon for $25, developed by ifeelweb.
The commercial case rests on a solid track record: 1,861 sales and a 4.76 out of 5 average across 92 reviews. Those numbers matter here because notification plugins sit close to the publishing workflow, and a weak one is discovered quickly. The vendor also keeps the listing current, with a last update recorded in October 2026 and declared compatibility stretching from WordPress 4.9 through the 7.0.x line.
What the plugin actually does beyond WordPress’s built-in alerts
WordPress already emails an administrator when a new post is submitted or published. That message is fixed, goes to one address, and cannot tell the difference between a draft, a pending review and a scheduled post. Post Status Notifier replaces that single behaviour with a rule engine, and the rule engine is the product.
Rules built from triggers, conditions and recipients
Each notification is a rule. A rule watches for a status change on a chosen post type, optionally filters by category, and then sends to a defined set of recipients. Filters can include or exclude categories — including categories belonging to custom post types — so a site with a busy news section can keep those alerts separate from slower editorial queues. There is also a whitelist and blacklist condition keyed to post IDs, a way to exclude individual recipients by user ID or email address, and a match condition that can be written in the plugin’s own template syntax for cases the built-in conditions do not cover.
Recipients can be WordPress users, users grouped by role (including custom roles created by other plugins), or plain email addresses held in custom lists. That last option is the practical one for clients and stakeholders who should receive updates but should not be given a WordPress account.
Templates with conditionals, loops and dynamic data
Message bodies are written as templates with placeholders. Standard placeholders cover post data such as title, author and status. Dynamic placeholders pull in any custom field or taxonomy term attached to the post, which is what makes the plugin usable on sites built with Advanced Custom Fields or similar tools — a notification can quote a booking date, a price field or a job location rather than just the post title.
The template syntax goes further than simple substitution. It supports if, elseif and else conditions and loops, along with filters that modify placeholder output. The filters follow Twig, a widely used PHP templating engine, so anyone familiar with Twig will recognise the patterns. In practice this means one rule can produce different emails depending on the post’s contents, instead of requiring several near-identical rules.
Delivery controls that matter on real sites
Per-rule settings cover CC, BCC and a custom FROM address, plus multiple file attachments. HTML email is supported, and templates can be saved for reuse across rules. SMTP credentials can be configured in the plugin’s options, which sidesteps the deliverability problems that come from relying on a server’s default mail function.
The mail queue, added in version 1.7, is the feature most likely to be undervalued until it is needed. It defers large batches of generated emails and runs through WordPress’s internal Cron API, with configurable batch size, recurrence and retry limits on failure. On a site where a single bulk publish or import can fire dozens of notifications at once, queueing is the difference between delivered mail and a timeout. Rules can also be exported and imported, which makes staging-to-production moves less painful.
Logging, integrations and extensibility
Optional logging records status changes against the rules that matched, and a dashboard widget surfaces the most recent entries — useful when someone claims they were never notified. The plugin is multisite compatible, ships with English and German translations, and declares compatibility with bbPress, WooCommerce, Easy Digital Downloads, Gravity Forms and the iFeelWeb framework it is built on. Custom modules can be written to add new notification services or new placeholders, and source files (JavaScript, HTML, CSS, PHP) are included.
Where Post Status Notifier fits, and where it does not
The clearest fit is an editorial site with more than one person touching content. A magazine with contributors, sub-editors and a publishing editor can route “submitted for review” to the editor and “published” back to the author, with different wording for each. A agency running client sites can point notifications at the client’s inbox without creating a user account for them.
Directory and marketplace builds are the second strong fit. The vendor names WP Job Manager, Calendarize.it, Crowdfunding by Astoundify and WP User Frontend as plugins it works alongside, and the pattern is the same in each case: a front-end submission changes a post’s status, and someone needs to know. Sites using Frontend Publishing Pro for user-submitted content are pointed at the same workflow.
It is the wrong choice for a single-author blog. WordPress’s default notification plus a transactional email plugin covers that ground for nothing, and the rule engine’s value only appears once there are distinct roles or post types to separate. It is also a poor fit for teams that want notifications delivered to Slack, Microsoft Teams or a CRM as the primary channel rather than email — the plugin is email-first, and other channels require custom module development rather than a setting.
Strengths and limitations
Strengths
- Rules are genuinely granular: post type, status, category, post ID and recipient can all be constrained independently, which is more control than most notification plugins offer.
- Dynamic placeholders reach into custom fields and taxonomies, so notifications carry real content rather than generic post links.
- The conditional template syntax with loops and Twig-style filters allows one rule to serve several scenarios, reducing rule sprawl.
- The mail queue with retry limits handles bulk status changes without flooding or failing silently.
- Logging and a dashboard widget give a record of what was sent, which is the first thing anyone asks for when a notification goes missing.
- Custom recipient lists remove the need to create WordPress accounts for external stakeholders.
- Active maintenance is evidenced by the update history and the breadth of declared WordPress version support.
Limitations
- The template syntax is a real skill. Conditions, loops and filters are powerful, but an editor who only wants to change a sentence in an email will need to learn the placeholder system or ask a developer.
- The browser compatibility list includes Internet Explorer 6 through 11. That is almost certainly inherited boilerplate from the framework rather than a tested claim, and it makes the specification sheet less trustworthy overall.
- Email is the only delivery channel out of the box. Slack, webhook and chat integrations require writing a custom module.
- Only English and German translations are bundled, so other locales depend on the site owner translating the strings.
- The listing does not state a minimum PHP version, which matters for anyone running an older host and is worth confirming with the developer before purchase.
How it compares with the wider notification category
Most alternatives fall into three groups. The first is WordPress’s built-in notification, which is free, requires no configuration and does exactly one thing badly — a single email to the admin address with no control over recipients or content. Post Status Notifier is a straightforward upgrade from that, and the gap is largest on multi-author sites.
The second group is general-purpose email and automation plugins. These are strong at routing form submissions and syncing to external services, and some can watch post status changes as one trigger among many. They tend to be broader but shallower on this specific job: fewer conditions tied to WordPress post status, weaker handling of custom fields and taxonomies in the message body, and no equivalent of rule-level CC, BCC and attachments.
The third group is editorial-workflow plugins that combine notifications with custom statuses, editorial comments and approval chains. Those are the right buy for a team that wants to redesign the review process itself. Post Status Notifier assumes WordPress’s existing statuses are sufficient and concentrates on who hears about them and what the message says. The distinction is worth being clear about before purchase, because the two categories overlap but solve different problems.
Frequently Asked Questions
Does Post Status Notifier work with custom post types and WooCommerce?
Yes. It supports posts, pages and all custom post types, and it handles every post status value rather than only draft and publish. The vendor declares compatibility with WooCommerce 5.x through 9.x, along with bbPress, Easy Digital Downloads and Gravity Forms, so status changes on those post types can trigger rules in the same way.
Can it send notifications to people who are not WordPress users?
Yes. Recipients can be stored in custom email lists inside the plugin, so clients, freelancers and stakeholders receive notifications without a WordPress account being created for them. Recipients can also be selected by user role, including custom roles registered by other plugins, or excluded individually by user ID or email address.
How is Post Status Notifier different from the emails WordPress already sends?
WordPress sends one fixed message to the site administrator. Post Status Notifier lets site owners define any number of rules, each with its own trigger, conditions, recipients, sender address, CC and BCC fields, attachments and templated message body. The message can include custom field and taxonomy data pulled from the post itself.
Will it slow down a site that publishes a lot of content?
It is built to avoid that. The mail queue, introduced in version 1.7, defers large volumes of generated notifications and processes them in batches via the WordPress Cron API, with configurable batch size, recurrence and retry limits. Successful sends can optionally be logged so delivery can be audited afterwards.
Verdict
Post Status Notifier is worth buying for any WordPress site where content passes through more than one pair of hands and the people involved need to know when something moves. The rule engine, dynamic placeholders and mail queue cover ground that free alternatives and general automation plugins do not, and at $25 with a 4.76 rating across 92 reviews the risk is low. Single-author blogs and sites that want chat-based notifications as their primary channel should look elsewhere. Teams that need to redesign the editorial process itself, rather than just notify people about it, should compare it against dedicated workflow plugins before committing.
