MailPoet plugin review and common issues

If using the MailPoet Sending Service, check your account for deliverability warnings in the MailPoet dashboard. The service has built-in reputation management, but spam complaints from recipients degrade your account’s reputation. Clean your list regularly: remove unengaged subscribers, process bounce reports, and ensure all subscribers explicitly opted in. If sending via your own SMTP, ensure SPF, DKIM, and DMARC DNS records are configured for your sending domain. Also avoid spam trigger words in subject lines and ensure your “From” email uses a domain you own.

Abandoned cart automation requires: (1) MailPoet Premium or the abandoned cart feature enabled; (2) the customer reached checkout and entered their email — MailPoet captures the email when it is typed into the billing email field; (3) the automation is active (not paused) in MailPoet → Automation; (4) WP-Cron is running reliably on your server (abandoned cart emails are scheduled via cron). Test by adding a product to cart, entering your email at checkout, then abandoning — check MailPoet → Automation → Recent Activity for the captured email.

Duplicate sends usually occur when a subscriber appears in multiple lists that are both targeted by the same campaign, and MailPoet’s duplicate prevention is not active. Check: (1) in the campaign’s sending settings, verify only the intended lists are selected; (2) enable MailPoet’s “Send to each subscriber once” option if your lists have overlap; (3) if using post notification emails, ensure only one notification automation is active for the same post types. Also verify the subscriber does not appear multiple times in your database with different email case variations (john@example.com vs JOHN@example.com).

In MailPoet → Settings → WooCommerce Emails, enable MailPoet as the sender for WooCommerce transactional emails. Select which WooCommerce email types MailPoet should handle (Order Received, Order Complete, etc.) and design a custom template for each. MailPoet’s templates support WooCommerce dynamic tags that insert order details, product names, prices, and customer information automatically. This gives WooCommerce transactional emails the same branded design as your marketing newsletters.

Go to MailPoet → Emails → New Email → Post Notifications. Select “Immediately” (sends as soon as a post is published) or schedule it (weekly digest of new posts, for example). Choose which subscriber list receives the notification and design the email template — MailPoet automatically inserts the latest post title, excerpt, and featured image. Once enabled, MailPoet monitors for new posts and dispatches the notification automatically with no manual campaign creation needed.

Yes — the MailPoet Sending Service is completely free for sites with up to 1,000 subscribers, and all features (automation, WooCommerce integration, signup forms, post notifications) are available. When your list grows beyond 1,000 subscribers, you need a paid plan or switch to a self-hosted SMTP service. If using your own SMTP (via FluentSMTP or WP Mail SMTP), MailPoet itself remains free regardless of list size — you pay only for your SMTP service.

MailPoet is more beginner-friendly with a simpler interface, dedicated WooCommerce transactional email replacement, and a free sending service that removes SMTP configuration complexity. FluentCRM offers more powerful automation branching, contact-level activity tracking, and flat unlimited-contact pricing that is significantly cheaper at scale. For a small WooCommerce store getting started with email marketing, MailPoet is the faster path. For established stores with large lists or complex automation needs, FluentCRM provides better long-term value.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.