Working prototype · public seasonality + lead-time context · peak-season commit decision

The order you place months early, against a forecast you cannot trust yet.

Toys sell in a short holiday window but source months ahead from Asia, so the buy quantity is committed long before demand is known. Peak Commit takes one seasonal SKU, a long lead time, and a forecast-error band, and shows the real tradeoff a planner lives in: order light and stock out, order heavy and mark down.

This is the planner's problem, not the CFO's: forecast accuracy, lead time, and the commit quantity are your levers, set in the S&OP room quarters ahead of the print. Pick a SKU profile: Peak Commit runs a synthetic Q4 demand curve through the lead time, scores the commit risk 1 to 99, and lands the recommended order so the verdict is on screen before you touch a slider. The one slider that matters, the commit quantity, sits right under the verdict.

01 · Commit a seasonal SKU

One click lands the recommended order.

Each preset loads a seasonal toy SKU: a Q4 demand peak, the Asia lead time that forces an early commit, and how wide the forecast could be wrong. The verdict shows the recommended commit and the expected cost of being wrong. The commit slider is the one control that matters; the rest are optional.

One click loads a SKU and lands the recommended commit. Drag the commit slider to feel the tradeoff.

Seasonal SKU · commit risk

...

...

...

...

...

Planner moves at this band

    The cost of being wrong

    At this commit, where the expected cost lands

    Demand vs commit

    Synthetic Q4 demand band and the units you committed

    demand band (forecast error) sold from commit excess to mark down

    Tune the SKU optional · sliders
    What this is and is not. The simulator reports the expected cost of the commit decision, split into lost-margin stockouts and markdown on excess, scored 1 to 99. It uses a classic newsvendor balance (the optimal commit sets the chance of selling the last unit equal to the cost ratio) so the recommended order is a known, defensible result, not a guess. The demand curve, the lead time, and the cost inputs are synthetic and tuned to the structure of a seasonal toy SKU, never to Mattel's real demand. The production extension reads the real demand history, lead times, and unit economics from the planning system.

    02 · Sources & method

    The structure is real, the SKU is synthetic.