ERP-vs-Ecom Inventory Variance %, Sage

Percentage variance between Sage Intacct on-hand inventory and the ecommerce platform’s stock count. Intacct Inventory module required.

​

At a glance

The headline parity number between your book-of-record (Sage Intacct Inventory Control on-hand quantity) and your selling channel (Shopify, BigCommerce, or Adobe Commerce stock count), expressed as a single percentage across the catalogue. When this number drifts above the alert line, you are either overselling stock you do not have or hiding stock you could be selling, and both cost money. The card requires the Sage Intacct Inventory module; Sage Accounting, Sage 50, and Sage 200 standard do not ship a perpetual inventory ledger, so the card hides itself for those merchants rather than showing a misleading zero.

​

Calculation

​

Worked example

1. The headline 6.8% is not one problem, it is three different problems with three different owners, and the card’s value is splitting them apart. A single percentage on a gauge tells you something is wrong; the SKU drill tells you what to do. The seasonal bulbs (received into Intacct, not yet listed on the storefront) are a merchandising backlog, not a data integrity fault. The discontinued furniture showing more on the storefront than in Sage is an active oversell risk and needs same-day attention. The wholesale-only pallets are correct as designed and should be excluded from the parity calculation through the field map. Three findings, three teams, one card.
2. The discontinued furniture cohort is the dangerous one even though it is small. 38 SKUs where the storefront shows 980 units against Sage’s 410 means the channel will accept roughly 570 orders it cannot fulfil. Each of those becomes a cancelled order, a refund, a support ticket, and a customer who may not return. This is the negative-variance, oversell-risk case, and it is exactly what SKUs with Intacct-vs-Ecom Inventory Drift >5% drills into at the line-item level. The catalogue gauge flagged the problem; the SKU table makes it actionable.
3. The seasonal bulbs inflate the headline without representing a real defect. 9,600 units sitting in Intacct with zero on the storefront because the listing has not gone live yet reads as 100% variance on those 120 SKUs and pulls the catalogue weighted figure up. This is why the card reports unmatched and not-yet-listed SKUs separately: the operations lead can see the bulbs are a “go list these” task, not a “fix the sync” task. Once listed, the variance on that cohort collapses to near zero.
4. The wholesale-only pallets should be carved out, not counted. 210 SKUs sold only through the Adobe Commerce wholesale portal and deliberately never synced to the Shopify DTC catalogue will always read as variance against the DTC channel. The field map supports a per-SKU or per-Class channel_scope exclusion so the parity number reflects only SKUs that are supposed to be in parity. Leaving them in permanently parks the gauge above the alert line and trains the team to ignore it, which is the worst outcome.
5. Pair the catalogue gauge with the dollar value to size the exposure. 6.8% quantity variance sounds tolerable until you weight it by value. The 38 discontinued furniture SKUs drifting on the oversell side are low-value clearance items; the parity problem there is reputational (cancelled orders) more than financial. If the same 6.8% had landed on the bestseller planters, the dollar exposure through Sage Total Inventory Value would be an order of magnitude larger. Always read the gauge next to the value card before deciding how hard to push.

​

Sibling cards merchants should reference together

​

Reconciling against Sage

Reports → Inventory Control → Item Stock Status (real-time on-hand by Warehouse, the canonical Intacct on-hand figure this card uses as its book-of-record basis) Reports → Inventory Control → Inventory Valuation (on-hand quantity and value per Location at the same scope as the dashboard filter) Inventory Control → Items list with the on-hand column exposed, filtered to active items, exported to compare against the ecommerce stock export Interactive Custom Report (ICR) built on the Inventory data source listing ItemID, QuantityOnHand, and WarehouseID to align against the storefront’s stock export by SKU

• Available-to-sell vs on-hand. Intacct on-hand includes committed and allocated stock; the ecommerce platform usually shows available-to-sell (on-hand minus committed). Comparing on-hand against available-to-sell manufactures drift. The field map aligns the definitions; confirm which basis each side uses.
• Multi-location aggregation. Intacct holds on-hand per Warehouse Location. The storefront typically shows a single number. If your fulfilment only ships from two of five Intacct locations, summing all five overstates the storefront’s effective availability. The field map can scope which locations feed the sellable basis.
• Unit of measure mismatch. A SKU stocked in cases in Intacct but sold in eaches on the storefront will read as a large false variance until the UOM conversion is mapped.

​

Known limitations / merchant FAQs

​

Tracked live in Vortex IQ Nerve Centre