The problem this app solves

A future prospect, an invalid enquiry and a genuinely lost deal need different treatment. Recording all three as lost makes pipeline cleanup harder to interpret and can leave leads that should be revisited forgotten in the archive.

Use explicit dispositions for loss, disqualification, nurture and other closure reasons. Due nurture records can return with a follow-up activity, while conflicting ownership or pipeline changes are surfaced for review rather than overwritten.

Features that support your daily work

• Semantic dispositions. Configure native lost, disqualified, nurture, no response, invalid, duplicate, spam/junk, outside territory, cleanup or custom classes with notes, manager-only access and nurture defaults.
• Governed archive. Company/team policies offer allow, recommend, require or managers-only modes. Required and manager-only archive rules are enforced on the server.
• Native true loss. True-loss dispositions call Odoo's native action_set_lost with the selected crm.lost.reason; probability and close-date semantics stay native.
• Conflict-safe recycle. Due nurture leads return to the pipeline once, with one follow-up activity. New owner, team, stage or probability changes create a reviewable conflict.
• Immutable history. Each governed transition stores the prior state, semantic class, note and recycle snapshot. Event history is read-only and access-controlled.
• PDF and CSV analysis. Review event trends in list, pivot and graph views, then print a native PDF or export a UTF-8 CSV for a company and date range.

A practical example

Illustrative workflow — the available actions depend on your configuration.

A prospect is not ready to buy this month. The salesperson records a nurture disposition and recycle date. When it becomes due, an unchanged lead returns with a follow-up activity; a newer manager change instead creates a reviewable conflict.

How the workflow works

1. Configure dispositions and an archive policy in CRM configuration.
2. Choose Record Disposition from a lead or opportunity and review the effect preview.
3. Use native lost semantics for a true loss, or archive a distinct nurture/disqualified/cleanup state.
4. Review due and conflict records in Nurture & Recycle Queue.
5. Let the hourly job restore an unchanged nurture record and schedule one follow-up; inspect conflicts before any manager action.

Configuration and navigation

Use the native CRM information architecture:

• CRM > Leads > Nurture & Recycle Queue
• CRM > Leads > Disposition Review
• CRM > Configuration > Lead Dispositions
• CRM > Configuration > Disposition Policies
• CRM > Reporting > Disposition & Recovery Analysis
• CRM > Reporting > Disposition PDF / CSV

Reports and exports

Disposition & Recovery Analysis provides immutable event list, pivot and graph views. Disposition PDF / CSV prints a lead disposition summary or exports occurred-at time, lead, event, disposition, class, owner/team, recycle date and note. CSV is UTF-8 with formula-sensitive values guarded; XLSX is not included.

See the workflow in Odoo

Explore the screens in sequence, from configuration to daily work and reporting. Each image includes a caption explaining its place in the workflow.

Disposition catalogue: semantic classes and required fields. Governance: company/team archive policy. Queue: due nurture and conflict-safe recovery work. Wizard: explicit disposition, note and recycle preview. Result: restored lead and one follow-up activity. Audit: a newer manager change is preserved as a conflict. Analysis: immutable disposition and recovery events. Reporting: date-scoped PDF and CSV output.

Compatibility and limits

Version	Odoo 15.0
Editions	✓ Community   ✓ Enterprise
Dependency	CRM (crm)
Deployment	Odoo.sh or private/on-premise hosting
Odoo Online	Not compatible — server-side lifecycle, authorization, audit and scheduled automation are required

Excluded: marketing campaign execution, email/SMS drip nurturing, automated win-back scoring, automatic duplicate merging, legal erasure/retention engine and generic archive replacement for non-CRM models.