Odoo Inventory Valuation: AVCO vs FIFO and the accounting impact

What inventory valuation means in Odoo

Inventory valuation in Odoo is governed by two independent settings that teams constantly conflate, and separating them is the single most useful framing for configuring the system correctly. The costing method decides what each unit of stock is worth; the accounting method decides when that worth reaches your general ledger. Choosing AVCO or FIFO changes your cost of goods sold and your balance-sheet inventory value; choosing Periodic or Perpetual changes the timing and the volume of the journal entries that sit behind those numbers.

A second split runs between the two applications that own valuation. The Inventory application maintains the real-time value of physical stock as goods are received and delivered; the Accounting application updates the financial books only when invoices and bills are posted, and then again at closing. Odoo's own valuation cheat sheet is explicit that it is not practical for accountants to post a journal entry for every inventory movement, so the accounting side reconciles to the inventory side through a closing entry rather than move by move. This is exactly why your Inventory > Reporting > Stock value and your Accounting > Review > Inventory Valuation value can differ in the short term, and why the closing process exists to bring them together.

In Odoo 19, valuation lives on stock moves rather than the older valuation-layer tables: each receipt, delivery, return, or adjustment carries quantity, unit cost, and total value. That redesign is what makes Perpetual post at bill/invoice time and still keep warehouse value live. This guide is the finance and valuation angle. For the warehouse operations that valuation sits on top of — receipts, transfers, deliveries, routes, and putaway — see the Odoo Inventory module guide; for the broader finance application — general ledger, bank reconciliation, and tax reporting — see the Odoo Accounting guide. The rest of this page covers the three costing methods, why LIFO is not one of them, Periodic vs Perpetual and the Odoo 19 redesign, Continental and Anglo-Saxon COGS timing, journal accounts, landed costs, returns under AVCO and FIFO, reporting and closing, common misconfigs, and how to choose.

The three costing methods: Standard, AVCO, FIFO

Odoo supports three costing methods, configured in Accounting settings and optionally overridden on a product category: Standard Cost (a fixed unit cost you update manually), Average Cost (AVCO, the weighted average of all units on hand), and FIFO (first in, first out). The same physical sequence of receipts and deliveries produces three different inventory values and three different costs of goods sold, and walking through one example makes the trade-offs concrete.

Take a product that starts with zero stock. You receive 8 units at $10, receive 4 more at $16, deliver 10 units to a customer, and finally receive 2 units at $6. Under Standard Cost fixed at $10, every receipt and delivery is valued at $10 regardless of what you actually paid, so the delivered batch costs 10 x $10 = $100 and you finish holding 4 units worth $40. The gap between the $10 standard and the real purchase prices does not sit in the stock value; it flows through a separate price-difference account, which is how Standard Cost keeps the on-hand value stable.

Under AVCO, the unit cost re-averages on every receipt only — deliveries do not change the moving average. The first two receipts total $144 across 12 units, so the average becomes $12; delivering 10 units removes 10 x $12 = $120, leaving $24 across 2 units; the final $6 receipt re-averages to $9 across 4 units, ending at $36. Formula: new MAP = ((current MAP x qty on hand) + (receipt price x receipt qty)) / (qty on hand + receipt qty). Under FIFO, the 10 delivered units are costed against the oldest layers first — 8 at $10 and 2 at $16, totalling $112 — leaving the 2 newest $16 units on the books at $32, which becomes $44 after the final $6 receipt. FIFO keeps each remaining inbound layer's own cost until it is fully consumed.

The ordering matters more than the arithmetic. In a rising-price run, FIFO assigns the oldest, cheapest costs to cost of goods sold, so gross profit is highest and remaining inventory reflects newer, higher costs; AVCO smooths swings into a moving average; Standard Cost decouples stock value from market price and pushes variance into a price-difference account. Which behaviour you want depends on whether you manage stable-cost manufactured goods, volatile-cost distributed goods, or import-heavy landed-cost goods — a decision we return to at the end of this guide.

Why LIFO is a removal strategy, not a costing method

A persistent source of confusion is LIFO. Odoo does support LIFO, but as a removal strategy, not a costing method. Removal strategies — which include LIFO and FEFO — decide which physical batch is picked first from a location; they do not change how the picked units are valued. You can configure a product to be picked last-in-first-out while still valuing it at average cost, and the Odoo valuation cheat sheet spells this distinction out directly.

The reason LIFO is not a costing option is regulatory. IFRS, through IAS 2, requires inventories to be measured using FIFO or weighted average cost, and LIFO is not permitted; US GAAP is the exception, permitting LIFO alongside FIFO and weighted average cost. Because Odoo ships a single global product, it builds the IFRS-compliant behaviour into the valuation engine and leaves LIFO to the physical-picking layer. If your business reports under US GAAP and elects LIFO for tax, that is a tax-led accounting choice handled outside Odoo's standard costing methods — and under the US LIFO conformity rule, electing LIFO for tax generally requires LIFO in the financial statements as well.

