Stock Release Channel Plan Process End Time
At launching a plan, a process end date is set on each release channel of the plan. It is then up to you to process the content of the release channel and at then end, close it and make it asleep.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0When you launch a preparation plan, you can now choose a process end date. That date is applied to every release channel in the plan, combined with each channel's own process end time.
This module links preparation plans with the process end time feature. It adds a new required date field, "Process End Date", to the wizard used to launch a preparation plan.
- The field appears on the launch plan wizard screen, right after the preparation plan selection, and is focused by default. It is pre-filled with today's date.
- When you confirm the launch, the module first runs the normal plan launch, then updates each release channel that can be woken up.
- For each such channel, the chosen date is combined with the channel's own process end time (for example 10:00 or 14:00) and converted from the channel's time zone to UTC before being stored on the channel.
- Channels that are not allowed to be woken up are left untouched.
It touches the launch wizard stock.release.channel.plan.wizard.launch and the release channel model stock.release.channel. The module installs automatically when both the plan and process end time modules are present.
Models and fields (1)
- stock.release.channel.plan.wizard.launch · extends an existing modelprocess_end_date
Text generated by AI (DeepSeek) from reading the Odoo 18.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 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/stock-logistics-release-channel.
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.