Inventory

Weighted Average Cost (WAC) for Apparel Inventory Valuation: When It Fits and When It Breaks

Weighted Average Cost (WAC) for Apparel Inventory Valuation: When It Fits and When It Breaks
By Lalith Nandan Kalava · Reviewed by Ruchit Dalwadi · · 9 min read

Inventory valuation is one of those finance topics that operations teams treat as accounting’s problem until the choice produces a 1 to 5 percentage point gap between reported and realized margin. Then it becomes everyone’s problem. Weighted average cost is the simpler of the three primary valuation methods, the default in many ecommerce platforms, and the right answer for some operating models and the wrong answer for others.

This guide explains how WAC actually calculates, when it fits apparel operating models and when it breaks, how it compares to FIFO and specific identification, and what the practical operational implications are for brands $5M to $100M running multi-channel operations.

What is weighted average cost and what does it actually calculate?

Weighted average cost is an inventory valuation method that recalculates a SKU’s unit cost every time inventory is received. The formula:

New WAC = (existing inventory value + new receipt value) / (existing units + new receipt units)

When the warehouse picks units to fulfill an order, COGS is calculated using the current WAC, regardless of which physical units actually shipped.

A worked example. A brand starts a season with 100 units of a SKU valued at $20 each, total inventory value $2,000.

The brand receives a second shipment: 50 more units, this time at $25 each (freight rates rose, or the duty rate changed, or the factory raised prices).

New WAC = ($2,000 + $1,250) / (100 + 50) = $3,250 / 150 = $21.67 per unit

After this receipt, every outbound shipment costs $21.67 in COGS. The system does not track which physical unit shipped (the $20 ones from receipt 1, or the $25 ones from receipt 2). It assumes a blended cost.

A third receipt arrives: 40 units at $24 each.

New WAC = ((150 - shipped units) × 21.67 + 40 × 24) / (remaining units + 40)

Each receipt rolls the average forward. Each outbound shipment uses whatever the current average is at that moment.

What problem does WAC solve?

WAC’s main operational benefit is simplicity. The system stores one cost per SKU. Outbound shipments use that one cost. Reporting is straightforward. No tracking of which lot of inventory is which physical unit. No complex landed-cost-by-receipt history.

The smoothing effect is a related benefit. Apparel brands buying the same SKU repeatedly across a season at varying freight and duty rates would otherwise show wild COGS swings depending on which receipt’s units shipped on which day. WAC produces a stable cost basis that makes month-over-month margin reporting more useful.

The method also pairs well with operating systems built around aggregate inventory rather than lot-tracked inventory. Shopify Plus’s reporting defaults to WAC. Most generic ERPs default to WAC. Most apparel-specific ERPs support both WAC and FIFO and let the brand choose.

When does WAC fit apparel operating models?

Three operating profiles where WAC is the natural choice.

Replenishment-program apparel. Core basics, year-round staples, replenishment SKUs reordered 6 to 10 times per year at slightly varying landed costs. The repeated-receipt pattern is exactly what WAC was designed for. The smoothing produces operationally useful margin reporting.

Single-collection brands buying once per season. A brand that produces a season’s worth of units in one production run and sells them out has only one receipt per SKU per season. WAC and FIFO produce the same number for that operation; the simpler method wins.

Operations on Shopify Plus or generic ERPs by default. Many systems default to WAC and require explicit configuration to switch. Brands that haven’t made an active choice are usually on WAC and don’t need to switch unless something specific is breaking.

When does WAC break?

Four operating profiles where WAC produces problems.

Profile 1: Dramatic landed-cost swings between receipts

When freight rates double during peak season, when tariffs shift mid-quarter, or when a factory raises prices significantly between PO commits, WAC averages the spike across all units. The brand reports a moderate cost increase across all units when in fact the latest units cost much more.

The operational implication: the brand makes pricing or reorder decisions on the average when the marginal unit costs much more (or much less) than the average. Pricing-to-margin from WAC during a tariff spike produces understated cost and overstated margin on units that haven’t actually arrived yet.

FIFO surfaces this differently: the receipts at the higher cost report COGS at the higher cost, immediately and visibly.

Profile 2: Per-unit cost precision matters

For luxury brands or made-to-measure operations where each unit may have a meaningfully different actual cost, WAC’s averaging hides the per-unit reality. A brand selling pieces at $400 retail with actual landed costs of $80 to $140 cannot meaningfully use WAC; the variance per piece exceeds what WAC’s smoothing can usefully report.

Specific identification (each unit tracks its actual cost) is the right method here. WAC reports a single number for the SKU, which loses the actual financial picture.

Profile 3: Tariff-exposure brands

Apparel brands with significant exposure to tariff-impacted countries (US tariffs on China, Vietnam, Bangladesh have all shifted in recent years) experience landed-cost volatility that WAC averages away. The financial-reporting implication is meaningful: WAC understates COGS during cost-rising periods and overstates COGS during cost-falling periods, by 1 to 5 percentage points of margin in each direction.

For tariff-exposed brands, FIFO produces more decision-useful margin reporting because each receipt’s actual cost is visible.

Profile 4: Compliance or audit requirements

Some operations require specific-identification or lot-tracked inventory: regulated categories, controlled goods, or audit requirements that demand traceability to specific receipts. WAC by definition cannot satisfy these requirements because it does not track which physical units ship from which receipt.

