Case Study · Women's apparel catalog brand

From $39K to $580K in One Season: How a Wool Jacket Changed Everything

$580K
Revenue captured in year two
Client: Women's apparel catalog brand
Revenue: $60 million
Source: Chapter 2 — Proving the Method

The Beginning

In August 2020, a women's apparel catalog brand launched a wool trench coat in a color they called milky blue. Essentially a light blue jacket. The brand had never sold a traditional trench style before, so the opening buy was appropriately cautious: 300 units, roughly $45,000 in inventory investment, no comparable history to plan from.

The placement was unremarkable. No cover. No dedicated spread. Just another item in the August catalog, surrounded by dozens of others competing for the same customer attention.

Then something unexpected happened. Within days of the catalog dropping, the jacket started moving. Not gradually. It jumped into the top ten best-selling styles in the book despite not being projected anywhere near that. By the time the numbers settled, 291 of those 300 units had sold in 21 days. Ninety-seven percent sell-through. Thirty-nine thousand dollars in sales. In August, before the fall season had even really begun.

Any reasonable analysis would call that a successful test. The brand had proven the customer wanted a trench-style jacket. Next season, buy more. Move on. That is not what happened.

The Problem Nobody Was Looking For

In catalog retail, the best sales window comes when a catalog first drops into customers' homes. Buyers are engaged, they are actively browsing, and they are most likely to purchase what they see. This window is called Peak Week, and most catalog brands extend it by sending the same book out a second time two to three weeks after the first drop. Two waves of customer engagement, if you have inventory to fulfill both.

The wool jacket sold out before the second wave hit. The catalog was still in customers' hands. The jacket was still on the page. The website still had the product listed. But the inventory was gone, and every customer who arrived after day 21 found nothing to buy.

Michael tracked this through a daily reporting system he had built over years of retail consulting, one that captured on-hand inventory every single day rather than just periodically. This is a detail that sounds minor but matters enormously. Most reporting systems tell you what sold. His system told him exactly when a product stopped being available, down to the specific day. That distinction is the difference between knowing you had a good seller and knowing exactly how much demand you failed to capture.

What his analysis showed was not a good seller. It was a capped seller. The jacket had not stopped selling because customers lost interest. It stopped selling because there was nothing left to sell.

Building the Lost Sales Case

From the daily snapshot data, Michael calculated what the jacket should have done across the full August through December selling window if inventory had been available to support it. His projection landed at $192,000 in potential revenue. Against the $39,000 actually captured, that was $153,000 in lost sales. Approximately 1,200 units of unmet demand.

He also acknowledged, openly, that the number was conservative. Once the jacket sold out in late August, customers stopped visiting the product page because there was nothing to see. No inventory meant no active marketing support on the item. No marketing support meant declining traffic. Declining traffic meant the lost sales calculation was based on incomplete demand data. The real number of customers who would have purchased if the product had been available was higher than any tool could measure.

This is one of the most important concepts in retail inventory analysis. When a product sells out, it does not just stop generating revenue. It stops generating data. The demand signal goes quiet. And when you try to calculate what you missed, you are working with a partial picture almost by definition.

Despite that limitation, the $153,000 figure was defensible, well-documented, and grounded in actual selling velocity from the days when inventory existed. That was enough to bring to leadership.

What Leadership Did With It

Michael presented the analysis to the CEO and Head Merchant. He walked them through the data, the methodology, and what a larger, better-supported version of this jacket could do in the following year.

The conversation went differently than he expected. In his experience, these moments often produce resistance. Leadership pushes back on the numbers, asks to cut the projection in half, or approves a modest increase while calling it aggressive. This time was different. They did not push back. They saw what the data was showing and leaned into it.

Together they designed a three-colorway plan for the following year. The original milky blue would return. Two new colors would be added: pink and camel. Total buy: 5,000 units. The launch strategy was deliberate. Two colors would open in the August catalog. The third would be held for the October drop, creating a planned traffic event that would drive customers back to the product page and expose them to all three colors simultaneously.

In catalog retail, this approach compounds in a specific way. When October drops and features the new color, it drives visits to the product detail page. Once a customer is on that page, she sees all three colors. If the August colors still have solid inventory and size availability, she may buy two. At minimum, the October launch drives fresh traffic to a product that would otherwise be losing momentum six weeks into the season.

The total planned revenue for year two was $750,000. Against the $39,000 from the year before, that number felt aggressive even to Michael. He stood behind it because the methodology supported it.

The Results

The season played out as the analysis had predicted. Total units sold: 4,300. Sell-through: 86%. Revenue: $580,000. Year-over-year increase: 1,387 percent. In raw dollars, the brand captured an additional $541,000 in revenue from a single style that one year earlier had been a modest test buy with three hundred units.

The trench jacket category stayed in the product line permanently after that season. Over the following years it generated millions in cumulative sales. None of that existed before Michael identified the lost sales signal hiding inside a 97 percent sell-through number that everyone else had called a win.

What this means for your business

The wool jacket case is a straightforward illustration of why daily inventory tracking changes the nature of the analysis you can do. With daily snapshots, you know exactly when a product ran out, how many selling days remained, and what daily velocity looked like before inventory hit zero. Those three data points are what make a lost sales calculation credible enough to take to a CEO.