SKUs with NetSuite-vs-Ecom Inventory Drift >5%, NetSuite

SKUs with NetSuite-vs-Ecom Inventory Drift >5% for NetSuite. Tracked in the Vortex IQ Nerve Centre, how to read it, why it matters, and how to act on it.

Metrics type: Key Metrics • Category: Cross-Platform: Revenue at Risk

Location-level NetSuite available vs ecom availability. Drives overselling on multi-channel SKUs.

At a glance

SKUs with NetSuite-vs-Ecom Inventory Drift >5% is a cross-platform: revenue at risk metric tracked from NetSuite data. It surfaces operational signal so you can spot regressions, opportunities, and structural patterns. Cross-reference the sibling cards below for the full diagnostic picture. This is a cross-platform card: it joins NetSuite to a sibling connector to surface insight neither shows alone. Gated: renders only when has_ecommerce_sibling.

What it counts	Location-level NetSuite available vs ecom availability. Drives overselling on multi-channel SKUs.
Sample type	Backend API data from NetSuite, refreshed on the standard data refresh.
Why it matters	The metric appears in the Cross-Platform: Revenue at Risk category and complements the sibling cards listed below. Track movement over time to identify regressions or opportunities.
Reading the value	Compare the current period to the prior period to read direction. Cross-reference siblings to triangulate cause.
Format	number
Time window	RT/24H
Alert trigger	>10 SKUs drifting
Sentiment key	erp_inventory_variance_pct
Roles	owner, finance, operations

Calculation

Calculated automatically from your NetSuite data on the standard refresh. See the At a glance summary for what it tracks and the worked example below for a typical reading.

Worked example

A representative reading of SKUs with NetSuite-vs-Ecom Inventory Drift >5% for a typical NetSuite account. The card reports the current value alongside a comparison against the previous period, direction matters. When it moves outside the expected range, cross-reference the siblings below to find the cause; use Vortex Mind to trace upstream causes and Ask Viq for natural-language exploration.

Sibling cards merchants should reference together

Card	Why merchants reach for it
ns_xc_order_invoice_reconciliation	Cross-Platform: Revenue at Risk sibling: Ecom Orders Missing Matching NetSuite Cash Sale / Invoice.
ns_xc_customer_master_drift	Cross-Platform: Revenue at Risk sibling: Ecom Customers Absent from NetSuite Customer Record.
ns_xc_aged_receivables_credit_risk	Cross-Platform: Revenue at Risk sibling: AR Aging on Customers with Active Ecom Orders.

Reconciling against the vendor’s own dashboard

Where to look in NetSuite’s own dashboard: find this metric (or its components) under the relevant report/section. Confirm the period boundaries and any filters match the Vortex IQ profile to reconcile cleanly. The Vortex IQ value may legitimately differ due to period definition, time zone, sampling, or how the vendor buckets the underlying records.