Payment reminders vs follow-up email plugins
Abandoned-cart and follow-up email plugins chase unfinished checkouts. Payment reminder plugins chase created-but-unpaid orders. Different problem, different tool.
Search for "WooCommerce follow-up emails" and most results are abandoned-cart plugins or marketing automation tools. They happily email a customer who left checkout halfway - but a created order waiting on BACS or invoice often falls outside their model.
Two different problems
- Abandoned cart - the customer filled a cart, maybe typed an email, and left without placing an order. The plugin's job is to pull them back to finish checkout. The "order" does not exist yet.
- Unpaid order - the customer completed checkout and the order exists, with a status like Pending or On hold, waiting on a bank transfer, invoice payment, or a card retry. Stock is reserved. The plugin's job is to get that specific order paid or released.
Abandoned-cart tools optimize for conversion: coupons, urgency, win-back sequences. A payment reminder is closer to accounts receivable: the sale is made, and the question is whether the money arrives before the stock hold expires.
Why generic follow-up plugins miss unpaid orders
- Trigger mismatch. Most listen to cart activity or newsletter events, not the "order unpaid for 48 hours" state. An order that never entered a cart flow triggers nothing.
- No gateway awareness. Reminding a Processing Stripe order is spam. A real reminder checks status and payment method together - BACS and invoice yes, paid card orders never.
- No stop-on-paid. Marketing sequences run on timers; they do not always re-check payment state. A "still waiting" email to someone who paid is worse than none.
- Wrong tone. Cart-recovery copy ("you left something behind!") reads badly on an order the customer thinks they already paid for.
What a dedicated payment reminder plugin does
A purpose-built tool treats the unpaid order as the unit of work:
- Status + gateway eligibility - only unpaid orders on pay-later methods get queued. Paid, cancelled, and card-gateway orders are never touched.
- A dry-run preview - before anything sends, you see the exact list of orders that would be emailed - how you avoid reminding 400 stale orders on day one.
- Stop-on-paid - every step re-checks the order before sending. The moment payment arrives, the sequence dies.
- An audit trail - which reminders went to which order, so "did we email them?" has an answer.
Payment Reminders is built this way: automation off by default, a preview before anything sends, and eligibility tied to order status and payment gateway.
Side by side
| Abandoned-cart / follow-up plugins | Dedicated payment reminders | |
|---|---|---|
| Target | unfinished carts, lapsed customers | existing unpaid orders |
| Typical trigger | cart abandoned, time since last order | order unpaid for X hours on a pay-later gateway |
| Knows order status | often not required to | yes - eligibility depends on it |
| Stops when paid | not their model | yes, before every send |
| Goal | conversion | getting a committed order paid |
| Copy style | marketing | accounts-receivable polite |
Can you run both?
Yes, and many stores should - they do not overlap. The cart tool recovers people who never ordered; the reminder tool recovers orders placed and never paid. Keep them in their lanes: do not point cart-recovery at on-hold orders, and do not expect a payment reminder to win back a window shopper.
The verdict
If your store takes bank transfers or other pay-later methods, the unpaid-order problem is real and a generic follow-up plugin will not fix it - use a dedicated reminder tool with gateway awareness, a dry run, and stop-on-paid. If your pain is shoppers who never reach the order screen, that is a cart-recovery problem and a different plugin's job.