by
WPAnchorBay
1 (0 reviews)
CartBay - Abandoned Cart Recovery for WooCommerce
Recover WooCommerce abandoned carts with a focused, consent-based 3-email recovery sequence. No custom tables. Set up in minutes.
CartBay ranks #66,435 among WordPress.org plugins with 1+ active installations, a 1/5 rating from 0 reviews, and was last updated Sep 9, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v1.1.1
Current Version v1.1.1
Updated 2 weeks ago
Last Update on 09 Sep, 2026
Refreshed 11 hours ago
Last Refreshed on
Downloads -61.9% this week
Rank
#66,435
—
No change
Active Installs
1+
-50%
KW Avg Position
N/A
—
No change
Downloads
282
+1 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
53,498
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 9 more installs to reach 10+
Rank Changes
Current
#66,435
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.1.1
- Last Updated
- Sep 09, 2026
- Requires WP
- 6.6+
- Tested Up To
- 7.1
- PHP Version
- 8.0 or higher
- Author
- WPAnchorBay
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about CartBay - Abandoned Cart Recovery for WooCommerce
Yes. CartBay requires WooCommerce 9.8 or higher and WordPress 6.6 or higher.
They solve different halves of the problem, and CartBay covers the half where most of the money is. WooCommerce's feature (an experimental option under WooCommerce > Settings > Advanced > Features) acts on an order that already exists. A shopper has to fill in checkout, press Place Order, and then not pay — WooCommerce keeps that order as pending and, two hours later, sends one email linking back to the order's payment page. CartBay acts earlier, where the drop-off actually happens. Most shoppers never press Place Order at all: they reach checkout, start filling it in, and leave. No order is ever created, so there is nothing for WooCommerce's feature to act on. CartBay captures the email at that moment — with the shopper's explicit consent — and recovers the cart itself.
Recovery before an order exists — the abandonment that never reaches Place Order. A three-email sequence with independently configurable delays, instead of a single email at a fixed two hours. Consent-first capture, with an unsubscribe link, a hashed suppression list, and WordPress's own privacy export and erase tools wired in. Real cart restore — the shopper's cart is rebuilt with variations, merged into whatever they have now, and clamped to current stock, rather than being sent to a payment page for one specific order. Secure, expiring restore links — hashed and valid for 48 hours, rather than a standard order-pay URL that does not expire. Coupons, including validity checks before sending so a dead code is never emailed. WooCommerce's feature has no coupon support at all. Reporting — captured, reminded and recovered carts, with recovered revenue attributed to the email that earned it.
No. While CartBay's capture is enabled, CartBay tells WooCommerce to stand down using the woocommerce_abandoned_cart_recovery_suppress filter that WooCommerce provides for this purpose, so one shopper never receives recovery mail from both systems. Note that WooCommerce's automatic sending is off by default in any case — it has to be enabled under WooCommerce > Settings > Emails > Abandoned cart recovery. CartBay's own session records are never picked up by WooCommerce's feature either, because they are not checkout orders. If you would rather run both, add this to your theme or a small plugin: add_filter( 'cartbay_suppress_woocommerce_recovery_email', '__return_false' ); Turning CartBay's capture off leaves WooCommerce's feature exactly as you configured it.
You do not need to. If you do turn it on, leave CartBay's capture enabled and CartBay will keep the two from overlapping. The one thing WooCommerce's feature adds that CartBay does not is a manual "send a recovery email" button on the order edit screen for a specific unpaid order.
Yes. CartBay natively supports both the classic checkout and the WooCommerce Block Checkout. On Block Checkout the consent field appears in the contact section as a WooCommerce additional checkout field.
Open WooCommerce > CartBay > Templates and click Edit in WooCommerce for the email you want to change. Each recovery email is a native WooCommerce email, so you can edit its subject, heading, preheader, body, button text, and additional content, and it automatically uses your store's WooCommerce email logo, colors, and footer - with the same preview and test-send tools as your other WooCommerce emails. Supported placeholders include {restore_url}, {coupon_code}, {coupon_expiry}, and {unsubscribe_url}.
No. CartBay strictly uses WooCommerce-native order storage and is fully compatible with WooCommerce HPOS (High-Performance Order Storage). There are no custom database tables.
CartBay Free lets you reference a coupon you created in WooCommerce > Marketing > Coupons and include it in your recovery emails as plain text for the shopper to enter at checkout. Automatically generated, unique, single-use expiring coupons that auto-apply at checkout are part of CartBay Pro.
Yes. Capture and recovery work normally. CartBay Free does not auto-apply coupons; any coupon code you configure is included in the recovery email as plain text for the shopper to enter at checkout.