The practical consequence is that teams arriving expecting a LIFO costing toggle will not find one. If matching the most recent costs to COGS is the goal, the closest Odoo-native options are FIFO combined with disciplined landed-cost capture, or a Standard Cost that you re-set to current replacement cost on a cadence. Neither reproduces LIFO accounting, and that is by design rather than an omission.

Periodic vs Perpetual, and the Odoo 19 redesign

Where costing answers what a unit is worth, the accounting method answers when that worth hits the ledger. Odoo offers two, set under Accounting > Configuration > Settings in the Inventory Valuation section: Periodic (at closing) and Perpetual (at invoicing). Periodic posts vendor bills as expenses and updates stock valuation only when you run the closing entry; Perpetual posts vendor bills as stock assets and recognises cost of goods sold when the goods are sold (customer invoice posted).

Odoo 19 fundamentally changed how Perpetual works, and this is the single most important thing to unlearn if you have read older tutorials. Before Odoo 19, Perpetual posted a real-time journal entry at every stock movement, which produced a flood of journal items and hurt performance, general-ledger clarity, and auditability. Since Odoo 19, Perpetual touches the stock valuation account at the invoice level, and a single closing entry reconciles the gaps — bills not yet received, invoices not yet issued, prepaid expenses, and deferred revenue. Valuation layers are gone; values live on stock moves. Partner write-ups of the redesign stress fewer journal entries, a cleaner general ledger, and faster performance — and that migration must rebalance legacy interim accounts before go-live.

The older "Automatic Accounting" / automated valuation toggle is gone. In Odoo 19 you configure Inventory Valuation (Periodic or Perpetual) in Accounting settings, optionally override per product category, and use Accounting > Review for Inventory Valuation, Bills to Receive, Billed Not Received, Invoices to Issue, and Invoiced Not Delivered. The cheat sheet frames configuration as a four-cell matrix of Continental vs Anglo-Saxon philosophy crossed with Periodic vs Perpetual timing. Odoo 19 supports all four with automated closing and accrual handling. For most SMEs the closing runs once a year; larger companies run it monthly, configurable as Manual, Daily, or Monthly under the same settings.

Continental vs Anglo-Saxon: when cost of goods sold is recognised

Underneath the Periodic and Perpetual choice is a deeper accounting philosophy that determines when cost of goods sold is recognised, and it tracks geography. In Continental accounting — the model used across much of continental Europe, including France, Belgium, and Germany — the cost of purchased goods is recorded as an expense when the vendor bill is posted, typically on receipt, regardless of whether those goods have been sold. Inventory becomes a period-end adjustment rather than a real-time asset on the balance sheet.

In Anglo-Saxon accounting — the model used in the United States, the United Kingdom, Canada, and Australia, and by most trading companies in the Gulf — purchases increase an inventory asset account, and cost of goods sold is recognised only when the customer invoice is posted, that is, when the goods are sold. This is the matching principle applied to inventory: expense follows revenue rather than purchase, so the income statement reflects the cost of what was actually sold in the period.

Odoo maps these philosophies to its timing methods. Periodic is the natural fit for Continental practice and is described in the documentation as the best practice in Europe; Perpetual is the natural fit for Anglo-Saxon practice and is described as the best practice in Anglo-Saxon countries such as the USA and India. The mapping is a default rather than a constraint — Odoo's own note is that companies may choose a different combination based on their needs — but staying on the default for your jurisdiction keeps the general ledger aligned with what auditors and tax authorities expect. Multi-company groups with both European and US entities should set philosophy and timing per company, not once for the whole database.

The journal entries and accounts behind valuation

The accounting impact lands on a small set of accounts that you configure once and then let the engine populate. The Stock Valuation account holds the inventory value as a current asset on the balance sheet. The Stock Variation account is the buffer that records the difference between posted inventory value and the real-time stock value recorded in the Inventory app, and it clears through the closing entry (or as bills and invoices catch up under Perpetual). An Expense or Cost of Goods Sold account recognises cost, and an Inventory Loss account on the Inventory Loss location captures shrinkage and adjustments separately from normal variation.

Odoo 19 removed the separate Stock Interim (Received) input and Stock Interim (Delivered) output accounts that older Perpetual setups used on every warehouse move. Those interims are replaced by Stock Variation as the unified buffer. On a typical Anglo-Saxon Perpetual path: validate a receipt and Inventory shows value immediately while Accounting shows the same amount under Stock Variation until you post the vendor bill (Debit Stock Valuation, Credit Payable). Validate a delivery and Inventory drops the value; posting the customer invoice then Debits COGS and Credits Stock Valuation alongside the revenue/receivable lines. Until bill and invoice are posted, Accounting > Review > Bills to Receive or Invoices to Issue flags the open gap — no GL flood of move-level entries.