How does WAC compare to FIFO and specific identification?

The three primary inventory valuation methods produce different reports from the same physical operation.

MethodHow it assigns costProsCons
WACRolling average across all receiptsSimple, smooths volatility, defaults in many systemsHides receipt-level cost reality, less accurate per-unit
FIFOOldest receipts cost out firstReflects actual receipt economics, better for cost-rising periodsMore complex tracking, each receipt’s history must be maintained
Specific identificationEach unit tracks its actual costMost accurate, supports per-unit margin and auditHighest tracking overhead, only practical for low-velocity high-value items

The choice has real financial implications. Consider a SKU with three receipts during a period of rising costs:

  • Receipt 1: 100 units @ $20 each = $2,000
  • Receipt 2: 50 units @ $25 each = $1,250
  • Receipt 3: 40 units @ $30 each = $1,200

If 80 units ship during the period:

WAC assigns 80 × $23.42 (the running average) = $1,874 in COGS. Remaining inventory: 110 units × $23.42 = $2,576.

FIFO assigns 80 × $20 (all from receipt 1) = $1,600 in COGS. Remaining inventory: 20 units @ $20 + 50 @ $25 + 40 @ $30 = $400 + $1,250 + $1,200 = $2,850.

The difference: FIFO reports $274 more inventory value and $274 less COGS for the period. On a small-scale example this seems modest; scaled across a $15M brand’s SKU catalog over a year, the difference can run hundreds of thousands of dollars and produce meaningfully different margin reporting.

How does the WAC choice affect operations?

Three operational implications matter beyond the financial-reporting differences.

Reordering decisions. A brand using WAC sees the smoothed cost when planning reorders. A brand using FIFO sees the most-recent cost (assuming oldest receipts have shipped). When deciding whether a SKU is still profitable to reorder at current vendor pricing, FIFO surfaces the answer faster.

Margin per channel. When WAC reports a single cost per SKU, channel-level margin reporting (wholesale margin, DTC margin, marketplace margin) uses that one cost. The actual margin reality may differ if the units that physically shipped to wholesale were from a higher-cost receipt while the units to DTC were from a lower-cost receipt. The operational implication for most apparel brands is small but non-zero.

Month-end close speed. WAC’s simplicity shows up at month-end close. The system has one cost per SKU; finance closes against current WAC. FIFO requires the system to track which specific receipts have remaining units and apply their costs; the close is more complex.

For brands that prioritize close speed and do not have the operating profile problems described above, WAC’s operational simplicity is meaningful. For brands with tariff exposure, dramatic landed-cost swings, or per-unit cost precision needs, the FIFO complexity is worth carrying.

What does the WAC implementation actually require?

For apparel brands $5M to $100M, three things matter for WAC to produce useful reporting.

Receipt-level cost capture

Every receipt records actual landed cost: FOB price plus freight plus duty plus inbound handling. The system uses this to compute the new WAC at receipt time. Brands that capture only FOB price get inflated reported margins because the WAC understates true cost.

Receipt vs cost timing

The receipt event must occur in the system before any outbound shipment uses the new WAC. If the warehouse picks and ships against the old WAC because the receipt has not been booked yet, the books are wrong even though the math is right.

One cost record per SKU

WAC requires the system to maintain exactly one current cost per SKU. Brands operating on stacks of separate systems (DTC platform with one cost, wholesale platform with another, accounting system with a third) discover at month-end that the three systems disagree about the same SKU’s cost. The reconciliation work undermines the simplicity that WAC was supposed to provide.

For apparel brands at this size band, the operating system architecture matters more than the valuation method choice. A connected system maintaining one cost record per SKU produces useful WAC reporting; a fragmented stack of systems with their own cost records produces unreliable reporting regardless of the chosen method.

Key takeaways

  • Weighted average cost (WAC) recalculates a SKU’s unit cost as a weighted average across all receipts every time new inventory arrives.
  • WAC fits apparel brands buying repeat SKUs at varying prices, brands with single-collection-per-season operations, and brands defaulting to WAC in their operating system.
  • WAC breaks for tariff-exposed brands, brands with dramatic landed-cost swings between receipts, brands needing per-unit cost precision, and brands with compliance or audit requirements.
  • FIFO is the more common alternative for mature mid-market apparel brands, particularly those with tariff exposure or freight cost volatility.
  • The choice produces 1 to 5 percentage points of difference in reported gross margin during periods of meaningful cost change.
  • Implementation requires receipt-level landed-cost capture, correct receipt vs shipment timing, and one cost record per SKU across the operating system.

If your finance team is reporting margin numbers that don’t match operational reality and you suspect WAC is hiding what is actually happening at the receipt level, the fix is usually structural rather than method-switching. Book a tailored demo to see how a connected operating record handles inventory valuation, landed cost, and margin reporting cleanly across both methods.

Frequently asked questions

L
Written by
Lalith Nandan Kalava
Senior Product Manager, Reporting and Operational Analytics, Uphance

Lalith writes about operational reporting and analytics for apparel brands, covering how connected data across inventory, orders, fulfillment, and warehouse execution translates into reporting that supports real decisions.

R
Reviewed by
Ruchit Dalwadi
Head of Product, Apparel Operations, Uphance

Ruchit writes about product strategy for apparel operations, covering how mid-market fashion brands use connected workflows to manage product development, inventory, orders, warehouse execution, and reporting.

More from the blog