Orders Blocked on Inventory or Credit, Sage

Card class: Hero • Category: Ecommerce Platform

Orders held by inventory shortage or credit hold in Sage Intacct, ranked by revenue at stake. The morning unblocking queue.

​

At a glance

Sage Intacct Orders that are blocked, ranked by dollar value. Block reasons include credit hold (customer over credit limit or terms-violated), inventory shortage (Order line cannot allocate stock), pending approval (workflow approver offline), pending Project authorisation, or pending Department-head sign-off where the merchant uses dimension-based approval. The morning unblocking queue.

​

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. Snapshot 14 Apr 26, 9:00am. Top 5 highest-value blocked Orders: Action playbook:

1. **Apex Industrial Supply: $132K stuck on credit hold across two Orders.** Customer has been a 3-year reliable payer; the credit limit was set in 2023 and not refreshed. Finance: review and raise limit by 25$132K Invoice within 7 days, ~$132K cash within 35 days.
2. Inventory Hold on SKU-44A: 120 units short blocking $62K. Procurement: confirm next inbound PO date. If >7 days, partial-ship the Order with the available 80 units and back-order the rest. Customer notified.
3. Project Authorisation Hold sitting 7 days on PRJ-NOVA. Project Manager has been on PTO. Backup approver should have been delegated; Operations to set up auto-delegation.
4. Cascading credit holds. Apex’s two Orders together push them to 145% of credit limit; raising the limit clears both. Without the Customer Credit Utilisation card, the cascade isn’t visible.
5. Cumulative cash impact: clearing 80% of the queue this week unlocks ~$490K of forward Invoices, ~$490K of cash within 5 weeks. The morning unblocking ritual is the single highest-leverage Operations habit a B2B Intacct merchant has.

​

Sibling cards merchants should reference together

​

Reconciling against the vendor’s own dashboard

Where to look in Sage Intacct:

Order Entry → List View → Filter: On Hold = TRUE Reports → Order Entry → Sales Order Register → Hold filter Customer → List View → Filter: Credit Hold = TRUE Interactive Custom Report (ICR) combining Order Entry + Customer + Inventory data sources

Intacct does not surface a single “blocked Orders by reason” view natively; the merchant must combine three filters (Order hold, credit hold, inventory short). Vortex IQ joins them automatically. Why our list may legitimately differ from a manual check: Cross-connector reconciliation: This card is internally Intacct-only; the block reasons live in Intacct’s Order and Customer records. Commerce platforms cannot block (they accept payment instantly), so there is no commerce-side counterpart.

​

Known limitations / merchant FAQs

What is a healthy blocked-Orders ratio? Below 5% of Open Order Value is healthy. 5-10% suggests credit policy or inventory planning is tight; >10% suggests structural problems (over-aggressive credit limits, chronic inventory shortages, or workflow approver bottlenecks). Should credit holds always be released same-day? No. Some are correct (genuinely over-extended customers). The card’s value is making the decision explicit and same-day; “release”, “raise limit”, or “decline and renegotiate terms” are all valid outcomes. Why does the card include Approval Holds? Because they are the silent killer. A $36K Order sitting 7 days in approval is real revenue lag and pure process waste. Surfacing them as part of the unblocking queue forces the conversation. Multi-Entity Console: how does the card scope? By default rolls up across all entities. Per-entity filter available so the East Coast Operations Manager only sees their queue. Can the card auto-unblock? No, intentionally. Releasing a credit hold is a Finance decision; auto-release would create audit risk. Ask Viq can draft the release in Intacct and require Finance approval before posting. My Implementation Partner says credit holds should be reviewed by AR not Operations. Right? Both. AR sets the credit limits; Operations needs visibility because Order fulfilment depends on it. The card is shared; Finance acts on the credit-hold rows, Operations on the inventory-hold rows. What threshold should I set for “high-value blocked”? Default $10K. Larger merchants ($50M+ revenue): $25K. Smaller:$5K. Calibrate to capture the top 20% of blocked Order value. How does this compare to NetSuite’s Open SOs Blocked? Conceptually identical. NetSuite uses status codes; Intacct uses hold flags + workflow state. The card normalises both into a unified “block reason” classifier. Does this card include B2B portal Orders? Yes if the portal Orders flow through Intacct’s Order Entry module. Standalone B2B portal Orders without Intacct integration are not in scope. Project Authorisation Hold is unique to my services-business setup. Does the card understand it? Yes if the Project dimension drives the Order workflow. Configure the Project Authorisation Hold rule in the field map. Default detection assumes any Order tagged to a Project with workflow_state = ‘Pending Project Authorisation’ is blocked under that reason.

---

​

Tracked live in Vortex IQ Nerve Centre

Orders Blocked on Inventory or Credit 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.