OOS with Open Order Demand, Sage

Card class: Cross-Channel • Category: Ecommerce Platform

Items with open Order demand but zero on-hand. The morning purchasing queue, ranked by Order value.

​

At a glance

Items with open Sage Intacct Order demand (committed via Order Entry) but zero or below-demand on-hand inventory. The morning purchasing queue, ranked by Order value at risk. The kill-shot view: show me every dollar of customer-promised revenue that is currently un-fulfillable because the warehouse is empty. The Operations team’s first read at 9am. Pair this card with Inventory Sync Drift for the over-sell-risk twin.

​

Calculation

Calculated automatically from your Sage 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 B2B distributor on Sage Intacct Multi-Entity Console. Two trading entities (US, Canada), four Locations (NJ-Primary, TX-Secondary, ON-Canadian, plus a CA-Reserve drop-ship Location). BigCommerce B2B Edition for the B2B book, Shopify Plus for D2C. Reading: real-time on 02 May 26 at 9:00 ET. Headline: 12 Items with open Order demand exceeding on-hand. Total un-fulfillable demand: $184,200. Largest single Item at risk: WIDGET-PRO-A at$42,800 across 8 Customer Orders. Top 8 OOS-with-demand cases: Five things to notice:

1. WIDGET-PRO-A’s $42,800 of un-fulfillable demand across 8 Customer Orders is the priority row, and the killer Sage Intacct insight is that the largest single Customer (Acme Corp at$18,400) sits inside the Top Customers worklist on Intacct’s CRM module. This means the Operations team’s choice is not just “expedite or apologise”; it is “which Customer relationship are we willing to risk?”. The Vortex IQ dimensional cut surfaces the Customer dimension on each row, so the Operations Lead can see at-a-glance whether the at-risk demand concentrates in strategic accounts or trickles across small Customers. If Acme Corp is a top-20 strategic account (visible on the Top B2B Accounts by Revenue sibling card), the action is to expedite PO #PO-2026-441 by air freight, which costs $1,800 in extra freight to protect$18,400 of revenue and a top-20 relationship. If Acme is small, the action is a polite delay-notification email.
2. GADGET-2026-X’s $28,400 with no PO placed is the avoidable-shortfall row. This is a new SKU (the same SKU that appears as an unmapped-orders cause on the Unmapped Orders card). The merchandiser launched it on the storefront, accepted 84 units of demand, and never placed a Purchase Order with the supplier because the Item record in Intacct’s Inventory Control module had not been linked to a Vendor. Recovery: place the PO immediately (4-week lead time on this product, so air freight expedite is required). Systemic fix: every new Item in Intacct should have a default Vendor and a min-PO trigger configured before the SKU is allowed live on commerce.
3. KIT-VEGA-2026’s partial-fulfilment row is the kit-handling case. 72 units of demand, 12 units on-hand. The Operations playbook should be: ship the 12 units against the oldest 12-unit-equivalent Orders today (this protects the oldest Customer wait), and place a PO replenishment for the remaining 60 units. The card surfaces the Order ages, which makes the FIFO decision automatic. Without the card, the Operations team typically ships against the largest Customer regardless of Order age, which is the wrong fairness model.
4. SEASONAL-Q2’s $18,400 of demand is the discontinued-Item issue. This is a SKU that Intacct shows as discontinued (active = false), but the commerce-side discontinuation has not propagated, so 145 units of customer demand sit against zero stock with no replenishment plan. Recovery: cancel the 145 units of Orders politely (with a substitute offer) within the next 24 hours. Systemic fix: the discontinuation workflow should auto-pause the SKU on commerce before any new demand can accrue. This row also appears on the Inventory Sync Drift card with 12 units of phantom commerce-side stock; the two cards are diagnostic twins.
5. MIN-COMPONENT is the project-dimension finding (1,420 units of demand from Foxtrot Group, tagged to Project PRJ-VEGA-2026). This is component demand for a project in the Implementation Services workflow, not a retail SKU. The Operations team’s playbook is different: Project-tagged demand needs to be reviewed with the Project Manager, because the project plan itself may have flexibility on the component delivery date. The Vortex IQ dimensional cut surfaces the Project tag in one click, where in NetSuite or SAP S/4HANA the same finding would require a separate Project-module query. For project-based services merchants, this is the killer Sage Intacct dimensional value.

