Percentage variance between on-hand quantities in Oracle Inventory Cloud and the quantities published on the ecommerce platform. A drift gauge; over 5% means oversell risk or phantom stockouts.
At a glance
The percentage difference between the on-hand quantities Oracle Inventory Cloud believes you hold and the quantities your ecommerce platform is advertising as available to buy. This is a cross-channel integrity gauge, and it is one of the most operationally dangerous numbers in the whole connector. When the two systems disagree by more than a few percent you are either overselling, taking orders for stock you do not have, or showing phantom stockouts, refusing orders for stock you do have. The gauge turns red at over 5% variance because beyond that threshold the drift is large enough to cost real revenue or real customer trust.
| What it counts | The absolute percentage variance between Oracle on-hand quantity and the ecommerce-published available quantity, aggregated across the SKUs matched between the two systems. Expressed as a percentage of the Oracle on-hand base. The companion SKUs with drift over 5% card lists the offending items. |
| Currency | n/a. This is a unit-quantity variance expressed as a percentage. |
| Inventory Org scope | Respects the dashboard’s Business Unit and inventory-org filter, matched against the storefront(s) those orgs feed. Multi-storefront estates can scope per channel. |
| Time window | RT / 24H. Live gauge with a 24-hour drift trend so you can see whether variance is widening or a sync just caught up. |
| Alert trigger | >5%. When aggregate variance exceeds 5%, the Nerve Centre raises a finding, because beyond that level oversell and phantom-stockout risk become material. |
| 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 retailer running Oracle ERP Cloud plus Oracle Inventory Cloud as the system of record, feeding a Shopify Plus DTC storefront and an Adobe Commerce B2B portal. Gauge snapshot 12 Apr 26, 24-hour trend included.| SKU group | Oracle on-hand qty | Ecom published qty | Variance |
|---|---|---|---|
| Core fast-movers (top 200 SKUs) | 412,800 | 410,100 | -0.7% |
| Seasonal apparel | 88,400 | 96,200 | +8.8% |
| Drop-ship / vendor-fed lines | 54,200 | 61,900 | +14.2% |
| Clearance | 22,100 | 20,400 | -7.7% |
| Aggregate variance (this card) | 577,500 | 588,600 | 6.4% |
- Aggregate variance is 6.4%, above the 5% threshold, gauge red. The Nerve Centre raises a finding. At 6.4% drift the storefronts are advertising materially more stock than Oracle believes exists, which is an oversell exposure heading into the weekend.
- The danger is concentrated, not spread. Core fast-movers are healthy at -0.7%. The variance is driven by seasonal (+8.8%) and drop-ship lines (+14.2%). The aggregate gauge tells you there is a problem; the SKUs with drift over 5% card tells you exactly which items to fix first.
- A positive variance is oversell risk; a negative variance is phantom stockout. Drop-ship at +14.2% means the storefront is selling stock Oracle does not show on hand, classic oversell that ends in cancellations and refunds. Clearance at -7.7% means Oracle holds stock the storefront has hidden, lost margin on goods you could be selling.
- Drop-ship lines are the usual culprit. Vendor-fed inventory often syncs on a different cadence (or via a feed Oracle does not own), so the storefront and Oracle diverge fastest there. This is a sync-architecture problem, not a counting error, and it is worth isolating drop-ship from owned stock in the field map.
- Read the 24-hour trend before reacting. A 6.4% reading that is falling fast usually means a sync batch is catching up after a backlog and will self-correct. A 6.4% reading that is climbing means the integration is drifting and needs intervention now. The gauge plus trend together distinguish a transient from a real failure.
Sibling cards merchants should reference together
This gauge is the headline integrity signal between Oracle and your storefronts. Pair it with these to find the offending SKUs and understand the downstream risk.| Card | Why pair it with ERP-vs-Ecom Inventory Variance |
|---|---|
| SKUs with Fusion vs Ecom Inventory Drift >5% | The line-item list behind this gauge. The gauge tells you there is drift; this card tells you which SKUs. |
| Inventory Value by Inventory Org | Which org feeds the drifting storefront; helps localise the sync fault. |
| On-Hand Inventory Value (by Inventory Org) | The Oracle side of the comparison, valued. |
| Low Stock Alerts | A phantom stockout (negative variance) often hides real available stock that low-stock logic should not be hiding. |
| Slow-Moving Items (>90d no movement) | Drift on slow-movers is lower risk than drift on fast-movers; cross-reference to prioritise. |
| Oracle Fusion Health Score | Inventory-sync integrity feeds the overall connector-health composite. |
Reconciling against Oracle ERP Cloud
Where to look in Oracle ERP Cloud:Navigator → Inventory → Inquiries → Manage Item Quantities (on-hand by item and org, the Oracle side) Navigator → Inventory → Reports → Item Quantities On Hand (bulk on-hand snapshot) Reports and Analytics → OTBI → Inventory Real Time Subject Area → On Hand Quantity (by item, by org)Manage Item Quantities gives the live Oracle on-hand figure for a specific SKU and org, which is the number to compare against what the storefront is advertising for the same SKU. For a bulk reconciliation, the Item Quantities On Hand report or OTBI on the Inventory subject area gives the full Oracle side; export the storefront’s published availability and join on SKU to reproduce the variance. Common mistakes when comparing against Oracle’s own reports:
- Comparing on-hand against available. Oracle on-hand is gross; the storefront usually publishes available-to-sell, which nets out reservations, safety stock, and allocations. The card compares like for like using the connector’s configured availability basis; a raw on-hand vs published comparison can show a variance that is actually a reservation, not a drift.
- Mixing orgs. A storefront may be fed by one org or several. Comparing storefront availability against a single org when it is actually multi-org sourced will look like a large variance.
- Forgetting drop-ship and vendor-fed lines. Vendor-fed availability may never live in Oracle on-hand at all. Including those SKUs in an on-hand comparison overstates the variance; the field map should mark them.
| Reason | Direction | Why |
|---|---|---|
| On-hand vs available-to-sell | Either | The storefront publishes available; Oracle holds on-hand. The card compares on the configured availability basis; a naive comparison over-reports variance. |
| Safety stock and buffers | Storefront lower | A deliberate buffer held back from the storefront shows as a negative variance that is intentional, not a fault. |
| Sync latency | Either | A 24-hour trend distinguishes a transient sync lag from real drift. A batch catching up narrows the gap without any physical change. |
| Multi-org sourcing | Either | A storefront fed by several orgs must be compared against the combined orgs, not one. |
| Drop-ship / vendor-fed lines | Card may over-report | Vendor-fed availability may not exist in Oracle on-hand at all; mark these in the field map. |