Capacity Booking: How Golf Bag Programs Reserve the Factory's Calendar

By the Custom Golf Bags Factory engineering team · Published September 22, 2026 · Updated September 22, 2026

Capacity Is the Real Currency

Buyers think in purchase orders; factories think in calendars. A golf bag factory's true inventory is not fabric or hardware — it is the finite number of line-weeks between Chinese New Year and the autumn shipping peak, and every week of it is spoken for or sellable exactly once. The buyer who understands this stops asking 'can you make my bags?' (the answer is always yes, eventually) and starts asking 'whose weeks are those?' — because the weeks, not the capability, are what runs out.

The scarcity has a shape, and the shape is the golf season. The Northern Hemisphere's floor sets cluster in February through April, which means production clusters in December through March, which means the line-weeks from mid-autumn to Chinese New Year are the most contested weeks in the category's year. A program that books its spring production in October is reserving at leisure; the same program calling in January is begging for cancellation scraps at premium rates. The buying calendar maps the selling side of this shape; capacity booking is the supply-side mirror of the same map.

The currency framing also explains the factory's behavior that buyers sometimes misread as unhelpfulness. When a factory asks for a deposit to hold dates, or declines to pencil a program in without a PO number, it is not being difficult — it is refusing to give away the only asset it cannot restock. Line-time given to a program that cancels is line-time that cannot be sold again at full value, and the factory's reservation terms are simply the price of that risk, stated honestly.

What a Production Slot Actually Is

A production slot is a reserved window of factory line-time — defined by a start week, a quantity, and a product family — against which the factory commits materials purchasing, line staffing, and a delivery date. Slots exist on a spectrum from a verbal pencil booking (worth little, evaporates under pressure) to a deposit-backed reservation with agreed terms (an asset the program can plan a season around).

The anatomy of a real slot has four components, and the booking conversation should produce all four in writing. The window: a start week and an end week, stated against the factory's calendar — with the standard 35-to-50-day production window for a custom golf bag order fitting inside it. The volume: a quantity range (a slot booked for 4,000 to 6,000 units, firmed to a number by a stated deadline) rather than a fiction of precision nine months out. The product family: which lines and skills the slot draws on — a staff-bag slot and a stand-bag slot are not interchangeable, because the sewing skills and the line balancing differ. And the terms: what each side owes if the other side moves.

The pencil-versus-reserved distinction deserves emphasis because it is where seasons are quietly lost. A pencil booking — 'we have noted your March window' — costs the factory nothing and protects the buyer not at all; when a bigger program's PO arrives with a deposit, the pencil entry moves. A reserved slot, backed by a deposit and a written confirmation, is a liability on the factory's books, and factories honor their liabilities for the same reason buyers honor theirs: the relationship is the business. The work of capacity booking is converting pencils into reservations, early, at the best terms the relationship supports.

Booking Backward From the Set Date

The booking chain runs backward from the only date that cannot move: the floor-set, the event, or the launch. The chain, link by link: the set date minus the receiving and allocation buffer (two weeks) gives the required dock date; the dock date minus the ocean transit and customs buffer (five to seven weeks for the standard FOB Xiamen sailing to a US warehouse, per the rhythm in the freight guide) gives the required ex-factory date; the ex-factory date minus the production window (35 to 50 days, quoted honestly with its range) gives the latest production start; and the production start minus the materials lead time the factory needs (fabric and hardware procurement, typically three to five weeks for stocked materials, longer for custom developments) gives the latest date the booking must be confirmed with specifications final. A mid-March floor set, chained backward, lands the booking decision in early autumn of the previous year.

Deposits and the Reservation Economics

The deposit is what converts a calendar conversation into a reservation, and its logic is mutual risk-sharing. The factory's risk: it holds line-time off the market and commits materials purchases against a program that might shrink or vanish. The buyer's risk: it commits cash months before goods exist, against a factory that might overbook. The deposit splits the difference — large enough that the factory can book the buyer's seriousness as revenue-adjacent, small enough that the buyer's working capital survives. In practice the reservation deposit often rides inside the standard T/T structure (the 30 percent production deposit of the 30/70 terms), with the slot confirmation letter stating that the deposit secures the window.

The negotiation levers, in order of usefulness: the multi-season commitment (a program that books spring and autumn together, or signs a rolling annual reservation, buys the factory's planning comfort and is rewarded with first-call on contested weeks), the early firm-up (offering to convert the quantity range to a firm number earlier than the deadline, in exchange for a deposit reduction), and the off-peak volunteer (a program willing to run its replenishment orders in the factory's quiet months — June through August for golf — is the customer factories remember when the contested weeks are allocated).

What deposits are not: they are not a penalty system, and programs should resist treating them as one. The deposit's purpose is alignment, not punishment — and the agreement language around it (the slot terms covered below) should state clearly what happens to the deposit in each scenario of cancellation or reduction, because the only bad deposit outcome is the undefined one.