Net operational impact: the 12 OOS-with-demand rows decompose into 5 expedite-PO actions ($94,400 of demand, recoverable inside 7-14 days), 3 cancel-or-substitute actions ($46,200 of demand, must be communicated to the Customer within 24 hours), 2 partial-fulfilment actions ($34,200 of demand, ship today against the oldest Orders), and 2 Project-dimension actions ($9,400 of demand, route to the Project Manager for plan review). The Operations Lead’s morning is structured by this card; without it, the same Operations Lead would spend 2 hours building the same view from Intacct’s Open Orders by Item report, the per-Item Stock Status report, the Customer master, and the Vendor / PO module, then making judgement calls without the dimensional context. This is the operational telemetry that no Implementation Partner pack and no commerce-platform inventory report can deliver alone. Sage Intacct’s strength on this card is the dimensional decomposition: every row carries its Customer, Item, Location, Class, and Project tag, so the Operations playbook is implicit in the data. The card surfaces the data; the playbook is one click away.

​

Sibling cards merchants should reference together

​

Reconciling against the vendor’s own dashboard

Where to look in Sage Intacct: The closest native equivalents in the Intacct UI are:

Reports → Order Entry → Open Orders by Item (the Order-side denominator) Reports → Inventory → Stock Status by Item (the on-hand side) Interactive Custom Report (ICR) that joins the two: Item + Location + open-Order-quantity + on-hand. The Implementation Partner can build this ICR in 60 to 90 minutes; once built, it becomes the morning purchasing-queue report Reports → Inventory → Reorder Recommendations is conceptually related but uses min/max reorder points, not committed-Order demand

The Implementation Partner pattern: most Partners run the Open-Orders-by-Item report weekly (or at month-end during the close pack), not in real-time. The Operations team builds an internal spreadsheet from the export and works it. Vortex IQ promotes this from weekly to real-time, with dimensional decomposition. Why our list may legitimately differ from a manual cross-check: Cross-connector reconciliation: This card IS the operational kill-shot for Sage Intacct merchants. Its value comes from joining Order Entry (commerce-driven demand) and Inventory Control (warehouse on-hand) in real-time, with dimensional tagging that makes the Operations playbook implicit. NetSuite, Oracle ERP Cloud, and SAP S/4HANA all expose similar data, but none of them surface the dimensional join (Customer + Item + Location + Class + Project on every row) as cleanly as Sage Intacct’s first-class dimensional model. For multi-Location, multi-Class, multi-Project mid-market merchants, this card is one of the strongest reasons to choose Intacct as the financial spine and Vortex IQ as the cross-stack telemetry.

​

Known limitations / merchant FAQs

