What the Annual Review Actually Decides
The annual line review makes three structural decisions for every SKU: continue as is, refresh (new colorway, hardware or configuration on the same chassis), or retire with a wind-down plan. A fourth, invisible decision — doing nothing — is the expensive default the review exists to replace.
The three decisions, stated as the outputs they are: the continue decision (the SKU that earns its slot again — the reorder placed on the existing specification, the production window booked, the shelf kept), the refresh decision (the chassis that survives but the surface that must change — the colorway rotated, the hardware upgraded, the configuration revised against the field evidence), and the retire decision (the SKU whose evidence says the slot belongs to something else — the wind-down planned, the capital released, the space handed to the next bet). Each decision has an owner, a date and a follow-through; the review that ends with 'keep everything for now' has made the fourth decision, which is the most expensive one on the menu.
The review's place in the calendar of disciplines, kept distinct from the monthly operations: the monthly rhythm manages the inventory water level (the sell-through rates, the storage costs, the reorder triggers — the operational corrections that keep the season running), while the annual review manages the portfolio architecture (which bets exist at all — the structural question the monthly meeting is too close to the fire to ask). The two feed each other in one direction only: the monthly evidence flows upward into the annual decision, and the annual decision resets what the monthly rhythm is allowed to do. Programs that confuse the two either hold eternal reviews that decide nothing, or run perpetual operations on a line architecture nobody ever chose.
The Data That Drives the Cut
The evidence pack, assembled before the meeting and not during it: the sell-through series (each SKU's units moved as a share of units available — by month and by channel, because the dealer channel's numbers and the direct numbers tell different stories), the margin contribution (each SKU's revenue minus its true landed cost from the cost model — the contribution dollars, not the contribution percentage, because the percentage flatters the low-volume hero), the quality record (each SKU's claim rate and its classes — the SKU whose zipper fails at three times the line average is a decision waiting), and the inventory age (each SKU's stock by aging bucket — the capital frozen in the 180-plus-day column that the review must price honestly).
The data hygiene that makes the evidence trustworthy: the attribution discipline (the SKU counted in the channel that sold it — the corporate order that consumed 200 units of a retail SKU counted as the program sale it was, not as retail velocity), the return-window honesty (the quarter with the holiday returns normalized, not deleted — the markdown months read with their context), and the comparability rule (each SKU measured against its own category peers — the travel cover judged against covers, not against the stand bag it is sold beside; the cross-category comparison that corrupts every decision it touches).
SKU Performance Bands
The review's sorting layer, run before any individual decision: the core engine (the two to five SKUs carrying the line — the anchor chassis in its proven colorways, the volume and the margin doing most of the work; the SKUs whose disruption is the line's largest risk), the steady contributors (the middle band — profitable, reliable, unremarkable; the band that funds the portfolio's experiments and gets the least meeting time because it rarely misbehaves), the long tail (the small-volume SKUs kept for strategic reasons — the price-tier completer, the channel's required token, the halo that justifies the range; each one must carry its strategic reason in writing or it is a candidate, not a fixture), and the drag (the bottom band — the SKUs whose contribution and trajectory no story rescues; the review's raw material).
The bands' honesty rules, because banding is where reviews go soft: the quantity discipline (the bands sized by behavior, not by quota — a healthy line does not guarantee an even distribution, and forcing four bands of ten from a forty-SKU line invents drag that does not exist), the movement rule (a SKU's band re-earned every year — last year's engine can be this year's contributor, and the drop SKU that converted its audience deserves promotion out of the tail), and the table below as the working frame the meeting actually uses.
| Band | Share of volume (typical) | Decision posture |
|---|---|---|
| Core engine | 50-70% of units | Protect, reorder, improve incrementally |
| Steady contributors | 20-40% | Continue; refresh surface on schedule |
| Long tail | 5-15% | Strategic justification in writing, or cut |
| Drag | 0-10% | Retire with a wind-down plan |
The Kill Criteria
The retirement triggers, written down before the review starts so the meeting applies rather than invents: the velocity trigger (two consecutive seasons below the line's minimum sell-through threshold — the number set from the channel's economics, not from hope), the margin trigger (contribution dollars below the slot's opportunity cost — the capital the SKU parks weighed against what a replacement SKU would do with it), the quality trigger (a claim rate that the quality record cannot attribute to one bad batch), and the strategy trigger (the SKU that drifted from the line's positioning — the direction the brand has moved away from, still occupying a slot and a price point).
The psychological traps that protect dying SKUs, named so the meeting can catch them in real time: the sunk-cost romance (the development spend, the sample rounds and the photography already paid — costs that exist whatever the decision, and therefore belong in no decision), the founder's favorite (the SKU with emotional sponsorship outranking evidence — the attachment priced honestly: what the favorite costs the line per year, stated in the meeting as a number), and the one-good-quarter defense (the recent spike cited as a trend — the spike tested against its cause: a one-off program order is an event, not a recovery, and the criteria written in advance are the only referee that survives contact with advocacy).
The Refresh Path
The middle decision the weak reviews skip: the refresh (the SKU whose chassis earns its slot but whose surface does not — the colorway that has dated, the branding that predates the current identity, the configuration that the field trials and the returns data have corrected), held distinct from both continuation and retirement: the refresh keeps the engineered core (the pattern, the construction, the build that the reorder data validates) while replacing the market-facing layer (the colors, the trims, the feature emphasis — the parts the customer actually sees changing), and it carries its own economics: a fraction of new-product development cost, most of the new-product marketing effect.
The refresh's disciplines: the specification hygiene (the changes made through the version-control protocol — the refreshed SKU getting its new revision documented, because the quiet refresh is the specification drift that arrives as a dispute), the continuity test (the customer who loved the old SKU recognizing its successor — the refresh that alienates the core buyer having traded loyalty for novelty, which is the trade that only the sell-through data can call), and the calendar fit (the refresh timed to the season's production window — the surface changes costing weeks, not months, but still owning a slot on the factory calendar the review must book).
New Product Slotting
The review's forward half, run against the space the cuts create: the vacancy map (the retirements and refreshes read as openings — the price points left uncovered, the use cases left unserved, the channels left with a story that no longer closes), the admission criteria (the new SKU facing the same evidence standards the old ones failed — its concept validated against the teardown intelligence and the trend read, its unit economics modeled on the MOQ and pricing reality, its slot justified before its design brief is written), and the portfolio pacing (the new entries sequenced — the launch calendar's carrying capacity respected, because three simultaneous launches in a small program are three underfed launches).
The discipline that keeps new products honest where old ones were not: the graduation rule (the new SKU launching with its review criteria attached — the first-year velocity target, the quality bar, the date it must earn its band; the probation made explicit so next year's review has a baseline instead of a debate), and the experiment framing (the genuinely uncertain concepts run as limited drops or small first runs — the low-MOQ structures and the rush capability priced as option premiums on information, which is exactly what a cautious first order buys).
Inventory Wind-Down Paths
The retire decision is only half made until its stock has a route: the ladder of exits, climbed in order of price protection — the primary channel first (the retiring SKU sold through its normal shelves at a planned markdown cadence — the markdown ladder run early, while the season still has traffic, because the 20-percent cut in May recovers more than the 50-percent cut in August), the secondary channels next (the outlet and bundle routes — the dealer channel's clearance appetite, the program channel's value-hunting, the kit-and-bundle packaging that moves two aging SKUs as one fresh offer), and the floor routes last (the resale and liquidation market that prices what remains — the honest floor value the review uses when it writes the exit's expected recovery).
The wind-down's timing arithmetic, run before the retire decision is announced: the burn rate (the remaining stock divided by its recent velocity — the months the exit will take at the current markdown path), the overlap rule (the successor SKU's arrival scheduled against the predecessor's exit — the shelf never showing both the dying and the rising product at full price, which is how brands train customers to wait for sales), and the write-down honesty (the exit's expected recovery booked into the season's cash plan at the floor-route value, not the ladder's hopeful top — the ladder's job being to beat the floor, the plan's job being to survive it).
The Supplier Conversation
The review's output travels one direction the internal meeting forgets: outward, to the manufacturing partner. The capacity signal (the next season's shape — which chassis volumes rise, which retire, which refresh — shared early enough to matter: the production calendar the factory builds has the review's outputs in it, and the program that shares its cut list in autumn gets the spring window it wants), the materials warning (the retirements that free the supplier to de-stock — the custom dyed fabrics and the branded hardware whose second-order pipeline should stop, before the supplier's warehouse holds a season of fabric for a SKU that no longer exists), and the development brief (the refreshes and new slots converted into the design process inputs — the review's decisions arriving as specifications, not as moods).
The two-way value the conversation returns: the supplier's intelligence feeding next year's review (the material discontinuations the mill has announced, the component price movements the cost model must absorb, the construction options the factory has added since the line was built), and the relationship's portfolio dimension (the supplier who sees the program's whole line plans capacity like a partner; the supplier who sees only orders plans like a vendor — the annual review, shared at the right depth, being one of the cheapest relationship investments the calendar offers).
Line Architecture After the Cut
The health check the post-review line must pass, read as three coverage maps: the price architecture (the surviving SKUs laid across the tiers — the entry point that recruits, the middle that earns, the top that haloes; the cut that removed a tier's only SKU having redesigned the architecture, not trimmed it), the use architecture (the surviving SKUs against the use cases — the walker, the rider, the traveler, the minimalist each still owning a clear answer; the gap a competitor's catalog will find before the market does), and the channel architecture (each channel's story still complete — the pro shop assortment, the resort program, the corporate offer; a line can be healthy in total and broken per channel, and channels feel the local version).
The smaller line's surprising economics, stated against the instinct to refill every vacancy: the concentration dividend (the same revenue on fewer SKUs — the unit costs improving with per-SKU volume, the inventory deepening where it turns, the marketing message sharpening to the stories that actually close), and the restraint rule (the vacancies that the maps show as genuine gaps filled deliberately, the vacancies that are merely empty slots left empty — the review's second year being where most programs re-bloat, adding back the tail they just removed because empty feels like missing; the architecture documents written at this review being the defense).
Worked Example: a 40-SKU Line Under the Knife
The review, run on a regional brand's full line: forty SKUs across stand, cart and carry chassis in eleven colorways — the evidence pack assembled (three seasons of sell-through by channel, the contribution dollars, the claim rates, the aging buckets), the bands sorted (five SKUs in the engine carrying 58 percent of units, twelve steady contributors, fifteen in the tail — eight with written strategic reasons that survived reading, seven without — and eight in the drag), and the decisions taken in one session against the pre-written criteria: eight retirements (the drag band, plus two tail SKUs whose strategic stories the meeting could not re-sign), five refreshes (contributors whose chassis held but whose colorways had dated — the palette rotated, the zipper pulls upgraded), three new slots admitted (the vacancies the maps showed: the missing entry tier, the travel segment, the personalization-forward SKU the corporate channel kept requesting).
The follow-through, run as the disciplines above prescribe: the wind-down (the eight retirements routed — five through the primary channel's early markdown cadence, two into the corporate value channel, one to the liquidation floor; the exit recovery booked at floor value and beaten by 31 percent), the supplier conversation (the cut list and the three new slots shared with the manufacturing partner in the autumn review meeting — the discontinued colorway's fabric pipeline stopped with 400 meters unbought, the refreshes' specification revisions issued through the version protocol), and the result one season later: the 28-SKU line posting higher revenue on 30 percent fewer units in stock, the engine SKUs deeper and cheaper per unit, the cash cycle shortened by five weeks — the annual cut doing in one meeting what two years of monthly operations had not.
Common Line Review Failures
The failure patterns, collected from programs that ran the meeting and missed the discipline: the emotional veto (the founder's favorite exempted from the criteria — the exception that teaches the organization the evidence is negotiable, after which the review is theater), the metric shortcut (the review run on revenue alone — the high-revenue SKU with the inventory appetite and the claim rate kept because the topline looked healthy, the capital truth never entering the room), the decapitation error (the long tail cut without reading its channel function — the entry-price SKU that recruited the accounts the engine SKUs later harvested, removed for its own numbers and missed in the next season's pipeline), and the indefinite deferral (the review postponed into the season — the meeting that becomes biennial, the drag band compounding quietly into the line's largest single position).
The counter-habits that keep the review real: the criteria pre-commit (the kill thresholds and the band definitions written before the data is seen — the rules negotiated in calm, applied under pressure), the decision minutes (each SKU's outcome and reason recorded — next year's review starting from last year's logic instead of from scratch, the documentation habit paying its least glamorous dividend), and the calendar lock (the review dated against the production calendar — early enough that the wind-down runs in-season and the new slots make the factory's window; the review that happens after the season's orders are placed being an audit, not a decision).
Frequently Asked Questions
What is an annual product line review?
A yearly structured decision meeting where every SKU in the line is judged on the same evidence — sell-through, margin contribution, quality record, inventory age — and assigned one of three outcomes: continue, refresh, or retire with a wind-down plan.
How often should a golf bag line be reviewed?
Annually for architecture, monthly for operations. The monthly rhythm manages stock levels and reorders; the annual review decides which SKUs exist at all. Timing the annual review before the production calendar is what makes it a decision rather than an audit.
What data do I need for a line review?
Four series per SKU: sell-through by month and channel, contribution dollars against true landed cost, warranty claim rate and class, and inventory by aging bucket. Clean attribution matters — program orders counted as program sales, not retail velocity.
What are SKU performance bands?
The sorting layer before decisions: core engine (protect), steady contributors (continue, refresh on schedule), long tail (justify strategically in writing or cut), and drag (retire with a wind-down plan). Bands are sized by behavior, not quota.
What are good kill criteria for a SKU?
Written in advance: two consecutive seasons below the sell-through threshold, contribution below the slot's opportunity cost, a claim rate not attributable to one batch, or drift from the line's positioning. Pre-written criteria are the only referee that survives advocacy.
Should I discontinue or refresh an aging SKU?
Refresh when the chassis earns its slot but the surface does not: new colorway, hardware or configuration on a validated build costs a fraction of new development and keeps most of the marketing effect. Retire when the engineering itself or the positioning has failed.
How do I clear inventory of a retired golf bag SKU?
Climb the exit ladder in order of price protection: primary channel at an early markdown cadence, then outlet, bundle and program channels, then the liquidation floor. Book the expected recovery at floor value and let the ladder beat it.
How many SKUs should a golf bag line have?
As few as the three coverage maps allow: every price tier you intend to play, every use case you serve, every channel's story complete. Most healthy programs concentrate revenue on fewer, deeper SKUs rather than refilling every vacancy the cut creates.
What is the biggest line review mistake?
Exempting a favorite SKU from the criteria — it teaches the organization that evidence is negotiable. Close behind: judging on revenue alone, cutting the tail's channel-recruiting SKUs, and postponing the review until the drag becomes the line's largest position.
How does the line review affect my supplier?
Share the cut list early: it books the production windows you want, stops fabric and hardware pipelines for retired SKUs before the supplier's warehouse fills with them, and converts refreshes and new slots into specifications instead of surprises.
What is a core engine SKU?
The two to five SKUs carrying most of the line's volume and margin — typically the proven chassis in its validated colorways. The engine gets protection, incremental improvement and inventory depth; its disruption is the line's largest risk.
Do new SKUs belong in the annual review?
Yes — admitted against the same evidence standards the retirees failed: validated concept, modeled unit economics, a written slot justification, and explicit first-year graduation criteria so next year's review has a baseline instead of a debate.
How do I keep the line from re-bloating after a cut?
Write the architecture documents at the review — the three coverage maps and the written band logic. Next season, fill only the vacancies the maps show as genuine gaps; empty slots are not missing products, and the documents are the defense against re-adding the tail.