In many companies the sales pipeline is an opinion: deals move to another stage when the salesperson "feels" they are going well. Odoo's CRM works if the pipeline describes observable facts and if every deal has a next action. Otherwise it becomes an archive of names.
Stages must be events, not hopes
A pipeline of "New, Interested, Very interested, Almost won, Won" does not say what has happened. A useful pipeline uses verifiable events: new lead, qualified (budget, authority, need confirmed), demo booked, proposal sent, negotiation, won or lost. For each stage the question is: what has happened for a deal to arrive here? If the answer is "the salesperson moved it", the stage measures nothing.
Every opportunity has a next activity
An opportunity with no planned activity does not appear in any daily report, generates no notifications and will be forgotten. After "proposal sent", a follow-up call within a few days; after "negotiation", sending the revised offer; on a new lead, a first call within a day. The activity completion rate is a leading indicator of pipeline health that is more reliable than stage progress alone.
The quotation lives in Odoo, all the way to delivery
The right flow: opportunity won, new quotation, products, prices, payment terms and address, sending by email with a PDF and an online confirmation link, customer confirmation, sales order, delivery order created automatically (for stocked products), invoice according to the invoicing policy. If the salesperson exports the quotation to Word, edits it and sends it from a personal mailbox, Odoo does not know what was agreed, and every later step has to be entered by hand.
The invoicing policy decides when you invoice
It is set per product. With ordered quantities the invoice can be created right when the order is confirmed (services, subscriptions, prepaid goods). With delivered quantities only after the delivery is validated (physical goods). Mixing the policies without noticing leads to invoices sent before shipment, or to goods delivered and never invoiced.
Price lists are discipline
A price list encodes the pricing rules that salespeople would otherwise negotiate from memory: a fixed price per product, a discount by customer category, quantity-break prices, time-limited promotions. Assigned to the customer record, it applies itself to every quotation. It is not extra complexity: it is what makes prices consistent.
Warning signs
- Opportunities with no next activity: the pipeline is stalled.
- All opportunities in the same stage for weeks: the stage criteria are not understood.
- No loss reason configured and no lost opportunity: losses are abandoned, not recorded.
- Quotations sent outside Odoo.
- "Ordered" policy on physical goods: invoices before delivery.
- Prices typed by hand on every line.
- Orders with no linked opportunity: no traceability from pipeline to revenue.
- Payment terms not set on the customer record.
- Won orders that do not generate deliveries: product type or route not configured.
- Many orders in "to invoice": the invoicing step is not run regularly.
Discovery: useful questions
How is a deal tracked today, in a spreadsheet or in a tool? Who prepares the quotations and with which template? How are prices and discounts decided, and who approves them? When do you invoice? The answer guides the path: if a spreadsheet is used today, the standard plus a process change is often enough; a complex product configurator or elaborate approval rules may instead require an extension, to be assessed after trying the standard.
An example
A company has three salespeople and three different ways of making quotations. With Odoo's CRM everyone starts from the same opportunity and uses the same template and the same price list. After a month the pipeline shows something that was not visible before: how many deals are stuck in "proposal sent" with no follow-up planned.
The skill at the end carries these rules in a form an agent can use to configure or check CRM and Sales.
This article is an OIAR skill
What you have just read is the content of a skill from the OIAR catalogue, written for people. Knowledge like this, but richer and deeper, written for the agents, drives the interviews, the analysis and the report inside the platform. Skills are used in OIAR: to try this one on a project of yours you need an account.
odoo-salesKnowledge to configure or assess Odoo Enterprise CRM and Sales: pipeline stages, activities, the quotation-order-delivery-invoice flow, invoicing policy, price lists. Use it when the user asks to set up or check the sales process in Odoo, with or without interviews.