Purchase Order Line Name To Picking
This module propagates the description from the purchase order lines to the stock picking
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Copies the description written on a purchase order line onto the related stock transfer lines, so warehouse staff see the same text on the receipt as on the order.
When a purchase order is confirmed, Odoo creates stock moves (the internal lines behind a receipt). This module makes sure the description of each purchase order line is carried over to those stock moves, so the text a buyer typed on the order appears on the corresponding transfer line.
Where it shows up:
- On purchase orders (purchase.order) and their lines (purchase.order.line), the description field is the one used.
- On the resulting stock picking and its move lines, the description shown to warehouse users is filled with that same text.
The behaviour is automatic: it happens when the stock moves are prepared from the purchase order line, so no extra button or menu is added. There are no new fields, no checks, no emails and no scheduled jobs in this module.
It only changes how the description is filled in; quantities, dates, products and prices are untouched. The module depends on purchase_stock, which is the standard link between purchases and inventory.
Depends on
Models and fields (1)
- purchase.order.line · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 14.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 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/purchase-workflow.
terminal Installation and usage
OCA documentation · Odoo 14.0Usage
Source · Odoo 14.0Integrated in the normal flow.
No verified information in OCA: Installation, Configuration.
Installation 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.