Spreadsheet Dependency in Apparel Planning: A Risk Analysis

Overview

Spreadsheet-based merchandising planning is not failing because spreadsheets are bad tools. It is failing because the planning function has grown — in SKU complexity, channel count, and data volume — beyond what spreadsheets were designed to handle.

This analysis quantifies the cost of spreadsheet dependency in apparel planning across three dimensions: operational overhead (reconciliation and coordination), financial exposure (errors in OTB, carry-over, and buy decisions), and strategic cost (decisions delayed or avoided because the data isn't accessible).

---

Risk Category 1: Operational Overhead

Reconciliation cost

The most quantifiable cost of spreadsheet planning is the time consumed by reconciliation — keeping the OTB file, assortment plan, and buy plan aligned as decisions are made and revised.

Each time a style is added to or removed from the assortment, the following manual updates are required:

• →OTB: Update planned receipts for the affected department and period
• →Assortment plan: Update style count, newness ratio, and depth targets
• →Buy plan: Update or remove the style's quantities
• →Size curve reference: Verify the size distribution is still assigned correctly
• →Allocation model: Remove or adjust door-level quantities

In a 200-SKU assortment, style-level changes happen dozens of times during the pre-season review window. The reconciliation burden is not one large event — it is continuous, and it consumes the highest-leverage planning time.

Practitioner estimates for reconciliation overhead in spreadsheet environments range from 3–5 days per season for a two-person team, to 6–10 days for larger teams managing more complex assortments.

Version control failures

When multiple team members work from the same planning file, version control becomes a manual discipline problem. Common failure modes include:

• →Two team members editing different versions of the same file simultaneously
• →The most recent version not being distributed before a planning meeting
• →Changes made during a meeting not being captured in the file until after the fact
• →A prior version being sent to a vendor or leadership team by mistake

Version control failures are rarely catastrophic in isolation. Their cost accumulates in the time spent identifying which version is current, reconciling changes made in parallel, and correcting decisions that were made on outdated data.

---

Risk Category 2: Financial Exposure

Formula errors in OTB models

OTB spreadsheet models are structurally fragile. The OTB formula — Planned EOP + Planned Sales + Planned Markdowns − BOP Inventory — requires consistent unit treatment (all at cost or all at retail) and accurate period-level inputs. When the model is extended across multiple departments and periods, the number of cells that must be correct for the total OTB to be accurate increases significantly.

Common error types in OTB spreadsheet models:

Mixed unit treatment: Some cells calculated at cost, others at retail — typically introduced when someone updates a subset of the model without reviewing the others.

Broken cell references: Formula cells that reference the wrong period, wrong department, or were not updated when rows were added or removed.

Hardcoded values: Prior-season actuals that were entered as static numbers and not updated when actuals were revised.

Stale markdown rates: Planned markdown percentages from a prior season still applied to the current season's OTB calculation.

An OTB model with any of these errors will produce a distorted picture of available buying room. The consequence is either overbuy (the error overstates available OTB) or underbuy (the error understates it). Both have financial cost: overbuy produces markdown exposure; underbuy leaves demand unsatisfied and sales on the table.

Carry-over errors

Carry-over decisions — which styles to bring back from a prior season — are among the highest-leverage decisions in pre-season planning. A carry-over style occupies OTB budget, takes up a style slot in the assortment, and brings forward inventory risk. Getting carry-over decisions wrong has compounding effects on the season.

In spreadsheet environments, carry-over analysis is typically performed informally: a buyer or planner reviews prior-season sell-through from memory or a separate hindsight file and makes a judgment call. Systematic criteria — minimum STR threshold, margin contribution floor, size availability review — are less consistently applied.

The result is that carry-over decisions in spreadsheet environments tend toward continuity bias: styles that were in the assortment before are more likely to remain, regardless of performance, because the analytical infrastructure to challenge them systematically is not in place.

Buy plan errors

The buy plan translates assortment decisions into purchase orders. Errors in the buy plan produce inventory at the wrong quantities, wrong sizes, or from the wrong vendors. The financial cost depends on whether errors are caught before or after POs are placed.

Pre-PO errors are recoverable. Post-PO errors may require vendor negotiations, order modifications, or cancellation fees — and the inventory impact is already in motion.

Common buy plan errors in spreadsheet environments:

Size quantity calculation errors: Manually applying a size curve percentage to a total quantity across dozens of styles produces arithmetic errors that compound.

Channel split errors: Miscalculating DTC vs. wholesale allocations at buy time results in one channel receiving more than it can sell and the other receiving less than it needs.

Vendor unit minimum errors: Not tracking vendor MOQs against buy quantities produces either shortfall (quantities below minimum) or inadvertent overbuy (rounding up to minimum in multiple styles).

---

Risk Category 3: Strategic Cost

The most significant — and least quantifiable — cost of spreadsheet dependency is strategic: decisions that don't get made because the data isn't accessible in time.

Deferred carry-over analysis

Prior-season sell-through analysis requires pulling data from one file, cross-referencing it with the current assortment list in another file, applying criteria, and documenting decisions. In most spreadsheet environments, this process takes longer than the time available before the carry-over decision window closes.

The result: carry-over decisions default to the prior year's assortment with marginal adjustment, rather than being rebuilt from performance data.

Missed in-season reallocation

In-season reallocation — moving inventory from underperforming styles or slow doors to faster-selling styles or high-velocity locations — requires identifying the signal (underperformance or overperformance) and executing the transfer before the markdown window closes.

In spreadsheet environments, the signal typically arrives in a weekly export, 3–7 days after the underlying event. By the time the planner identifies the opportunity, models the transfer, and gets approval, the optimal reallocation window has often passed.

Size curve optimization deferred

Updating size curves from prior-season sell-through data requires comparing bought % by size against sold % by size, by category and channel, and producing a revised distribution. In a spreadsheet environment, this is a multi-hour analytical project that is often deferred to "after the buy" — which means it is deferred to the following season.

The result is that size curves in spreadsheet environments tend to persist from season to season with minimal revision, even when the underlying sell-through data would support meaningful changes.

---

The Threshold Analysis

Spreadsheet planning is not universally inadequate. At small scale — under 100 active SKUs, single channel, one or two planners — the reconciliation overhead is manageable and the risk of catastrophic error is lower.

The threshold at which spreadsheet risk exceeds the cost of migration is reached at:

| Factor | Threshold | |---|---| | Active SKU count | 200–250+ | | Planning team size | 3+ people sharing the same files | | Channel count | 2+ (DTC + wholesale require separate OTB tracks) | | Seasons managed simultaneously | 2 (current-season management + next-season pre-planning) | | Prior-season errors caught | More than 1 material OTB or buy error per season |

At any two of these thresholds, the recurring cost of spreadsheet reconciliation and error correction exceeds the annual cost of a purpose-built planning tool. At three or more, it is not close.