How to find the late purchase orders that matter in NetSuite

What NetSuite already gives you

In NetSuite, everything you need to judge a late purchase order already exists. It sits in records and searches built for different jobs:

• The purchase order list (Transactions > Purchases > Enter Purchase Orders > List): orders with a status such as *Pending Receipt* or *Partially Received* still have quantities to receive.
• The Expected Receipt Date of each line: the date you expect the goods, next to the order's *Receive By* date.
• The item record, Locations subtab: on hand, available, reorder point and preferred stock level by location.
• Saved searches: the tool that joins all of this into one exportable list.

Each one answers part of the question. None of them ranks your late orders by the stock risk behind them. A past-due purchase order list sorted by date tells you who is late, not who to call first.

The method, step by step

1. Build a saved search of late purchase order lines

Create a transaction saved search: type *Purchase Order*, status *Pending Receipt* or *Partially Received*, main line *false*, and expected receipt date before today. In the results, show the item, vendor, quantity, quantity received, expected receipt date and location. Export it to CSV. If your vendors confirm dates, note which lines were never confirmed: their date is still your request.

2. Get stock and usage for each item

Take available quantity per item and location from an item saved search. For usage, sum the quantities that left stock over a fixed window, for example the last 12 weeks: item fulfillments for goods shipped, and assembly builds or work order issues for components consumed. Use the same window for every item. If you use Advanced Inventory Management, compare with the item's demand per day, and check how it is calculated before trusting it.

3. Compare days of cover with the real arrival date

Days of cover = available stock / average daily usage. For each late line, take the date you now expect it to arrive, and check whether another open order for the same item and location arrives earlier. If cover runs out before any order arrives, the line is a shortage risk.

4. Sort by days of cover, shortest first

Among the shortage risks, the item with the fewest days of cover goes to the top. That is your chase list for today. For each line, write down stock, usage, cover, the expected receipt date and days late: when you call the vendor, you are discussing facts.

Illustrative example, not a customer result

Two lines from the same saved search:

• Line A, steel bracket: 9 days late. 3,000 available, usage of about 50 a day: 60 days of cover. Another order arrives next week.
• Line B, power supply: 2 days late, never confirmed by the vendor. 60 available, usage of about 15 a day: 4 days of cover. No other open order.

Sorted by days late, line A comes first. Sorted by days of cover, line B does, and line B is the one that can stop shipments this week.

Where the manual method breaks

• It does not scale. A saved search gives you the lines; computing cover and checking other open orders item by item works for ten lines, not for two hundred every Monday.
• Usage needs care. New, seasonal or lumpy items make a 12-week average misleading. Flag them rather than trusting the number.
• Dates are only as good as their maintenance. If vendor updates are not entered, the expected receipt date is still the original one.
• Days of cover tells you when an item runs out, not which customer order or work order it affects. Linking the two still needs your planners and your bill of materials.

How WERISCO does it

WERISCO automates the data work behind these steps: it reads every open order line, computes days of cover for each part and flags late or undated orders by severity, with the evidence on each line. With NetSuite, it works from saved-search exports you already know how to run: available stock by item and location, and open purchase order lines. There is no WERISCO NetSuite connector today; see the NetSuite integration page. The first supply chain audit needs only those two exports. WERISCO reads only; nothing is written back to NetSuite, and your team decides what to chase.