Items with on-hand value > 0 and zero sales in 180 days. Direct write-down candidate.
At a glance
Items in Oracle Inventory Cloud with on_hand_value > 0 AND sales_last_180_days = 0. The direct write-down list. Sums the dollar value of dead stock across all inventory orgs in the Business Unit scope.
Calculation
Calculated automatically from your Oracle ERP Cloud data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US Fortune 500 outdoor-equipment retailer on Oracle ERP Cloud. Snapshot 14 Apr 26. Total inventory $124M.
Five things to notice:
- $14.8M of dead stock = 11.9% of total inventory. Above the comfort zone; healthy outdoor retail keeps dead-stock ratio under 8%.
- **3.1M.
- $2.4M is dead AND has active ad spend. This is the Dead Stock with Active Ad Spend cross-platform kill shot. Pause those ads immediately.
- 1,840 SKUs is a long tail. Pareto applies: the top 100 dead-stock SKUs probably hold 60% of the value. Sort by unit value descending and tackle the heavy hitters first.
- Action playbook: Pause ads on dead SKUs, clearance markdown 30 to 50%, write-off / scrap aged 365+ items, audit purchasing logic to prevent recurrence (the buyer who ordered the 365+ stock should have a conversation).
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in Oracle ERP Cloud: Oracle does not ship a single Dead Stock report; build via OTBI:
OTBI → Inventory Real Time Subject Area + Order Management Real Time joined on Item, filtered for On Hand > 0 AND Shipped Quantity (180D) = 0
Reports → Inventory → Slow / No Movement Report
The Slow / No Movement Report is the closest native equivalent.
Why our number may legitimately differ:
Cross-connector reconciliation:
Known limitations / merchant FAQs
What is a healthy dead-stock-as-percent-of-total ratio? By industry: fashion 5-12%, electronics 3-8%, industrial / B2B distribution 8-15%, grocery / consumables under 3%. Above the upper end means purchasing forecasts are systematically over-shooting demand. Why 180 days as the default? Industry standard for “no clear demand signal”. Configurable per workspace. Seasonal merchants, does the card respect seasonality? Yes via a seasonality calendar in the field map. Snow gear sold zero in July is not dead; it is seasonal. Without a calendar, all 180D-zero items flag. My new-product launches always show as dead-stock initially. Will they appear here? Yes, if 180+ days passed and they have not sold. The new-product flag (custom item attribute) suppresses the alert during a configurable warmup period (default 60 to 90 days). Does this include consigned inventory? No. Consigned (supplier-owned, on your shelf) is not your write-down risk. Multi-Business-Unit, per-BU view? Yes. Drill-down by BU reveals which warehouse / DC has the dead-stock problem. SAP equivalent? SAP S/4HANA has the Stock Aging app + a Slow/Non-Moving Materials Fiori app; conceptually the same. NetSuite equivalent? NetSuite Inventory Items → Saved Search:quantity_available > 0 AND sales_last_180_days = 0. Vortex IQ runs equivalent logic on both NetSuite and Oracle, allowing customers in transition between the two to keep continuous reporting.
RMCS or revenue-recognition impact?
None. This card is inventory-side, not revenue-side.
Auto-action available?
Pause-ads-on-dead-SKU action via Dead Stock with Active Ad Spend. Markdown / write-off remain manual decisions for Finance.