---

Every retail buyer has a spreadsheet story. A formula that grew for three years until no one fully understood it. A model that worked perfectly until the person who built it left. A 47-tab workbook that takes 40 minutes to refresh before the Monday morning buy meeting.

Excel is where demand planning starts for almost every growing brand. It's also where it eventually breaks. The question isn't whether to use a spreadsheet — it's recognizing when you've outgrown one.

This is a practical walkthrough of what building a 26-week demand forecast actually looks like in each environment, where each approach genuinely excels, and what forces brands to make the switch.

What a 26-week demand forecast needs to do

Before comparing tools, it's worth agreeing on what a real planning forecast requires:

• Seasonality adjustment — a T-shirt sells differently in July than in November. Your forecast needs to weight recent history by the seasonal pattern of each category, not just average it.
• Sell-through pacing — how fast is current inventory moving relative to where it needs to be by end-of-season? This determines urgency of reorders.
• Size and color curve application — aggregate demand doesn't tell you how many size 8s to buy. You need historical size distributions applied at the SKU level.
• Lead time and safety stock — a 12-week vendor lead time means you're placing orders based on forecasted demand starting 12 weeks from now, plus a buffer.
• Reorder signals — which styles are at risk of stocking out before their end date? Which have too much coverage?
• Purchase order export — the forecast isn't useful until it becomes an actual buy quantity by style, size, and color that can be sent to a vendor.

This is the full job. Let's look at both environments against this standard.

Building the forecast in Excel

Step 1: Compile your sales history

You start by pulling weekly sales data from your POS or ERP — units sold, units on hand, receipts — usually by style-color-size. This lands in a raw export that needs cleaning: removing cancelled orders, accounting for returns, normalizing week numbering across years.

In Excel, this is usually VLOOKUP chains or Power Query. If your ERP exports clean data, great. If not, expect 2–3 hours of prep work before you can forecast anything.

Step 2: Build the seasonal index

A seasonal index tells you how much a given week's demand differs from the annual average. You compute it by calculating the ratio of each week's historical sales to the trailing 52-week average, typically across 2–3 years.

In Excel, this is a manageable formula: =AVERAGE(week_n / annual_avg) iterated across 52 rows per category. The problem is when you have 8 categories with different seasonal patterns — outerwear peaks differently than basics — you need 8 separate index tables, and keeping them in sync with your history updates becomes a maintenance burden.

Step 3: Apply the index to generate forecasts

Multiply your baseline demand rate (recent weeks' average, deseasonalized) by the seasonal index for each forward week. For a single style, this looks like:

Straightforward in theory. In practice, this gets complicated fast when you have 200+ active styles. Each style needs its own baseline. You also need to handle styles with fewer than 8 weeks of history differently than mature styles — new introductions need a different logic path.

Step 4: Build the size and color curves

This is where most Excel models start to crack. To get from a style-level forecast to SKU-level buy quantities, you need a size curve: "of the demand for Style X in Category Y, what percent historically goes to size S, M, L, XL?"

Building this from scratch means aggregating size-level sell data across styles in each category, computing the distribution, and applying it as a multiplier. Doing this for 6 categories × 4 size ranges × potentially per sub-category is a significant modeling effort. Most small teams approximate it — or skip it and buy "intuitively" by size.

Step 5: Calculate open-to-buy and reorder recommendations

Now you need to compare forecasted demand against current inventory plus any on-order to determine what needs to be reordered. You need to account for lead time (if lead time is 10 weeks, you're looking at weeks 11–26 for your reorder decision), minimum order quantities, and your open-to-buy budget.

In Excel this is doable — it's a series of nested IFs and SUMIFs — but it's also brittle. If one cell breaks, the reorder signals are wrong and there's no error alert. Finding that break is forensic work.

Step 6: Export the purchase order

Usually a manual step: copy the reorder quantities, transpose to the vendor's template, assign style numbers and colorways, send. Some teams have a macro for this. Most don't.

Where Excel demand forecasting breaks down

Challenge	Excel	Purpose-built tool
Data refresh (weekly)	✗ Manual copy-paste or macro	✓ CSV upload, instant recalc
Seasonality by category	~ Manual index tables, prone to staleness	✓ Auto-computed from uploaded history
Size and color curves	✗ Often skipped or approximated	✓ Auto-pooled by category / sub-category
New styles (< 8 wks data)	✗ Requires special case logic	✓ Handled by category fallback
Reorder alerts	~ Formulaic, breaks silently	✓ Live, sorted by urgency
Price elasticity	✗ Rarely modeled	✓ Regressed from markdown history
Sell-through tracking	~ Manually computed	✓ Auto-calculated per style
PO export	✗ Manual copy / macro	✓ One-click export
Auditability	~ Hard to trace formula chains	✓ Transparent input → output
Setup cost	✓ Low (free, familiar)	~ Low if well-designed; medium otherwise

When Excel is still the right answer

Excel demand forecasting isn't wrong. It's often exactly right. The spreadsheet approach works well when:

• You have fewer than ~50 active styles and one or two categories
• Your seasonal pattern is simple (one peak, predictable)
• You're not doing size-level buying (buying by style total only)
• You have someone on the team who owns and understands the model
• Your data export is clean and consistent

A well-built spreadsheet that one person deeply understands is more reliable than a poorly-implemented software tool. Don't let this article push you to add complexity you don't need yet.

When purpose-built tools become necessary

The clearest signals that you've outgrown spreadsheet planning:

• The model takes more than 2 hours per week to refresh. If your planning process is mostly data wrangling, not actually planning, you're spending the wrong time.
• Multiple buyers are working in the same file. Version conflicts in shared spreadsheets cause errors that are invisible until they're costly.
• You're consistently wrong on size distribution. If you're regularly marked out on one size while sitting on inventory in another, your size curves need automation.
• You have more than 3–4 active seasons in your model at once. Managing historical index tables across multiple seasons in Excel creates compounding complexity.
• You've had a "formula break" incident. If a broken cell link has ever caused a bad buy decision, the model is too fragile for the stakes.

What the transition actually looks like

The practical truth about switching to a purpose-built demand planning tool: the first thing buyers discover is that the software surfaces problems their spreadsheet was hiding. Styles they thought were healthy show concerning sell-through trajectories. Size curves they assumed were stable turn out to be badly skewed.

This is a feature, not a bug. Better visibility is the point. But it means the transition isn't just a software change — it's a calibration process where you reconcile what the tool is showing against your own institutional knowledge. Budget two to four weeks of parallel running before fully trusting the new system's outputs.

The transition is also faster than most teams expect if the data is clean. A well-designed planning tool should get you to your first forecast within an hour of uploading your first CSV — not after weeks of onboarding.