The real cost of overstock: what your ERP isn't telling you

Ask a retail CFO how much overstock costs them, and you'll almost always get the same answer: "We have X million euros of excess inventory, we see it in the ERP." The answer is sharp, quantified, reassuring. It has one flaw: it's largely wrong.

Not because the ERP is wrong about the stock value — it does its job. But because the book value of excess stock represents only a fraction of what it actually costs the company. Overstock is one of the rare items in the company where the bill visible in the information system corresponds to maybe 20 to 30% of the total cost absorbed. The rest spreads across dozens of diffuse, desynchronized line items — and, this is the heart of the problem, never consolidated in a single dashboard.

The market numbers are telling. Globally, retailers lose hundreds of billions of euros every year to excess inventory. Sector analyses converge on an annual carrying cost between 20% and 30% of stock value — and up to 32% in sectors like fashion or consumer goods. That means €100M of overstock costs between €20M and €30M per year just to be held, before a single markdown. The question isn't whether overstock is expensive: it's why this astronomical bill stays invisible in most organizations.

Let's look in detail at what the ERP captures, what it misses, and why this blind zone has become one of the biggest margin reservoirs in modern retail.

What the ERP sees (and what it thinks it sees)

The ERP is a remarkable tool for what it was built to do: keep the ledger, track physical and financial flows, guarantee accounting integrity. On stock, it answers three questions with near-perfect accuracy: how many units, at what value, at what location.

The problem starts the moment you try to go further. Because the useful question for the retailer isn't "how much do I have?", but "how much does this stock cost me every week I keep it, and how much margin will I lose if I do nothing?". For that question, the ERP is structurally ill-equipped.

Three reasons.

First, the ERP reasons in flows and book value, not in economic risk. A unit worth €50 in stock for three weeks is treated exactly like a unit worth €50 in stock for twenty-six weeks. Accounting-wise, it's the same line. Economically, the second is almost certainly doomed to a deep markdown, a costly transfer, or an outlet disposal — in short, a loss of margin already written into the future.

Second, the ERP doesn't naturally cross stock with forecasted demand. It knows what's there, not what should be there. To know whether stock is in excess, you have to compare it to a localized sales forecast, a target cover, an actual velocity — all information that lives in other systems (BI, planning, e-commerce) and that's never automatically reconciled.

Third, and most serious, the ERP doesn't value opportunity cost. And it's probably the heaviest overstock cost: what this stock prevents you from doing elsewhere. The shelf space tied up, the cash locked in, the future markdown risk, the room lost for products that actually sell. None of these costs appears on an accounting balance.

Result: leadership reads in the ERP an overstock at X million euros, thinks that's the problem to solve, and has no idea the real problem is probably two to four times larger.

The seven cost layers no one aggregates

The total cost of overstock builds in successive strata. Each is measurable separately, but almost no organization adds them up in the same dashboard. Let's break them down.

Layer 1: direct carrying cost

The least invisible part. Warehouse rents, energy, insurance, handling, depreciation, taxes. With the explosion in logistics costs in recent years — warehouse rents at historic highs, labor costs up over 10% since 2021, interest rates long elevated — this line has structurally grown. On its own, it already represents 15 to 20% of stock value per year.

ERPs capture part of these costs, but rarely allocated to the SKU. No one knows what really costs, for example, keeping a long-tail SKU that takes three shelf slots in store and one cubic meter in the warehouse.

Layer 2: capital tied up cost

Stock is frozen cash. At a typical retailer's scale, €50M of excess stock represents, at current average financing rates, several million euros a year in pure financial cost — not counting the effect on banking covenants or investment capacity. With rising interest rates over recent years, this line has simply exploded: per sector benchmarks, retailers' financial costs have grown 40% since 2021. Stock you used to keep "for safety" was once marginal in financing cost; it now weighs heavily on EBIT.

The ERP sees stock as an asset. The CFO knows it's also an implicit debt — but almost never has the tool to measure that debt at the SKU level.

