Know exactly why you win and lose every deal
Enforce structured won and lost reason capture across CRM, guided wizards, and sale order lines, then turn that data into revenue-weighted win/loss analytics your team can act on.
Reps mark opportunities lost with no reason, or type free text that produces dozens of synonyms for the same root cause. Odoo has no native won-reason concept at all, so the story of why deals succeed disappears the moment they close — leaving managers unable to answer “why are we losing” or “which competitor keeps beating us.”
Deal Won & Lost Reasons enforces standardized won and lost reason capture everywhere a deal can close — form, bulk action, and wizard dialog — then layers in competitor tracking, price-gap percentage, guided notes, automatic lost-lead recovery, and a revenue-weighted analytics dashboard so every closed deal becomes usable intelligence.
This app speaks your language.
Tell us the language your team works in and we translate this module for you, free of charge — so everyone works in the language they know best.
Request my free translation →No hidden fees. No subscription.
Everything you need to turn closed deals into intelligence
Every capability below is implemented in the module.
Won and lost reason master data
A managed Won Reason list mirrors Odoo's native Lost Reasons, giving you one consistent, centrally configured picklist for both outcomes instead of scattered free text.
Competitor registry
Track every company that beats you on a managed Competitor list, with a smart button on each competitor showing exactly how many deals they have won from you.
Enforcement across every path
Required reason capture is enforced on the form button, the Won and Lost wizard dialogs, and bulk pipeline actions — not just one bypassable button — so completeness stays high.
Price-gap tracking
Log the price-gap percentage against the winning competitor on every lost opportunity, answering not just why you lost but by how much.
Guided closing notes
A prompted context note with a configurable minimum length replaces blind character counts, encouraging reps to write something reporting can actually use.
Automatic lost-lead recovery
Configurable recovery rules match a lost reason and source stage to a target team and stage, automatically re-routing and reactivating recoverable leads instead of letting them disappear.
High-value loss escalation
Losses above a configurable revenue threshold automatically create an escalation activity for the team manager, so the biggest losses never go unreviewed.
Revenue-weighted win/loss analytics
A dedicated Win/Loss report, with list and pivot views, breaks down every closed opportunity by reason, competitor, and revenue — not just deal count.
Sale order line-level lost marking
Mark individual quotation lines as lost with their own reason directly from the order line row, capturing lost intelligence below the opportunity level.
How it works
Configure
Define won and lost reasons, build your competitor registry, and set enforcement toggles and thresholds from Sales/CRM Settings.
Capture
Reps mark opportunities won or lost through guided wizards that require a reason, competitor, price gap, and closing note before the deal can close.
Route
Recovery rules automatically reassign recoverable lost leads to a new team and stage; high-value losses escalate to the sales manager.
Analyze
Revenue-weighted Win/Loss reports break down outcomes by reason, competitor, team, and rep so managers can act on real data.
See it in action
Every screen below is captured directly from a running installation.
The Won Reasons master list mirrors Odoo's native Lost Reasons, giving managers one place to standardize the picklist used across every wizard and report.
Each won reason form includes a leads-count smart button linking straight to every opportunity closed for that reason.
A managed Competitor registry tracks every company your team competes against.
The competitor form's smart button opens every deal lost to that competitor in one click.
The native Lost Reasons list is extended with an “Others” flag and per-company scoping, without any parallel setup.
Lost-lead recovery rules match a reason and source stage to a target team and stage for automatic re-routing.
Configure a recovery rule to reactivate a lost lead and reassign it to a new team and stage the moment its trigger conditions match.
A Win/Loss Details page on the opportunity form captures the won reason, an “Others” free-text fallback, and the closing note.
The same page captures the lost reason, competitor, price-gap percentage, and closing note for every lost deal.
The guided Won wizard enforces reason and closing-note capture before the opportunity can close.
The extended Lost wizard adds competitor and price-gap capture on top of Odoo's native reason and note fields.
The Win/Loss report lists every closed opportunity alongside its reason, competitor, and revenue.
Pivot by reason, competitor, team, or rep to see exactly where revenue is won and lost.
Enforcement toggles for required won reason, lost reason, and note length, plus the high-value loss escalation threshold, live in Sales/CRM Settings.
Mark individual quotation lines as lost with their own reason directly from the order line row.
Frequently asked
Does this replace Odoo's native Lost Reasons?
No — it extends them. Your existing lost reasons keep working; the module adds a matching Won Reason list plus enforcement, competitor, price-gap, and analytics on top.
Can I make reason capture optional instead of mandatory?
Yes. Required won reason, required lost reason, and required note are independent toggles in Settings, so you can tune enforcement per team without editing views or code.
Does it work with sale order lines, or only CRM opportunities?
Both. Opportunities get the full won/lost wizard and analytics; sale order lines get their own inline mark-lost action with a per-line reason for line-level reporting.
Is it multi-company ready?
Yes. Won reasons, lost reason extensions, competitors, and recovery rules are all company-aware, so each legal entity can maintain its own configuration and audit trail.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Enforced won and lost reason capture, competitor and price-gap tracking, automatic recovery routing, and revenue-weighted analytics for Odoo CRM and Sales.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
CRM (crm)
• Calendar (calendar) • Contacts (contacts) • Discuss (mail) • Invoicing (account) |
| Lines of code | 1021 |
| Technical Name |
cerevantix_deal_won_lost_reasons |
| License | OPL-1 |
| Website | https://cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module