Why does ERP not protect apparel margin on its own?

ERP is built to record transactions and control finance after decisions are made — purchase orders, receipts, costs, inventory. The decisions that actually set margin happen earlier: the line plan, open-to-buy, assortment, buy quantities, size curves, and timing. ERP faithfully records the outcome of those decisions but does not help make them, so the margin is largely determined before ERP ever sees the order.

Why do brands still use spreadsheets if they have ERP?

Because ERP starts at the PO and the planning work happens upstream of it. Teams build spreadsheets to do the line planning, OTB, assortment, and size-level buying that ERP does not own, then feed the result in as orders. The spreadsheet is filling the gap between where planning happens and where ERP begins.

Where exactly does the margin leak?

In the handoffs. An OTB number set in a spreadsheet drifts from the receipts recorded in ERP; a size curve decided in one file is re-keyed into the buy with errors; a production delay never reaches allocation; markdowns get taken reactively because no connected view flagged the overbuy early. Each gap is small; across a season they compound into margin that was decided correctly and then lost in translation.

Is the answer to replace ERP?

Usually not. ERP is good at what it is for — transactions, finance, and control. The gap is upstream, in the connected commercial planning that ERP was never designed to own. The practical move is to add a connected planning and workflow layer that feeds clean, reconciled decisions into ERP, rather than ripping out the system of record.

What does "connected" actually change?

It keeps the line plan, OTB, assortment, buy, size curves, POs, production status, and allocation on one shared record, so a decision in one stage updates the rest without re-keying. The reconciliation that teams do by hand between spreadsheets and ERP becomes continuous instead of periodic — which is where the exposed margin lives.

// Resources · Executive

Why ERP and Excel still leave apparel margins exposed

Most apparel brands run on ERP plus spreadsheets — and margin still leaks, because the decisions that set margin happen upstream of ERP and the spreadsheets that make them never reconcile cleanly back to it. The system of record is not the problem. The gap in front of it is.

This is a practical, executive-level look at where that gap sits, why two capable tools still leave it open, and what a connected commercial workflow changes — without rip-and-replace.

Short answer

ERP records transactions and controls finance after decisions are made. Spreadsheets make the upstream planning decisions — line plan, OTB, assortment, size curves, buy — but do not reconcile continuously back to ERP. Margin is set upstream and lost in the handoffs between the two. A connected planning layer that feeds reconciled decisions into ERP closes the gap that neither tool was built to own.

// What each tool is actually for

What ERP and Excel are each actually for

ERP is a system of record. It is excellent at recording transactions, controlling cost and finance, and keeping the books straight once orders exist. What it is not built for is the upstream commercial planning that decides what those orders should be — the line plan, the open-to-buy, the assortment, the size-level buy, and the timing. By the time a purchase order reaches ERP, the margin-defining choices have already been made.

The spreadsheet is where those choices get made, precisely because ERP starts too late and rarely speaks apparel’s language of drops, size curves, and seasonal flow. It is flexible, fast, and familiar. But it is also disconnected: it models the decision and then hands a number across a gap, with no continuous link back to the receipts, costs, and inventory ERP holds.

Definition — Margin exposure: Margin exposure is the gap between the margin a plan was designed to deliver and the margin actually realized — the erosion that happens when planning decisions and the system of record drift apart across a season instead of staying reconciled in real time.; Used by: Merchandising leaders, planning directors, finance partners; Related: Open-to-buy, markdown, sell-through, connected planning

// Where the gap sits

Where the gap sits

The planning-to-record gap that exposes margin
Decision	Where it is made	Where it is recorded	The exposure
Open-to-buy	Spreadsheet	ERP receipts	OTB drifts from actual intake
Assortment & buy	Spreadsheet	ERP purchase orders	Re-keyed quantities, transcription error
Size curves	Spreadsheet	ERP order lines	Wrong size mix bought, sold at markdown
Production timing	Email / spreadsheet	ERP / 3rd party	Late receipts miss the selling window
Markdowns	Reactive	ERP after the fact	Taken late because no early signal

Open-to-buy

Where it is made: Spreadsheet
Where it is recorded: ERP receipts
The exposure: OTB drifts from actual intake

