Abandoned Cart & Re-Engagement Automation

This is a purpose-built Frappe application with its own module, installed cleanly into your bench alongside ERPNext. At its core are dedicated DocTypes — an Abandoned Cart record that captures the customer, cart lines, subtotal, and last-activity timestamp, a Recovery Sequence that defines the ordered steps (channel, delay, template, coupon rule), and a Recovery Message Log that tracks every send, delivery, click, and conversion for attribution. Detection is wired through hooks.py doc events on Quotation and Sales Order (and the POS Invoice draft state), plus a scheduler_events cron job that sweeps for carts whose last_activity has exceeded your configured threshold and enqueues them via the Frappe background worker. Nothing polls the database in a tight loop — it uses ERPNext's own scheduler and queue.

Each sequence step resolves against a channel adapter. WhatsApp goes out through the ERPNext WhatsApp integration (or a provider of your choice) using approved template messages; email uses Frappe's native Email Queue and Email Template rendering; SMS routes through your existing SMS Settings gateway. Message bodies are Jinja templates with full access to the cart context, so a customer sees the actual products they left behind, the running total, and a deep link back to the webshop cart — not a generic "come back" note. Coupon injection is handled by a server script that generates or reserves an ERPNext Coupon Code scoped to that customer and interpolates it into the message only when your rules allow it (for example, escalating discount on the second or third touch). Win-back campaigns for dormant customers reuse the same engine, keyed off last-purchase date rather than cart abandonment. Everything is exposed through whitelisted REST methods so your webshop front end, marketing tools, or a headless storefront can register cart events and read recovery status, and access is governed by proper Role Profiles and permission rules so marketing staff never see more than they should.

Because this is build-to-order, ECOSIRE does not hand you a generic download. We start with a short scoping call, confirm your ERPNext version (v15 or v16), your live channels (WhatsApp/email/SMS providers), your webshop or POS setup, and your discount policy, then write the app to fit. You receive installable source pinned to your version, a staging UAT pass, and a documented rollback path before anything touches production. Typical delivery is 2–4 weeks from confirmed scope. You keep the git repository and the whitelisted API contract, so the automation is yours to extend, not a black box you rent.