SKUs whose on-hand count differs between Oracle ERP Cloud (system of record) and commerce platform. Sync-failure detector.
At a glance
SKUs whose on-hand count in Oracle Inventory Cloud (system of record) differs from the commerce platform’s available-to-sell count. Sync-failure detector. Each row is a SKU with Oracle qty, commerce qty, drift, and last sync timestamp.
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 home-goods retailer on Oracle ERP Cloud + Shopify Plus + Adobe Commerce. Snapshot 14 Apr 26. 12,400 SKUs mapped between Oracle and the two commerce platforms.
Top 3 drift cases:
Five things to notice:
- 184 SKUs where Oracle has more than commerce. Commerce is understating availability. Lost sales risk: customers see “out of stock” on commerce when warehouse has stock. Cause: stuck inventory sync from Oracle to commerce.
- 92 SKUs where commerce has more than Oracle. Commerce is overstating availability. Overselling risk: customers can place orders that warehouse cannot fulfil, leading to refunds, customer complaints, NPS hit. Cause: stuck inventory deduction from commerce back to Oracle (orders shipped but inventory not deducted in commerce mirror).
- The FURN-SOFA case is the most painful. Oracle has 248 units; commerce shows 0; the Shopify Plus storefront marked it as out-of-stock. 14 hours of lost ad-driven traffic and lost sales on a $1,400-MSRP item.
- Cause analysis: Most drift originates from Oracle Integration Cloud (OIC) inventory-sync flow failures. OIC’s monitoring shows individual integration runs but does not surface the cumulative business impact. Vortex IQ does.
- Action playbook: Prioritise high-drift, high-value SKUs. Force-resync from Oracle. Audit OIC’s inventory-sync health. Consider implementing a freshness-check alert: if commerce inventory has not been updated in 6+ hours, flag.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look:Oracle Inventory Cloud → Manage Item Quantities (Oracle truth) Commerce platform admin → Products → Inventory (commerce truth) OIC → Monitoring → Inventory Sync Integration (the integration health view)OIC’s monitoring shows individual sync runs; this card aggregates the resulting state drift into a business view. Why our list may legitimately differ:
Cross-connector reconciliation:
This IS the cross-connector card. Pairs Oracle on-hand with commerce-platform availability for each mapped SKU.