The Question Behind Every Purchase Order
Order quantity = forecast demand for the cover window + pipeline stock for the 35-50 day lead time + safety stock set by your error history — staged through a commit ladder (fabric first, cut in tranches) so the MOQ 200 minimum never forces an all-at-once bet.
The question sounds like 'how many should we buy' and is actually three questions wearing one coat: how many will sell (the forecast — a statement about the market), how many must we commit to at once (the structure — a statement about the supply chain and its MOQ 200 floor), and how wrong can we afford to be in each direction (the asymmetry — a statement about the program's economics, where the stockout cost and the overstock cost are almost never equal). Programs that ask only the first question produce forecasts; programs that ask all three produce buy plans. The difference shows up in February, when the forecast-only program is either dark on its best SKU or drowning in its worst, and the buy-plan program is mid-ladder with options still open.
The comforting fact the discipline rests on: the number will be wrong, and that is fine. Every forecast in this category is an estimate under genuine uncertainty — the goal is never accuracy in the fortune-teller sense but error that is bounded, measured and biased toward the cheaper side. A forecast process that lands within a predictable band of actuals, structured so the supply chain can flex the final quantity late, beats a heroic point prediction that staked the whole season on being right. The sections below build that process in order: situation first, then signals, then base rates, then the quantity math, then the commitment structure that keeps the bet small as long as possible.
The Three Forecasting Situations
The first sorting act, because the method follows the data: the new product (no sales history — the forecast must be borrowed from reference classes and early signals, and the buy must be small enough to survive being wrong), the running style (one or two seasons of history — enough for a curve and a bias correction, not enough for confidence), and the proven reorder (multiple seasons, stable channels, a reorder rhythm that can be read like a tide table — the situation where the forecast earns real precision and the discipline shifts to the consistency side). Most portfolio mistakes come from running the wrong situation's method: the new SKU forecast with reorder confidence, or the proven seller hand-waved because the meeting ran long.
The situation table the planning meeting should start with — the honest inventory of what each case actually knows:
The table's practical edge: the situation also sets the commitment structure. New products belong at the bottom of the commit ladder with options preserved; proven reorders can commit fabric and capacity early because the demand risk has already been paid down by history. Confusing the two — committing a new product like a proven one because the team loved the samples — is the single most expensive forecasting error in the category, and it is a process failure, not a market surprise.
| Situation | Signals available | Method that fits |
|---|---|---|
| New product, no history | Reference SKUs, pre-orders, inquiry flow, comparable programs | Base-rate anchor plus early-signal read, bought small |
| Running style, 1-2 seasons | Sell-through curve, channel reorder rhythm, coded returns | Curve projection with bias correction from last season |
| Proven reorder, 3+ seasons | Multi-season history, reorder intervals, account velocity | Interval-based planning with a full commit ladder |
| Event-driven demand | Calendar, signed bookings, gift deadlines | Date-certain planning — the event does not move |
The Signals That Actually Predict
The predictive signals, ranked by how honestly they arrive: sell-through (the weekly rate at which stock converts to sales — the only signal that is money already changing hands, readable from the first fortnight and more predictive of the season's shape than any pre-season opinion), inquiry and quote flow (the leading indicator the B2B program owns natively — the questions accounts ask in January describing the season they will buy in March, which is why the customer conversation is a forecasting instrument and not just a research one), and pre-orders (the only signal with a signature on it — discounted or committed early orders that convert opinion into obligation). Each beats the expert hunch, including the founder's, and the planning meeting that starts with these three signals ends with better numbers than the one that starts with enthusiasm.
The secondary layer, useful for shape rather than volume: the event calendar (tournaments, corporate outings, gift deadlines — date-certain demand that does not move with the weather, readable a season ahead from the corporate and tournament pipelines), the channel feedback (the distributor and account reads — directionally honest, systematically optimistic, best used as a ceiling rather than a point), and the category weather (participation trends, retail traffic, the macro currents that lift or sink every boat — useful for the annual plan, too blunt for the SKU). The discipline: volume comes from the primary signals, shape from the secondary, and the two never trade places.
The Base-Rate Discipline
The anchor that keeps every forecast honest: before any story about why this SKU will fly, write down what SKUs like it have actually done — the reference class of comparable products in the program's own history first (the stand bag launched last year at the same price band into the same channel), the category's patterns second (the shape of a golf softgoods launch — the early spike on novelty, the settling into velocity, the season curve), and only then the adjustment for what is genuinely different this time. The base rate is the forecast; the story is a correction to it, capped in size and required to name its evidence. The order matters because the untrained process runs it backward — story first, anchor never — and the backward process is how programs buy three seasons of a SKU the market wanted one season of.
The failure mode the discipline exists to catch has a name in every planning meeting: 'this time is different.' Sometimes it is — the drop model genuinely runs different economics, the celebrity collaboration genuinely breaks the reference class — but the honest count across a portfolio is that the base rate is right far more often than the exception, and the correction for the claimed exception should carry a burden of proof proportional to its size. The working rule: adjustments up to a modest band around the base rate need a reason; adjustments beyond it need evidence; and the biggest adjustment in the meeting gets the smallest quantity commitment until the first sell-through data arrives. The base rate is not pessimism — it is the price of admission the market charges every story.
From Forecast to Buy Quantity
The conversion arithmetic, run per SKU: the cycle stock (the forecast demand for the cover window — the weeks until the next realistic replenishment lands, not until the season ends), plus the pipeline stock (the demand that will occur while the replenishment is being made and shipped — the 35-50 day production window plus ocean transit means a reorder decision feeds demand roughly two to three months out, and the forecast must cover that shadow), plus the safety stock (the buffer the next section sizes honestly), minus the stock on hand and on order. The output is the buy quantity before constraints; then the constraints bite — the MOQ 200 floor per spec, the case-pack rounding, the fabric-dye lot that wants a minimum of its own.
The constraint handling is where the plan becomes honest: when the computed quantity falls under the MOQ floor, the answer is not to round up blindly — it is a go or no-go decision made with eyes open (the SKU that cannot justify its minimum gets redesigned, bundled, or cut, and the annual review is where that conversation recurs), and when the floor forces buying beyond the cover window, the excess is acknowledged as a deliberate position with a markdown plan, not smuggled into the forecast as optimism. The quantity table summarizes the components:
The worked arithmetic from a mid-band program: a running stand-bag SKU forecasting 90 units a month, on a quarterly replenishment rhythm — cycle stock 270, pipeline stock 210 (70 days of demand across production and transit), safety stock 60, on-hand 140 — buy quantity 400, which clears the MOQ floor honestly and rounds to the case pack. The number on the PO is 400; the forecast was 90 a month; the difference between the two numbers is the entire content of this section.
| Quantity component | What it covers | Sizing rule |
|---|---|---|
| Cycle stock | Demand between replenishment landings | Forecast units for the cover window |
| Pipeline stock | Demand during production and transit | One full lead-time of demand (35-50 days plus freight) |
| Safety stock | Forecast error and delay | Set by service target and error history, not by feel |
| MOQ floor | The factory minimum — 200 pieces per spec | Under the floor is a go or no-go decision, not a round-up |
| Case-pack rounding | Carton multiples the line packs | Round to the pack, never to the wish |
The Commit Ladder
The structure that lets a program be wrong cheaply: instead of committing the full season's quantity at the full season's uncertainty, the buy is staged down a ladder of commitments, each rung smaller and later than the last. The fabric commitment first (the material bought for the season's full plan — the cheapest, most flexible commitment, converting to any colorway the line allows), the capacity reservation second (the production window booked with the factory — the scheduling asset that costs little to hold and much to find late), the first cut third (the initial tranche at the MOQ-efficient minimum, released to market as the live test), and the replenishment tranches last (cut against actual sell-through — the largest dollars committed at the smallest uncertainty, when the curve has declared itself). The ladder's logic is the whole forecasting philosophy in one structure: push the big money as far down the uncertainty curve as the supply chain allows.
The factory conversation the ladder requires, which is a feature rather than a friction: the season plan shared early (the forecast, the ladder structure, the decision dates — the factory that sees the plan can hold the fabric and the capacity that make the ladder possible, which is why the OEM relationship is a planning asset and not just a production one), the tranche mechanics agreed (the re-cut minimums, the dye-lot matching discipline, the lead time per tranche — the color consistency across tranches being a specification question, answered before the season rather than during it), and the honest floor (the ladder cannot go below the MOQ per cut — the structure that flexes quantity, not below physics). Programs that run the ladder report the same season's forecast error costing a fraction of what it cost before — same market, same uncertainty, different structure.
Safety Stock Without the Guilt
The buffer, de-moralized: safety stock is not timidity priced in units — it is the rational purchase of availability, sized by two numbers the program owns. The first is the error history (how wrong the forecasts actually run, measured as the spread of past forecast-versus-actual — the program that has never measured its error is guessing its buffer, and the first season of measurement usually halves the argument about how much to hold), and the second is the service target (the availability the channel strategy requires — the program supplying retail accounts on reorder rhythms needs higher availability than the program selling one-and-done seasonal buys, because the stockout cost differs, which the understock section prices). Higher error or higher service target, larger buffer; the formula is boring and the boring is the point.
The disciplines that keep the buffer honest: it is sized per SKU (the volatile new colorway and the four-year black stand bag do not share a buffer percentage — their error histories differ by multiples), it is reviewed on the same calendar as the forecast (the buffer that is never revisited becomes permanent inventory, and permanent inventory is the overstock section's raw material), and it is visibly labeled in the stock report (the buffer separated from the cycle stock — because the day the buffer is silently treated as sellable stock is the day the service level quietly becomes a lie). The guilt-free frame: a buffer sized by error history and service target is a calculated cost of doing business; a buffer sized by anxiety is a warehouse bill with a rationale attached.
The Overstock Honesty
The cost of buying too much, counted in full because it arrives in installments: the carrying cost (storage, insurance, capital and handling — the category's running rate that compounds quietly at roughly two points per month of held inventory when every leg is counted), the markdown cost (the exit price of surplus softgoods through the channels the wind-down paths map — the seasonal product exiting at thirty to fifty cents on the planned dollar when the season turns), and the opportunity cost (the capital frozen in the wrong SKU being the capital not spent on the right one — the replenishment not placed, the new colorway not launched, the cash cycle lengthened by exactly the months the surplus sits). Summed honestly, a unit overbought for a full season commonly costs the program its entire planned margin — which is why the overbuy is the expensive error direction for most softgoods portfolios.
The prevention that actually works, since exhortation does not: the buy plan reviewed against the base rate before release (the section-four discipline catching the story-driven overbuy at the only moment it is free), the ladder structure capping the first cut (the new SKU's initial tranche sized to survive total failure — the optimism priced at the tranche level where it belongs), and the surplus response planned in advance (the markdown ladder and channel sequence written before the season — the program that decides its exit prices in advance exits at them, and the program that improvises exits at the market's prices). The honest summary: overstock is a forecasting error compounding at two points a month, and the cheapest point of intervention is the signature on the PO.
The Understock Math
The other error direction, priced with equal honesty because meetings chronically underprice it: the visible cost is the lost margin on the unsold units (real, and usually overstated in the meeting — it is the cost everyone sees), and the invisible costs are the ones that compound. The channel cost: the account that reorders and hears 'six weeks' learns a lesson about the program's reliability, and the lesson is priced into every future order (the reorder rhythm broken once rarely fully recovers — the understock taxing next season's forecast, not just this one's). The demand-destruction cost: the customer who finds the SKU dark does not wait — the substitution happens in the moment, and a share of the demand never returns even when stock does. The data cost: the stockout truncates the sell-through curve exactly where it was most informative — the program learns it bought too little but not how much too little, and next season's forecast inherits the blindness.
The asymmetry verdict the two sections together deliver: for most B2B softgoods programs the overstock is the more expensive steady-state error (its costs compound monthly and certainly), but the understock is the more expensive strategic error at the moments that matter (the hero SKU, the new account's first order, the season that establishes the reorder rhythm). The practical resolution: bias the buffer toward availability on the SKUs and moments where the channel cost concentrates (the proven sellers, the opening orders, the event-dated demand that cannot wait), and bias the tranche structure toward caution everywhere else (the new, the speculative, the story-driven). The two error costs are both real; the craft is knowing which one you can afford, per SKU, per moment.
The Season's Buying Rhythm
The calendar the whole discipline hangs on, worked backward from the market's fixed points: the retail season opens when it opens (the spring floor-set and the gift quarter being the two immovable dates in most Northern Hemisphere programs), the goods must land with receiving and allocation time in hand (the warehouse needing its weeks), the ocean leg needs its month-plus, and the production window needs its 35-50 days — the chain of immovable durations placing the production commitment in a window the calendar, not the courage, determines. The pre-season booking exists because this arithmetic leaves no room for the forecast to be late: the fabric and capacity rungs of the ladder fall due before the season's first sell-through data exists, which is exactly why the base rate and the signals carry so much weight in the pre-season number.
The in-season rhythm that runs behind the pre-season commitment: the replenishment windows (the tranche decisions scheduled against the sell-through readings — the first read at week two or three carrying real signal, the second at week six carrying the season's shape, the last call computed from the lead time so the final tranche lands before the season closes), the exception lane (the event-dated demand from the signals section running on its own earlier clock — the tournament and corporate calendars booking their production slots a full cycle ahead, because the event does not move and the buffer cannot help), and the honest late-season rule (the replenishment that cannot land with enough selling weeks left is declined — the late tranche that arrives into a closing season being next year's overstock wearing this year's optimism). The rhythm is unforgiving; that is what makes it worth writing down.
A First-Year Forecast, Worked
The method end to end, from a composite first-year program launching three SKUs: a core stand bag, a cart bag, and a statement colorway. The base rates built from reference classes (the stand bag anchored on the category's dominant use-case — the program's research and the channel's reads converging on a modest first-year velocity; the cart bag at a fraction of it; the colorway explicitly labeled a story forecast with a capped adjustment), the signals priced in (the pre-order window offered to the first twenty accounts converting 14 of them — the only signature-grade signal the first year gets, and it landed inside the base-rate band, which is what confirmation looks like), and the quantities computed per the fifth section: stand bag at MOQ 200 (the computed need coming in just under the floor — the go decision made with the excess acknowledged as launch stock), cart bag at 200 against a softer need (the floor forcing the position — flagged for the review habit), colorway declined for season one (its story forecast never cleared its evidence bar).
The season's verdict and the learning ledger: the stand bag sold through 78 percent by season end (forecast within its band — the tranche two declined by the ladder when the curve said no), the cart bag reached 54 percent (the floor-forced position confirmed as the season's planned markdown — exited through the pre-written channel sequence at 61 cents on the planned dollar), and the colorway's absence became the year's best decision (the market's actual color reads, harvested from the season's customer signal, reshaping it for a season-two launch on evidence instead of story). The first-year numbers that mattered most were not the sales — they were the error measurements: the program exited year one knowing its forecasts run optimistic by a measurable band on story-driven SKUs and near-true on reference-class ones, which is the calibration every subsequent season is built on.
The Forecast Review Habit
The closing discipline, because a forecasting process without measurement is astrology with spreadsheets: every forecast recorded (the number, the date, the signals behind it — written down before the season, not reconstructed after), every actual read against it (the sell-through curve, the tranche decisions, the stockout and surplus events — the season's ledger closed honestly), and the error analyzed for structure (the consistent optimism on new products, the consistent pessimism on reorders, the channel that always reads high — the biases that are stable enough to correct being the only kind worth having). The output is the calibration table: the program's own adjustment factors, derived from its own history, applied to next season's stories.
The habit's compounding, which is the real product: season one buys the error measurement, season two buys the first corrections, and by season three the program owns something its competitors cannot copy — a forecasting process tuned to its own channels, its own category position and its own biases, with the cash plan, the ladder structure and the factory relationship all running on numbers it trusts. The forecast will still be wrong; it will be wrong within a known band, in the cheaper direction, with tranches still open. That is the entire ambition of the math behind the buy — and in a category where the number on the PO carries the whole business, it is enough.
Frequently Asked Questions
How do I forecast demand for a brand-new golf bag?
Borrow before you believe: anchor on reference SKUs and category launch curves (the base rate), add pre-orders and inquiry flow as evidence, cap the story adjustment, and buy small — a first tranche sized to survive total failure, with tranches staged against real sell-through.
What data do I need to forecast golf bag sales?
Start with what money already proves: weekly sell-through by SKU and channel, reorder intervals per account, coded returns, and signed pre-orders. Add the event calendar and inquiry flow for shape. Channel opinions are ceilings, not points — use them last.
How do I calculate the order quantity for a custom golf bag?
Cycle stock (forecast for the cover window) + pipeline stock (demand during the 35-50 day production window plus transit) + safety stock (from your error history and service target), minus stock on hand — then apply the MOQ 200 floor and case-pack rounding honestly.
How does the 35-50 day production lead time change my plan?
It means every reorder decision feeds demand two to three months out — your forecast must cover that shadow. Stage commitments down a ladder (fabric, capacity, first cut, tranches) so the largest dollars commit at the smallest uncertainty, and decline tranches that cannot land with selling weeks left.
What is a commit ladder in buying?
A staged commitment structure: buy the season's fabric first (cheapest, most flexible), reserve production capacity, cut an initial tranche at the MOQ-efficient minimum, then cut replenishment tranches against actual sell-through. It converts one big bet into a sequence of small ones.
How much safety stock should a golf bag program hold?
Sized by two numbers you own: your measured forecast error and the availability your channel strategy requires. Retail-account programs need more than one-and-done seasonal sellers. Size it per SKU, label it visibly, and review it with every forecast cycle.
What does overstock really cost?
Counted fully: roughly two points per month in carrying cost, plus markdown exits at 30-50 cents on the planned dollar for seasonal goods, plus the frozen capital that did not fund the right SKU. A unit overbought for a full season commonly costs its entire planned margin.
What does a stockout really cost?
More than the lost margin: the account whose reorder hears 'six weeks' prices your reliability into every future order, the walk-away demand never fully returns, and the truncated sell-through curve blinds next season's forecast exactly where it was most informative.
What if my forecast is below the MOQ of 200 pieces?
That is a go or no-go decision, not a rounding exercise: redesign, bundle, or cut the SKU — or take the 200 with the excess acknowledged as a deliberate position with a pre-written markdown plan. Never smuggle the difference into the forecast as optimism.
How often should I re-forecast during the season?
On a schedule tied to signal: first sell-through read at week two or three, shape confirmation around week six, and each tranche decision recomputed from the lead time. Between reads, hold the plan — reacting to single weeks destroys more value than it saves.
What is a good forecast error for a softgoods program?
One that is measured, bounded and biased to the cheaper side. Reference-class SKUs should land near true after a few seasons; new products will miss wider — which is why they are bought small. The unmeasured error is the only disqualifying one.
Should I share my forecast with the factory?
Yes — it is a planning asset. The factory that sees your season plan and ladder structure can hold fabric and capacity for your tranches, quote dye-lot consistency across cuts, and flag material risks early. Shared plans are what make the commit ladder physically possible.