-
-
Notifications
You must be signed in to change notification settings - Fork 729
Description
Summary
During the evaluation of the stock_move_quick_lot module for a potential migration to Odoo 17, I found that a part of the functionality it provides seems to be covered by native features in the core version of Odoo 17.
Context
In Odoo 16, the stock_move_quick_lot module provides a quick way to assign lot numbers and expiration dates directly from the Operations tab in a picking, specifically at the stock.move level.
Observations in Odoo 17
In Odoo 17, out-of-the-box and without installing any additional modules:
- The Detailed Operations (
stock.move.line) in incoming shipments (receipts) now allow direct entry of lot numbers and expiration dates via the Detailed Operations smart button. - However, this capability exists only at the
stock.move.linelevel, whereas the OCA module enabled entry at thestock.movelevel, which can make a difference in user workflows and data entry efficiency.
Key Differences
| Feature | stock_move_quick_lot (OCA v16) |
Odoo 17 Core |
|---|---|---|
| Lot/Expiration Entry UI | Directly in the Operations tab | In the Detailed Operations view |
| Affected Model | stock.move |
stock.move.line |
Related Work
A key element that may justify continued interest in this module or its logic is the following PR: [IMP] stock_move_quick_lot: Allow to assign existing lots in detailed operations for pickings with create lots option enable
This PR enables assigning existing lots in detailed operations for pickings with the 'create lots' option enabled by introducing a method to handle lot assignments dynamically and updating the UI to ensure lot_id is saved correctly.
Open Questions
- Does the improved lot/expiration entry at the
stock.move.linelevel in Odoo 17 make thestock_move_quick_lotmodule obsolete? - Should we migrate the module to v17 to preserve the quicker
stock.move-level entry flow? - Is PR [IMP] stock_move_quick_lot: Allow to assign existing lots in detailed operations for pickings with create lots option enable. #866 functionality still relevant in Odoo 17?
- Are there still valid use cases or workflow preferences where the OCA module offers significant UX improvement?
Proposal
I’d like to open the discussion to determine whether:
- The module should be migrated to v17,
- It should be deprecated due to redundancy,
- Or its functionality should be reworked to address only the gaps still present in Odoo 17 core.
Feedback and thoughts from the community are highly appreciated!