WakeMyCart – Abandoned Cart Recovery for WooCommerce

By Plugins.shop

0+ active installationsVersion 1.1.32

WooCommerce abandoned cart recovery with one editable email reminder, cart restore links and local reports. No account required.

Description

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.

Signed-in checkout preference checks store an opaque account key, a random security token and an update time locally. Withdrawal changes this token so an older checkout request cannot silently restore permission. Inactive markers expire after 48 hours; scheduled cleanup removes at most 100 expired markers per run. The next preference check also rejects an expired token. WordPress personal-data tools include marker information and removal for the verified WordPress account email, without exporting the security token. This is separate from the address entered at checkout.

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.

Recovery exports separate current permission and cart state from historical snapshots. Nested data includes readable fields and a labelled Base64 original JSON value for lossless decoding. Text containing markup, entities or backslashes is labelled as HTML entities where necessary for WordPress’s HTML report, with an exact Base64 UTF-8 companion. These are export representations only; stored cart data is not rewritten.

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.

Installation

Requires MySQL or MariaDB with InnoDB tables. SQLite is not supported; on a detected unsupported database WakeMyCart stops recovery before migrating settings and shows an administrator notice without blocking WooCommerce.

For an existing store, back up WordPress first and pause recovery sending. Replace Free with 1.1.32, then optional Pro 1.1.32, without uninstalling. Existing Pro 1.1.27 and 1.1.31 remain compatible; versions older than 1.1.22 are not compatible with the current handler interface. Review settings, waiting messages and message history before resuming. Malformed saved product-bundle selections or reminder text may need correction before recovery can resume; valid Unicode text, template placeholders and supported bundle selections remain available.

New checkouts created while signed in can be associated with that WordPress account using an opaque local identifier. Explicit withdrawal can stop those account-owned checkouts across sessions. Guest checkouts, older records and guest checkouts carried into a login are not assigned to an account by matching an entered email. Their email unsubscribe link stops reminders for that address; withdrawal in the original checkout still stops that cart. Updating does not invent ownership for historical records or recall email already handed to a sender.

  1. Activate WooCommerce and install the Free ZIP or use Plugins > Add New. Test on staging first.
  2. Open WakeMyCart > Set up and test recovery. Choose your sender, edit the reminder and confirm a test email arrives.
  3. Review shopper permission and your privacy notice. Enable capture and sending separately.
  4. Test an opted-in checkout, restoration and unsubscribe. Check Recovery health. Quiet stores need server-triggered WordPress scheduled tasks for reliable timing.
  5. Optional Pro: pause sending, keep Free active, install the compatible add-on, connect and activate this store. Activation leaves the sending switch unchanged; review Pro settings before resuming. Update Free first when Pro requires it. Update separately; do not uninstall.

Cloud or recoverkit-folder copies need migration instructions. Do not delete the original to update. Ask support about reviewed import/sender handover before enabling emails; unknown prior sending outcomes remain held.

FAQ

Does Free capture carts before checkout?

No. Free captures opted-in checkouts; Pro lets browsing shoppers request their cart by email. Neither promises to capture every cart or recover every sale.

Are contacts or reminder frequency limited?

Free has no subscription-based monthly recovery-contact quota. It creates at most one reminder per eligible checkout. A separate safety cap limits reminders to the same shopper email address across checkouts in each UTC calendar month. New installs default to three; you can choose 1–100 in either Free or Pro. Raising this cap does not expand previously recorded shopper permission. Your email provider’s limits still apply.

Positive checkout-capture updates also have shared abuse limits: 60 per entered email address, 300 per direct network peer and 3,000 per store in each fixed UTC hour, with bounded counter storage. Shared networks or reverse proxies can share the peer limit. When a limit or required storage check fails, recovery capture is refused temporarily; normal WooCommerce checkout remains available. Withdrawal and unsubscribe are not subject to these positive-capture limits. These safeguards apply in both editions and do not verify mailbox ownership.

Why has a reminder not arrived?

Check capture/sending controls, permission, delay, frequency limits, order status and Recovery health. Scheduled tasks need a working runner. Test your sender and check provider logs and spam folders. Provider acceptance does not guarantee delivery.

What happens when Pro expires or is disconnected?

Successfully activated local Pro tools continue after subscription expiry; private downloads and updates need eligible access. Disconnecting clears Pro activation and pauses sending while preserving saved work. Free works without an account after you deliberately resume sending.

What if I deactivate or remove Pro?

Free remains available. Pro designs, flows and history remain stored but need the compatible add-on to work. Queued Pro messages and cart-link requests can stop; reinstalling does not replay skipped messages automatically. Cost-protected coupons need Pro’s validator when redeemed. Review pending work and sending controls first. Existing valid links retain expiry and privacy checks.

Where is shopper data stored?

Recovery records stay in WordPress. Sending shares addresses and message contents with your mail provider. Account/migration exceptions are below. WakeMyCart adds no open-tracking pixel. Local reminder links record a click only after successful, confirmed cart restoration; simply opening the confirmation page does not count. Historical click counts are not recalculated. Remote images contact their host. Review provider tracking settings.

More Plugins