Assortment & buy

Where it is made: Spreadsheet
Where it is recorded: ERP purchase orders
The exposure: Re-keyed quantities, transcription error

Size curves

Where it is made: Spreadsheet
Where it is recorded: ERP order lines
The exposure: Wrong size mix bought, sold at markdown

Production timing

Where it is made: Email / spreadsheet
Where it is recorded: ERP / 3rd party
The exposure: Late receipts miss the selling window

Markdowns

Where it is made: Reactive
Where it is recorded: ERP after the fact
The exposure: Taken late because no early signal

None of these is a failure of ERP or of the spreadsheet. Each is a failure of the connection between them.

// Why the leak compounds

Why a small gap becomes a margin problem

Any single handoff looks harmless. A number is copied, a file is emailed, a delay is noted. The cost is cumulative and directional: errors and drift do not cancel out, they accrue against margin. An overbuy that a connected OTB would have flagged in week two is discovered in week ten, when the only lever left is markdown. A size break decided in a spreadsheet but mis-keyed into the buy sells through unevenly and ends the season in clearance. Because the reconciliation between planning and the record is periodic and manual, the brand is always learning about exposure after the window to act has narrowed.

// What connected planning changes

What a connected commercial workflow changes

A connected workflow layer does not replace ERP and does not ban spreadsheets from genuine ad-hoc work. It keeps the line plan, open-to-buy, assortment, buy plan, size curves, purchase orders, production status, and allocation on one shared record, and feeds clean, reconciled decisions into ERP rather than a stack of re-keyed exports. The reconciliation teams do by hand becomes continuous, so exposure surfaces while it can still be corrected — when an overbuy is forming, not after it has shipped. It is the layer that sits in the gap ERP and Excel leave open.

// Summary

ERP is a system of record for transactions and finance; it does not own the upstream planning that sets apparel margin.
Spreadsheets make those upstream decisions but never reconcile continuously back to ERP — the two drift across a season.
Margin leaks in the handoffs: OTB vs receipts, re-keyed buys and size curves, late production, reactive markdowns.
The leak compounds because reconciliation is periodic and manual, so exposure is discovered after the window to act has closed.
A connected commercial workflow layer feeds reconciled decisions into ERP and makes exposure visible early — without replacing the system of record.

// Related resources

See it in RetailNorthstar →

// FAQ

Frequently asked questions

Why does ERP not protect apparel margin on its own?: ERP is built to record transactions and control finance after decisions are made — purchase orders, receipts, costs, inventory. The decisions that actually set margin happen earlier: the line plan, open-to-buy, assortment, buy quantities, size curves, and timing. ERP faithfully records the outcome of those decisions but does not help make them, so the margin is largely determined before ERP ever sees the order.
Why do brands still use spreadsheets if they have ERP?: Because ERP starts at the PO and the planning work happens upstream of it. Teams build spreadsheets to do the line planning, OTB, assortment, and size-level buying that ERP does not own, then feed the result in as orders. The spreadsheet is filling the gap between where planning happens and where ERP begins.
Where exactly does the margin leak?: In the handoffs. An OTB number set in a spreadsheet drifts from the receipts recorded in ERP; a size curve decided in one file is re-keyed into the buy with errors; a production delay never reaches allocation; markdowns get taken reactively because no connected view flagged the overbuy early. Each gap is small; across a season they compound into margin that was decided correctly and then lost in translation.
Is the answer to replace ERP?: Usually not. ERP is good at what it is for — transactions, finance, and control. The gap is upstream, in the connected commercial planning that ERP was never designed to own. The practical move is to add a connected planning and workflow layer that feeds clean, reconciled decisions into ERP, rather than ripping out the system of record.
What does "connected" actually change?: It keeps the line plan, OTB, assortment, buy, size curves, POs, production status, and allocation on one shared record, so a decision in one stage updates the rest without re-keying. The reconciliation that teams do by hand between spreadsheets and ERP becomes continuous instead of periodic — which is where the exposed margin lives.

// The cost of disconnected work

Disconnected workflows do not just slow teams down — they create planning risk, margin leakage, and late decisions.

See the connected operating model →Build the business case →