Getting Started
Learn what CartBay does, confirm requirements, install the plugin, activate your license, and launch your first recovery sequence.
CartBay Documentation
Recover abandoned WooCommerce checkout revenue with consented capture, a three-email sequence, restore links, coupons, analytics, and safe AI-agent controls.
What It Does
Section titled “What It Does”CartBay helps WooCommerce stores recover abandoned checkout revenue. It captures opted-in checkout visitors, tracks abandoned carts, sends a focused three-email recovery sequence, restores carts through secure links, offers optional recovery coupons, and reports recovered revenue inside the WordPress admin.
How CartBay Works
Section titled “How CartBay Works”
CartBay captures a customer’s email from the checkout page when they enter it (classic and block checkouts are both supported). If the customer leaves without completing the purchase, CartBay marks the session as abandoned after a configurable timeout. A sequence of up to three recovery emails is then sent automatically, each with customizable timing and optional discount coupons. Every email includes a unique restore link that, when clicked, reloads the customer’s cart and redirects them to checkout. Analytics track the full funnel — tracked, abandoned, recovered, and revenue — so you can measure recovery performance at a glance.
Core Capabilities
Section titled “Core Capabilities”- Consent-based checkout capture for classic checkout and WooCommerce Block Checkout.
- WooCommerce-native abandoned cart sessions stored through order objects.
- Action Scheduler-powered abandonment detection and email scheduling.
- Three recovery email steps with editable WooCommerce email templates.
- Secure restore and unsubscribe links using hashed tokens.
- Optional CartBay-generated recovery coupons with validation safeguards.
- Overview analytics for tracked carts, abandoned carts, recoveries, revenue, restore clicks, and failed restores.
- Notification tracking for queued, attempted, sent, failed, retry-queued, delivered, and canceled recovery emails.
- Optional protected AI-agent REST and WordPress Abilities access.
Main Workflows
Section titled “Main Workflows”- Install CartBay and activate the license.
- Configure checkout capture, consent text, and abandonment timeout.
- Set the three-email recovery sequence timing.
- Customize recovery email templates in WooCommerce email settings.
- Configure recovery coupons in Offers if your sequence uses incentives.
- Verify email delivery with Test Mode and the test flow.
- Monitor CartBay Overview and Notifications after launch.
Start From
Section titled “Start From”User Guide
Configure CartBay admin sections for capture, recovery sequence, notifications, templates, offers, settings, and troubleshooting.
Developers
Review CartBay architecture, storage, REST routes, hooks, background jobs, templates, emails, build, and QA references.
AI Agents
Use protected agent access, safe automation workflows, and operational guardrails for CartBay AI-agent integrations.
Quick Links
Section titled “Quick Links”- Requirements
- Installation
- License Activation
- Quick Start
- CartBay Overview
- Capture
- Recovery Sequence
- Templates
- Offers
- Notifications
- Settings
- FAQ
Who This Is For
Section titled “Who This Is For”- Store owners who want to recover more WooCommerce checkout revenue.
- Store administrators who need to configure capture, emails, coupons, and reporting.
- Support teams who need to diagnose email delivery, restore links, coupons, or recovery attribution.
- Developers who need architecture, storage, REST API, hooks, templates, and QA details.
- AI agents and automation systems that need safe, least-privilege CartBay workflows.
How to Navigate This Documentation
Section titled “How to Navigate This Documentation”Start with Getting Started if you are installing CartBay for the first time. Use the User Guide when configuring a specific CartBay admin section. Use Developers for architecture, integration, and extension details. Use AI Agents when enabling automation or MCP-based workflows. Use Others for FAQ, discovery endpoints, and documentation metadata.