Under Continental Periodic, the same vendor bill Debits Expense and Credits Payable — goods are expensed on purchase — and stock value is sorted out at closing when variation moves into the Stock account. A customer invoice under Continental posts stock variation and income rather than the Anglo-Saxon COGS/Stock pair. The closing entry reconciles the two worlds: it moves the period's stock variation into Stock under Continental practice, or realises remaining variation as COGS under Anglo-Saxon practice, and aligns accounting inventory with Inventory's real-time value. Two refinements matter in practice. With Perpetual plus Standard Cost, a Price Difference account on the product category captures the spread between standard price and actual billed price. For manufacturers, a Cost of Production location account isolates production-related variation — under Anglo-Saxon Perpetual, finished goods and component valuation update when a manufacturing order is validated, with Cost of Production as the counterpart.

Landed costs and the true cost of goods

Vendor-invoice cost is rarely the true cost of goods. Freight, insurance, customs duties, and handling fees all belong in inventory valuation, and Odoo's Landed Costs feature allocates them to the products on a receipt so that cost of goods sold and stock value reflect what the goods actually cost to bring in. It is enabled under Inventory > Configuration > Settings in the Valuation section, after which you nominate a Default Journal for the landed-cost entries.

Landed costs are modelled as Service products flagged Is a Landed Cost on the Purchase tab, each carrying a Default Split Method that decides how the charge is spread across the receipt. Equal divides it evenly across products, By Quantity spreads it per unit, By Current Cost weights it toward the more expensive items, and By Weight or By Volume spread it by the relevant physical measure. You add the landed-cost line to the vendor bill, generate the landed-cost record, link it to the validated transfer, compute, and validate — Odoo then posts a journal entry that re-values the affected stock. Under AVCO that re-value feeds the moving average; under FIFO it adjusts the layers tied to the receipt.

One hard constraint shapes the decision. Landed costs can only be applied to products in a category whose costing method is AVCO or FIFO; Standard Cost categories cannot absorb landed-cost adjustments, because a fixed cost has no mechanism to recompute. For import-heavy distributors this is a strong reason to choose AVCO or FIFO over Standard Cost regardless of other preferences, since capturing true landed cost is what makes gross margin on imported goods trustworthy in the first place. Apply landed costs promptly after the related receipt: late allocation leaves early deliveries costing vendor price only and distorts COGS until the adjustment lands.

Returns under AVCO and FIFO: where valuation diverges from the vendor price

Returns are where controllers first notice that warehouse value and commercial price are not the same number — especially under AVCO. Odoo's official average-price documentation is explicit: products returned to suppliers are commercially credited at the original purchase price on the credit note, but internal inventory valuation treats the return as stock leaving at the current average cost. If you bought at $10, later receipts pushed MAP to $12, and you return a unit, Inventory drops by $12 while the vendor credit may still be $10. The gap sits in Stock Variation until later bills, invoices, or the closing entry clear it. That is standard AVCO behaviour, not a misposting.

