> ## 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. # Inventory AvailableQuantity Went Negative, Oracle ERP Cloud > Inventory AvailableQuantity Went Negative is a live alert feed that fires when any item's available on-hand quantity in Oracle Inventory Cloud drops below zero. **Card class:** [Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > A live alert feed: any item whose available on-hand quantity in Oracle Inventory Cloud has gone below zero. Negative available stock signals a transaction-sequencing or integration error and drives oversell and costing problems. ## At a glance > Inventory AvailableQuantity Went Negative is a real-time alert feed, not a trend KPI. It watches on-hand availability across your Oracle Inventory Cloud inventory organisations and raises an entry the instant any item-subinventory combination shows a negative available quantity. On-hand should never legitimately fall below zero: a negative balance means a transaction posted out of sequence (an issue or shipment recorded before the matching receipt) or an integration wrote a bad quantity. Left unattended, negative available quantity corrupts costing, lets the commerce platform oversell stock you do not have, and distorts every downstream availability calculation. Each row in the feed is one item that has crossed below zero so operations can chase the specific transaction that caused it. | | | | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | Each row is one item / inventory-organisation (and where relevant subinventory or lot) combination whose available on-hand quantity in Oracle Inventory Cloud is currently below zero. The feed lists the item, the inventory org, the negative quantity, and when it crossed zero. | | **Why it should never happen** | Available on-hand is a physical count. A negative value is not a real position; it is the symptom of a transaction posted out of order or an integration error writing an invalid quantity. It is always an exception, never normal variance. | | **Business Unit scope** | Respects the dashboard's selected Business Unit and inventory-organisation filter. By default watches every inventory org the connected role can see. | | **Time window** | `RT` (real-time alert feed, re-evaluated each sync) | | **Alert trigger** | `any item AvailableQuantity < 0` - a single negative item raises a feed entry | | **Roles** | owner, operations, engineering | ## 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 Fortune 500 omnichannel retailer runs Oracle Inventory Cloud across two fulfilment inventory organisations, US-DC-EAST and US-DC-WEST, feeding a Shopify Plus DTC channel through Oracle Integration Cloud (OIC). On 14 Mar 26 a warehouse integration replayed a batch of shipment confirmations before the matching receipt transactions landed, and three items dropped below zero on-hand. | Item | Inventory org | Available quantity | Likely cause | | ---------------------------- | ------------- | ------------------ | -------------------------------------------- | | SKU-44120 (Wireless Earbuds) | US-DC-EAST | -84 | Shipment confirmations posted before receipt | | SKU-90711 (Travel Mug) | US-DC-EAST | -12 | Same replayed batch | | SKU-22305 (Yoga Mat) | US-DC-WEST | -3 | Cycle-count adjustment posted twice | Four things to notice: 1. **None of these are real physical positions.** You cannot ship 84 more earbuds than exist. The negative value is a sequencing artefact: the shipment was recorded before the receipt that should have preceded it. The physical stock is fine; the transaction record is not. 2. **The commerce platform will oversell against it.** Until availability is corrected, Oracle still reports a position that downstream systems read. Pair this feed with [SKUs with Fusion-vs-Ecom Inventory Drift >5%](/nerve-centre/kpi-cards/oracle-erp/skus-with-fusion-vs-ecom-inventory-drift-5) to see whether the negative has already pushed the storefront out of parity. 3. **Costing is affected.** Cost Management values issues and receipts against on-hand layers. A negative quantity breaks the cost layering, so COGS and inventory valuation can both go wrong until the sequence is repaired. That is why engineering sits alongside operations on the role list; the root cause is usually an integration or sequencing defect. 4. **The feed clears as each item is corrected.** Once the missing receipts post or the duplicate adjustment is reversed in Oracle, availability returns to a valid non-negative value and the row drops out on the next sync. ## Sibling cards merchants should reference together A negative on-hand is an inventory-integrity break. Pair this feed with the cards that show its downstream effects and related stock issues. | Card | Why pair it with Inventory AvailableQuantity Went Negative | | ----------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- | | [SKUs with Fusion-vs-Ecom Inventory Drift >5%](/nerve-centre/kpi-cards/oracle-erp/skus-with-fusion-vs-ecom-inventory-drift-5) | A negative on-hand almost always pushes the SKU out of parity with the storefront. Read the two together. | | [ERP vs Ecom Inventory Variance](/nerve-centre/kpi-cards/oracle-erp/erp-vs-ecom-inventory-variance) | The broader variance picture across all items, of which a negative is the worst case. | | [Low Stock Alerts](/nerve-centre/kpi-cards/oracle-erp/low-stock-alerts) | A false negative can mask a genuine low-stock position, or invent one. | | [OOS with Open Sales Order Demand](/nerve-centre/kpi-cards/oracle-erp/oos-with-open-sales-order-demand) | Negative availability is often what tips an item into an out-of-stock state against live demand. | | [OIC Integration Flow Failures (24h)](/nerve-centre/kpi-cards/oracle-erp/oic-integration-flow-failures-24h) | If an integration wrote the bad quantity, the failed or out-of-order flow shows here. | | [Total Inventory Value](/nerve-centre/kpi-cards/oracle-erp/oerp-total-inventory-value) | Negative quantities distort the valued total until corrected. | | [Oracle Fusion Health Score](/nerve-centre/kpi-cards/oracle-erp/oracle-fusion-health-score) | The composite that an inventory-integrity break drags down. | ## Reconciling against Oracle ERP Cloud **Where to look in Oracle ERP Cloud:** The closest native equivalents in the Oracle Fusion UI are: > **Navigator → Supply Chain → Inventory Management → Manage Item Quantities** (on-hand and available by item and organisation) > **Inventory Management → Review Completed Transactions** (the transaction history that drove the balance below zero) > **Reports and Analytics → OTBI → Inventory Management → Inventory On-hand Balance Real Time** Manage Item Quantities shows current available on-hand per item and inventory org. Any item showing a negative there is what this feed surfaces. The Review Completed Transactions page is where you trace the out-of-sequence issue or duplicate adjustment that drove it negative, which is what operations and engineering need to repair the balance. Common mistakes when comparing against Oracle's own reports: * **Reading on-hand instead of available.** On-hand and available differ once reservations and transfers are in play. The feed tracks available quantity; compare against the same column in Oracle. * **Wrong inventory organisation.** A SKU can be positive in one org and negative in another. The feed spans every org in scope; a single-org query understates. * **Looking after a correction.** If the missing receipts have already posted, Oracle now shows a valid balance while the feed still shows the prior negative until the next sync. **Why our number may legitimately differ from Oracle's reports:** | Reason | Direction | Why | | ----------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------- | | **Available vs on-hand definition** | Either | The feed uses available quantity, net of reservations. An Oracle on-hand view that ignores reservations can read differently. | | **Inventory-org scope** | Either | The feed aggregates every inventory org in the filter; a single-org Oracle query shows fewer rows. | | **Sampled at sync** | Card lagging | If a corrective receipt posts between syncs, the feed shows the prior negative until the next refresh. | | **Subinventory vs org roll-up** | Either | A net-positive org can still hold a negative subinventory or locator; the feed surfaces the level it is configured to watch. | ## Known limitations / merchant FAQs **Is this a trend chart or an alert list?** An alert list. Each entry is a specific item that has gone below zero on available on-hand. The feed clears row by row as each item is corrected back to a valid balance. There is no trend number to watch; the target is an empty feed. **How can available quantity ever go negative?** It should not represent a real position. A negative value almost always means a transaction posted out of sequence (a shipment or issue recorded before its matching receipt) or an integration wrote an invalid quantity. The physical stock is usually fine; the transaction record is wrong. **Does a negative balance mean we oversold?** Not necessarily, but it creates the conditions for it. While Oracle reports a corrupted position, downstream systems including the commerce storefront read from it, so the SKU can be sold against a number that is not real. That is why parity with the storefront is a sibling card to read immediately. **Why is engineering on the role list?** Because the root cause is usually technical: an out-of-order integration replay, a duplicated transaction, or a sequencing defect in the inbound flow. Operations owns the physical correction; engineering owns fixing the integration so it does not recur. **Can Vortex IQ fix the negative balance?** No. Correcting inventory transactions is a controlled action inside Oracle Inventory Cloud, under your inventory-control policy. Vortex IQ detects the negative in real time, names the item and org, and notifies owner, operations, and engineering. Your team posts the corrective transaction in Oracle. **Does costing recover automatically once the balance is fixed?** Once the missing receipts post or the duplicate is reversed, Cost Management re-establishes valid on-hand layers and costing returns to normal going forward. Any COGS or valuation already recorded against the corrupted layer may need a controlled adjustment; your finance team handles that inside Oracle. *** ### Tracked live in Vortex IQ Nerve Centre *Inventory AvailableQuantity Went Negative* 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.