Your product is manufactured or bought to order. Your vendor delivers in ten days. And yet Odoo promises the customer a delivery in four days, then creates a request for quotation dated last week. It is not a configuration mistake: it is how Odoo 19 (and 20) computes the promised date. Here is what the standard really does, why the usual workarounds are costly, and the free module I wrote so that the promise takes the supply chain into account.
1. The symptom: an impossible promise from the quotation on
The case was described very precisely on the Odoo forum. A product on Replenish on Order (MTO) + Buy, with these settings:
- customer lead time of the product: 4 days;
- vendor lead time: 10 days;
- days to purchase (Inventory setting): 2 days;
- security lead time of the company: 0.
On the quotation, Odoo shows an expected date at D+4. At confirmation, the Buy rule creates the request for quotation by going back ten days from that date: it is therefore dated six days in the past. The customer expects a delivery nobody can make, and the buyer finds a purchase order that is already late on the day it is created.
The documentation suggests that lead times add up. They do… for purchase planning, not for the date announced to the customer.
💡 Key takeaway
In a make-to-order flow, the realistic minimum lead time here is 12 days (10 + 2), not 4. Odoo promises 4.
2. What the standard does, checked in the code
I read the source code of Odoo 19 and Odoo 20 rather than trusting the documentation:
- The lead time of the sales line is a plain copy. In the sale_stock module (Odoo 19), the line takes the customer lead time of the product, and nothing else: no look at the route, the vendor or the bill of materials. In Odoo 20, the computation moved to sale, but it does exactly the same.
- The planned date follows from it. At confirmation, the delivery deadline is the commitment date, or else the order date + this lead time; the security lead time is removed and the procurement starts.
- The Buy rule goes back from that date. The request for quotation is dated “date needed in stock − vendor lead time”. If the needed date is too close, the request for quotation falls in the past, without any warning.
- Yet the core knows how to compute it. A method of the stock rules adds up the lead times of the chain: rule delays, vendor lead time and days to purchase (purchase), manufacturing lead time and days to prepare the manufacturing order (manufacturing), component picking steps. It is used by replenishment rules and the forecast report. Never by sales.
💡 Key takeaway
The gap is not a missing setting: sales simply do not call the computation that purchase and manufacturing already use. Odoo 19 and Odoo 20 behave the same way.
3. The usual workarounds, and what they cost
Inflating the customer lead time of the product. You set 12 days instead of 4. It works until the day the vendor changes its lead time, a second vendor is added, or the company sets its days to purchase to 3: then every product form must be revisited, and nobody does it. The figure becomes wrong without anything flagging it.
Typing the commitment date by hand. The salesperson has to redo the calculation in their head, line by line, knowing the lead time of each vendor. That is exactly what an ERP should spare them.
Fixing it afterwards. The buyer pushes back the request for quotation, the planner moves the delivery, and someone calls the customer back. The cost is not technical, it is commercial.
💡 Key takeaway
All these workarounds copy by hand information Odoo already has: the real lead time of the supply chain.
4. The solution: MTO Realistic Lead Time, a free module
I wrote a small module, free and under the LGPL-3 licence, for Odoo 19 and Odoo 20, Community and Enterprise. It reinvents no calculation: it calls the one the core already uses for purchase and manufacturing.
- For every line whose confirmation will create a purchase or a manufacturing order, it walks through the stock rules exactly as the procurement will (route of the line, warehouse, delivery steps), then adds up the lead times of the chain and the security lead time of the company.
- The lead time of the line becomes the longest of the two: the product one or this minimum. In the forum example, 12 days instead of 4; the expected date of the quotation becomes reachable and the request for quotation is no longer backdated.
- If the salesperson enters a commitment date that is too close, or shortens the lead time by hand, a warning appears on the quotation, line by line: “the supply chain needs 12 days, the delivery date leaves 5”. Nothing is blocked: they can promise less, but knowingly.
- An optional Supply Lead Time column shows the minimum on every line.
Products delivered from stock keep the standard behaviour. Performance-wise, the rules are walked once per product, not per line: measured on Odoo 19, reading a quotation of 30 lines of the same product costs 24 queries, like a one-line quotation; each additional distinct product adds two.
What the module does not do, honestly: the vendor used is the first one on the product form, as in the lead times of replenishment rules; a “take from stock, otherwise order” rule is treated as an order (a cautious estimate); and the lead time is recomputed when the product, the route or the warehouse changes, not when the lead time of a vendor is changed afterwards.
The module, its screenshots and its FAQ are on the page MTO Realistic Lead Time.
💡 Key takeaway
The promised date finally relies on the same calculation as purchase and manufacturing planning. A single source of truth: the vendor pricelist and the bill of materials.
⚔️ The Match: standard Odoo vs MTO Realistic Lead Time
| Criterion | Standard Odoo 19 / 20 | With the module |
|---|---|---|
| Lead time announced (forum case) | 4 days | 12 days |
| Date of the request for quotation | 6 days in the past | Today or later |
| Commitment date too close | No signal | Warning per line |
| Vendor lead time changed | Product forms to update by hand | Used on the next quotation |
| Products sold from stock | Product lead time | Product lead time (unchanged) |
Case measured on an Odoo 19 demo database: customer lead time 4 d, vendor lead time 10 d, days to purchase 2 d, security lead time 0. Same standard behaviour checked in the Odoo 20 source code.
The Verdict: a promised date must come from the same calculation as your purchases
In a make-to-order flow, Odoo knows how long it takes to buy or manufacture; it simply does not
tell sales. The module closes that gap without changing your habits.
Do your customer lead times, routes and replenishment rules tell the same story?
It is one of the first things I look at during an
Odoo audit.
Your product is manufactured or bought to order. Your vendor delivers in ten days. And yet Odoo promises the customer a delivery in four days, then creates a request for quotation dated last week. It is not a configuration mistake: it is how Odoo 19 (and 20) computes the promised date. Here is what the standard really does, why the usual workarounds are costly, and the free module I wrote so that the promise takes the supply chain into account.
1. The symptom: an impossible promise from the quotation on
The case was described very precisely on the Odoo forum. A product on Replenish on Order (MTO) + Buy, with these settings:
- customer lead time of the product: 4 days;
- vendor lead time: 10 days;
- days to purchase (Inventory setting): 2 days;
- security lead time of the company: 0.
On the quotation, Odoo shows an expected date at D+4. At confirmation, the Buy rule creates the request for quotation by going back ten days from that date: it is therefore dated six days in the past. The customer expects a delivery nobody can make, and the buyer finds a purchase order that is already late on the day it is created.
The documentation suggests that lead times add up. They do… for purchase planning, not for the date announced to the customer.
💡 Key takeaway
In a make-to-order flow, the realistic minimum lead time here is 12 days (10 + 2), not 4. Odoo promises 4.
2. What the standard does, checked in the code
I read the source code of Odoo 19 and Odoo 20 rather than trusting the documentation:
- The lead time of the sales line is a plain copy. In the sale_stock module (Odoo 19), the line takes the customer lead time of the product, and nothing else: no look at the route, the vendor or the bill of materials. In Odoo 20, the computation moved to sale, but it does exactly the same.
- The planned date follows from it. At confirmation, the delivery deadline is the commitment date, or else the order date + this lead time; the security lead time is removed and the procurement starts.
- The Buy rule goes back from that date. The request for quotation is dated “date needed in stock − vendor lead time”. If the needed date is too close, the request for quotation falls in the past, without any warning.
- Yet the core knows how to compute it. A method of the stock rules adds up the lead times of the chain: rule delays, vendor lead time and days to purchase (purchase), manufacturing lead time and days to prepare the manufacturing order (manufacturing), component picking steps. It is used by replenishment rules and the forecast report. Never by sales.
💡 Key takeaway
The gap is not a missing setting: sales simply do not call the computation that purchase and manufacturing already use. Odoo 19 and Odoo 20 behave the same way.
3. The usual workarounds, and what they cost
Inflating the customer lead time of the product. You set 12 days instead of 4. It works until the day the vendor changes its lead time, a second vendor is added, or the company sets its days to purchase to 3: then every product form must be revisited, and nobody does it. The figure becomes wrong without anything flagging it.
Typing the commitment date by hand. The salesperson has to redo the calculation in their head, line by line, knowing the lead time of each vendor. That is exactly what an ERP should spare them.
Fixing it afterwards. The buyer pushes back the request for quotation, the planner moves the delivery, and someone calls the customer back. The cost is not technical, it is commercial.
💡 Key takeaway
All these workarounds copy by hand information Odoo already has: the real lead time of the supply chain.
4. The solution: MTO Realistic Lead Time, a free module
I wrote a small module, free and under the LGPL-3 licence, for Odoo 19 and Odoo 20, Community and Enterprise. It reinvents no calculation: it calls the one the core already uses for purchase and manufacturing.
- For every line whose confirmation will create a purchase or a manufacturing order, it walks through the stock rules exactly as the procurement will (route of the line, warehouse, delivery steps), then adds up the lead times of the chain and the security lead time of the company.
- The lead time of the line becomes the longest of the two: the product one or this minimum. In the forum example, 12 days instead of 4; the expected date of the quotation becomes reachable and the request for quotation is no longer backdated.
- If the salesperson enters a commitment date that is too close, or shortens the lead time by hand, a warning appears on the quotation, line by line: “the supply chain needs 12 days, the delivery date leaves 5”. Nothing is blocked: they can promise less, but knowingly.
- An optional Supply Lead Time column shows the minimum on every line.
Products delivered from stock keep the standard behaviour. Performance-wise, the rules are walked once per product, not per line: measured on Odoo 19, reading a quotation of 30 lines of the same product costs 24 queries, like a one-line quotation; each additional distinct product adds two.
What the module does not do, honestly: the vendor used is the first one on the product form, as in the lead times of replenishment rules; a “take from stock, otherwise order” rule is treated as an order (a cautious estimate); and the lead time is recomputed when the product, the route or the warehouse changes, not when the lead time of a vendor is changed afterwards.
The module, its screenshots and its FAQ are on the page MTO Realistic Lead Time.
💡 Key takeaway
The promised date finally relies on the same calculation as purchase and manufacturing planning. A single source of truth: the vendor pricelist and the bill of materials.
⚔️ The Match: standard Odoo vs MTO Realistic Lead Time
| Criterion | Standard Odoo 19 / 20 | With the module |
|---|---|---|
| Lead time announced (forum case) | 4 days | 12 days |
| Date of the request for quotation | 6 days in the past | Today or later |
| Commitment date too close | No signal | Warning per line |
| Vendor lead time changed | Product forms to update by hand | Used on the next quotation |
| Products sold from stock | Product lead time | Product lead time (unchanged) |
Case measured on an Odoo 19 demo database: customer lead time 4 d, vendor lead time 10 d, days to purchase 2 d, security lead time 0. Same standard behaviour checked in the Odoo 20 source code.
The Verdict: a promised date must come from the same calculation as your purchases
In a make-to-order flow, Odoo knows how long it takes to buy or manufacture; it simply does not
tell sales. The module closes that gap without changing your habits.
Do your customer lead times, routes and replenishment rules tell the same story?
It is one of the first things I look at during an
Odoo audit.