Stock Move Name From Sale Line
This module set stock move name from sale order line when is confirmed. By default Odoo set the product name (display_name).
auto_awesome What this module does
AI-generated from the code · Odoo 15.0When a sale order is confirmed, the resulting stock moves take their description from the sale order line instead of the product name. This makes warehouse documents easier to identify.
This module changes the description shown on stock moves created from a confirmed sale order. Normally Odoo uses the product name for those moves; with this module the text of the sale order line is used instead.
- It works automatically when a sale order is confirmed and its delivery stock moves are generated.
- The description of the stock move is taken from the sale order line, so any custom text written on the line appears on the warehouse document.
- It affects the sale order line and the stock rule logic that prepares the move values.
- No new menus, screens, buttons or reports are added; the change is only visible in the description of the generated stock moves.
- No extra checks, restrictions, emails or scheduled jobs are added.
The module depends on sale_stock, so it only applies to sales flows that create stock moves. It is useful when the product name alone is not enough to identify what should be picked or delivered, for example when the sale line contains a specific reference or customer instruction.
Depends on
Models and fields (2)
- stock.rule · extends an existing model
- sale.order.line · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 15.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 15.0
Confirmed on 2026-11-03 in branch 15.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.