Sample output from the Pick-Pack-Ship Latency Profile prompt in the Sonar AI Prompt Library, run against a NetSuite test account. Every name and number here is test data. Back to the post · The library
π¦ Pick-Pack-Ship Latency Profile
Stage-by-stage fulfillment timing by location, item & order size β where orders actually wait, and what it costs
Generated 2026-07-28240 item fulfillments analyzed111 unfulfilled open sales ordersSource: live NetSuite transaction data (SuiteQL)
Executive Summary
Once a fulfillment exists, it ships same-day almost everywhere. The latency β and the money β sits upstream of the pick and in a stale unfulfilled backlog.
94.6%
Same-day pick rate
227 of 240 fulfillments created the day the SO was entered
$1.93M
Shipped same-day
Order value flowing through with zero wait
$402K
Dollar-days of delay
13 delayed fulfillments Γ avg 91.4 days late Γ order value
$116K
Unfulfilled backlog
111 open SOs never fulfilled ($67.8K real + $48.3K future-dated)
$3,938
Stuck in WIP
9 fulfillments frozen at Picked/Packed, never shipped
The Pipeline: Where the Wait Lives
Stage 0 Β· Order β Pick
0β360 days
β 100% of latency lives here. Median 0d, but a long tail of backorder waits β plus 111 orders that never enter the pipeline at all.
β
Stage 1 Β· Picked
6 stuck
Fulfillments at status A. All but one are stale (900+ days).
β
Stage 2 Β· Packed
3 stuck
Status B. One live: IF #240, Miami, packed 28 days ago.
β
Stage 3 Β· Shipped
231 β
96% of all fulfillments completed. Pickβship is effectively same-day.
Stage transitions measured from SO createddate β Item Fulfillment createddate (via transactionline.createdfrom), and fulfillment status (A=Picked, B=Packed, C=Shipped). This account keeps no system-note audit trail on fulfillments, so intra-warehouse pickβpackβship durations are represented by current stage + dwell age.
Latency by Location order β pick, days
New York is the benchmark: 105 fulfillments, never a single day of lag. Miami and Chicago carry chronic multi-month waits. Lines with no location assigned are the worst cohort β unowned orders wait longest.
Location
Fulfillments
Avg days
Profile
Median
Max
% Same-day
(no location on lines)
36
33.0
0
360
64%
05: Miami
7
26.6
0
174
70%
03: Chicago
4
16.2
0
138
88%
Store #140 Boston
1
8.0
8
8
0%
01: San Francisco
120
1.9
0
360
97%
Store #100 San Francisco
1
0.0
0
0
100%
02: New York
105
0.0
0
0
100%
04: Denver
2
0.0
0
0
100%
π New York ships 105/105 same-day. β Miami is the systemic laggard at every stage: slowest picks (avg 26.6d), the only live stuck shipment (IF #240, packed 28d), and the largest regional share of the unfulfilled backlog. San Francisco is fast on average (97% same-day) but produced the two worst outliers β two fulfillments created 360 days after their SOs (#23174/#23175), likely abandoned orders finally swept.
Latency by Order Size counter-intuitive, consistent
Order size
Count
Avg days
Max
% Same-day
π΄ Small (1β3 lines)
93
12.4
360
89%
π‘ Medium (4β8 lines)
74
0.3
19
97%
π’ Large (9+ lines)
73
0.1
6
99%
π‘ Every long-latency incident is a small order. Large orders get prioritized (likely B2B/wholesale flows with dedicated handling); 1β3-line orders fall through a crack β probably batch-released only when someone manually sweeps the queue.
Items That Wait stock-out signature
The high-volume electronics catalog (iPads, MacBooks, monitors β 34 fulfillments each) ships at 0.0 days, 100% same-day. The waits concentrate entirely in soft-goods / specialty SKUs β a classic backorder pattern, not a warehouse-labor problem.
Item
Fulfillments
Avg days
Max days
Signal
Salida Backpack BU
8
90.9
360
Chronic β repeat offender across 12 delayed lines
227 fulfillments Β· zero wait β the healthy baseline
$11,365
Value shipped late
13 fulfillments Β· avg 91.4 days late
$401,882
Dollar-days in transit-wait
Ξ£ (order value Γ days waited) β revenue recognition & cash conversion drag
Unfulfilled backlog by age β $116,094.68 total
Age bucket
Orders
Value
Share of value
0β30 days
1
$1,410
1%
31β90 days
12
$24,646
21%
91β365 days
9
$30,268
26%
Over 1 year
45
$11,520
10%
Future-dated (demo data)
44
$48,252
42%
Where the recoverable money is
π° $54,913 β fresh & fulfillable (0β365d)
22 orders young enough that the customer is likely still waiting. Single largest item: SO #315 at $17,753 (91β365d bucket). Fulfill or communicate.
π§Ή $11,520 β stale, close it (1yr+)
45 orders over a year old. These distort demand planning and committed-inventory calculations. Close or cancel.
π¦ $3,938 β stuck WIP
9 picked/packed fulfillments. Inventory is committed but not moving β it's invisible to available-to-promise.
Stuck In-Process Fulfillments picked or packed, never shipped
IF #
Stage
Location
Created
Dwell (days)
Order value
Disposition
240
PACKED
05: Miami
2026-06-29
28
$86
β‘ Live β ship it or investigate carrier hand-off
229
PICKED
01: San Francisco
2024-02-07
901
$61
Stale β cancel/clean up
230
PICKED
01: San Francisco
2024-02-07
901
$353
Stale β cancel/clean up
226
PICKED
01: San Francisco
2023-02-12
1,261
$203
Stale β cancel/clean up
212
PICKED
03: Chicago
2022-01-27
1,642
$47
Stale β cancel/clean up
213
PICKED
02: New York
2022-01-27
1,642
$2,047
Stale β highest value of the stuck set
207
PACKED
04: Denver
2022-01-27
1,642
$915
Stale β cancel/clean up
211
PACKED
04: Denver
2022-01-27
1,642
$126
Stale β cancel/clean up
241
PICKED
Store #140 Boston
2027-09-04
future
$100
Future-dated demo record
Recommended Actions
NOWShip IF #240 (Miami).
Packed 28 days ago and sitting. The only genuinely live stuck shipment in the pipeline. Check carrier hand-off / tracking assignment.
WEEK 1Triage the $54.9K fulfillable backlog (22 orders, 0β365 days).
Start with SO #315 ($17,753). For each: fulfill, split-ship available lines, or proactively notify the customer.
WEEK 2Close the stale tail: 45 SOs over 1 year ($11.5K) + 8 stale stuck fulfillments.
These inflate committed inventory and pollute demand signals. A one-time bulk close restores data hygiene.
FIX ROOT CAUSEAdd a small-order release sweep & backorder escalation.
The at-risk profile is precise: 1β3-line orders containing specialty SKUs (Salida Backpacks, saws, printers) routed to Miami/Chicago or left with no location. A daily automated release for small orders + a reorder-point review on the 5 offending SKUs eliminates most of the tail. Replicate New York's process β 105/105 same-day β at Miami.
MEASUREEnforce line-level location on Sales Orders.
The "(no location)" cohort is the slowest (avg 33 days) and largest backlog segment β orders nobody owns. Make location mandatory at order entry so every order has a warehouse accountable for it.
Methodology. Population: 240 item fulfillments (231 Shipped / 3 Packed / 6 Picked) linked to originating sales orders via transactionline.createdfrom; 111 open SOs (status B/D/E) with no fulfillment lines. Latency = fulfillment createddate β SO createddate (calendar days). Order values from foreigntotal. Dollar-days = Ξ£(order value Γ days waited). This demo account contains future-dated transactions (SOs through 2028); they are flagged and excluded from latency conclusions. No system-note audit trail exists for fulfillment status transitions in this account, so pickβpackβship internal durations are approximated by current stage + dwell age. Generated by Sonar AI Β· 2026-07-28.