Ask most warehouse teams what an item is worth and they'll tell you the quantity on hand. Ask finance the same question and you'll get a very different answer, because "worth" in an accounting sense depends on which units are deemed to have been sold, what it actually cost to land them in your warehouse, and whether you can even tell one unit apart from another. Inventory valuation is where these two views collide, and getting it wrong doesn't just distort a report — it misstates your gross margin, your tax liability and your balance sheet, every single month, quietly and compounding.
This guide walks through the two valuation methods that matter in practice — FIFO and weighted average — how landed cost feeds into either one, and how batch and serial tracking change the picture entirely by letting you value specific units instead of relying purely on a formula. If you run distribution, manufacturing or anything with regulated or individually warranted stock, this is the layer of ERP that determines whether your financial statements reflect reality or a convenient approximation of it.
Why Inventory Valuation Isn't Just a Bookkeeping Detail
Inventory is usually one of the largest single line items on a company's balance sheet, and the value assigned to it flows directly into two places that matter enormously: cost of goods sold on the profit and loss statement, and the closing inventory asset value on the balance sheet. Change the valuation method, or apply it inconsistently, and both numbers move — even though not a single unit of stock has physically changed.
That sensitivity is exactly why valuation method isn't a setting you pick once and forget. It determines reported profit in periods of rising or falling purchase prices, it affects how much tax a business pays in a given year, and it's one of the first things an auditor checks when reviewing inventory, because a mismatch between the declared method and the actual costing logic in the system is a classic sign of a control weakness.
There's also an operational dimension that's easy to underrate: valuation isn't just about what stock is worth today, it's about whether every stock movement — a sale, a transfer, a write-off, a return — carries a defensible cost with it. If the costing logic behind those movements is inconsistent or manually patched, the value of on-hand inventory drifts away from reality a little at every transaction, and by year-end the gap can be substantial without anyone having made an obviously wrong decision along the way.
FIFO vs Weighted Average: How Each Works
First-In-First-Out (FIFO) assumes that the oldest stock on hand, by receipt date, is the first to be issued or sold. When you record a sale, the system pulls the cost from the earliest unconsumed purchase layer first, then moves to the next-oldest layer once that one is exhausted. The practical effect is that cost of goods sold tends to lag current purchase prices, while the value of remaining inventory tracks closer to recent cost — which matters a lot in periods where input prices are moving, because FIFO and a more current-cost method can report meaningfully different margins on the exact same sales.
Weighted average valuation works differently: instead of tracking discrete purchase layers, it recalculates a single blended cost per unit every time new stock is received, by dividing total inventory value by total quantity on hand. Every unit issued after that point — sale, transfer, or consumption into production — is costed at that same blended average, regardless of which physical batch it actually came from. It's simpler to maintain, smooths out short-term price volatility, and tends to be the more common default for businesses dealing in commodity-like items where the specific purchase layer genuinely doesn't matter.
Neither method is universally "correct" — the right choice depends on what you're selling and how prices move. FIFO makes sense when physical stock rotation genuinely follows an oldest-first pattern (which is true of almost anything perishable or shelf-life limited) and when you want reported margin to reflect the real economics of holding stock through a price change. Weighted average makes sense for high-volume, fungible items where tracking individual purchase layers adds administrative overhead without adding decision-useful information — bulk raw materials, fasteners, generic consumables, and similar SKUs where one unit is truly interchangeable with the next.
One point worth being explicit about: valuation method and physical picking method are two separate decisions that often get conflated. You can physically pick oldest stock first on the warehouse floor while the system values issues on a weighted average basis, or vice versa. They should usually be aligned for perishables, but for non-perishable items it's entirely reasonable to pick nearest-bin for efficiency while valuing on weighted average for simplicity — the two don't have to move in lockstep.
Landed Cost: Freight, Duty and the Real Cost of Stock
Whichever valuation method you use, it's only as accurate as the cost figure feeding into it — and the purchase order price alone is rarely the full cost of getting an item into a sellable state in your warehouse. Landed cost adds everything else: inbound freight, customs duty, insurance, clearing agent fees, and any inspection or handling charges incurred before the stock is available to sell. Valuing inventory at purchase price alone systematically understates cost and overstates margin on every imported or freight-heavy item, and the distortion gets worse the more of your catalog comes from overseas suppliers.
The mechanics matter here: landed cost components typically arrive on separate documents — a freight invoice, a customs bill of entry, an insurance premium — that don't always land in the system on the same day as the goods receipt. A workable approach allocates these additional costs back across the receiving purchase order, usually proportionally by value or weight, and updates the unit cost of the received batch before it enters the valuation layer. Done manually in a spreadsheet, this step is one of the most commonly skipped parts of costing, simply because it's tedious to reconcile freight bills against goods receipts after the fact.
Landed cost also interacts directly with valuation method in a way that's easy to miss. Under FIFO, an unusually expensive freight month creates a distinct, identifiable cost layer that will eventually work its way through cost of goods sold as that stock is issued — so a one-off shipping cost spike shows up as a temporary margin dip later, not immediately. Under weighted average, the same freight spike gets blended into the running average cost immediately, spreading its effect thinly across every unit issued from that point forward rather than concentrating it on the units it actually applies to. Neither behavior is wrong, but not knowing which one your system is doing makes margin analysis very hard to trust.
Batch Tracking for Expiry and Lot-Level Traceability
Batch (or lot) tracking groups units received or produced together under a single batch identifier, typically carrying a manufacture date, expiry date and supplier or production reference. It's the standard traceability mechanism for pharmaceuticals, food and beverage, chemicals, cosmetics and any regulated goods category — but it's just as useful for electronics components and industrial parts, where a defect traced to one production run needs to be isolated without recalling everything the company has ever sold.
The valuation angle is where batch tracking earns more than a compliance checkbox. Because each batch carries its own received cost — including its share of landed cost — the system can value stock at the batch level rather than purely by formula. That means when a specific batch is sold, transferred, or written off for expiry, the cost recorded against it is the actual cost of that batch, not an estimate produced by averaging across everything currently in stock. This is particularly important for expiry write-offs: knowing the exact cost of the batch being scrapped, rather than an average figure, is the difference between an accurate loss entry and a rough guess dressed up as one.
Batch tracking also changes how FIFO gets enforced operationally. Rather than FIFO being a costing assumption applied after the fact, batch-aware systems can enforce first-expiry, first-out picking directly at the point of dispatch — flagging or blocking an attempt to issue a later-dated batch while an earlier-expiry batch of the same item still sits on the shelf. That closes the gap between what the valuation method assumes happens and what actually happens on the warehouse floor, which is where a lot of quiet inventory loss occurs in businesses relying on manual batch discipline.
QTT-ERP's Inventory module handles batch tracking as a native attribute of the item, not a bolt-on report — batch number, expiry date and received cost travel with the stock through every movement, so a sales return, an expiry write-off or a recall query can be resolved against the exact batch involved rather than reconstructed from purchase history after the fact.
Serial Tracking for Individually Warranted Items
Serial tracking goes a step further than batch tracking by assigning a unique identifier to every single unit rather than to a group of units. It's the right fit for anything with an individual warranty, a service history, or a regulatory requirement to trace one specific unit through its lifecycle — machinery, appliances, electronics, vehicles and their major components, and any equipment that will need servicing, replacement parts, or warranty claims tied to that exact unit later.
From a valuation standpoint, serial tracking is the most precise option available: each unit's actual landed cost — including its specific share of freight and duty from the purchase order it arrived on — is attached to it individually, and stays attached through transfers, service events and eventual sale. There's no averaging and no assumption about which purchase layer it belongs to, because the system already knows. When that unit is sold, cost of goods sold reflects exactly what that unit cost, not a formula's estimate of what a typical unit of that item costs.
The tradeoff is administrative: serial tracking requires capturing and scanning a unique identifier at every stage — receipt, put-away, transfer, dispatch — which is worthwhile for high-value or individually warranted items but excessive for low-value, high-volume stock where the cost of tracking exceeds the value it protects. A sensible policy applies serial tracking selectively, typically by item category or unit value threshold, rather than switching it on universally and generating friction for items that don't need it.
This is also where warranty and after-sales service genuinely depend on inventory data being right. A support team fielding a warranty claim needs to pull up the exact unit's purchase date, supplier, and service history in seconds — not dig through a spreadsheet cross- referencing a serial number against a sales invoice. QTT-ERP's Inventory module supports serial tracking end to end, from goods receipt through sale, transfer and service, so that history is one lookup away rather than a reconstruction project.
Where Valuation Method Meets Batch/Serial Costing
It's worth being precise about how these two ideas — valuation method and batch/serial tracking — actually interact, because they're often described as if they're the same decision when they're not. Valuation method (FIFO or weighted average) determines how cost flows through issues when you're relying on a formula applied across fungible stock. Batch and serial tracking, by contrast, let you bypass the formula entirely for the units that carry their own identified cost, because you already know exactly what that specific unit or lot cost to land.
In practice, most businesses run a hybrid: items under batch or serial tracking are valued at their actual identified cost, while everything else — bulk, fungible, non-tracked stock — runs on whichever formula-based method (FIFO or weighted average) is configured for that item category. This isn't a compromise so much as the correct application of each approach to the stock it fits: identified cost where individual units are meaningfully different from each other, formula-based averaging where they genuinely aren't.
Where businesses run into trouble is applying a formula-based method to stock that should really be identified-cost — averaging away real cost differences between batches that actually matter for margin analysis, expiry write-offs, or warranty cost recovery. The symptom is usually a gross margin report that looks smooth and plausible in aggregate but falls apart the moment someone tries to explain the margin on a single order, because the cost figure behind it was never real to begin with — just an average standing in for it.
Keeping Valuation Consistent Across Warehouses
Multi-location businesses add another layer of complexity: the same item, sitting in two different warehouses, can easily end up with two different average costs if each location's receipts and issues are costed independently. That's not necessarily wrong on its own — it can reflect genuinely different freight costs to reach each location — but it becomes a problem the moment stock is transferred between warehouses or consolidated for financial reporting, because "what is this item worth" no longer has one answer.
The cleanest approach sets valuation method once at the item or item-category level and applies it identically across every warehouse, while still tracking cost layers or batches separately per location so that location-specific freight or handling differences are captured accurately rather than blended away. Inter-warehouse stock transfers should carry the originating cost with them — including any additional freight incurred in the transfer itself — rather than resetting to a local average on arrival, which is a common source of valuation drift in businesses that treat each warehouse as its own costing silo.
This matters even more at consolidation time. A finance team closing the books across five branches needs total inventory value to be a sum of consistently-costed numbers, not five different costing logics stitched together after the fact. QTT-ERP connects multi-warehouse stock movements directly to Finance, so a transfer, a batch receipt or a serial dispatch at any location updates the same underlying valuation ledger the consolidated balance sheet draws from — rather than requiring a manual reconciliation step between operations and accounting at month-end.
Financial Reporting and Audit Implications of Getting It Wrong
Inventory valuation errors don't announce themselves. A misapplied method, an unallocated landed cost, or a batch write-off costed against the wrong lot doesn't throw an error — it just quietly makes the balance sheet and profit and loss statement slightly wrong, and that small error compounds every period it goes uncorrected, because each new transaction builds on a cost base that was already off.
Auditors specifically test inventory valuation for two things: whether the declared method is applied consistently across the period, and whether the values are supportable by underlying documentation — purchase invoices, landed cost allocations, batch or serial records. A business that can't reproduce how a specific item's cost was arrived at, on request, is exactly the kind of finding that turns into a qualified audit opinion or a management letter comment, even when there's no actual fraud or malicious intent involved — simply an inconsistent or undocumented costing process.
The downstream effects reach beyond the audit itself. Overstated inventory value inflates reported profit and, potentially, tax liability in a given year, only to correct itself (often unfavorably) in a later period when the error is found — which is a worse outcome than getting it right from the start. Understated inventory does the reverse, understating profit and potentially triggering unnecessary questions from lenders or investors reading the numbers at face value. Neither direction of error is harmless, and both are avoidable with a costing process that's applied consistently and traceable back to source documents.
The practical takeaway is that valuation accuracy isn't a year-end cleanup task — it's a byproduct of how consistently costing rules are applied to every single transaction throughout the year. A system that enforces one valuation method per item category, applies landed cost automatically at goods receipt, and carries batch or serial cost through every subsequent movement removes most of the manual judgment calls that are where these errors actually creep in.
Where to Go From Here
None of this is abstract accounting theory — it's the layer that determines whether the margin figure on your monthly report reflects what actually happened in your warehouse, or a convenient approximation that will need correcting later. The right combination of valuation method, landed cost allocation, and batch or serial tracking depends on what you sell and how regulated or individually warranted it is, but the underlying principle is constant: cost should be as identified and as consistently applied as the nature of the stock allows.
If you're evaluating whether your current setup gets this right, the fastest way to find out is to pick one item, trace a single unit or batch from purchase order through to sale, and see whether the cost figure at each stage is something you can actually explain and defend — or something a formula produced without anyone checking it against reality.
See your own valuation logic in action
Book a free QTT-ERP demo and we'll walk through FIFO, weighted average, landed cost and batch/serial tracking against your actual item list.
Book a Free DemoFrequently Asked Questions
FIFO assumes the oldest stock (by receipt date) is the first to leave, so cost of goods sold reflects older purchase prices while the closing balance reflects the most recent ones. Weighted average recalculates a single blended cost across all units on hand every time new stock arrives, so every unit issued carries the same average cost regardless of which physical batch it came from.
FIFO is the natural fit for perishables because it mirrors the physical practice of issuing older stock before newer stock to avoid expiry loss, and it keeps reported cost of goods sold aligned with the batches actually being consumed. Weighted average can still be used alongside FIFO physical picking, but the two should not be treated as interchangeable when shelf life is a real constraint.
Batch tracking is most obviously needed for expiry-driven goods, but it's also valuable for anything where you need to trace a manufacturing lot backward — raw material recalls, warranty claims tied to a production run, or regulatory compliance in electronics, chemicals and industrial components. If a defect could ever require you to identify which customers received a specific production run, batch tracking earns its keep.
Technically many systems allow it, but doing so makes consolidated financial reporting significantly harder to reconcile and audit, since the same item can show a different cost basis depending on which location it happens to sit in. Most businesses are better served by setting valuation method at the item or item-category level and applying it consistently across every warehouse.
Without batch or serial tracking, cost of goods sold is only ever an estimate produced by a valuation formula. With batch or serial tracking, the system can attach the actual landed cost of the specific unit or lot that was sold, which is materially more accurate — particularly when landed costs vary between purchase orders due to freight, duty or exchange rate movement.
Incorrect valuation misstates both the balance sheet (inventory asset value) and the profit and loss statement (cost of goods sold and gross margin), which auditors will flag as a material weakness if the gap is significant. It also undermines physical stock counts, since the counted quantity may be correct while its assigned value is not, making variance analysis unreliable until the valuation method and its application are corrected.
Written by the QTT-ERP Team
Queen Touch Technology builds QTT-ERP, a connected ERP platform for Indian manufacturers, distributors and service businesses. This guide draws on patterns we see across implementations.