Sales Orders held by inventory shortage or credit hold, ranked by revenue at stake. The morning unblocking queue.
At a glance
Sales Orders held by inventory shortage, credit hold, or workflow gating, ranked by revenue at stake. The morning unblocking queue every Controller and Operations lead works on at 9am.
| What it counts | Open SOs flagged with at least one of: OnHold = T, CreditHold = T, Backorder > 0 on any line, or Status = 'Pending Approval' for more than 24 hours. Each row shows reason, age, and revenue at stake. |
| Reason classification | Inventory hold (insufficient stock at the SO’s location), Credit hold (customer over credit limit or terms breached), Approval pending (>24h in Pending Approval), Custom workflow hold (extension fields). |
| Tax treatment | Net of tax. Amount column reflects pre-tax SO total. |
| Shipping | Included in the Amount column. |
| Refunds | n/a (pre-Invoice stage). |
| Currency | OneWorld: reporting currency at current FX. Single-subsidiary: native subsidiary currency. |
| Multi-subsidiary | Respects dashboard filter; defaults to all subsidiaries the role can read. |
| Time window | RT (real-time snapshot) |
| Alert trigger | >0 high-value blocked, where high-value defaults to >$10K per SO (configurable per workspace) |
| Sentiment key | blocked_so |
| Roles | owner, finance, operations |
Calculation
Calculated automatically from your NetSuite 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 wholesale distributor (Annual revenue ~$60M) on NetSuite OneWorld. Snapshot 14 Apr 26 at 9am ET.| SO # | Customer | Amount | Block Reason | Days blocked |
|---|---|---|---|---|
| SO-48201 | Acme Stores Inc | $84,000 | Credit hold (over limit by $12K) | 3 |
| SO-48189 | Birch & Co | $61,000 | Inventory hold (3 SKUs OOS) | 5 |
| SO-48177 | Continental Retail | $52,000 | Pending Approval (legal review) | 7 |
| SO-48155 | Dakota Outfitters | $44,000 | Inventory hold (1 SKU back-ordered) | 2 |
| SO-48142 | Evergreen Group | $38,000 | Credit hold (2 invoices > 60 days overdue) | 1 |
| (24 more rows under threshold) | various | $148,000 | mixed | varies |
| Blocked SO Value (this card) | $427,000 | |||
| of which High-Value Blocked (>$10K) | $279,000 |
- **12K over their 84K starts moving.
- $61K Birch & Co inventory hold is an Operations problem. 3 SKUs OOS on the SO. The card surfaces the SKUs (drill-down). Operations either expedites the PO, partial-ships, or substitutes. Each path has revenue and customer-experience implications.
- $52K Continental Retail in legal review for 7 days is the slow leak. Custom workflow gating doesn’t auto-resolve. The Controller pings General Counsel; if it’s stuck >14 days the customer typically cancels and orders elsewhere.
- $38K Evergreen Group credit hold is a structural signal. Two invoices > 60 days overdue means this customer is becoming an AR risk. Releasing the new SO without addressing the overdue might compound the problem. Pair with Customer Credit Utilisation.
- **The card sentiment alert fires at any value > 279K. That’s the morning unblocking queue, by definition.
Sibling cards merchants should reference together
| Card | Why pair it with Open SOs Blocked |
|---|---|
| Open SO Value | The full pipeline. This card is the blocked subset; together they show what fraction of pipeline is stuck. |
| Credit Hold Orders | The credit-block subset. Different remediation than inventory blocks. |
| Customer Credit Utilisation | Why customers go on credit hold. Predictive view. |
| Low Stock Alerts | Why SOs go on inventory hold. Pair to see whether stock-outs are causing the blocks. |
| Total Inventory Value | The macro-level inventory health. |
| SO to Invoice Lead Time | Blocks lengthen lead time directly. Track them together to attribute cause. |
| Overdue Invoices Value | Customers with overdue invoices are credit-hold candidates. Predictive linkage. |
| shopify.total_revenue / bigcommerce.total_revenue | Commerce inflow, if blocks are growing while inflow is steady, throughput is the problem. |
Reconciling against the vendor’s own dashboard
Where to look in NetSuite: There is no single native report. The closest manual approach:
Saved search: Transaction.Type = SalesOrd AND Status = 'Pending Approval' OR OnHold = T OR CreditHold = T, sorted by Amount descending.
Most NetSuite Admins build this on day one, then retire it when SuiteAnalytics dashboards came in. Vortex IQ runs the equivalent every 15 minutes and adds the reason classification.
Adjacent NetSuite reports that look related but aren’t:
- Backorder by Item: shows SKUs short, not the SOs blocked by them. Different unit.
- Customers Over Credit Limit: shows customers, not SOs. Useful for credit ops; not the operational unblock queue.
- Approval History: workflow-level audit trail, not a current-state dashboard.
| Reason | Direction | Why |
|---|---|---|
| 24-hour Pending Approval threshold | Card excludes fresh SOs | The card filters Pending Approval to SOs older than 24 hours, on the basis that approval is expected within a day. A bare saved search includes new SOs that aren’t actually stuck. |
| Custom hold flags | Either | Some accounts add custom check-box fields (“Pending Compliance”, “Awaiting CSR review”) that mark holds. The card respects them only if the field map registers them. |
| Backorder logic | Either | NetSuite’s Backorder logic depends on Inventory Location, Subsidiary, and Item record settings. A SKU “OOS” at the warehouse fulfilment location is fine if the SO routes from a different location. The card uses the SO’s commit-quantity field, which respects this. |
| Real-time vs cached refresh | Small | Card refreshes every 15 minutes; saved searches are on-demand. SOs released or newly held in between drift. |
| Card | Relationship |
|---|---|
| shopify.inventory_pending_orders (if available) | Commerce-side OOS allocation. A spike there often correlates with inventory-hold rises here within 24-48 hours. |
| shopify.refund_count | If Inventory holds drag too long, customers cancel. Refund spike on this connector signals upstream. |