Skip to main content
Card class: Cross-Channel • Category: Ecommerce Platform
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.
What it countsWHERE oracle.on_hand != commerce.available_to_sell for each SKU mapped between the two systems. Threshold filter (default 5 units) suppresses noise from minor cycle-count drift.
Currencyn/a (unit-count metric).
ChannelsAll connected commerce platforms (Shopify, BigCommerce, Adobe Commerce, Salesforce Commerce Cloud).
Time windowReal-time snapshot.
Alert triggerany SKU drift >5 units
Rolesowner, 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 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.
Drift typeSKU countAvg drift
Oracle higher than commerce (commerce understates availability)184-22 units
Commerce higher than Oracle (commerce overstates availability)92+18 units
Total drift SKUs276
Top 3 drift cases:
SKUOracle qtyCommerce qtyDriftLast syncRisk
FURN-SOFA-3SEAT-GREY2480-24814 hours agoLost sales (commerce oversold then ran out, switched off)
FURN-RUG-12X8064+642 days agoOverselling risk (commerce will accept orders we cannot fulfil)
LAMP-FLOOR-BRASS84142+5818 hours agoOverselling risk
Five things to notice:
  1. 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.
  2. 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).
  3. 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.
  4. 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.
  5. 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

CardWhy pair it with Inventory Sync Drift
Total Inventory ValueOracle-side truth.
OOS with Open SO DemandIf commerce showed it as available but warehouse is OOS, that is the overselling outcome.
Low Stock AlertsWhen sync drift means commerce sees stock that is actually depleted.
Commerce-platform inventory cardsThe other side of the drift.

​
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:
ReasonDirectionWhy
Reservation logicEitherOracle on-hand minus reservations vs commerce available-to-sell. The card uses available-to-sell (post-reservation) on both sides for parity.
Multi-warehouse aggregationEitherCommerce may show the merchant’s website availability; Oracle sums across multiple warehouses. Field map controls aggregation.
Sync windowCard flags during in-flight syncCommerce update lags Oracle by minutes during sync; minor drift is expected.
Cross-connector reconciliation: This IS the cross-connector card. Pairs Oracle on-hand with commerce-platform availability for each mapped SKU.

​
Known limitations / merchant FAQs

Should the drift ever be zero? At any given moment a few units of drift is normal due to sync timing (commerce update lags Oracle by minutes). Persistent drift beyond the threshold (default 5 units) means a sync failure or process gap. Multi-warehouse, how does aggregation work? Configurable. Default: commerce shows webstore-fulfillable availability; Oracle aggregates the warehouses tagged as commerce-fulfillment. Drill-down shows per-warehouse. OIC sync failures, where do I see them? OIC monitoring console shows the integration runs. This card surfaces the resulting business-state drift, which is what Operations should care about. Auto-resync from this card? Configurable per workspace. Default: surfaces the drift, lets a user trigger force-resync via Ask Viq. Auto-resync without human review is risky if the drift indicates a deeper data issue. My commerce platform shows real-time availability via API; is this card real-time too? Vortex IQ reads both sides every 5-15 minutes. Within that window the card is current. For sub-minute real-time, the commerce platform’s own API and Oracle’s Manage Item Quantities are live. SAP equivalent? Same logic for SAP S/4HANA + commerce platforms. Vortex IQ supports both.

​
Tracked live in Vortex IQ Nerve Centre

Inventory Sync Drift 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.