Smart detection via a 30-second heartbeat system. When a customer leaves the cart page without purchasing, the module detects inactivity and automatically marks the cart as abandoned after a configurable threshold.

Escalating email sequences bring customers back. Up to 3 professional HTML emails with increasing urgency, each containing a secure one-click link back to their cart.

Guest cart recovery captures the customer's email during checkout — even if they never log in. No sale is lost just because a customer didn't create an account.

Full analytics with pivot tables and graphs. Track recovery rates, revenue recovered, email performance, and trends over time to optimize your strategy.

Admin Dashboard — Abandoned Cart List

The main Abandoned Carts list view shows every tracked cart with status badges, cart value, item count, number of emails sent, and whether the recovery link was clicked. Color-coded decorations highlight abandoned, email-sent, recovered, and expired carts at a glance. Bulk actions let you send reminders or resolve multiple carts at once.

Professional Email Templates

Three responsive HTML email templates with escalating urgency: a purple friendly nudge, a green gentle follow-up, and a red final notice. Each email includes the cart total and a prominent one-click recovery button. Templates use Jinja rendering for dynamic content and support partner language detection.

Settings Panel

All configuration lives in Website > Configuration > Settings under the Abandoned Cart Recovery section. Toggle the module on/off, set the abandonment threshold, configure email delays and intervals, enable guest recovery, and set recovery link validity — all from one clean settings panel.

Analytics Dashboard

The Cart Analytics dashboard provides pivot tables and graphs to analyze abandonment trends, recovery rates, and revenue recovered. Filter by state, group by customer or website, and track performance over weekly or monthly intervals to optimize your recovery strategy.

Dependencies:

• base
• web
• website
• website_sale
• product
• sale
• mail

Compatibility:

• Odoo 17.0 Community Edition
• Odoo 17.0 Enterprise Edition
• Bootstrap 5 compatible
• Works with all standard themes

Automation:

• Scan & mark abandoned carts — every 15 min
• Send recovery emails — every 30 min
• Check recovered carts — every 1 hour

API Endpoints:

• /cart/current_order — Session cart lookup (JSON-RPC)
• /cart/activity — Heartbeat (JSON-RPC, 40 req/min)
• /cart/capture_email — Guest email capture (5 req/5 min)
• /cart/recover/<token> — One-click cart recovery
• /cart/unsubscribe/<token> — One-click email opt-out

File Structure:

ecommerce_abandoned_cart/
├── controllers/
│   └── main.py               # 5 JSON/HTTP endpoints
├── data/
│   ├── cron_data.xml          # 3 automated crons
│   ├── default_config.xml     # 12 default settings
│   └── mail_template_data.xml # 3 email templates
├── models/
│   ├── abandoned_cart.py      # Core model
│   ├── res_config_settings.py # Settings panel
│   └── sale_order.py          # Cart activity + conversion
├── security/
│   ├── abandoned_cart_security.xml  # Groups & rules
│   └── ir.model.access.csv    # ACL permissions
├── static/
│   ├── description/
│   │   ├── icon.png
│   │   ├── index.html
│   │   ├── admin_dashboard.png
│   │   ├── email_templates.png
│   │   ├── settings_page.png
│   │   └── analytics_dashboard.png
│   └── src/
│       ├── css/
│       │   └── abandoned_cart.css
│       └── js/
│           ├── cart_activity_tracker.js
│           └── email_capture.js
├── views/
│   ├── abandoned_cart_views.xml  # Tree/form/search
│   ├── dashboard_views.xml       # Pivot/graph
│   ├── recovery_page_template.xml
│   ── res_config_settings_view.xml
├── wizards/
│   ├── abandoned_cart_bulk_action_wizard.py
│   └── abandoned_cart_bulk_action_wizard_views.xml
├── __init__.py
├── __manifest__.py
├── hooks.py                      # Clean uninstall
├── LICENSE
└── README.md

Step 1 — Customer adds items to cart

A JavaScript widget sends a heartbeat every 30 seconds while the customer is on the cart page. The cart value and item count are tracked automatically.

Step 2 — Customer leaves without purchasing

When the heartbeat stops and the inactivity threshold is exceeded (default: 60 minutes), the cart is automatically marked as abandoned.

Step 3 — Recovery email is sent

A professional HTML email with a direct link back to their cart is sent automatically. Up to 3 reminders at increasing urgency if the customer doesn't return.

Step 4 — Customer clicks and completes purchase

The one-click recovery link takes them back to their cart. When the order is confirmed, the cart is automatically marked as converted. Revenue recovered!

Emails are queued, not sent instantly

Like every email in Odoo (invoices, order confirmations, notifications), recovery reminders are queued through Odoo's standard mail system. The module creates a mail.mail record in the outgoing queue instead of connecting to your SMTP server directly. This keeps the automation crons fast and never blocks them on a slow mail server.

Who delivers the queue?

Odoo's built-in scheduled action "Mail: Email Queue Manager" (Settings > Technical > Scheduled Actions) picks up queued emails and sends them. Its default interval in Odoo 17 is once per hour — so a queued recovery email can wait up to ~60 minutes before it is actually delivered, depending on when it was queued relative to the last run.

"Emails Sent" counts when queued, not delivered

On a cart, Emails Sent and Last Email Sent On are recorded the moment the email is created in the queue — not when it leaves your server. If a customer says "I never received the email", check the actual delivery state, not the cart counter.

Checklist when an email doesn't arrive

• Is an outgoing mail server configured (Settings > General > Discuss > Outgoing Mail Servers) with valid credentials?
• Check the recipient's Inbox and Spam — mail from datacenter IPs is often filtered.
• Inspect the queue: Settings > Technical > Email > Outgoing Mail. State outgoing = still waiting; exception = delivery failed (the reason is stored on the record).
• Click Send on the queued message (or run the "Mail: Email Queue Manager" cron) to force delivery now.
• For faster delivery, lower the interval of "Mail: Email Queue Manager" (e.g. to every 5 minutes) — recovery emails then leave within minutes of being queued.