At a glance
SKUs at or below their reorder point. The forward-looking fulfilment risk view: if you don’t reorder, you’ll stock out.
| What it counts | Items where QuantityAvailable < ReorderPoint. Each row shows current available, reorder point, vendor, lead time, recommended reorder quantity. |
| Per-location | Reorder point is set per Item × Location. Card lists each location’s shortfall. |
| In-transit | Subtracted from available calculation if NetSuite’s purchase-order workflow is in use. |
| Currency | Reorder cost in vendor’s billing currency. |
| Subsidiary scope | Respects dashboard filter. |
| Time window | RT |
| Alert trigger | Any SKU below reorder point. Configurable to high-priority SKUs only. |
| Roles | owner, 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 apparel distributor on NetSuite. Snapshot 14 Apr 26.| SKU | Description | Available | Reorder Pt | Lead time | Vendor |
|---|---|---|---|---|---|
| BR-A-001 | Brand A Premium Tee Black M | 24 | 50 | 14 days | Supplier 1 |
| BR-A-002 | Brand A Premium Tee Black L | 38 | 60 | 14 days | Supplier 1 |
| BR-B-014 | Brand B Polo Navy XL | 8 | 30 | 21 days | Supplier 2 |
| BR-C-022 | Brand C Hoodie Grey S | 12 | 40 | 30 days | Supplier 3 |
| BR-D-008 | Brand D Kids Tee | 0 | 25 | 14 days | Supplier 1 |
| (78 more SKUs below threshold) |
- BR-D-008 at 0 available is OOS now. Backorders in Open SOs Blocked reflect this. 14 days to receive new stock.
- BR-B-014 at 8 vs 30 reorder point is the urgent reorder. 21-day lead time. If demand stays steady, 8 units last ~5 days. Order today or stock out.
- BR-C-022 at 30-day lead time is the planning challenge. Need to forecast 30 days of demand, not just till next reorder.
- The card surfaces vendor details so Operations can pick up the phone immediately.
- Pair with OOS with SO Demand for the cross-channel killer view: SKUs with open SOs awaiting them.
Sibling cards merchants should reference together
| Card | Why pair it with Low Stock Alerts |
|---|---|
| OOS with SO Demand | Stock-outs with confirmed demand. The double-killer signal. |
| Open SOs Blocked | Inventory holds caused by these SKUs. |
| Inventory Turnover | Fast-turning SKUs need higher reorder points. |
| Top SKUs Value | Best-sellers. Don’t run out of these. |
| Total Inventory Value | Macro level. |
Reconciling against the vendor’s own dashboard
Where to look in NetSuite:Reports → Inventory → Items Below Reorder Point Lists → Items withWhy our number may legitimately differ:QuantityAvailable<ReorderPointfilter
| Reason | Direction | Why |
|---|---|---|
| Reorder point setup | Either | Items with no reorder point are excluded by both. Items with stale reorder points may show inappropriately low or high. |
| In-transit treatment | Either | NetSuite’s standard report subtracts on-order PO quantity; card defaults same. |
| Per-location | Either | NetSuite’s report defaults to single location; card includes all. |
| Card | Relationship | Why |
|---|---|---|
| shopify.inventory_pending_orders | Commerce-side OOS allocation | Shopify shows OOS at allocation time. NetSuite shows reorder-point breaches. |
| OOS with SO Demand | Cross-channel | The SOs blocked by these stock-outs. |