Skip to main content
Use Case — Seasonal Planning

Apparel Runs on Seasons.
Your Planning System Should Too.

Seasonal planning coordinates OTB, assortment, buy timing, and in-season management across Spring/Summer and Fall/Winter cycles — with each season as a distinct financial commitment, not a slice of an annual spreadsheet.

RetailNorthstar is built around the apparel seasonal calendar. Both seasons are live simultaneously, carry-over logic spans season boundaries, and in-season actuals feed the next-season plan in real time.

Why seasonal planning is harder than annual planning

Each season is a separate financial commitment

Spring/Summer and Fall/Winter are not subdivisions of an annual budget — they are distinct financial commitments with separate OTB targets, margin goals, and receipt schedules. Managing them as a single pool obscures the trade-offs and allows one season to silently borrow from the other.

Carry-over logic runs across season boundaries

Not all styles end cleanly at season close. Some carry-over to the next season — either as planned continuations or residual inventory. Managing which styles carry over, at what depth, and against which season's OTB requires explicit structure that most planning tools handle poorly.

Pre-season timeline is compressed by buy lead times

Seasonal buy decisions must be made 4–6 months before the season starts — while the current season is still selling. Planning the next season while managing the current one is the standard operational state for apparel planning teams, and it requires a system that can hold both seasons simultaneously.

In-season actuals affect next-season planning

Current-season sell-through is the primary input for next-season decisions. Brands that wait until season close to analyze performance are already behind on the next-season plan. Real-time in-season data needs to feed the forward-looking planning process.

From season OTB to in-season sell-through

01
Set season OTB and financial targets
Establish separate OTB budgets, margin % targets, and receipt schedules for each season. Spring and Fall operate as distinct financial models — not subdivisions of an annual total.
02
Review prior-season hindsight
Prior Spring performance informs next Spring's assortment. Prior Fall informs next Fall's. Seasonal hindsight — sell-through, size results, margin contribution — is structured within the platform, available before planning begins.
03
Build the seasonal assortment
New introductions and carry-over decisions are made against the season's OTB and the hindsight data. Carry-over styles must re-earn their place based on performance — not automatically include by default.
04
Execute the seasonal buy
Buy quantities by style, color, size, and vendor are set against the season's delivery windows. OTB reconciles in real time as buy decisions are made.
05
Track in-season against plan
Actual sell-through by style is tracked against the seasonal plan in real time. Signals — stockouts, underperformers, reallocation opportunities — surface during the selling period, while action is still possible.

Seasonal structure native to the platform

Separate OTB by season
Spring/Summer and Fall/Winter are tracked as distinct financial models with separate OTB budgets, receipt targets, and margin goals.
Cross-season carry-over management
Carry-over styles are explicitly tracked between seasons — with prior-season performance data available to inform depth decisions for the continuation.
Simultaneous season management
Plan next season while managing the current one. Both seasonal models are live simultaneously — the current season's actuals feed into the next season's planning workflow.
Delivery window management by season
Pre-season and in-season deliveries are scheduled by season and period, ensuring receipt timing aligns with the selling calendar.
Seasonal size curve management
Size curves differ by season — summer sizing patterns may differ from winter. Separate seasonal size curves are applied at buy time for each season's assortment.
In-season actuals informing forward plan
Current-season sell-through data updates the planning view in real time, feeding next-season OTB calibration and assortment decisions before the season closes.

Seasonal planning questions

How does seasonal planning work in apparel?

Seasonal planning in apparel is the process of managing the full planning cycle — OTB, assortment, buy, and allocation — for each of the two primary selling seasons: Spring/Summer and Fall/Winter. Each season is a discrete financial commitment with its own OTB budget, margin targets, receipt schedule, and sell-through objectives. Pre-season planning for each season happens 4–6 months before the season starts, meaning brands are always planning the next season while managing the current one.

What is the difference between seasonal planning and annual planning in apparel?

Annual planning (or the Merchandise Financial Plan) establishes the full-year financial targets — total sales, gross margin, inventory investment. Seasonal planning translates those annual targets into season-specific OTB budgets, assortment structures, and buying plans for Spring/Summer and Fall/Winter. The annual plan is the financial umbrella; seasonal plans are the operational execution within it. Managing both requires a system that connects annual targets to season-level planning decisions.

How does RetailNorthstar handle carry-over styles between seasons?

RetailNorthstar tracks carry-over styles as explicit assortment objects that span season boundaries. Prior-season performance data — sell-through rate, size results, margin contribution — is available when making carry-over vs. discontinue decisions. Carry-over styles that re-enter the assortment are planned against the new season's OTB with depth targets informed by their most recent performance, not default continuation at prior-season quantities.

Related

Built around the apparel seasonal calendar.

See how RetailNorthstar manages Spring and Fall seasons simultaneously — with connected OTB, assortment, buy planning, and in-season sell-through tracking.