odoo/documentation#19852
Created by fw-bot
Statuses:
- ci/documentation: (runtime 874s)
- ci/codeowner_coverage: (runtime 38s)
- label
- odoo-dev:saas-19.4-19.0-inventory-valuation-operations-impact-improvement-rexhu-562193-fw
- head
- 6b1f8aac5a24a240249538c12965ce0c683cab3b
- merged
- 5 days ago by Rex Hu (rexhu)
| odoo/documentation | |
|---|---|
| 19.0 | #19838 |
| saas-19.1 | #19849 |
| saas-19.2 | #19850 |
| saas-19.3 | #19851 |
| saas-19.4 | #19852 |
| master | #19853 |
[IMP] inventory: operations valuation article clarification
What this PR does and why it's needed
Clarifies the "How inventory operations affect valuation" article by retitling it to better reflect its scope and by explaining the distinction between the Unit Cost shown on a stock movement and the Cost field on the product form, which can otherwise be mistaken for the same value.
Changes
Inventory Valuation
- Renamed the page title from "How inventory operations affect valuation" to "Valuation of stock movements and inventory operations" for clarity.
- Clarified that Unit Cost is specific to each stock movement, and fixed its costing-method reference link.
- Added an important note explaining that the Cost field on the product form shows the average price of the product — even under the FIFO costing method — and is affected by outbound stock movements in that case; it is informational only and not used for valuation.
Additional changes during review
These changes were made in a follow-up commit (implementing Felicia's review suggestion) and later squashed into the final commit, all within content/applications/inventory_and_mrp/inventory/inventory_valuation/operations_valuation.rst:
-
:guilabel:→ italics for "Cost" field (lines 187-190)
Changed:guilabel:Cost`` to plain italic Cost throughout the callout, since it refers to the product form field conceptually rather than as clickable UI. -
New clarification on Cost field's role in adjustments (lines 192-194)
Replaced the old closing line ("The Cost field is not used for valuation, and is only informational") with a more accurate statement:
> "The value in the Cost field is used as the unit price for :ref:inventory/operations_valuation/inventory-adjustments, even when using the FIFO costing method." -
Renamed virtual location (line ~319)
Inventory Loss location -> Inventory adjustment location, matching Odoo's actual naming. -
Reworded valuation trigger for adjustments (lines 318-322)
Changed from "based on the current unit cost of the product" to "based on the difference between the counted quantity and the expected quantity" - a more precise description of what drives the value change. -
New paragraph added (lines 328-330)
> "Inventory adjustments use the product's current averaged cost as the :ref:unit cost <inventory/operations_valuation/stock-movement-reported-values>for the stock movement."
Net effect: 24 insertions, 8 deletions. The core addition clarifies that inventory adjustments always use the product's averaged cost as the unit price - even under FIFO - correcting the earlier (less precise) statement that the Cost field was purely informational.
This 19.0 PR can be FWP up to master.
Forward-Port-Of: #19838