Open Sales Orders, NetSuite

Card class: Card

​

At a glance

Count of NetSuite Sales Orders currently in an open lifecycle state. The metric is a real-time pipeline view: how many SOs are sitting somewhere between created and fully invoiced. It is the operational pulse VP Finance and the Controller use on a Monday 9am cash-flow review to size the working-capital pipeline, identify ageing SOs that should already have flipped to Invoice, and spot the buildup that warns the warehouse is behind on fulfilment.

​

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 of industrial fasteners on NetSuite OneWorld, three subsidiaries (US Inc parent, UK Ltd, AU Pty), single web store on SuiteCommerce Advanced, B2B portal layered on top, and EDI inbound from 14 retailer customers. Snapshot Monday 04 May 26, 09:12 EST. Headline: 1,847 Open SOs across the consolidation. Subsidiary breakdown: State breakdown (US Inc subsidiary): What VP Finance sees on the Monday morning review:

1. The 410 SOs in Pending Billing are the cash-flow priority. These are fully shipped goods waiting for someone to flip them to Invoice. At an average $3,679 each, that is roughly$1.5m of revenue that NetSuite has not yet recognised in GL because the Invoice has not posted. Cross-reference SO to Invoice Lead Time: if the lead time has crept from 1.2 days to 3.8 days, the AR clerk is behind, and DSO will follow within a week.
2. The 612 in Pending Fulfillment is the warehouse buildup. Healthy distribution warehouses keep this number turning daily; a build-up of >2x average daily order volume signals the warehouse is constrained (people, inbound stock, carrier pickup). Cross-reference SOs Blocked on Inventory or Credit to see how many of the 612 are actually waiting on inventory rather than on labour.
3. The 18 Pending Approval is healthy. A US distributor running 50 to 80 new SOs per day should expect 20 to 40 in approval at any moment if the credit-review cycle is 4 to 8 hours. Above 50 means the credit team is bottlenecking; below 5 means approval has gone fully automated, which is fine if Customer Credit Utilisation is healthy and worrying if you are approving customers who should be flagged.
4. UK and AU lower count is mix, not health. UK and AU are smaller markets; the 412 and 125 reflect natural volume differences. The metric to watch by subsidiary is days-of-sales-in-pipeline, not the raw count.
5. The 1,847 baseline. Historical norm for this distributor is 1,650 to 2,100; today’s 1,847 is squarely mid-range. A jump to 2,400 with no corresponding ATR (Average Time to Resolution) movement is the signal that demand has stepped up; a jump with rising lead time is the signal that fulfilment is the bottleneck.

The VP Finance action this week: nudge the AR clerk on the 410 Pending Billing batch (worth roughly 4 days of DSO improvement if cleared in 24h), no action needed on Pending Fulfillment beyond the daily warehouse standup, monitor the 18 Pending Approval for backup if it climbs over 30 by Wednesday.

​

Sibling cards merchants should reference together

Open Sales Orders is a count; almost every diagnostic question requires pairing it with one of the following:

​

Reconciling against the vendor’s own dashboard

Where to look in NetSuite’s own dashboard:

Transactions > Sales > Enter Sales Orders > List, then filter Status to: Pending Approval, Pending Fulfillment, Partially Fulfilled, Pending Billing, Pending Billing/Partially Fulfilled. The row count at the bottom of the list is the directly-comparable figure.

For OneWorld merchants, repeat the filter with the Subsidiary selector at the top of the search results pane to compare per-subsidiary counts. The closest dashboard portlet is Customise Dashboard > Standard Content > Reminders > Sales Orders to Approve / Fulfill / Bill. The portlet does not give you a single rolled-up count; it splits across three reminder types. Sum them for an apples-to-apples figure. For the SuiteAnalytics view, the saved-search All Open Sales Orders (System-Provided in most accounts) is the canonical query Vortex IQ runs against. Why our number may legitimately differ from NetSuite’s: Cross-connector reconciliation: The killer reconciliation here is to find commerce orders with no NetSuite SO at all. That gap is the Commerce Orders Without NetSuite SO card; the dollars on that card are revenue you charged the customer for and never booked into the GL.

​

Known limitations / merchant FAQs

