Stock Move Valuation Usage

This module allows to trace the usage of stock move valuation. That is, makes it possible to identify which stock moves were used as sources for a given outgoing stock move, and how much quantity and value was taken from each source move.

Note: In Odoo 19.0, stock valuation layer model was removed and valuation is now tracked directly on stock moves through the 'value' field.

This kind of traceability is important in case that at some point you want to conduct a revaluation (for example, in case that the purchase order price changes after the products have been received into stock).

Also, it changes the way the outgoing move values are calculated in order to respect the MTO case. When creating the outgoing move valuation, Odoo uses FIFO to consume from the first available incoming moves with value. The module stock_move_valuation_usage improves this process. For standard FIFO, it always uses the oldest move. However, for MTO cases, when there is a fixed link between the incoming move and the outgoing move, the system should use the specific incoming move not just the oldest one. Also, when the case is not MTO, the system should avoid using moves that are "reserved".

[!IMPORTANT] This is an alpha version, the data model and design can change at any time without warning. Only for development or testing purpose, do not use in production. More details on development status

Table of contents

Usage

• Create a product with that uses a category with automatic inventory valuation and FIFO costing method.
• Create a purchase order for this product and receive it into stock.
• Deliver the product to a customer and check the completed stock move in 'Inventory / Reporting / Stock Move Valuation Usage', where you will be able to identify the source moves that were used to value this move, and the quantity and value that was taken.
• Create several MTO order
• Deliver the products to a customer in a random way and check the section 'Move Valuation Usage'. The MTO logic is respected, then FIFO applies.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

• ForgeFlow

Contributors

• ForgeFlow S.L. <<contact@forgeflow.com>>
  • Jasmin Solanki <<jasmin.solanki@forgeflow.com>>

Maintainers

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/stock-logistics-workflow project on GitHub.

You are welcome to contribute. To learn how please visit <https://odoo-community.org/page/Contribute>.