Stock restrict by planned consumed date
This module avoids to reserve goods having an expiration time prior to the customer's planned consumed date.
> [!NOTE] > This module du not change the fefo strategy implementation and won't > optimized reservations. First order still reserve the first Expired > goods even the expected consumed date is later.
auto_awesome What this module does
AI-generated from the code · Odoo 17.0Prevents Odoo from reserving stock whose lot expiration date is earlier than the planned consumed date on a stock move, so goods that would expire before they are needed are not set aside.
When a stock move has a planned consumed date, this module changes how Odoo looks for available stock and how it reserves it. It passes that date into the stock availability search, and then filters out any lot whose expiration date is before the planned consumed date. Lots without an expiration date are kept.
This affects the stock.move and stock.quant models. It does not change the FEFO (first expired, first out) strategy itself, and it does not optimize reservations: the first reservation attempt may still pick the earliest-expiring goods even if the planned consumed date is later.
There are no new menus, screens, buttons, or reports. The change happens automatically during reservation and availability checks for moves that carry a planned consumed date. The module depends on stock_move_planned_consumed_date and product_expiry, so the planned consumed date field and lot expiration dates must already be in use.
Depends on
Models and fields (1)
- stock.move · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 17.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 17.0
Confirmed on 2026-11-03 in branch 17.0 of OCA/stock-logistics-workflow.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.