Accurate outcomes turn a crowded CRM pipeline into useful business evidence. For a Canadian manufacturer selling made-to-order equipment to distributors and industrial customers, open opportunities can quickly pile up when buyers delay projects, choose another supplier, or stop responding.
When salespeople leave old records open, archive them without an outcome, or mark them Lost with no details, management cannot see what is really happening. We recommend treating every Won and Lost result as part of your sales history, not as a simple housekeeping task. Consistently recorded Won and Lost outcomes help managers analyse sales performance and give Odoo Predictive Lead Scoring historical results to learn from.
Close Opportunities with a Clear Outcome
In standard Odoo 20 CRM, Won, Lost, and archived records mean different things. A Won opportunity records a successful sales outcome. A Lost opportunity records an unsuccessful result and gives the salesperson an opportunity to add a Lost Reason and Closing Note. Archiving changes whether a record is active, but it does not replace recording a known sales result.
From the CRM pipeline, salespeople can open an opportunity and select Lost. The Mark Lost dialogue lets them choose an existing Lost Reason or create a new one directly in the Lost Reason field. They can also enter a Closing Note before selecting Mark as Lost.
In standard Odoo 20, both fields are optional when an opportunity is marked as Lost. If salespeople leave them blank, the opportunity is still closed, but managers have less information for reviewing lost deals and identifying recurring reasons.
Consider a stalled machine-components opportunity. A representative may archive the record simply to clear a busy pipeline. The opportunity then disappears from usual active views, yet management cannot tell whether the buyer rejected the proposal, delayed the project, or found a better fit elsewhere. When opportunities are archived without being marked Won or Lost, they have no defined sales outcome. As a result, they may be excluded from Odoo's Win/Loss analysis, making it harder for managers to compare successful and unsuccessful opportunities over time.
We suggest setting a simple expectation: if the sales result is known, close it as Won or Lost. Archive records only when archiving is genuinely appropriate, such as a duplicate or a record that should no longer appear in active work queues.
Create Lost Reasons Your Team Can Use Consistently
Lost Reasons give your team a shared way to classify lost sales opportunities. In Odoo 20 CRM, users with CRM configuration access can manage them through CRM > Configuration > Lost Reasons.
A short list works better than a long one. Each reason should describe a distinct commercial outcome, so reports do not split the same issue into several labels.
- Price
- Selected Competitor
- Budget Not Approved
- Delayed Timing
- Product Requirements Not Met
For example, entries such as “Too Expensive,” “Price Too High,” and “Budget Issue” may sound different, but they can blur reporting. One salesperson may select a price-related reason while another chooses a budget-related reason for nearly the same buyer response.
Closing Notes add the detail that a structured category cannot hold. A representative could select Selected Competitor, then note that the buyer chose a local supplier with shorter lead times and on-site installation. The Lost Reason supports reporting consistency. The Closing Note preserves useful context for account reviews, product discussions, and future follow-up decisions.
Although Lost Reasons are valuable for loss analysis, they are not standard Predictive Lead Scoring inputs. Their standard purpose is to document why an opportunity was closed as lost. In Odoo 20 Enterprise, scoring uses the fields selected in the Predictive Lead Scoring configuration, rather than automatically treating every CRM field or Lost Reason as a scoring variable.
Turn Lost Records Into Useful Sales
Analysis
Odoo 20 CRM lets managers analyse sales outcomes from CRM > Reporting > Pipeline. To review lost opportunities, they can use the Lost filter. When preparing a Win/Loss analysis, managers should also enable Include archived so that archived lost opportunities are included in the results. They can then group and filter the data by Lost Reason, salesperson, sales team, and other available CRM fields.
Odoo 20 also allows salespeople to restore a lost opportunity if the customer reopens discussions or the project becomes active again. To do this, they open the CRM pipeline, apply the Lost filter, select the opportunity, and click Restore on its form. The record returns to the active pipeline, allowing the sales team to continue working on it.
When an opportunity is marked as lost, salespeople can enter additional context in the Closing Note field in the Mark Lost dialogue, directly below Lost Reason. This note can explain why the deal was lost, such as a delayed project, a competitor's offer, or a change in the customer's requirements.
The Pipeline Analysis reporting area organizes recorded opportunity data in graph, pivot, and list views. Managers can compare results by:
- Salesperson or sales team
- Reporting period
- Pipeline stage
- Lost Reason
- Opportunity tags or categories
Pipeline Analysis groups opportunities using the CRM data recorded by the team, including Lost Reason. Managers should review Closing Notes and customer feedback to understand the circumstances behind each lost deal.
Suppose one sales team selects Budget Not Approved for almost every lost opportunity, while another uses Price, Delayed Timing, and Product Requirements Not Met. A report could make budget limitations appear to be the dominant sales barrier. In reality, the difference may reflect inconsistent classification habits rather than customer behaviour.
When patterns are recorded consistently, they can guide productive questions. Should your team review qualification criteria? Are delivery commitments affecting decisions? Is product positioning clear enough? Are salespeople hearing the same objections across a certain segment? We recommend checking Closing Notes, customer feedback, and operational context before making major changes based on report totals alone.
Give Predictive Lead Scoring Better Historical Data
Predictive Lead Scoring is available in Odoo 20 CRM in both Community and Enterprise editions. It runs automatically and uses historical Won and Lost opportunities to calculate the probability of success for active leads and opportunities. To adjust the criteria used in the calculation, go to CRM > Configuration > Settings and select Update Probabilities in the Predictive Lead Scoring section.
Once enabled, administrators choose the CRM fields that the scoring model can use to evaluate leads and opportunities. Odoo uses historical Won and Lost outcomes and the selected field values to calculate a probability that a newer record will be won. The feature needs sufficient, accurately recorded historical outcomes to produce useful results.
Odoo uses historical Won and Lost outcomes to train Predictive Lead Scoring. Administrators can configure CRM fields for the scoring calculation, while Stage is part of the scoring process. Teams should review these settings and maintain accurate opportunity outcomes so the model can learn from relevant historical data.
For a manufacturer, the risk is easy to see. If delayed capital projects stay open indefinitely, the pipeline can look healthier than it is. If viable opportunities are marked Lost only to clear a salesperson’s queue, the historical record can look worse than reality. Odoo can still generate probabilities, but they should be treated cautiously because the underlying outcome data is less trustworthy.
Build Discipline Before Depending on Forecasts
Reliable sales analysis starts with a clear operating routine. Sales managers can review aging opportunities, define when a deal should stay open, and set expectations for when it must be closed as Won or Lost. We also recommend requiring a meaningful Lost Reason through team policy and asking for a Closing Note when customer feedback could affect future decisions.
Some controls require more than standard Odoo CRM behaviour. Required fields, approval steps, detailed closing rules, tailored reports, and workflow enforcement can involve configuration or custom development. The right approach depends on how much governance your team needs without making CRM updates harder than they need to be.
A periodic review keeps small data problems from becoming permanent reporting problems. Include sales, operations, and leadership when recurring loss reasons point to product, delivery, capacity, or positioning concerns. Sample recently closed records, look for vague or duplicate reasons, and identify opportunities that were archived when they should have been marked Won or Lost.
Lost sales opportunities are still valuable evidence when they are closed properly. Regular pipeline reviews help managers identify missing Lost Reasons, incomplete Closing Notes, and opportunities that should have been marked Won or Lost. Correcting these records improves sales reporting and maintains better historical data for Predictive Lead Scoring.
Turn Lost Deals Into Better CRM Decisions
Kodershop helps businesses connect lost sales opportunities to stronger Odoo CRM reporting, workflows, and forecasting. Our team can assess where data gaps or inconsistent processes are limiting visibility across your pipeline. Contact us to discuss an ERP approach that supports more confident commercial decisions.