OdooWiki OCA HUB

CRM won reason

crm_won_reason folder_open OCA/crm open_in_new
Customer Relationship Management License: AGPL-3

This module adds possibility to define lost & won reasons to be applied on leads.

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Lets salespeople record why an opportunity was won, just like lost reasons. A new 'Won' button opens a small pop-up where a win reason is chosen before the opportunity is marked as won.

This module extends the CRM app so that winning an opportunity can be documented with a reason, mirroring the existing lost-reason feature.

  • On an opportunity form, the standard 'Mark as won' button is hidden and replaced by a new highlighted 'Won' button (keyboard shortcut w). It only appears when the opportunity is still active, is not already at 100% probability and is not a plain lead.
  • Clicking it opens a small pop-up titled 'Won Reason' where the user picks a reason from a list and confirms with 'Submit' (or cancels). Confirming marks the opportunity as won and stores the chosen reason on it.
  • The existing reasons list (menu renamed 'Win or Lost Reasons') now shows a type column: each reason can be flagged as 'Won' or 'Lost' (default 'Lost').
  • The lost pop-up only offers reasons that are of type 'Lost' (or have no type), and the won pop-up only offers reasons of type 'Won' (or no type), so the two lists stay separate.
  • The chosen win reason is saved on the opportunity itself, so it can be reported on later.

It touches the CRM opportunity (crm.lead), the reason list (crm.lost.reason), the lost wizard (crm.lead.lost) and adds a new won wizard (crm.lead.won). Salespeople have full access to the new wizard.

Depends on

crm
Models and fields (4)
  • crm.lead · extends an existing modelwon_reason_id
  • crm.lead.won · new modelwon_reason_id
  • crm.lead.lost · extends an existing modellost_reason_id
  • crm.lost.reason · extends an existing modelreason_type

Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 2 confirmed, 7 with no information of 9 versions.

terminal Installation and usage

No verified information

Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.