Dead Stock Is a Decision, Not Bad Luck

Dead stock is not a ghost in the warehouse. It is a receipt for decisions that once made sense, then stopped being reviewed. Forecast buffers, minimum order quantities, slow SKU cleanup, and supplier lead-time assumptions can all turn into inventory that occupies cash, space, and management attention. Inventory turnover is the signal that tells you which decisions are still sitting on the shelf. 

What does inventory turnover really tell you? 

Inventory turnover indicates how efficiently a business is using its inventory investment. It is calculated by dividing the total value of inventory consumed during a period by the total inventory valuation, helping supply-chain leaders understand how effectively inventory is being utilized over time. If the value of inventory consumed in a year is 2 million against a total inventory valuation of 500,000, turnover is four. In plain English, the business turns its stock four times per year. 

That number becomes more useful when converted into days. Divide 365 by the turnover ratio. Four turns equals about 91 days on hand. Eight turns equals about 46 days. Two turns equals about 183 days. 

The ratio is not a moral judgement. Faster is not always better. A high-turn item with unstable supply can create stockouts. A low-turn spare part may be acceptable if it protects a high-value asset. The question is whether the turnover matches the product’s margin, demand pattern, lead time, and service promise. 

Oracle Fusion Cloud SCM documentation describes the inventory, item, lot, planning, and supply-chain data that support this kind of review. The external reference for product capability should stay with Oracle’s Supply Chain Management documentation. The business interpretation belongs to you. 

For Orbrick’s supply-chain persona, the KPI is Optimized Inventory Turns. That wording matters. The goal is not maximum turns. The goal is the right turn rate for cash, margin, service, and risk. 

Which decisions create dead stock before it looks like a problem? 

Dead stock grows quietly because each decision looks reasonable in isolation. 

A planner raises safety stock after a supplier misses a delivery. Nobody revisits the buffer when the supplier stabilises. A buyer accepts a larger minimum order quantity because the unit price looks attractive. Demand drops, but the reorder rule stays in place. An engineering change replaces an item, yet old revisions remain without a disposition owner. A new SKU gets added for a customer request, then survives long after demand disappears. 

If you think that sounds like a storage problem, flip the frame. Inventory is not sitting still. It is voting on yesterday’s decisions with every day it stays unsold. 

The early signs are practical. A SKU hits reorder point even though trailing demand is falling. Open purchase orders exceed the last twelve months of usage. A lot crosses 180 days on hand without a clearance plan. A supplier buffer remains above its original exception threshold. An item has demand in one location and dead stock in another. 

These are not random events. They are process memories. The system remembers what people decided, even when the people have moved on. 

How do you read inventory turnover by SKU instead of hiding behind averages? 

Portfolio averages hide the work. One fast-moving SKU can cover ten slow movers. A category-level ratio can look stable while a specific location is turning into a museum. 

The practical review should cut turnover by SKU, location, supplier, age bucket, lot, item lifecycle, margin, and demand volatility. Start with age and demand. A high-value item with 180 days on hand and falling usage deserves attention before a low-value item with the same age but stable service need. 

Then compare turnover with service signals. Pair the ratio with fill rate, backordered rate, expedite cost, and supplier lead-time performance. Low turns plus healthy service may indicate overstock. High turns plus rising backorders may indicate understock. The metric only becomes useful when read with the neighbouring signals. 

The paired how-to, Reading inventory turns by SKU in Oracle Fusion SCM, should show this in practice. Pull item-level stock, age, lot, planning, purchase order, and demand history. Then sort by cash value, age, and demand decline. The management question is how to act on the view. 

Here is a simple working sequence: 

1. List SKUs with the highest inventory value. 
2. Add days on hand and last twelve months of demand. 
3. Flag items above the age threshold you set for that category. 
4. Split the list by supplier and location. 
5. Assign action: consume, transfer, return, sell down, redesign, or stop buying. 

That fifth column is where the work becomes real. Without it, the report is only a neatly arranged complaint. 

What should a supply-chain leader do when turnover is too low or too high? 

Low turnover needs a cause map before it needs a policy change. 

If demand fell, stop future purchase triggers and review forecast assumptions. If minimum order quantities caused the pileup, renegotiate or group orders more carefully. If supplier lead time drove the buffer, compare the original lead-time risk with the current one. If engineering change created the issue, assign disposition before the next revision arrives. If SKU proliferation is the cause, retire slow variants rather than asking the warehouse to absorb strategy drift. 

High turnover deserves equal care. If turns rise because demand is healthy and service is stable, good. If turns rise because stock is too thin, you may be creating backorders, expediting, and unhappy customers. Inventory turnover can flatter a business that is slowly starving service. 

Use a controlled pilot. Pick one supplier, category, or location. Change one policy at a time: reorder point, safety stock, minimum order quantity, or replenishment frequency. Measure turns, fill rate, backordered rate, and expedite cost before and after one demand cycle. 

