> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Slow-Moving Items (>90d no movement), Oracle ERP Cloud > Slow-Moving Items (>90d no movement) from Oracle ERP Cloud. The value of inventory with no transaction movement in over 90 days, the early stage of the dead-stock pipeline where cash is trapped before it becomes a write-down. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > Value of inventory with no movement for over 90 days. The early stage of the dead-stock pipeline, where cash is trapped before it becomes a write-down. ## At a glance > The on-hand value of items that have had no transaction movement, no issue, no receipt, no sale, in more than 90 days. This is the leading edge of the dead-stock pipeline. By the time inventory shows up on the [Dead Stock Value](/nerve-centre/kpi-cards/oracle-erp/dead-stock-value) card it is usually past saving; this card catches it 90 days earlier, while there is still time to discount, transfer, or stop reordering. The number is cash trapped on the warehouse floor before the accountants have to write it down. | | | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The on-hand value of items whose most recent inventory transaction (sale, issue, receipt, transfer, adjustment) is older than 90 days, summed across the inventory orgs in scope, valued at the configured cost method. Counts the quantity still on hand, not the historic quantity. | | **Currency** | Multi-Ledger: reporting currency at cost-rate FX. Native currency available per org. | | **Cost method** | Respects the method configured per inventory org (Average Cost or Standard Cost typically). | | **Inventory Org scope** | Card respects the dashboard's selected Business Unit and inventory-org filter. Rolls up every org the connected role can see by default. | | **Time window** | Real-time snapshot (RT). The 90-day no-movement test is evaluated against the live transaction history at each sync. | | **Alert trigger** | `>10% of inventory value`. When slow-movers exceed 10% of total on-hand value, the Nerve Centre raises a finding. | | **Roles** | owner, finance, operations | ## 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 omnichannel apparel and home-goods retailer on Oracle ERP Cloud plus Oracle Inventory Cloud. Snapshot 12 Apr 26. Total on-hand value across all orgs is \$280,300,000. | Slow-mover category | On-hand value (USD) | Days since last movement | | -------------------------------------------------- | ------------------- | ------------------------ | | End-of-life seasonal apparel | \$14,200,000 | 90 to 180 | | Discontinued home accessories | \$9,800,000 | 180 to 365 | | Spare parts and fittings (legitimate low-velocity) | \$4,300,000 | 90 to 365 | | Overbought promotional stock | \$6,100,000 | 90 to 150 | | **Slow-Moving Items (this card)** | **\$34,400,000** | | Five things to notice: 1. **\$34.4M is 12.3% of total inventory, above the 10% alert threshold.** The Nerve Centre raises a finding. At 12.3% the merchant has more than one dollar in eight tied up in stock that has not moved in a quarter, which is a working-capital drag and a forward write-down signal. 2. **Not all slow-movers are bad.** The \$4.3M of spare parts and fittings is legitimately low-velocity by design; you stock a replacement part you might sell twice a year. Filter these out using ABC class or item category before treating the whole number as a problem. The card flags movement, judgement decides intent. 3. **The \$14.2M of end-of-life seasonal is the actionable layer.** It is the freshest cohort (90 to 180 days) and the most rescuable. A markdown event or a channel transfer now prevents it sliding into the [Dead Stock Value](/nerve-centre/kpi-cards/oracle-erp/dead-stock-value) cohort, where recovery rates collapse. 4. **The \$9.8M of discontinued accessories is already at risk.** Past 180 days, recovery is hard. This is the bridge between slow-moving and dead. Cross-reference [Dead Stock Threshold Breach](/nerve-centre/kpi-cards/oracle-erp/dead-stock-threshold-breach). 5. **The \$6.1M of overbought promo is a reorder-policy signal.** If stock bought for a promotion is now slow, the demand forecast was wrong. Pause any standing reorder rules on these SKUs before the next buy cycle compounds the problem. ## Sibling cards merchants should reference together Slow-Moving Items is the early-warning stage of the inventory-health pipeline. Pair it with these to see the full lifecycle from at-risk to written-down. | Card | Why pair it with Slow-Moving Items | | ------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- | | [Dead Stock Value](/nerve-centre/kpi-cards/oracle-erp/dead-stock-value) | The next stage. Today's slow-movers become tomorrow's dead stock if no action is taken. | | [Dead Stock Threshold Breach](/nerve-centre/kpi-cards/oracle-erp/dead-stock-threshold-breach) | The alert tier when dead stock crosses a configured ceiling. | | [Inventory Aging](/nerve-centre/kpi-cards/oracle-erp/inventory-aging) | The full aging curve; slow-movers are the right-hand tail. | | [Total Inventory Value](/nerve-centre/kpi-cards/oracle-erp/oerp-total-inventory-value) | The denominator the 10% alert is measured against. | | [Inventory Value by Inventory Org](/nerve-centre/kpi-cards/oracle-erp/inventory-value-by-inventory-org) | Which org is hoarding the slow-movers. | | [Inventory Turnover Ratio](/nerve-centre/kpi-cards/oracle-erp/inventory-turnover-ratio) | A falling turnover ratio is the macro signal; this card is the line-item detail. | | [Inventory Carrying Cost](/nerve-centre/kpi-cards/oracle-erp/oerp-inventory-carrying-cost) | What the slow-moving stockpile costs you per period to keep holding. | ## Reconciling against Oracle ERP Cloud **Where to look in Oracle ERP Cloud:** > **Navigator → Inventory → Reports → Inactive Items Report** (or Item Quantities On Hand with last-transaction date) > **Navigator → Cost Management → Reports → Slow Moving and Excess Inventory** (where the Cost Management slow-moving report is configured) > **Reports and Analytics → OTBI → Inventory Real Time Subject Area** (filter on Last Transaction Date older than 90 days) The Inactive Items Report run with a 90-day no-activity window should match the SKU list behind this card. OTBI filtered on Last Transaction Date is the most flexible way to reproduce the value, because it lets you join on-hand quantity, unit cost, and last-movement date in one subject area. Common mistakes when comparing against Oracle's own reports: * **Confusing item age with last-movement age.** An item received 200 days ago but issued last week has moved recently and is not a slow-mover. The card tests the last transaction date, not the receipt date. A report keyed on receipt date will overstate. * **Counting receipts as movement when your policy does not.** Some teams treat a receipt as movement; others only count outbound issues and sales. Confirm which transaction types your slow-moving definition includes. The card counts any inventory transaction as movement by default. * **Forgetting the on-hand filter.** An item that moved 120 days ago but is now at zero on-hand has no trapped cash and should not count. The card values only items still on hand. A report that lists all historic slow-movers will overstate the value. **Why our number may legitimately differ from Oracle's reports:** | Reason | Direction | Why | | ----------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Movement definition** | Either | The card counts any inventory transaction as movement. A report that counts only outbound issues will flag more items as slow. Align the transaction-type set. | | **Sync timing** | Either | Card is real-time; a scheduled Oracle report is as of its last run. An item that moved this morning clears the card immediately but not the overnight report. | | **Cost method per org** | Either | Average vs Standard Cost changes the value of the same flagged quantity. | | **ABC / category exclusions** | Card may be higher | If your slow-moving policy excludes spare-parts or service categories, configure the field map; otherwise the card includes them. | | **In-transit and reserved** | Either | Reserved-but-unmoved stock counts as on hand here. A report that nets out reservations reads lower. | ## Known limitations / merchant FAQs **What exactly counts as movement?** Any inventory transaction: a sale, an issue, a receipt, an inter-org transfer, or a cycle-count adjustment. If a SKU has had none of these in 90 days and still has on-hand quantity, it counts. By default a receipt counts as movement; if your policy only treats outbound activity as movement, the field map can narrow the definition. **Why 90 days and not 60 or 180?** Ninety days is the conventional first tripwire in Fortune 500 inventory governance: long enough to exclude normal seasonal lulls, short enough to act before recovery rates collapse. The 90-day window is the card definition; the sibling [Dead Stock Value](/nerve-centre/kpi-cards/oracle-erp/dead-stock-value) card handles the deeper, harder-to-recover cohort. **Are spare parts and slow-by-design items going to inflate this?** Yes, unless you exclude them. A replacement part you sell twice a year is correctly identified as slow-moving by the data but is not a problem by intent. Use ABC class or item category in the field map to carve out legitimate low-velocity categories before treating the total as actionable. **Does reserved stock count as slow-moving?** If it is reserved against an open Sales Order but has not physically moved in 90 days, yes, it still counts as on hand with no movement. The reservation does not reset the last-movement clock. Cross-reference open demand before acting. **How does this relate to dead stock?** Slow-moving is the early stage; dead stock is the terminal stage. This card catches inventory roughly 90 days before it lands on [Dead Stock Value](/nerve-centre/kpi-cards/oracle-erp/dead-stock-value), giving you a window to discount, transfer, or stop reordering while recovery is still economic. **The alert fired but our spare-parts business legitimately holds slow stock. Can we tune it?** Yes. The 10%-of-inventory-value trigger is the default. You can exclude designated low-velocity categories from the numerator so the alert measures only the inventory you consider genuinely at risk. **Does Average vs Standard Cost change the flagged list?** No, the list of flagged SKUs is driven by movement dates, not cost. Cost method only changes the dollar value attached to each flagged SKU and therefore the total. **Differences vs SAP slow-moving analysis?** SAP S/4HANA derives slow-moving and dead stock from last-movement dates in the material master and movement history; Oracle derives it from inventory transaction history per org. The concept is identical, the data model differs. Vortex IQ supports both. *** ### Tracked live in Vortex IQ Nerve Centre *Slow-Moving Items (>90d no movement)* is one of hundreds of KPI pulses Vortex IQ tracks across Oracle ERP Cloud and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.