My OOS-with-demand list is huge (50+ Items). Where do I start? Sort by demand-dollar descending and work the top 10. The Pareto rule applies: the top 10 of 50 typically account for 70 to 80% of the un-fulfillable demand dollars. Within the top 10, sort by Customer dimension to identify any concentration in a strategic account; those rows go first. The card supports both sorts directly. A row shows 0 on-hand and 22 units of demand, but the warehouse staff swear there is stock. What is happening? Three possibilities: (1) the on-hand figure is stale (Intacct sync hasn’t run since the last receipt; force-refresh), (2) the Item is in a Location not configured for the demand-side commerce channel (the Operations team sees stock at TX-Secondary but the BigCommerce demand routes to NJ-Primary; cross-reference Inventory Sync Drift), or (3) the stock is committed to an earlier Order in the FIFO queue (the visible on-hand is already promised). The card surfaces each cause via the dimensional tags. How do I handle Project-dimension demand? Route it to the Project Manager rather than treating it as urgent operational demand. Project-tagged Orders typically have flexible delivery dates inside the project plan; the project manager can re-sequence component delivery without customer notification. The Sage Intacct Project dimension is exactly this kind of separator; the card surfaces the tag so the Operations team knows to escalate rather than expedite. Multi-Entity Console: do I run this card per entity or consolidated? Per entity, almost always. Demand is tagged to a Customer and Customers are tagged to entities; Locations are entity-scoped. Aggregating across entities mixes US-warehouse stock visibility with Canadian-warehouse stock, which is not how the Operations team works. The card defaults to per-entity views; pivot via the dashboard filter. My discontinued SKUs keep showing here. How do I suppress them? Two options: (1) configure the discontinuation workflow so that Intacct’s active = false flag immediately propagates to commerce as available_for_purchase = false, preventing new demand; (2) add a field-map filter that excludes Items with active = false from this card. The second is faster but masks the real issue (stale demand against discontinued SKUs); the first is the systemic fix. Can I auto-cancel low-priority Orders against OOS Items? Yes via Ask Viq, with explicit authorisation. Vortex IQ supports a “cancel and notify” action that posts an Order cancel against a configurable filter (e.g. “all Retail D2C Class Orders against discontinued Items, with substitute offer”). Most merchants prefer to cancel manually for the customer-experience side; the action is supported for high-volume scenarios. Backorder-allowed Items keep showing here. Is that right? Default behaviour is to include all Items; if your operational model allows backorders as routine, configure the field map to exclude allow_backorder = true Items from this card. The trade-off: hidden-backorder Items can sit at risk of supplier delay if you are not separately monitoring the backlog. Most merchants configure two cards: this one with backorders excluded, and a separate Backorder Aging card to monitor the supplier-fulfilment side. Sage Intacct Order Entry vs Order Management module: which feeds this card? Order Entry. The Order Management module (a higher-tier Intacct add-on) extends Order Entry with allocation rules, advanced shipping, and multi-warehouse routing; the card reads from the underlying Order Entry data so it works on both standard and Order-Management configurations. REST vs XML API freshness? Both are used. The XML API for the bulk Open-Orders-by-Item read; REST for incremental Order events. The card refreshes on both Order events (new Order placed, Order shipped) and Inventory events (PO received, Inventory Adjustment posted), so the freshness is event-driven rather than poll-driven on most workspaces. My Implementation Partner runs the purchasing queue weekly. Does this card replace their workflow? It augments rather than replaces. The Partner’s weekly review is good for systemic patterns (which Vendors are slipping, which Items are routinely understocked, where the supply chain has drift). This card is good for daily operational telemetry (what is at risk right now, which Customer is affected, which PO needs expediting). Both are useful; the daily telemetry is what Sage Intacct does not natively expose. Sage Intacct vs NetSuite on this card? NetSuite has SOs Blocked on Inventory which is the equivalent metric. The Sage Intacct version is decomposed by more dimensions out of the box (Project, Class, Location, Customer all queryable in one read), where in NetSuite the same decomposition typically requires a SuiteAnalytics workbook. For services-heavy or multi-Class merchants, Intacct’s read is faster; for single-Class, single-Location B2B distribution, both behave similarly. **The card shows Canadian-sub Items with USD demand $. How is FX handled?** Each Item's demand$ is shown in the booking entity’s currency natively (Canadian sub Items in CAD), with a separate consolidated USD column for the cross-entity total. The card respects whichever currency the user pivots into via the dashboard filter.

---

​

Tracked live in Vortex IQ Nerve Centre

OOS with Open Order Demand is one of hundreds of KPI pulses Vortex IQ tracks across Sage 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.