That discipline keeps the team from swinging between too much stock and too little stock. Shelves fill. Shelves empty. The customer still has to be served. 

How does Business Value Maximization turn inventory data into an outcome? 

Business Value Maximization (BVM) turns the turnover review into a measured outcome. It follows S.E.E.R.: Sense, Evaluate, Execute, Retrospect and Refine. 

Sense means establishing the baseline. Current turnover by SKU, dead-stock value, age, location, supplier, and fill-rate impact. Evaluate means identifying which decisions created the issue. Forecast policy, buying rule, supplier buffer, engineering change, or SKU governance. Execute means changing the operating rule and assigning an owner. Retrospect and Refine means proving whether cash release, fill rate, and backorder movement improved. 

Inside a Value Discovery engagement, Second Sight can serve as an in-engagement capability for process mining and KPI baselining. It is not a stand-alone SaaS offer. It is part of the consulting wrapper that links Oracle Fusion data with measurable supply-chain outcomes. 

This distinction is central to Orbrick. Orbrick is a boutique Oracle Cloud / Fusion consulting firm that specialises in Oracle’s existing Fusion Applications customers and also takes new customers. Orbrick competes on outcomes, not staffing volume. The pricing model reflects that: Orbrick is the only Oracle Cloud consulting firm operating fully on at-risk, outcome-based pricing, paid only on measurable business impact. 

For the reader, the value is the method. You do not need a perfect transformation charter to begin. You need one clean SKU view, one clear decision owner, and one measured result. 

What should you do in the next inventory review? 

Run a one-week dead-stock decision review. 

First, choose the scope. Pick a category, warehouse, supplier, or business unit. Second, calculate turnover and days on hand by SKU. Third, add demand trend, age bucket, open purchase orders, supplier lead time, and margin. Fourth, rank the list by cash value at risk. Fifth, assign an action for the top twenty items. 

The action list should use plain verbs: 

• Consume through planned demand. 
• Transfer to a location that still needs it. 
• Return to supplier where terms allow it. 
• Sell down with margin guardrails. 
• Redesign the item or replace the old revision. 
• Stop buying until the signal changes. 

That last one is often the most powerful. Dead stock continues when the future buying rule keeps recreating the past mistake. 

This is why Optimized Inventory Turns belongs beside supplier performance and backordered rate. Inventory is a cash story, but it is also a service story. When those signals move together, leaders can act with more confidence. 

What mistakes make inventory turnover reviews less useful? 

The first mistake is chasing one perfect turnover target. Inventory does not work that way. A high-margin spare part, a seasonal finished good, a regulated healthcare item, and a fast-moving component do not deserve the same number. The review should start with category intent. Is the item protecting service, supporting production, meeting regulatory need, or sitting there because nobody closed the loop? 

The second mistake is ignoring item lifecycle. A new SKU may need early stock while demand stabilises. A mature SKU needs tighter buying rules. An end-of-life SKU needs a disposition plan before the replacement arrives. Without lifecycle context, teams punish the wrong items and protect the wrong ones. 

The third mistake is separating finance from supply chain. Finance sees trapped cash. Supply chain sees service risk. Procurement sees supplier terms. Operations sees the shelf. Each view is true, but incomplete. A useful review brings those views together around one SKU list and one decision column. 

The fourth mistake is letting the report become the work. A turnover dashboard can become a very polished way to say “we have slow movers.” That is not enough. Every flagged item needs an owner, a next action, and a review date. If the action is “monitor,” set a date and a threshold. Otherwise “monitor” becomes a polite word for “ignore.” 

This is where the paired how-to earns its place. Once Reading inventory turns by SKU in Oracle Fusion SCM gives you the list, the leadership work is deciding what each slow mover is allowed to become: consumed, transferred, returned, sold down, redesigned, or stopped. 

One practical meeting format helps. Put the top fifteen slow movers on screen. For each item, ask: who ordered it, why was it ordered, what demand did we expect, what changed, and what decision is needed now? Keep the answer short. If nobody in the room can explain why the stock exists, the next action is not more analysis. The next action is ownership with named owners. 

One more question is worth adding: what will stop this item from returning to the list next quarter? If the reorder rule stays unchanged, the team may clear today’s stock and recreate tomorrow’s pile. Close the loop by changing the buying rule, supplier agreement, forecast review, or lifecycle status. Dead stock is expensive. Repeated dead stock is a management habit. 

The key insight: dead stock is rarely bad luck. It is often the result of an inventory decision that was once reasonable but is no longer relevant and now needs clear ownership and action. 

Start with the ERP Maturity Quiz to see whether your Oracle Fusion setup is ready for this kind of KPI-led review. Then use Business Value Maximization to connect the metric to cash and service outcomes. If you want to baseline slow movers inside your own Oracle Fusion environment, request a Value Discovery session. For the technical half of this series, pair this article with Reading inventory turns by SKU in Oracle Fusion SCM and use Second Sight as the process-mining capability inside the engagement.