Skip to main content
Nerve Centre KPIs · Audit Profile · Sentiment Settings 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-platform: revenue at risk (the kill-shot area)

  • Cross-platform: late shipments joined to commerce_sibling orders -> revenue at risk per channel
  • Cross-platform: dispatch-to-collection lag correlated with order_ref - which channels are slowest
  • Cross-platform: open claims with no Jira tracker_item -> CS coverage gap

​
Severity thresholds

​
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