Odoo CRM Lost Reasons: Learn Without Distorting the Pipeline
Short answer: Odoo CRM lost reasons are useful when they explain why a real buying process ended. Use a small, consistent set of reasons and add context in the closing note. I would review the evidence behind a loss before using the report to change prices, sales targets or qualification rules.
Applies to
Odoo 19 CRM in Community or Enterprise. The corresponding Odoo 20 lost opportunity documentation was reviewed and describes the same lost reason and restore workflow. The reporting categories below are suggested business definitions, not a predefined Odoo taxonomy.
What should a lost reason tell the business?
A lost reason should point to a decision the business could investigate. Price, missing capability, delivery timing and no approved budget suggest different actions. A category called “not interested” usually hides the question the manager needs answered: why was this opportunity in the pipeline and what changed?
Separate an actual competitive loss from poor qualification. If a buyer selected another supplier, there was a buying decision. If an enquiry never had a budget, sponsor or clear requirement, the issue may be qualification. Combining both situations makes the sales team appear to lose deals that were never ready to buy.
Keep the categories small enough that salespeople can choose consistently. If every lost opportunity creates a new reason, the report becomes a collection of individual phrases. I prefer a manageable list agreed by the team, with a closing note for the circumstances that do not fit neatly into a label.
What does Odoo record, and what needs a policy?
Odoo provides a Lost action, a Lost Reason selection and a Closing Note. The documentation states that the reason and note are optional. A team expectation to complete them is therefore a process rule unless additional enforcement has been deliberately implemented.
The system also allows lost records to be found and restored. That is useful when a postponed project restarts, but it does not mean every old lead should return to the active forecast. The salesperson should record what has changed, who confirmed it and what action is due next.
Take care with merging. Odoo documents that merging a lost opportunity with an active one brings the resulting record into the pipeline. A cleanup exercise can therefore change the visible pipeline. Review the business meaning before merging records purely because their contact details are similar.
How do you avoid blaming price for every loss?
Ask for the evidence. Did the buyer explicitly reject the commercial offer, or did they stop replying before receiving a final proposal? Was the total scope comparable to the competing offer? Was a delivery constraint described as a price problem because it was easier to record?
This is not a request for a lengthy investigation on every small sale. A concise note can be enough: “buyer confirmed a lower total installed cost elsewhere” or “budget approval postponed, no competing order confirmed”. The distinction keeps the report honest.
Review lost reasons alongside the stage reached and the quality of qualification. A large group of early enquiries marked lost on price may indicate that the enquiry form or initial conversation attracts the wrong requirements. A late stage pattern may justify a different commercial response.
Worked example: two enquiries both labelled expensive
Imagine an equipment supplier reviewing two illustrative opportunities. One customer received comparable quotations and chose a competitor because installation was included. Another customer asked for a quotation to prepare next year’s budget and never intended to place an order this quarter.
The first case supports a review of how installation is packaged and explained. The second belongs in a timing or qualification discussion. Giving both the same price reason could lead the supplier to reduce prices without fixing either problem.
The manager updates the category definitions with the sales team. Historical records are only changed where the supporting evidence is available. Uncertain cases remain uncertain rather than being rewritten to make a cleaner chart. Future closing notes identify whether a purchase actually occurred elsewhere.
When it fits and when it doesn’t
This approach fits teams using pipeline reviews to improve qualification, proposals and follow up. It is especially useful when managers disagree about why opportunities are being lost.
It does not make a small or incomplete dataset statistically conclusive. A handful of remembered conversations cannot establish a market trend. Use the report to identify questions, then review the underlying opportunities before making broader decisions.
Common mistakes
Making a new category for every case. Use agreed reasons and put the detail in the closing note.
Treating silence as confirmed price rejection. Record that the reason is unconfirmed when the buyer has not explained it.
Restoring every historic enquiry. Require a renewed buying signal and a next action.
Changing old reasons to suit a target. Preserve the basis for any correction and avoid rewriting uncertain history.
What should the monthly review produce?
Choose a small number of actions that follow from the evidence. These might include improving an initial qualification question, clarifying installation scope or changing how delivery availability is confirmed. Give each action an owner.
At the next review, ask whether the new process was used and whether the quality of the notes improved. The first useful result is often a more trustworthy explanation of the pipeline. Better decisions depend on that explanation before they depend on a more attractive win rate.
Related
Read Activities, Forecasting and Reporting in Odoo CRM for the connected workflow.
Official references
How this article was checked: official Odoo 19 documentation was reviewed in October 2026. Odoo 20 references were also checked; material differences or moved pages are identified above. Examples are illustrative business scenarios, not client results or tests on a live database.
If you need help translating these decisions into your own workflow, see my Odoo consulting services.
? Frequently asked questions
Are lost reasons mandatory in Odoo CRM?
The documented Lost Reason and Closing Note fields are optional. A business can adopt a completion policy, but should not assume the standard form enforces it.
Can a lost opportunity be restored?
Yes. Odoo documents restoring lost opportunities. Restore one when there is a credible renewed buying process and a clear next action.