Know whether a delivery date holds before you promise it
The planner works back from the date the customer wants, through production and purchasing, and tells you whether it holds: from the quotation, inside Odoo.
Three steps The problem The plan Capacity Stock Monitoring Questions
Three steps, from quotation to shop floor
1. Check the quotation
The Earliest Date button shows, for each product, the earliest date it can be delivered and why: stock, a planned receipt, purchase or production.
2. Plan the order
The bill of materials is exploded level by level and each level is scheduled back from the delivery date, on the working calendar.
3. Launch after review
Nothing is ordered by itself: RFQs and manufacturing orders are created from the planned orders, only for those due in the next days.
The problem
Standard Odoo plans after the sale. It does not tell you whether the date holds.
A promise made blind
Reorder rules and make-to-order routes react after the sale. The salesperson has no answer to the customer's first question: when?
Stock counted twice
Two orders see the same stock on hand. The planner counts stock at the delivery date, after what was already promised to other orders.
A full workcenter nobody sees
The standard planning does not know how long an order takes or whether a workcenter is already overloaded that week.
The plan
One plan, from the customer's date to the first purchase
A verdict in three colours
OK, Warning when the margin is below the safety buffer, Blocked when the date is impossible, with the earliest achievable date. Shown as a banner on the sale order.
Backward from the date
Production end, production start, purchase launch and component receipt, computed back on the working calendar. When the dates fall in the past, the planner plans forward from today.
A tree of planned orders
Manufacturing for each level of the bill of materials and purchasing for each short component, linked to the sale order.
Already in the quotation
A quotation is planned as a simulation, with nothing reserved; once sent, its demand counts for the next orders.
Purchase orders the vendor accepts
Quantities follow the vendor's minimum, and RFQs for the same vendor and warehouse are consolidated on one order, on the same line when product and price match.
Dates that follow the documents
A new date on a purchase line or a manufacturing order moves the planned orders up the bill of materials, and the delivery date is written on the picking.
Capacity
Hours required against capacity, week by week
Production time from the routing
The operations are grouped by workcenter; the slowest one, with its efficiency and calendar hours, sets the production time.
Load per workcenter and week
Green up to 80%, yellow up to 100%, red above. Pivot, graph and Gantt with the production and purchase dependencies.
Levelling
In an overloaded week, the orders with the most slack move one week later, with their sub-levels; firmed orders stay put. A dry run shows the result first.
Projected stock
Stock over time, not stock today
Material situation
Every receipt and issue of a product in date order, with the cumulative stock, the quantity available to promise and the order that each line serves. Per warehouse, with PDF and Excel export.
Replenishment for stock
Issues without a sale order and min/max rules handed to the planner get proposals staggered in time, over a horizon of 90 days by default, without ordering again what an RFQ already asked for.
One owner per product
A product is ordered either by the planner or by the standard Odoo rules, never by both.
Several warehouses
Each planned order carries the warehouse of its sale order, and stock is allocated per warehouse.
Monitoring
When the plan slips, someone knows
Dashboard
Blocked orders, warnings, replenishments, the share of orders planned on time over 30 and 90 days, and the busiest workcenters.
Delivery risk board
Sale orders grouped as Critical, At risk or On track, with the planned orders behind the risk and a to-do to warn the customer.
Daily deviation check
A purchase not launched, a late purchase order or a manufacturing order not started changes the status, writes in the chatter and creates an activity for the salesperson.
Escalation
An order blocked for more than the set number of days escalates its overdue activities, and the logistics manager gets an email.
Frequently asked questions
Does it replace the standard Odoo planning?
No. It runs on Sales, Manufacturing, Purchase and Inventory, and creates standard RFQs and manufacturing orders. Products you leave to the standard reorder rules stay with them.
Where does it stop?
It does not optimise the production sequence, compare what-if scenarios or reschedule by itself after a breakdown. For that you need a dedicated scheduling system; the planner covers the delivery promise and the capacity check.
What data does it need?
Bills of materials with operations, workcenter calendars, vendor lead times and delivery dates on the sale orders. Where a lead time is missing, a default from the settings applies.
Which Odoo apps does it need?
Odoo 19 Enterprise, with Sales, Manufacturing, Purchase and Inventory. It is available in Odoo Apps. This module is in beta.
And a purchase list from the sales history?
That is NAP, for stock driven by statistics rather than by orders.
Can it explain a delay?
Yes, with the Advanced Planner AI Assistant: it explains the cause, proposes options and drafts a message for the customer.
Let's plan one of your orders
Send us a product with its bill of materials and a delivery date, and we will show what the planner says.