Layer 3: future markdown cost

This is the layer that turns overstock into a time bomb. A product in excess today will almost certainly be marked down tomorrow — and the longer you wait, the deeper the required markdown. In seasonal categories, a 4-to-6-week delay on a markdown decision can take the necessary discount from -20% to -50%, with a brutal leverage effect on gross margin.

This future markdown obviously doesn't appear in the ERP. It appears in the P&L at the end of the season, as a drop in gross margin rate — but by then, it's too late to prevent it.

Layer 4: obsolescence cost

Particularly violent in fashion, electronics, toys, and food. A product going out of season, out of trend, or approaching its expiration date loses value non-linearly: it might keep 90% of its value for months, then lose 60% in a few weeks. The ERP records this loss a posteriori, as a depreciation provision. No traditional tool forecasts it before it materializes.

Layer 5: bad localization cost

The most ignored cost, and one of the largest. Most retailers aren't globally overstocked — they're imbalanced between locations. The same product can be in excess in 30 stores and stocked out in 50 others. Accounting-wise, the ERP sees acceptable global cover. Economically, it's a double cost: you'll mark down where there's too much, you'll lose sales where it's missing.

Reference studies show that retailers lose up to 4% of their sales to stockouts, even as their warehouses and some of their stores overflow with the same product. It's the purest illustration of the ERP's limit: it knows how much, it doesn't know where it should be.

Layer 6: diffuse operational cost

The more stock is in excess, the more operational noise it generates. Longer counts, more complex picking, more frequent inventory errors, extra handling, growing unknown shrinkage, supplier returns negotiated in panic. These costs are never attributed to overstock; they get absorbed into general expenses. Yet they typically represent 2 to 5% more of the annual cost of holding stock.

Layer 7: commercial opportunity cost

The most serious, and the most invisible. Every square meter occupied by a product that doesn't rotate is a square meter not occupied by a product that would sell. Every euro tied up in overstock is a euro that doesn't fund a best-seller's replenishment, a new collection's launch, a new corner's opening. This cost has no line on a P&L. But it's probably the most structuring long-term.

Why the addition is never done

When you total these seven layers, the annual cost of overstock frequently comes out between 25 and 35% of its value. On €100M of excess stock, that's €25M to €35M evaporating every year, much of which will materialize later as markdown, provision, or missed revenue. And yet almost no organization does this addition. For three reasons.

First reason: the data is fragmented. Carrying is in general ledger, markdown in merch, capital cost in finance, stockouts in commercial, obsolescence in provisions. Each department sees its part of the cost. No one sees the total.

Second reason: responsibilities are diluted. Overstock is the result of a chain of decisions — buying, planning, allocation, store execution — where each link optimizes locally without seeing the global effect. The buyer secured volume, the planner covered risk, the merchandiser respected the assortment plan, the store manager took what was sent. Everyone did their job. And yet at the end of the season, the overstock is there.

Third reason: the tools weren't built for this question. The ERP is a bookkeeping tool, not an economic steering tool. BI answers descriptive questions, not predictive ones. Merchandising operates by category, not by SKU/store. And between all these tools, the unifying layer is missing — the one that would say, in real time: "here are the 500 SKU/store pairs costing you the most, and here's the recommended action for each."

Overstock isn't a stock problem, it's a decision problem

This is probably the most useful perspective shift for retail leadership. We long treated overstock as a sourcing problem: "we bought too much." That analysis is right but incomplete. Most of the time, overstock isn't the result of a bad initial buy — it's the result of a series of micro-decisions not taken over the product's life cycle.

No reallocation between stores when the imbalance forms. No early markdown on slowing SKUs. No supplier return when the contractual clause exists. No targeted promotion on the affected stores. No transfer to the e-commerce channel that could have moved it. No preventive negotiation with the supplier on the next order. At every step, an opportunity for prevention or correction was missed — not from bad will, but because no one had visibility, time, and tool simultaneously to act.

