Peak Season Failures Are Planning Failures
The story brands tell themselves after a bad peak season usually involves demand surprises: "We didn't expect that much traffic," "The viral moment came at the worst time," "Wholesale pulled forward orders we didn't anticipate." Some of those factors are real. Most of the time, the actual root cause is earlier and more structural: the planning window started too late, the forecast was built at the wrong level of granularity, or the inventory commitments were made without an adequately stress-tested demand scenario.
Peak season inventory failures almost never happen because demand was genuinely unpredictable. They happen because the planning work that should have been done in weeks 12–8 before peak didn't get done until weeks 4–2. By then, PO lead times have closed, DC space is committed, and the team is forced into an improvised response rather than an executed plan.
The 12-week preparation framework isn't a guarantee of a perfect peak — supply chains have real uncertainties that no amount of planning eliminates. But it compresses the category of "fixable planning failures" significantly.
Weeks 12–10: Build the Demand Foundation
The first phase of peak preparation is building the demand foundation: establishing what your baseline forecast is for the peak period and identifying where it's most uncertain.
This starts with historical decomposition. For each major SKU group, break down prior-year peak performance into its components: base demand (what you'd expect without a peak uplift), seasonal index (the historical ratio of peak-period demand to average weekly demand), channel mix during peak (DTC vs. wholesale vs. store tends to shift in peak periods — DTC typically increases as a share due to holiday gifting), and any known uplift drivers (planned promotions, confirmed editorial features, influencer partnerships).
The seasonal index calculation requires at least two prior peak seasons of data to be meaningful. For brands in their second or third year of operation, this is often the first time they're running this analysis with real historical context. The result is a range — not a single number — that captures the variability in peak uplift observed in prior years.
By end of week 10, you should have: a SKU-level peak demand forecast with low/base/high scenarios, a channel-split version of that forecast, and an explicit identification of the three to five SKUs where the forecast uncertainty is highest (these will get the most attention in subsequent weeks).
Weeks 10–8: PO Commitments and Lead Time Reconciliation
This window is typically the last opportunity to make meaningful PO adjustments for peak season inventory, given that most international suppliers work on 60–90 day lead times and domestic suppliers on 30–45 days. If peak is in early December, the PO commitment window for international supply is typically closing in September.
The critical task in weeks 10–8 is reconciling your demand forecast against your current inventory commitments. For each major SKU:
- What is the current on-hand position?
- What POs are already placed and what is their expected delivery timing?
- What is the gap between total committed inventory (on-hand + inbound) and peak demand forecast at the base and high scenarios?
- Is the gap fillable within the available PO window?
SKUs with significant gaps against the base scenario should get incremental POs placed immediately. SKUs where the high scenario implies potential stockout but the base scenario is covered should get a contingency conversation with the supplier: can they accommodate an incremental order of X units if needed within Y weeks? Having that conversation in week 9 is very different from having it in week 2 when the answer is almost certainly no.
Weeks 8–6: DC Capacity and Channel Pre-allocation
As peak inventory starts arriving at the DC, two operational preparations become critical: DC capacity management and channel pre-allocation.
DC capacity for peak can be surprisingly constraining. Brands that run lean DC operations the rest of the year often find that peak inventory receipts — arriving across multiple POs over a compressed 4–6 week window — overwhelm their normal receiving and put-away capacity. The result is delayed DC processing that pushes inventory into the available-to-ship position later than planned, which in turn delays store and DTC availability at exactly the time when demand is accelerating.
Channel pre-allocation means establishing ahead of time how peak inventory will be distributed across channels. Rather than making this decision reactively as each PO is received, the pre-allocation plan specifies: for each major SKU, what percentage goes to wholesale (if applicable), what goes to DTC forward stock, and what goes into the store replenishment pool. The plan should be built against your channel demand forecast from the week 12–10 phase and revised as forecasts are updated.
Weeks 6–4: Demand Signal Monitoring and Forecast Updates
Six weeks before peak, early demand signals start to become available. Pre-orders (if you run them), early-season sell-through in stores, initial wholesale reorder velocity, and social/marketing engagement on peak-season campaigns all provide leading indicators that should feed a forecast revision.
The relevant question isn't "is our forecast right?" — no forecast is precisely right. The question is: "Are early signals pointing toward the high scenario, the base scenario, or the low scenario?" And: "For which specific SKUs is the signal most divergent from our base forecast?"
A brand that launched pre-orders for a gift set on October 15 for a holiday peak can look at pre-order velocity by November 1 and draw meaningful conclusions about whether their base demand forecast is tracking. A brand that doesn't run pre-orders but does have wholesale POS data from early November store selling can check whether their wholesale sell-through rate is running above or below the prior year's pace at the same point in the season.
These signals should feed a formal forecast revision — not a wholesale rebuild, but an adjustment to the base scenario and an update to which scenario (base vs. high vs. low) appears most likely. The PO window for last-minute incremental orders may be closing, but channel pre-allocation can still be adjusted, store replenishment priorities can be updated, and DC reorder buffers can be recalibrated.
Weeks 4–2: Execution Mode
By week four, the planning decisions are largely made. What remains is execution: ensuring inventory is flowing into the right channels on the right timeline, monitoring real-time sell-through against forecast, and making allocation adjustments as actual demand deviates from forecast.
The most important metric to track in this window is daily sell-through rate against your peak forecast's daily demand curve. If you modeled that a given SKU would sell 45 units/day in the first two weeks of December and it's actually tracking at 62 units/day, you need to be recalculating your remaining WOS at each location and adjusting replenishment priorities immediately — not at the end of the week when the stockout may already have occurred.
The Scenario That Breaks Most Peak Plans
The scenario that breaks otherwise well-prepared peak plans is the unexpected demand concentration: a specific SKU or small group of SKUs dramatically outperforms while the balance of the catalog tracks to forecast. The total peak demand looks roughly right in aggregate, but the mix is wrong — you oversold five SKUs and had excess inventory in twenty others.
We're not saying this is avoidable in all cases — true demand surprises happen, especially when an item goes viral or gets unexpected media coverage. But many "demand concentration surprises" aren't actually surprises. They're scenarios where early signals were available but weren't acted on because the planning team was managing the catalog at the aggregate level rather than the SKU level.
The brands that respond best to peak season are the ones watching SKU-level signals in real time, with the pre-established allocation rules and supply chain relationships to act on those signals quickly. The 12-week framework creates the conditions for that responsiveness. It doesn't eliminate uncertainty — it replaces reactive panic with prepared flexibility.
