If you’ve spent any time configuring replenishment rules in Odoo, you’ve probably wrestled with security lead times. They were the buffer days you added to purchase orders and manufacturing orders as a hedge against delays — a “just in case” margin that often created more confusion than confidence.
That concept is being retired. In its place, Odoo is introducing “horizon days” — a cleaner, more intuitive way to define how far ahead the system should look when planning replenishment. And while the inventory team was at it, they also wired quality control directly into three-step warehouse operations.
Why Security Lead Times Had to Go
The old model worked like this: you’d set a vendor lead time (say, 10 days for a supplier to deliver), then add a purchase security lead time (maybe 3 days) as padding. The system would trigger replenishment 13 days before you needed the goods.
The problem was layering. You had purchase security lead times, manufacturing security lead times, and regular lead times all stacking on top of each other. The diagrams in the documentation alone required a legend to decode. For teams running both purchase and manufacturing replenishment, the math became genuinely opaque.
Horizon days simplify this fundamentally. Instead of adding buffer days to individual lead times, the system now uses a single forward-looking window. You tell Odoo how many days ahead to scan for demand, and it calculates replenishment timing from there. The mental model shifts from “pad each step” to “look this far ahead.”
What Actually Changed in the Documentation
This isn’t a minor terminology swap. The entire lead times reference has been restructured:
- All references to purchase security lead times and manufacturing security lead times have been removed
- The lead time diagrams — those flowcharts showing how days stack up from order to delivery — have been completely redrawn to reflect the new model
- Text examples no longer reference buffer days; instead, they walk through horizon-based calculations
- Screenshots throughout the replenishment section have been replaced with current interface captures
- Sections have been reordered to align with how Odoo’s just-in-time logic actually processes operations
The documentation also adds missing anchors to the “types of lead times” section and clarifies how the system calculates “days to prepare manufacturing order” — a setting that was previously under-documented.
Three-Step Warehouse Flows Get Quality Checkpoints
Separately, Odoo has added quality control documentation for three-step inventory flows. If you’re not familiar with Odoo’s warehouse routing options: a three-step receipt flow means goods arrive at an input location, move to a quality inspection area, and then get shelved in stock. The reverse applies for shipping — pick, pack, then ship.
Until now, the documentation focused on the physical movement of goods through these steps but didn’t address where quality checks fit in. The new documentation organizes information around quality control for both inventory operations and package handling within three-step flows.
This matters for regulated industries — food, pharmaceuticals, electronics — where inspection isn’t optional. Having quality checks documented as part of the standard three-step flow means teams can configure inspection points without inventing their own workarounds.
The Bigger Picture: Simpler Warehouse Logic
Both changes point in the same direction: Odoo is simplifying how warehouses think about time and quality. Horizon days reduce the cognitive overhead of replenishment planning. Quality checks in three-step flows reduce the implementation overhead of compliance.
For teams already using Odoo’s inventory prediction tools, the horizon days model integrates naturally. Predictions tell you what you’ll need; horizon days tell the system how far ahead to act on those predictions. Together, they create a replenishment engine that’s both smarter and easier to configure.
If you’re running a warehouse on Odoo and you’ve been fighting with lead time buffers, this is the update you didn’t know you were waiting for. And if you’re operating a three-step flow without formal quality checks, now’s the time to wire them in — the documentation finally supports it end to end.