Find the shipment behind the carrier average
Set the scope once before reading the numbers
The selected warehouse comes from the operator’s current context. Period, client, carrier, and service filters then carry through every KPI, table, trend, state result, and problem-shipment view.
The dashboard names the current calculations plainly: transit starts at label creation, dispatch starts at order creation, and the cost card reflects the stored paid-label prices in this example.
Shipment Insights
Current warehouse: Dallas Fulfillment Center
Period
Last 30 days
Client
Northline
Carrier
USPS
Service
All Services
- Avg Transit Time
- 2.4dLabel creation to delivery
- Avg Dispatch Time
- 4.2hOrder creation to label creation
- On-Time Delivery
- 88.9%Delivered within seven calendar days
- Total Delivered
- 216Delivered labels in this scope
- Avg Shipping Cost
- $7.95Paid label price · example shown in USD
- Problem Shipments
- 14Unique labels matching a problem rule
The “On-Time Delivery” value is the current product calculation: delivery within seven calendar days of label creation. It is not presented as a carrier promise.
Open the carrier result into the services that produced it
A carrier average can hide a slower or more failure-prone service. The expanded row keeps shipment count, transit time, seven-day delivery share, failure, return, and paid cost beside each stored service ID.
The evidence explains the mix; it does not invent a recommendation or call the seven-day calculation a carrier SLA.
Carrier Performance
Expanded to the service IDs stored on the labels.
| Carrier | Shipments | Avg Transit | On-Time | Failure | Return | Avg Cost | Total Cost |
|---|---|---|---|---|---|---|---|
USPS | 240 | 2.4d | 88.9% | 4.2% | 1.7% | $7.95 | $1908.00 |
The parent row explains the whole carrier scope; service rows show which mix produced that average without inventing a recommendation.
Compare the cohort over time and across destinations
Delivery Trend groups outcomes by the date each label entered the cohort. Transit by Destination State then pairs delivered-label elapsed time with its sample count, so a small slow region does not masquerade as the whole network.
The chart and state list use the same warehouse and filters as the KPI and carrier table above.
Delivery Trend
Buckets follow label-created date.
Swipe to see later dates →
Transit by Destination State
Delivered-label elapsed time with sample size.
Washington WA
92h
20 delivered
California CA
72h
50 delivered
New York NY
60h
36 delivered
Florida FL
48h
30 delivered
Texas TX
40h
80 delivered
Turn a problem view into shared follow-up
Delayed, Stuck, Failed, and Not Scanned are separate rule views over the same scoped labels. Open a row and record whether the shipment is being investigated, remains unresolved, or has been resolved.
Categories can overlap. Saving follow-up currently updates the label record timestamp used by Last Update and Delayed or Stuck recency; it does not refresh the carrier’s tracking history.
Problem shipment rule views
Delayed is the current view; the counts below can overlap because one label may match more than one rule.
Resolved hidden
- Delayed
- 2Shown below
- Stuck
- 2
- Failed
- 10
- Not Scanned
- 3
| Tracking | Carrier | Destination | Days | Category | Status |
|---|---|---|---|---|---|
| 9400111899223847210538 | USPS | Seattle, WA | 9 | Delayed | Investigating |
| 9400111899223847210828 | USPS | Tacoma, WA | 8 | Delayed | Unresolved |
Investigation status records shared follow-up. Saving it currently advances the label record’s Last Update timestamp, which can affect Delayed or Stuck recency, but it does not refresh carrier tracking.
Know what the review can—and cannot—change
The carrier evidence can narrow an investigation. It does not turn an operating calculation into a carrier promise or a shared status into carrier remediation.
- Overlapping rules
- Unique KPI
- Shared status
- No carrier action
- Why do the problem-tab counts not add to the KPI?
- Yes. Delayed, Stuck, Failed, and Not Scanned are rule views, and a label may appear in more than one. The overview Problem Shipments KPI counts unique matching labels.
- What changes when follow-up status is saved?
- It records None, Investigating, Unresolved, or Resolved and currently advances the label record timestamp used by Last Update and some recency rules. It does not request a carrier scan or file a claim.
Trusted by 3PLs and brands
See it in your operation
Bring us the carrier review your team still runs from anecdotes
Show us the warehouse, client, carrier mix, delivery questions, and exception queue your team reviews today. We’ll map those decisions against the same operating scope.
No sales call is required to get sandbox access.
Continue exploring
Related workflows
Automations
Automation
Turn repeated warehouse decisions into visible, validated rules and inspect every run or retry.
Carrier Integrations
Shipping
Connect carriers through supported setup paths, keep team-owned connection state visible, and control available services.
Rate Shop
Shipping
Define exact service pools, delivery requirements, and a bounded preference evaluated at label purchase.
Reports & Analytics
Analytics
Run scoped operational reports, inspect recent detail captured with each result, export table data, and schedule recurring reviews.