Skip to main content
Metrics type: Cross-Platform Metrics • Category: Ecommerce Platform
Items with open Sales Order demand but zero on-hand. The morning purchasing queue, ranked by Sales Order value.

​
At a glance

SKUs with open Sales Order demand but zero on-hand inventory. Each row is a SKU with the SO dollars at risk plus the open SO count. The morning purchasing queue, ranked by SO value descending. The mirror of Dead Stock with Active Ad Spend: under-stocked + has demand vs over-stocked + over-promoted.

​
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 industrial-supply distributor on Oracle ERP Cloud. Snapshot 14 Apr 26. Top 8 OOS-with-SO-demand cases: Total revenue at risk: $824,400 across 16 SKUs (top 8 shown). Five things to notice:
  1. $284K of revenue is blocked on roller bearings. A PO was placed 02 Apr 26 with 21-day lead time, so arrival ETA is ~23 Apr 26. Customer SOs are dated 04 Apr to 12 Apr; if delivery commitments are firm at order date + 14 days, there is risk on the older SOs.
  2. FILT-ECON-LRG and SEAL-VITON-50MM have NO PO placed. This is the actionable signal. Purchasing missed the demand or the system did not trigger a reorder. Drill into the Low Stock Alerts card to confirm reorder logic.
  3. PUMP-CENT-2KW has a 45-day lead time and no PO. This is the highest-risk row: $98K of demand and over a month of sourcing time. Customer service likely needs to communicate revised delivery dates.
  4. The cross-platform angle: Cross-reference Inventory Sync Drift. If commerce platform was showing these SKUs as in-stock when Oracle had zero, the customer order experience just took a hit, and you may have new orders coming in for items that cannot ship.
  5. Action playbook: Place expedite POs on the no-PO rows immediately. Communicate revised dates to customers on long-lead items. For high-volume items, review the Min/Max planning rules in Oracle Inventory Cloud to ensure auto-reorder triggers are tight enough.

​
Sibling cards merchants should reference together

​
Reconciling against the vendor’s own dashboard

Where to look in Oracle ERP Cloud:
Inventory → Reports → Stock Out Items with Demand Order Management → Manage Orders filtered to inventory-hold reasons OTBI → custom analysis joining Inventory Real Time + Order Management Real Time
Why our list may legitimately differ: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

Why is this a hero / kill-shot card? Because it surfaces the exact dollar value of revenue that is blocked due to inventory shortage, with PO status visible. Most ERPs surface the OOS view OR the open-SO view but not the intersection. The intersection is what Operations needs. Why include in-transit or back-order considerations? Configurable. Default: in-transit excluded (safer for commitment). If your merchant’s sales process commits delivery against in-transit, the field map can include. Multi-warehouse, can a SKU be OOS in one warehouse and in stock in another? Yes. The card flags by inventory-org level. A SKU with stock in Warehouse A but zero in Warehouse B (where the SO is sourced) appears here. Drill-down shows per-warehouse. Can Vortex IQ trigger expedite POs? Surfaces the candidates; PO placement is a Procurement decision. Ask Viq can route to Procurement with the row context. Differences vs SAP / NetSuite? Same logic. Vortex IQ supports all three.

​
Tracked live in Vortex IQ Nerve Centre

OOS with Open Sales Order Demand 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 or book a demo to see this metric running on your own data.