Weighted Average Cost (WAC) for Apparel Inventory

It is the second Tuesday of the month, finance is closing the prior period, and the gross margin number on the P&L is 3.2 points lower than what the merchandising team has been quoting to the CEO all quarter. The buyer pulls up the SKU-level cost file. The receiving manager pulls up the freight invoices from the last container, which arrived at almost double the rate of the prior one. The controller pulls up the inventory valuation report. Three people, three different cost numbers for the same SKU. The accounting method at the center of this argument is usually weighted average cost.

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 apparel 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 in apparel inventory?

Weighted average cost (WAC) is an inventory valuation method that recalculates a SKU’s unit cost as a rolling weighted average across every receipt. The formula is straightforward: new WAC equals existing inventory value plus new receipt value, divided by existing units plus new receipt units. When the warehouse picks units to fulfill an order, COGS is calculated using the current WAC at that moment, regardless of which physical units actually shipped or which receipt they came from.

That is the quotable definition. The operational reality is more nuanced, because the same formula produces useful reporting in some apparel operating profiles and misleading reporting in others.

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 then 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, whether 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 minus shipped units) times 21.67 plus 40 times 24) divided by (remaining units plus 40). Each receipt rolls the average forward. Each outbound shipment uses whatever the current average is at that moment.

From the go-lives I have run this year, the pattern is consistent: brands rarely choose WAC, they inherit it. Shopify Plus reports default to WAC. Most generic accounting systems default to WAC. The choice was made by the software, not the finance team, and nobody examined whether it fit the operating model until the margin number stopped reconciling.

What problem does WAC solve for apparel brands?

WAC’s main operational benefit is simplicity. The system stores one cost per SKU. Outbound shipments use that one cost. Reporting is straightforward. There is no tracking of which lot of inventory is which physical unit, no complex landed-cost-by-receipt history to maintain across years of replenishment buys.

The smoothing effect is the 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 for trend analysis, even if it hides the receipt-level reality.

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, including Uphance, support both WAC and FIFO and let the brand choose based on operating profile rather than software default.

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 because no single receipt is unusual enough to distort the average.

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 accounting systems by default. Many systems default to WAC and require explicit configuration to switch. Brands that have not made an active choice are usually on WAC and do not need to switch unless something specific is breaking in the margin reporting.

When does WAC stop working for apparel?

Four operating profiles where WAC produces problems.

Why does WAC break during landed-cost swings?

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 have not actually arrived yet. FIFO surfaces this differently. The receipts at the higher cost report COGS at the higher cost, immediately and visibly, the moment those units start shipping.

When does per-unit cost precision matter more than smoothing?

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, where 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 across a mixed catalog of pieces with widely varying construction and material inputs.

Why is WAC risky for tariff-exposed apparel brands?

Apparel brands with significant exposure to tariff-impacted countries (US tariffs on China, Vietnam, and 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 as those units flow through. The buyer reordering against current vendor pricing sees the real cost on the most recent receipt, not the smoothed cost blended with cheaper inventory bought before the tariff change.

When do compliance requirements rule out WAC?

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. For most apparel brands this profile does not apply, but for brands handling regulated fibers, organic certifications, or category-specific compliance, the method choice is constrained.

How does WAC compare to FIFO and specific identification?

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

WAC assigns cost as a rolling average across all receipts. Pros: simple, smooths volatility, defaults in many systems. Cons: hides receipt-level cost reality, less accurate per-unit.

FIFO assigns cost from the oldest receipts first. Pros: reflects actual receipt economics, better for cost-rising periods, surfaces tariff and freight changes immediately. Cons: more complex tracking, each receipt’s history must be maintained in the system.

Specific identification tracks each unit’s actual cost. Pros: most accurate, supports per-unit margin and audit. Cons: highest 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 at $20 each, total $2,000
• Receipt 2: 50 units at $25 each, total $1,250
• Receipt 3: 40 units at $30 each, total $1,200

If 80 units ship during the period, WAC assigns 80 times $23.42 (the running average) equals $1,874 in COGS. Remaining inventory: 110 units at $23.42 equals $2,576.

FIFO assigns 80 times $20 (all from receipt 1) equals $1,600 in COGS. Remaining inventory: 20 units at $20 plus 50 at $25 plus 40 at $30 equals $400 plus $1,250 plus $1,200 equals $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 that drives different reorder, pricing, and assortment decisions.

How does the WAC choice change daily 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 because the most recent receipt’s actual cost is sitting on the margin report.

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, and it grows with the size of the landed-cost variance between receipts.

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 a WAC implementation actually require?

For apparel brands $5M to $100M, three things matter for WAC to produce useful reporting. This is where the 6 Breakpoints of Apparel Operations framework intersects directly: inventory truth (breakpoint 3) and reactive reporting (breakpoint 6) both degrade fast when the cost record is wrong.

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. This is the single most common WAC failure I see at go-live: the cost field in the system holds FOB only, and freight and duty are booked to a separate GL account that never touches the inventory valuation.

Receipt versus shipment 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. This breaks most often when the 3PL receives physical units a day or two before the brand’s operating system records the receipt, and outbound orders ship in that window against stale cost.

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 in the first place.

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 with each tool holding its own cost records produces unreliable reporting regardless of which method is selected. This is the structural problem Uphance was built to solve: one cost record per SKU, used by the order module, the warehouse module, and the reporting module without translation.

What this means for an apparel operations team

The WAC versus FIFO debate is real, but it is downstream of a bigger question: does your operating system maintain one trusted cost record per SKU, captured at receipt with full landed cost, and used consistently across every downstream module. If yes, the method choice becomes a finance preference shaped by your operating profile. If no, switching from WAC to FIFO will not fix the margin reporting because the underlying data is wrong before the method runs.

The operating profile guides the choice. Replenishment basics, stable freight, no tariff exposure: WAC is fine. Tariff-exposed sourcing, freight rate volatility, dramatic landed-cost swings between receipts: FIFO produces decision-useful reporting that WAC hides. Luxury or made-to-measure with per-unit cost variance: specific identification is the right answer regardless of how much overhead it adds.

The 1 to 5 point margin gap that shows up at month-end is rarely a method problem. It is almost always a data problem: FOB captured but not landed cost, receipts booked late, multiple systems each holding their own version of the cost record. Fixing the structural problem makes either WAC or FIFO report cleanly. Leaving the structural problem in place makes both methods produce numbers nobody trusts.