CartBay

The problem

Every WooCommerce store loses orders the same quiet way: a shopper fills a cart, reaches checkout, and leaves. No error, no complaint — just a cart that never converts. Recovering even a slice of those is some of the cheapest revenue a store can earn, because the intent was already there.

What CartBay does

CartBay captures a shopper’s email at checkout (with consent), notices when a cart is left behind, and follows up with a short, timed sequence of recovery emails — up to three — that brings the shopper back to finish the order:

• Consented email capture at checkout — no dark patterns, on classic and Block Checkout alike, with editable consent text so a store can match its own policy.
• Abandoned-cart detection on a configurable timeout.
• One-click cart restoration via secure hashed-token links, so the shopper picks up exactly where they left off.
• Test mode, so the whole sequence can be rehearsed before a real shopper sees it.

The Pro edition adds the full three-email sequence, auto-generated recovery coupons with validation safeguards that stop them stacking or leaking, and the revenue reporting — tracked, abandoned and recovered carts, restore clicks, and real recovered revenue rather than estimates.

It’s built to WordPress standards (WordPress 6.6+, WooCommerce 9.8+, PHP 8.0+), GPL-licensed, and free on WordPress.org.

Building it at WPAnchorBay

CartBay is the second plugin I’ve taken from a blank repo to a live WordPress.org listing at WPAnchorBay, after ProductBay — same discipline: plain PHP against WooCommerce and WordPress hooks, every input sanitized and every action capability-checked for the wp.org review, and documented so it can be maintained. Shipping a second plugin turned the first one’s lessons into a repeatable process instead of a one-off.