That's exactly where the modern fight against overstock plays out. Less in upstream buying control — which obviously matters — than in the ability to continuously orchestrate the hundreds of small decisions that, summed up, make the difference between a healthy stock and a toxic one.

Taking back control: from the accounting snapshot to an economic view

Retailers who structurally lower their total cost of stock all share an approach built around three principles.

Principle 1: unify the data first. As long as sales, stock, logistics flows, store performance, and supplier data live in silos, no serious optimization is possible. The first brick of an anti-overstock strategy isn't a new algorithm — it's a unification layer that reconciles POS, ERP, e-commerce, supply chain into one usable repository.

Principle 2: move from tracking to deciding. Seeing the problem is no longer enough. Dashboards showing aging stock, excessive cover, or weak sell-through have existed for years — and haven't reduced overstock. What's missing is the next step: turning these signals into concrete, prioritized, executable decisions. Which SKU, in which store, do you transfer, mark down, return, or leave alone?

Principle 3: industrialize at the SKU/store level. Overstock lives in the details. At a network's scale, you have tens of thousands of SKU/store pairs to steer continuously. No human team can do this by hand — not because people aren't competent, but because the combinatorial complexity simply exceeds available cognitive capacity.

Retailers who've implemented this approach report significant structural gains. Public benchmarks converge: a 20-30% reduction in overstock, a 15-25% drop in stockouts, a 2-4% lift on sales, and an EBIT improvement between 1 and 3 points. On a retailer generating €500M in revenue, that's €5M to €15M of net margin moving columns — not because more was sold, but because the hidden bill of un-steered stock stopped getting paid.

The Solya approach: make stock talk, not just count

That's precisely the transition Solya runs at retailers who want to go beyond their ERP's limits. Not to replace it — the ERP stays essential as the system of record — but to add on top the layer ERPs were never built to carry: a decision and operational execution layer, capable of turning observed stock into steered stock.

Concretely, Solya connects to the retailer's existing data sources — POS, ERP, e-commerce, supply chain, internal tools — and rebuilds a unified, continuously updated view at the SKU/store level. That data is then enriched with economic signals: actual cover vs target, future markdown risk, inter-store imbalance, comparative velocity, supplier constraints. The result isn't another dashboard. It's an actionable decision feed: this SKU to transfer from store A to store B, this one to mark down in priority, this one to flag to the supplier for negotiation, this one to protect from an unnecessary markdown.

The chain's business rules — margin floors, brand-specific handling, logistics constraints, operation calendars — are embedded in the engine, which applies them systematically while leaving the teams free to adjust. The goal isn't to replace the human, but to extract them from the repetitive mechanics so they can focus on high-value trade-offs: assortment strategy, supplier negotiation, price positioning, customer experience.

What Solya brings, in the end, is what traditional ERPs can't do: turn an accounting view of stock into continuous economic steering. See, understand, decide, execute — without breakage, at scale, without depending on an Excel team rebuilding the truth every Monday morning.

The question isn't how much stock you have

It's how much it actually costs you. Not according to your ERP. According to what the seven layers added up reveal.

Most retail leadership teams discover, when they do this exercise seriously, that they absorb an annual overstock cost two to three times what they imagined. And that a significant fraction of this cost is avoidable — not by shrinking assortment, not by tightening buys, but by industrializing the cascade of small operational decisions that turn toxic stock into healthy stock.

In a sector where every EBIT point counts, this is probably today the most accessible — and most systematically left on the table — margin reservoir.

---

How much does your overstock really cost you?

At Solya, we offer retail leadership teams a personalized 30-minute overstock diagnostic to map, on your own data, the seven cost layers absorbed by your organization and identify where the most accessible margin reservoirs hide. Not a generic product pitch: a concrete conversation, grounded in your context, that walks away with a quantified estimate.

👉 [Book your Solya diagnostic] — 30 minutes, by video, with one of our retail experts.

You'll walk away with:

• A map of your main hidden cost lines
• An estimate of recoverable margin potential
• The first priority use cases to take action