Stock Move Common Destination
This module adds a M2m field common_dest_move_ids on stock.move in order to compute all the moves having a chained destination move sharing the same picking as the actual move's destination move.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Adds a read-only "Common destination moves" list on the stock move form, showing other moves whose next step lands in the same transfer as this move's next step.
This module helps warehouse users spot related operations that are heading to the same destination transfer. On the stock move form, inside the existing linked-moves group, a new read-only field called "Common destination moves" appears. It lists other stock moves that share the same destination transfer as the move you are looking at.
- The list shows, for each related move, its transfer, product, source and destination locations, quantity, unit of measure and status.
- The field is computed automatically whenever the move's destination moves or their transfers change; users cannot edit it.
- It can also be used in filters and searches, so you can find moves that have common destination moves.
Technically, the module extends stock.move with a computed many-to-many field and adds it to the standard stock move form view. No new menus, buttons, reports or scheduled actions are added. The information is purely informational and appears only on the individual stock move screen.
Depends on
Required by other modules
Models and fields (1)
- stock.move · extends an existing modelcommon_dest_move_ids
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: 4 confirmed, 5 with no information of 9 versions.
Sources · Odoo 13.0
Confirmed on 2026-11-03 in branch 13.0 of OCA/stock-logistics-warehouse.
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.