Skip to content
العربيةLet’s talk

Practical guide

Odoo CRM pipeline review: when to advance, follow up or close a deal

Give each Odoo CRM stage an exit rule, assign the next activity and record why a deal was lost. Use a worked quotation example and a sales review worksheet.

Lava Solutions · · 4 minute read

Two people arrange sticky notes on a glass board during a planning workshop.
Illustrative stock photo. Photo: airfocus / Unsplash.

A quotation has sat in the same Odoo CRM stage for three weeks. Should the salesperson advance it, schedule a call or close it? Look for three pieces of evidence: what the buyer last confirmed, what would justify moving the deal forward and who owns the next action. The age of the quotation tells a manager which record to open. The buyer’s decision determines what to do with it.

Agree what earns a change of stage

Start with a recent won opportunity and another that stopped progressing. Ask the salespeople to reconstruct the buyer decisions in each. Use the decisions they can demonstrate to define the stages. A sent quotation is easy to verify, but it says little about whether the person approving the purchase has seen it. Decide which of those events your team needs the pipeline to represent.

Odoo lets teams adapt their stage names. The following worksheet gives example rules for a service business. Write the evidence in the opportunity and ask the salesperson who received it to make the change. These are team review criteria. If the team expects software to enforce a rule, test that requirement separately. Odoo 20 stage settings.

Current stageEvidence to move forwardIf the evidence is missing
DiscoveryThe buyer confirms the problem, scope and person reviewing the offer.Arrange a scope discussion and record the unanswered question.
Preparing an offerThe named reviewer receives the agreed version and confirms when it will be considered.Check receipt and the decision process with the contact.
Buyer reviewThe buyer confirms acceptance or communicates a decision to decline.Record the open decision and when the buyer expects to resolve it.

Give the next activity a finish line

Odoo CRM activities can be tied to an opportunity. Write a summary that a colleague could act on, assign a person and choose a due date. “Call Samira on Tuesday to check whether purchasing approved the revised quantity” gives the salesperson something specific to find out. After the call, record the answer and schedule the next action it warrants. Completing a call and securing purchasing approval are separate events in this worksheet. Odoo 20 CRM activities.

Review stalled opportunities with the owner

In the weekly review, ask the owner to show the last buyer response and the next commitment. A deadline the seller missed calls for a new owner or a realistic follow-up date. A buyer waiting for a scheduled committee meeting can stay in the same stage with a dated check after the meeting. A clear decision to cancel the purchase calls for closure. If the reason is unknown, keep the explanation factual.

In Odoo 20, a stage can have a Days to rot threshold that flags cards for attention. Check the setting in your version and choose a threshold that fits the stage. A technical review and a straightforward quote acknowledgement may reasonably have different waiting periods.

Record the evidence behind a loss

Odoo’s loss action offers a reason and a closing note. Both are optional in the documented flow. Agree a short list of reasons your team can use consistently, such as project cancelled or another supplier selected. If the only fact is that the buyer has stopped responding, avoid recording price as the cause. Review lost records by reason and look for patterns that the notes actually support. Odoo 20 lost opportunities.

A fictional review of a delayed quotation

A maintenance supplier sends two service options to a facilities manager. The buyer confirms receipt and a Thursday committee review, so the salesperson records the quotation version and schedules a Friday call. On Friday the buyer says the committee requested a breakdown by building. The opportunity stays open while the salesperson prepares the breakdown. If the buyer later cancels the project, the salesperson records the cancellation and the date of the message. A colleague can now explain both decisions from the same record.

To test the setup, give two colleagues the same sample opportunity and ask each to choose the stage, next action and closure reason independently. Resolve any disagreement in the written definitions before training the team. Use the role-based training guide to rehearse the weekly review. For help configuring your own stages, contact Lava with your current stage names and an anonymised example of a decision the team finds difficult.

Sources & further reading

A useful next step

Bring one real workflow.

Share the process you want to improve, the systems involved and the decision you need to make.

Talk to Lava ↗