The Peak Season Scramble

Peak season in golf bag manufacturing is not a metaphor — it is the twelve to sixteen weeks when the category's entire Northern Hemisphere spring production competes for the same lines. The scramble's physics: every program's backward chain lands on the same December-to-March production weeks; Chinese New Year removes two to four weeks from the middle of that window and adds a pre-holiday rush and a post-holiday restart ramp; and the factories' honest capacity — the lines times the weeks times a realistic efficiency — is simply smaller than the demand placed on it. Somebody books late and does not ship, every year. The scramble is the process that decides who.

The behaviors that win the scramble are unglamorous: book early (the September-October booking for spring production is the single highest-leverage date in the program's year), firm up honestly (a slot firmed at 5,000 units and shipped at 5,000 builds the credibility that gets next year's contested weeks; a slot firmed at 8,000 and shipped at 4,000 spends it), and stay flexible on the edges (a program that can accept a two-week earlier start, or split its order across two adjacent windows, gives the factory room to solve its jigsaw — and factories solve jigsaws in favor of flexible customers).

The scramble's losing behaviors, for completeness: the phantom booking (holding two factories' slots for the same order and dropping one — the industry is small, and the dropped factory remembers), the spec-freeze violation (changing the design after materials are purchased against the slot, then being surprised the window moved), and the assumption of abundance (planning the season as if the factory's calendar were infinite, then discovering in January that December was the plan).

Sharing Capacity Honestly

A factory's calendar is shared infrastructure: the same lines serve the program's orders and its competitors', and pretending otherwise produces bad planning. The honest conversation about sharing has three parts. First, the overlap question, asked directly: which weeks are historically your most contested, and which programs anchor them? The factory will not name names, but it will describe shape — and the shape is enough to know whether the program's ideal weeks are the factory's crowded ones. Second, the priority question: where does this program stand when contested weeks are allocated? The answer is earned, not granted — by forecast accuracy, by payment discipline, by years together — and the scorecard discipline works in both directions, because factories keep scorecards too.

Third, the growth question, asked before the answer is urgent: if this program doubles, where does the capacity come from? The good answers are concrete (a second line in the peak weeks, a sister line with transferable skills, the quiet-season pre-build of stable SKUs against forecast); the bad answers are soothing. A program growing faster than its factory's honest capacity is a program that will learn about dual sourcing whether it planned to or not — better to plan it.

The counterintuitive truth about sharing: a factory running at one hundred percent of theoretical capacity is a red flag, not a green one. Lines need slack for the rework, the machine failure, the rush order from the anchor customer. A factory at eighty-five percent utilization with the program's slots protected inside it is a healthier home than a factory at one hundred and five percent, whatever the enthusiasm of its promises.

The Slot Agreement Terms

The slot confirmation — whether a standalone letter or a section of the season's PO — earns its keep by defining five scenarios in advance. The window terms: start week and end week, the quantity range, and the firm-up deadline by which the range becomes a number. The specification terms: what 'specs final' means and by when (the tech pack version, the golden sample signed — the artifacts the manufacturing agreement already governs), and what happens to the window if specifications slip. The cancellation terms: the deposit's fate at each notice interval — cancelled twelve weeks out versus four weeks out are different events, and the terms should say so. The delay terms: whose risk absorbs a factory-side slip (the remedy ladder pre-priced, as the agreement guide prescribes) and a buyer-side slip (the window re-queued, not necessarily re-created). And the substitution terms: whether the factory may offer, and the buyer accept, an equivalent earlier or later window when the calendar shifts — the flexibility clause that solves most collisions before they cost anything.

The terms that matter most are the ones both sides hope never to read, and the drafting rule is the agreement guide's rule: the document is written by reasonable people in peacetime for use by stressed people in season. A slot confirmation that fits on one page, signed, is worth more than a ten-page framework nobody can find in February.

When Forecasts Miss the Booking

The forecast-to-slot mismatch is the discipline's routine test, and it arrives in two directions. The over-booking — the slot reserved for 6,000 units against a season now tracking to 4,000 — is the gentler problem: handled early, it is a gift to the relationship. The playbook: tell the factory the moment the sell-through data turns (the forecasting discipline produces the signal; the capacity discipline acts on it), release the excess window while it is still sellable (twelve weeks out, another program can use it; four weeks out, it is waste), and accept the agreed deposit terms on the released portion without haggling — the terms were the price of the reservation, paid gladly for the option value it carried all season.

The under-booking — the season tracking to 7,500 against a 6,000 slot — is the harder direction, and its playbook is sequenced: first, the honest ask (can the slot stretch — adjacent weeks, a second shift, a parallel line; factories can often find ten to twenty percent inside the calendar for a customer they want to keep), then the triage (which SKUs must make the set date and which can follow in a second window — the channel map usually dictates the priority), then the bridge (partial air freight for the units that make the difference between a set and a miss, priced against the margin math the freight guide lays out), and only then the market response (re-phasing the launch, managing the accounts with the truth early).

Both directions share one rule: the factory hears the miss from the program, early, with the data attached. The programs that get rescued in peak season are the ones whose misses were never surprises.

Losing a Slot and Recovering

Slots are lost three ways, and the recovery differs by cause. The self-inflicted loss — the spec freeze missed, the firm-up deadline passed, the deposit delayed until the window was resold — is recovered by humility and speed: the honest conversation about what remains (cancellation scraps, a compressed window at peak rates, a split across two smaller windows), the internal post-mortem that fixes the calendar process, and the bridge plan that protects the set date with the tools above. The factory-side loss — the line failure, the material delay, the anchor customer's emergency that consumed the window — is recovered through the slot agreement's delay terms: the pre-priced remedy ladder, the priority claim on the next available window, and, if the season is truly at risk, the activation of the second source the transition playbook keeps warm.

The third loss is the strategic one: the program that discovers its growth has outrun its slot allocation — the factory, rationing honestly, offers 5,000 units of window against a 9,000-unit plan. This is not a crisis; it is the signal to execute the capacity plan the sharing conversation should have produced: the second line, the sister factory, the quiet-season pre-build. Programs that read the signal early add capacity as a strategy; programs that read it late add it as an emergency, at emergency prices.

Whatever the cause, the recovery documentation matters: what was lost, why, what it cost, and what changed in the process. The capacity file that records losses honestly is the one that stops repeating them.

Capacity Across Multiple Programs

The buyer running several product lines — bags, headcovers, soft goods — or several brands faces the portfolio version of the discipline: the factory's calendar is one resource, and the programs draw on it jointly. The portfolio rules: book the portfolio, not the products (a single seasonal booking conversation covering all lines gets better aggregate windows than five separate conversations competing with each other), sequence by margin-at-risk (the SKU whose missed set date costs the most gets the safest window; the evergreen replenishment gets the flexible one), and use the portfolio as leverage (the program that brings the factory a balanced year — peak-season staff bags plus quiet-season headcovers and pouches — is booking capacity with the factory's own utilization problem as its ally).

