> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# NetDispatch audit profile, Vortex IQ

> What the Vortex IQ NetDispatch health audit checks: NetDispatch: Dispatch-to-Collection SLA, Sub-Carrier Health & Cross-Channel Leak

**[Nerve Centre KPIs](/nerve-centre/kpi-cards/net-dispatch) · [Audit Profile](/nerve-centre/kpi-cards/net-dispatch/audit) · [Sentiment Settings](/nerve-centre/kpi-cards/net-dispatch/sentiment)**

NetDispatch is a UK courier-dispatch software / aggregator. CloudHub probe shows 1 active merchant with NetDispatchAccountID-only auth (no username/password stored, suggesting IP allowlist or SFTP pattern). Public docs are limited - exact API shape needs C# backend extraction. Findings center on dispatch-to-collection SLA (the core NetDispatch value prop) and sub-carrier consolidation visibility.

## What this audit checks

### Authentication & access

* Account ID still authenticates (no 401)
* IP allowlist intact (if used) - source IP matches NetDispatch-side configuration
* Production base URL reachable

### Dispatch-to-collection SLA (the core NetDispatch promise)

* Median dispatch-to-collection lag > 24h
* Dispatch-to-collection > 48h on > 1% of shipments (cutoff misses)
* Awaiting-collection backlog > 5% of total (queue stretching)

### Sub-carrier consolidation health

* Single-sub-carrier dependency > 80%
* Sub-carrier OTD spread > 10pp
* New sub-carrier added without OTD baseline

### Exceptions, claims & cost

* Exception rate > 3% rolling 30D
* Open claims unresolved > 7 days
* Avg cost / shipment up >10% vs prior period
* Claim value as % of NetDispatch revenue > 2% rolling 90D

### Cross-channel: revenue at risk (the kill-shot area)

* Cross-channel: late shipments joined to commerce\_sibling orders -> revenue at risk per channel
* Cross-channel: dispatch-to-collection lag correlated with order\_ref - which channels are slowest
* Cross-channel: open claims with no Jira tracker\_item -> CS coverage gap

## Severity thresholds

| Signal                               | Warn | Critical |
| ------------------------------------ | ---- | -------- |
| `on_time_delivery_rate`              | 95   | 90       |
| `dispatch_to_collection_hours`       | 12   | 24       |
| `cutoff_miss_pct`                    | 0.5  | 1        |
| `awaiting_collection_backlog_pct`    | 3    | 5        |
| `exception_rate`                     | 2    | 3        |
| `open_claims_age_days`               | 7    | 14       |
| `shipping_cost_per_order_change_pct` | 5    | 10       |
| `sub_carrier_concentration_pct`      | 70   | 80       |
| `claim_value_pct_of_revenue`         | 1    | 2        |
| `auth_token_failures_24h`            | 1    | 5        |

## Data sources

* `GET TBD - pending CloudHub C# backend URL extraction` - Auth probe + tenant metadata
* `GET TBD - pending CloudHub C# backend URL extraction` - Shipment list + dispatch SLA tracking
* `GET TBD - pending CloudHub C# backend URL extraction` - Tracking events