Renewal Rescue for WooCommerce
| 开发者 | lukeaxiomflow |
|---|---|
| 更新时间 | 2026年9月4日 07:35 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Every retry in the pipeline: which renewal, how much, when the next attempt runs.
- Recent outcomes: which retries recovered the payment, which failed.
- "Needs a human": renewals that failed every automatic retry and are still unpaid — nothing further happens on its own for these.
- Recovered-revenue counter: renewals and amount that came back through retries in the last 30 days.
- Which of your gateways can actually run an automatic retry (manual methods like bank transfer can't).
- One-click enable for the retry system itself if it's off (it writes the standard WooCommerce Subscriptions setting).
- Edit the number of retries, the wait between attempts, which attempts email the customer or the store owner, and the order/subscription status applied while waiting.
- Live "runs at T+X" preview of the whole schedule.
- Applied through the retry system's own documented
wcs_default_retry_rulesfilter — WooCommerce Subscriptions keeps doing the retrying; you finally control the schedule. - Hard safety bounds (each wait 1 hour–14 days, up to 8 retries, whole schedule inside 30 days) and one-click reset to the built-in rules.
- Digest email (daily or weekly): exhausted retries needing action, what runs next, what got recovered. Only sent when there's something to say.
- Site Health checks: retry system off, exhausted unpaid renewals, retry actions sitting past-due in the queue.
- WP-CLI:
wp rrwc status --format=json. - Event log history is your setting, defaulting to keep everything. It is housekeeping, not a tier: no build removes the bound for you.
- Gateway-specific retry schedule (treat PayPal failures differently from Stripe).
- Retry timing windows — run retries in business hours, skip weekends.
- Card-expiry pre-dunning: email customers to update their card before the renewal fails.
- Your own recovery email at chosen attempt numbers.
- Slack / webhook alerts when retries are exhausted (HIGH VALUE flag above your threshold).
- REST status endpoint and CSV export for agencies.
安装:
- Install and activate. You'll find Renewal Rescue in the admin menu.
- It expects the WooCommerce Subscriptions extension (or another plugin built on subscriptions-core, e.g. WooPayments subscriptions). Without one, the cockpit simply waits.
- If the retry system is off, the cockpit offers the one-click enable. Then set your schedule under Retry Schedule.
屏幕截图:
常见问题:
Does it work without WooCommerce Subscriptions?
It activates fine but has nothing to watch: the failed-payment retry system it manages is part of WooCommerce Subscriptions (and subscriptions-core hosts such as WooPayments subscriptions).
Does a schedule change affect retries that are already scheduled?
No — that's how the retry system works: a retry keeps the rule it was created with. Your schedule applies to retries created after you save it.
What happens if I set fewer retries than the built-in five?
Retries stop after your last row, and the renewal order is treated as failed sooner. The editor shows the full timeline so this is never a surprise.
Which gateways can retry automatically?
Only gateways that support charging the stored payment method again (Stripe, PayPal vaulting, WooPayments and similar). Manual methods — bank transfer, cheque, cash on delivery — always need the customer to pay. The cockpit lists your gateways with their capability.
Does it change or delete any WooCommerce Subscriptions data?
No. It reads the retry pipeline; the only writes are the standard enable-retry setting and your saved schedule (applied via the documented filter). Uninstalling removes only Renewal Rescue's own table and options.
Where do the customer retry emails come from?
The standard WooCommerce Subscriptions retry emails — your schedule chooses on which attempts they go out. Pro can additionally send your own custom recovery email.
更新日志:
- Initial public release: failed-renewal cockpit, no-code retry schedule editor with a runs-at preview, recovered-revenue tracking, exhausted-retry watchlist, digest email, Site Health tests and WP-CLI with JSON.