Why is my Open SO count climbing every Monday? Almost universally a fulfilment-cadence artefact. Most warehouses pause Saturday afternoon through Monday morning; SOs created Friday-Sunday accumulate in Pending Fulfillment and the pile is largest first thing Monday. By Tuesday afternoon the count typically returns to mid-week baseline. The pattern is healthy unless the Tuesday afternoon figure is also rising week over week (then you have a structural fulfilment capacity issue). The count is 1,847 but Open SO Value shows $6.35m. Is the$3,438 average meaningful? Marginally. The arithmetic mean masks a heavy long-tail: most distributors see a few B2B orders worth $50,000 to$500,000 sitting alongside hundreds of small orders worth $200 to$1,500. The right view is the median, on Average SO Value, and the top-20 SO list which Vortex IQ exposes via Ask Viq. Ask Ask Viq “show me the top 20 open SOs by value”, you typically find that 5% of the SOs hold 50% of the dollar pipeline. Should Pending Approval be in the count? Yes, by Vortex IQ’s definition. The merchant question this card answers is “how many SOs are in the pipeline?”, which includes “SOs we created but the credit team has not signed off on”. If you want pure post-approval pipeline, use SO State Breakdown and read the non-approval rows directly. Does this include SOs from the SuiteCommerce web store? Yes. SuiteCommerce / SCA orders write directly to NetSuite as standard SOs. They are indistinguishable in this count from manually-entered or EDI-inbound SOs. Filter by source on the SO record (or by sales channel custom field) if you need the channel split. My OneWorld account: does this count include intercompany SOs? Yes by default. Intercompany SOs (subsidiary A selling to subsidiary B) are real SOs in NetSuite. If you want third-party only, filter by Customer.subsidiary != Transaction.subsidiary. Vortex IQ exposes the per-subsidiary view that already excludes intercompany when the merchant tags subsidiaries in the manifest. What is the difference between Closed and Cancelled in NetSuite? Cancelled = the SO was rejected before fulfilment; the customer did not receive goods. Closed = the SO is operationally finished (typically because it was fully fulfilled-and-billed and posted to revenue, or because the merchant chose to close it manually rather than fulfil the remainder of a partial). Both states drop the SO out of the open count. Why does my Open SO count look low for the volume I do? Two usual causes. (1) Auto-Bill is enabled (Setup > Accounting > Auto-Generate Statements), which causes SOs to flip directly from Pending Fulfillment to Billed once the Item Fulfilment posts, skipping Pending Billing. The pipeline is shorter, so the count is structurally lower. (2) The merchant is using cash-sale flow (Cash Sale instead of Sales Order) for ecommerce, which never creates an SO. SuiteCommerce can be configured for either flow; cash-sale stores see this card permanently low. Does this respect the Period Lock? No. NetSuite’s Accounting Period Lock prevents posting to a closed period; it does not affect transaction lifecycle states. SOs continue to flow through Pending Fulfillment > Billed regardless of period status. The count is current-state, not period-state. My distributor: I have a backlog of 2,400 Pending Fulfillment SOs. How do I reduce it without throwing more labour at the warehouse? Three plays in order of impact: (1) Identify the SKUs that drive >40% of pick volume and move them to forward-pick (closer to the pack stations). (2) Re-batch the warehouse pick-pack waves: 4 waves of 600 lines each is more efficient than 12 waves of 200. (3) Audit SOs Blocked on Inventory, often 15 to 25% of “pending fulfilment” is actually waiting on stock that never arrived; close or partial-ship those out of the count first. A SO sat in Pending Billing for 14 days. Why didn’t anyone bill it? Three usual causes: (1) The Item Fulfillment posted but no one ran “Bill Sales Orders” (Transactions > Sales > Bill Sales Orders). NetSuite does not auto-create the Invoice unless the merchant enabled the Auto-Bill saved search. (2) The customer is on Pending Approval for billing terms, often a credit-team check that fell off the queue. (3) A custom workflow blocked the auto-billing for orders flagged with custom criteria (e.g. requires manager sign-off >$10k). Open the SO; the System Notes tab shows the workflow trail.

---

​

Tracked live in Vortex IQ Nerve Centre

Open Sales Orders is one of hundreds of KPI pulses Vortex IQ tracks across NetSuite 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.