Stock Release Channel Carrier Alternative
Glue module between Release channel and Carrier Alternative.
When released moves part of a channel are assigned a new picking with an alternative carrier, recompute the channel for that new picking. If no channel is found, the new picking won't be released.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Automatically keeps the release channel correct when a delivery is split and gets an alternative carrier, and prevents the new delivery from being released if no channel matches.
This is a technical glue module that works behind the scenes with the release channel and carrier alternative features. It does not add any new menu, screen or button.
When a released transfer is split because an alternative carrier is used, the new transfer inherits the original release channel. This module checks that the carrier on the new transfer is still the same as before. If the carrier changed, it clears the release channel on that transfer and asks Odoo to find the right channel again based on the new carrier.
- If a matching release channel is found, the transfer keeps working normally.
- If no release channel is found for the new carrier, the transfer is excluded from the release process, so it will not be released.
It touches the stock.move model and the release channel field on transfers (picking_id.release_channel_id), and it relies on the carrier alternative logic from the dependent modules. It is installed automatically when both dependent modules are present.
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: 1 confirmed, 8 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.