WakeMyCart – Abandoned Cart Recovery for WooCommerce

WakeMyCart reminds opted-in WooCommerce shoppers about unfinished checkouts, keeping recovery records in WordPress.

Use WordPress email, connect an SMTP server directly or use your own Resend account. Free needs no WakeMyCart account or subscription; your email provider’s limits and charges still apply.

Included in Free

• Checkout cart capture with shopper permission.
• One reminder per eligible opted-in checkout, with an editable subject, message and delay of 1–168 hours after the last checkout activity.
• Three email layouts, your store logo and accent color.
• Email previews and test emails to one address you choose.
• Cart restoration through a confirmation page, plus unsubscribe controls.
• Recorded recovery activity, attributed orders, queued reminders and Recovery health. Attribution does not prove additional sales or profit.
• Separate capture/sending controls, frequency safeguards and privacy export/erasure.

How it works

1. A shopper gives reminder permission at checkout.
2. For eligible unfinished checkouts, WakeMyCart schedules one reminder and rechecks recorded permission, unsubscribes, sending settings, frequency safeguards and recorded purchases before sending.
3. The shopper follows the email link and confirms cart restoration.

On a new installation, capture and sending are off until you enable them.

Checkout permission is recorded from the shopper’s checkout choice and stored on this site; it does not verify ownership of the entered email address. Capture and sending safeguards reduce abuse but cannot prevent every unsolicited request.

Optional separate Pro add-on

Pro is an optional paid add-on installed separately from Free. It adds multi-stage sequences, cart saving before checkout, conditional follow-ups, advanced designs, experiments, cost-aware offers and detailed reports. All included Free tools remain available without Pro.

Keep Free active as the shared recovery engine. Pro needs one successful activation through an eligible account per store; private downloads and automatic updates require eligible access. Activated local tools continue through subscription expiry or temporary service outages. Pro activation currently supports single-site WordPress installations.

Free and Pro | Setup guide | Support

External services

Email delivery

WordPress email uses your store’s mail configuration. Direct SMTP connects only WakeMyCart recovery mail to the server you choose, using authenticated STARTTLS or TLS. Test and recovery sends share sender/recipient addresses and message contents with that server. SMTP credentials are encrypted in your WordPress database and are never sent to WakeMyCart’s account service. Your provider’s terms, privacy policy and limits apply. With Resend, saving the sender triggers authenticated domain checks at https://api.resend.com using your API key. Routine periodic checks normally run no more than once every six hours, even with recovery paused. Checks retrieve domain-verification status, not shopper records. Test/recovery emails send sender/recipient addresses and message contents. Optional signed delivery feedback reaches your store’s webhook.

Saving a WordPress email or SMTP sender stops routine Resend checks and pauses recovery. Prepared messages retain their original provider configuration. To end Resend access, keep recovery paused, disable optional Pro cart emails, review pending messages and revoke the Resend key. In-flight requests cannot be recalled. Provider retention is separate.

Resend privacy | Resend terms

Optional WakeMyCart account

Local Free recovery needs no account connection. Explicit connection for Pro activation, private updates, downloads or account services sends merchant account/store-registration information, installation/protocol identifiers and coarse recovery-health codes. Normal local-engine account requests exclude shopper names, emails, carts, products, orders, messages, recovery tokens and shopper hashes.

Disconnect in Setup & settings to stop account-service requests. Free updates use WordPress or a manual ZIP without an account; only Pro requests authenticated private updates. Older cloud records need reviewed cleanup. Old links and delivery feedback may use a temporary compatibility relay for up to 365 days, an exception to local-only recovery processing.

Once the local engine is active (including migration hold), old direct rk_restore links are retired and return an unavailable-link message. This prevents stale legacy permission from bypassing local withdrawals. Current local links and the authenticated migration relay retain their current consent, suppression, expiry and purchase checks; the relay does not reactivate old direct links.

WakeMyCart privacy | Service terms

Data and removal

The 1.1.22 upgrade preserves the original reminder/sequence settings in a separate non-autoloaded local option before creating Free’s single reminder. Pro maintains its own sequence settings. Reviewed settings imports retain the original input locally; no shopper list is imported by the CartFlows settings importer. These settings archives remain until explicit plugin-data deletion on uninstall. Legacy cloud jobs with unproven ownership remain held for review and are not replayed automatically.

Cart snapshots normally remain for 30 days after activity; recovery detail for 90 days. Terminal prepared email bodies are cleared after 48 hours. Unsubscribe links can last 365 days; anonymous local summaries 13 months. Minimal suppression keys prevent renewed contact. Cleanup needs a working scheduler. Provider records, backups and WooCommerce orders have separate retention.

Checkout-capture abuse counters store purpose-separated, hourly keyed hashes of the entered address and direct network peer, counts and window times, not raw addresses or IPs. Counters expire two hours after their UTC-hour start and are removed by bounded cleanup on capture and scheduled maintenance; a stopped scheduler can delay deletion. Storage is capped at 4,096 counters plus one nonpersonal coordination row. WordPress personal-data export/erasure includes the recipient’s temporary counters; shared peer/store controls expire separately. A backwards server-clock change pauses positive capture rather than resetting its budgets.

After Pro removal, shared privacy tools still cover prior cart-email requests: details/links expire after seven days, de-identified counts after 30 days and hashed abuse limits after two days, with scheduled cleanup.

WordPress Tools > Export/Erase Personal Data covers recovery records. Erasure blocks stale callbacks recreating shoppers; historical totals freeze when underlying recovery order copies are deleted. Deactivation preserves data. Uninstall deletion is off by default and can be enabled in advanced settings. Removing Pro preserves the shared database. No plugin alone establishes GDPR compliance.

Explicit Pro plans/download/activation actions or Pro reloads can store a task/date per browser, store and administrator. Tasks are used for up to 14 days; expired entries are removed on the next workspace read. Use Forget this task or clear storage to remove them. Pro preview visibility/invitation dismissals persist until restored or browser storage is cleared. Opening a preview records no task. Preferences hold no shopper data, campaign content or credentials; no analytics are sent.

An optional review invitation requires 30 days since the first real scheduled reminder attempt and five first attempts across three UTC days. Failed handoffs count; retries, tests/self-tests and local/development/staging sites do not. Delivery, purchases, revenue or opinions do not affect eligibility. Choose review, remind in 14 days or never. Opening review dismisses it without checking submission. Capped counts/dates and per-user/site reminder preferences stay in WordPress, shared by editions; no shopper identities or review telemetry. Help remains available; its link explains review availability.

Source and translations

Readable workspace source, exact lockfile and build tools: source/README.md. Library licences: THIRD-PARTY-NOTICES.txt. WordPress supplies React/ReactDOM. Translation templates: languages/. Translations cover standard labels and interface, not merchant-written emails.