The optional More Plugins page lists other Plugins.shop tools. Its catalogue and logos are bundled locally; opening it sends no catalogue or tracking request. External product websites open only when you choose their links. No plugin is installed or activated from this page.

Screenshots

Changelog

1.1.32

  • Keep the current checkout’s saved reminder choice visible after navigation; refresh changed cart contents without creating a second reminder or silently granting permission.
  • Bind new signed-in checkout ownership to the account, not a typed email, and protect cross-session withdrawal against stale capture attempts. Guest and historical checkouts keep their documented boundaries.
  • Preserve quoted and escaped privacy-export data with readable nested fields and explicitly labelled lossless originals; distinguish historical snapshots from current consent.
  • Add paginated message history, outcome reasons and paused-sending feedback to the Free workspace.
  • Correct migration guidance, reminder validation messages, subject personalization, latest-test feedback, navigation and singular reminder wording.
  • Keep Free and Pro release numbers matched at 1.1.32; preserve the separate Pro implementation and existing activation behavior.

1.1.31

  • Report failed stale-message checks as storage failures instead of treating the recovery runner as healthy.
  • Check plugin cleanup lookups before deleting retained data and report cleanup failures so removal can be retried.
  • Preserve the approved interface, Free reminder and separate Pro functionality.
  • Refresh the actual Free interface screenshots and captions; number the optional Pro release 1.1.31 without changing its features.

1.1.30

  • Sanitize sender details before checking required values and saving the sender.
  • Validate product-bundle field types before restoring a saved cart, preserving supported selections and encoded variation values.
  • Check provider responses and signed legacy payloads before using identifiers, timestamps or pagination cursors.
  • Reject unsupported reminder control characters and malformed manual-reconciliation input without changing the approved interface or Free/Pro feature split.

1.1.29

  • Retire direct legacy cart-restore links when the local engine is active so stale legacy permission cannot bypass local unsubscribe or cart state.
  • Count local reminder-link clicks only after a successful, nonce-confirmed cart restoration, not a scanner or preview GET.
  • Add bounded, shared checkout-capture abuse limits while keeping withdrawal and normal checkout available.
  • Stop recovery safely on unsupported database drivers and clarify the MySQL/MariaDB with InnoDB requirement.

1.1.28

  • Validate add-on and nested custom-field identifiers without silently renaming options; reject unsafe recovery data while preserving normal cart additions.
  • Bound checkout JSON decoding and sanitize configured scalar fields before capture, restoration, display and order attribution.
  • Revalidate saved add-on/custom data before restoration and preserve valid configured checkout-field names in order metadata.

1.1.27

  • Validate queued recovery epochs before comparison and refuse malformed values without sending.
  • Load recent-cart message records together instead of querying separately for each cart; storage failures remain visible.
  • Preserve the accountless Free reminder, approved interface and separate Pro feature implementation.

1.1.26

  • Stop imports safely when local recovery records cannot be read, preserving existing shopper withdrawals.
  • Report legacy capture and queue storage failures instead of acknowledging an unsuccessful save.

1.1.25

  • Standardize PHP formatting and improve internal API documentation for maintenance and review.
  • Preserve the single-reminder Free workflow, optional preview switch and existing recovery safeguards.

1.1.24

  • Use a compact, keyboard-accessible switch for optional Pro previews while keeping the header visible.
  • Preserve remembered preview preferences, permanent links and existing recovery controls.

1.1.23

  • Group Agency tools with the optional Pro previews, using the same remembered hide/show preference.
  • Keep Migration in Free’s Advanced tools and preserve the working first-setup navigation.
  • Clarify the internal Explore Pro icon and remove a duplicate sidebar divider.

1.1.22

  • Add Plugins.shop attribution and a local More Plugins catalogue without changing recovery controls.
  • Move optional Pro previews below the working navigation and remember their hide/show preference in this browser.
  • Implement Free recovery as one reminder per eligible checkout, with a singular editor and configuration.
  • Move sequence timing, progression and premium message decisions entirely into the separate Pro add-on.
  • Preserve legacy settings, message identities and uncertain sending outcomes across the matched upgrade.
  • Require a reviewed single-reminder choice for Free settings imports.
  • Clarify the per-shopper monthly safety cap and the separately installed optional paid Pro add-on.
  • Match the current pluginsshop ownership metadata.
  • Report failed privacy reads and unreadable saved-cart exports instead of treating them as completed work.

1.1.21

  • Clarify how to test checkout capture on the same store before enabling recovery.
  • Capture checkout consent immediately instead of waiting for the typing delay.
  • Require a key for a first Resend connection and invalidate stale test acknowledgements after sender changes.
  • Keep setup guidance and the Free reminder label clear.
  • Open setup after activating Free and add a Settings shortcut on the Plugins screen.

1.1.20

  • Connect an SMTP server directly in Free or Pro, alongside WordPress email and Resend.
  • Keep email setup simple with relevant fields, encrypted credentials and a test to your chosen inbox.
  • Existing sender choices stay saved; changing a sender pauses recovery until you review and enable it.

1.1.19

  • Add an honest-review invitation after real use, with remind-later and permanent-dismissal choices.
  • Keep Help and feedback links visible.

Earlier notes: changelog.txt.