Worked shape of a vendor return under AVCO (illustrative, same logic as partner Odoo 19 scenarios): on-hand MAP is $57.62 after mixed receipts; you reverse-transfer 20 units and post a credit note at the original $60 purchase price. Inventory reduces by 20 x $57.62 = $1,152.40; the credit note hits Payable and Stock at $1,200. The roughly $47.60 difference is Stock Variation — vendor commercial price versus inventory cost. Customer returns reverse the path: reverse the delivery, issue a credit note, and Odoo restores stock and reverses COGS using the cost that was on the original outbound move (not necessarily today's MAP).

FIFO returns are layer-sensitive. Standard Odoo FIFO consumption takes from the oldest remaining layers when stock leaves, including some return paths — which can disagree with auditors who expect a purchase return to reverse the original receipt layer. Community OCA modules such as stock_account_fifo_return_origin exist specifically to force purchase returns onto the origin receipt's valuation when standard FIFO outbound logic is not acceptable for audit. If FIFO layer integrity on returns is a hard requirement, test return scenarios on a copy of production before go-live and decide whether standard behaviour or an audited OCA approach fits your auditors.

Never change a product's category costing method while meaningful stock is on hand without an accountant-led plan. Switching Standard ↔ AVCO ↔ FIFO with stock re-values residual quantity under the new method and can scramble historical COGS comparisons. Prefer emptying or counting stock, closing the period, and switching at period start. Category-level account maps (valuation journal, stock valuation account, price difference, expense/COGS) must be complete before the first Perpetual adjustment — a missing Inventory Valuation Journal is a common reason inventory adjustments fail validation.

Reading the reports and running the closing

Two reports carry the valuation story. In the Inventory application, Reporting > Stock shows real-time quantities and values per product, location, company, and lot, and you can restate the view as of a past date. Clicking a product's Unit Cost traces how the current value was derived — especially useful under AVCO, where each receipt re-averages the cost — and clicking Total Value shows the incoming moves that still have remaining quantity, with FIFO retaining each layer's individual value while AVCO and Standard Cost show the current average. In FIFO or AVCO you can also Adjust Valuation on remaining quantity from a previous incoming move when a layer needs a controlled correction.

In the Accounting application, Review > Inventory Valuation is where finance sees the gap — the older Inventory-app "Stock Valuation" report many Odoo 18 users bookmarked is not the same screen after the Odoo 19 redesign. The Review report opens with an Initial Balance, shows Stock Variation as the difference between posted accounting value and the Inventory application's real-time value, and projects an Ending Stock that takes effect once the closing entry is posted. Generating the entry produces a draft Stock Closing transaction you review and post, after which the Stock Valuation and Stock Variation accounts update in the general ledger.

When deliveries and invoices are out of step, accrual views close the loop. Odoo surfaces Bill To Receive, Invoices To Be Issued, Billed Not Received, and Invoiced Not Delivered under Accounting > Review; creating accrual entries recognises revenue and expense in the correct period. Under Anglo-Saxon Perpetual these entries also pull value out of the buffer Variation account and allocate it where it belongs, such as Goods Received Not Invoiced. The Inventory Loss and Cost of Production accounts keep adjustments and production variation out of the main stock-variation flow so controllers can explain residual variation without drowning in noise.

Common misconfigurations that break valuation

Most valuation tickets are configuration mistakes, not costing-math bugs. First: mixing Continental chart expectations with Anglo-Saxon Perpetual (or the reverse) without redesigning the chart of accounts — COGS never appears when you expect it, or expenses double-count purchases. Align philosophy, Periodic/Perpetual, and account maps per company before the first real bill.

Second: incomplete product-category account maps. Perpetual categories need Stock Valuation, Stock Variation (or the equivalent buffer fields Odoo 19 exposes), Expense/COGS, Inventory Valuation Journal, and — for Standard Cost — Price Difference. Missing journal configuration is a frequent cause of failed inventory adjustments. Third: enabling landed costs after months of Standard Cost history, or applying freight only to some receipts — margins on early lots stay understated forever unless you revalue carefully.

Fourth: Odoo 18 → 19 upgrades with non-zero Stock Interim (Received) or Stock Interim (Delivered) balances. Those interims no longer drive the new flow; official guidance is to rebalance residual interim balances into the stock valuation account (Odoo ships a Stock Valuation rebalance interim Accounts server action) on a test database first, with an accountant review. Fifth: treating LIFO removal strategy as LIFO costing, or flipping category costing mid-period with stock on hand. Sixth: expecting Inventory Reporting > Stock and Accounting Review > Inventory Valuation to match every day without closing or without posting bills and invoices — under Odoo 19 that temporary gap is by design.

How to choose the right method

Choosing well means deciding the costing method, the accounting method, and whether landed costs apply — ideally once, at setup, because changing costing method mid-stream re-values your stock and is not a casual toggle. For costing, Standard Cost suits manufacturers with stable, known input costs who want predictable unit economics and are set up to maintain the standard; AVCO suits distributors whose purchase prices move and who want cost of goods sold and inventory smoothed without manual upkeep; FIFO suits businesses whose physical flow matches oldest-first and who want recent costs reflected in inventory, and AVCO or FIFO is required if you need landed costs.

For the accounting method, default to your jurisdiction's philosophy: Periodic for Continental European entities where purchase-as-expense is the norm, Perpetual for Anglo-Saxon entities that capitalise stock and recognise COGS on sale. Set the Periodic Valuation closing cadence — Manual, Daily, or Monthly — to match how often finance needs the books to match the warehouse, and remember that under Odoo 19 Perpetual you typically set closing to Manual and let the single closing entry reconcile residuals at period end while bills and invoices drive day-to-day valuation posts.

Three cautions round out the decision. First, if you operate across Continental and Anglo-Saxon entities, plan the configuration per company rather than database-wide. Second, if you are upgrading to Odoo 19 on Anglo-Saxon Perpetual, legacy stock input and output accounts are no longer used and any non-zero balances must be rebalanced into the stock valuation account — review the server action on a test database with an accountant first. Third, if landed costs matter to your margins, commit to AVCO or FIFO from day one and script return/credit-note tests so finance knows how MAP vs PO price gaps will look. The fastest way to lock these choices against your actual chart of accounts and reporting cadence is an ERP Readiness Call, and our AI-accelerated delivery model is designed to deliver up to 3x faster than a traditional rollout.

Frequently asked questions