The multi-factory version follows the same logic one level up. Programs with a primary and a warm second source should book deliberately across both: the primary carries the contested peak windows, the second source carries the overflow and the quiet-season runs that keep its lines familiar with the product. The second source that produces nothing for two years is not a second source; it is a name in a file, as the transition playbook's heartbeat order rule makes plain.

A Season Booked Ahead, Worked

A worked year from a mid-size program shipping roughly 18,000 bags annually, told as a calendar: in September, the season-planning week — the sell-through data from the current year, the retail partners' early reads, and next year's floor-set dates assembled into the draft plan. In October, the booking conversation with the factory: two slots reserved — a December-to-February window for 8,000 to 10,000 units (the spring set, the contested weeks, booked while they are still available) and a June-to-July window for 5,000 to 6,000 units (the autumn replenishment, deliberately placed in the factory's quiet season, which the factory's pricing quietly rewards). The reservation letter records the windows, the ranges, the firm-up deadlines (eight weeks before each window's start), and the deposit terms riding the standard 30/70 structure. In November, specifications locked for spring; the materials procurement starts inside the slot. In December, production begins — on the first week of the reserved window, because the booking was real. In February, the spring goods ship; in early March, they make the floor set. In April, the sell-through data says the season is tracking fifteen percent over plan; the program calls the factory in the same week, stretches the June slot by 1,500 units — available, because June is quiet — and the autumn replenishment arrives in August, whole. Total drama: zero. Total extra cost: the deposit interest and one phone call. The boring year is what capacity booking buys.

The counterfactual, told in one sentence: the same program booking its spring production in January finds the December-to-February windows gone, ships in April, misses the floor set by five weeks, spends the difference on air freight and apologies, and learns the discipline in the most expensive classroom available — the one this guide exists to make unnecessary.

The Calendar as a Relationship

Capacity booking ends, as every discipline in this library ends, at the relationship. The factory's calendar is allocated each year by people who remember: which programs booked early and shipped what they booked, which firms up honestly, which pays on the 30/70 rhythm without reminders, which releases excess windows while they still have value. The allocation of contested weeks is, in the end, a judgment call — and judgment calls go to the programs that have made themselves easy to plan around.

The long-game behaviors compound: the rolling annual reservation renewed each autumn, the quiet-season orders volunteered when the factory's lines are light, the forecast misses reported early with data attached, the slot terms honored without re-negotiation when the season turns. None of them appears on a purchase order, and all of them appear in the factory's allocation meeting. The program that treats the calendar as a relationship discovers, year by year, that the contested weeks stop being contested — because the factory saved them. That is the finished form of capacity booking: not a transaction about line-time, but a standing arrangement between two businesses that plan together.