[supply-chain exception management]

Every shipment that needs a human. Nothing else.

Built for mid-market ops teams running three or more carriers: Throughline reads carrier feeds and EDI 214/990 directly, no TMS or ERP integration required to start.

38 min [median detection, carrier signal to flagged row · illustrative]

Book a demo Open the ROI calculator

[soc 2 type ii · 14-day trial · no card]

PROD Exceptions / Today [sample data]

LATE 3 SHORT 2 MISROUTE 1 6 open

Sample exception queue of six shipments with issue type, owner, lane, and hours behind promised arrival. The counts above are computed from these rows.
Shipment	Issue	Owner	Lane	ETA Δ
SHP-48211	LATE	–	ORD → DFW	+38h
SHP-48207	SHORT	JL	ATL → MEM	+4h
SHP-48198	MISROUTE	RM	LAX → PHX	+51h
SHP-48187	LATE	JL	ORD → MSP	+9h
SHP-48173	LATE	–	DFW → ELP	+26h
SHP-48160	SHORT	AC	SAV → CLT	+2h

[counts computed from the six shipments above · illustrative]

[run by operations teams at] [illustrative / demo brands]

KESSLER INDUSTRIAL
Ferrostat
Blue Heron Foods
Calder & Voss
Tessellate
Norwick Components

38min

[01 / detect · median time-to-flag, every connected feed]

[02 / triage]: 94%; of exceptions closed by rule, without paging a human
[03 / resolve]: 11.2h; returned per exception cycle, against the manual baseline

[illustrative product metrics]

[how it works]

Detect, triage, resolve. In that order, every time.

PROD Exceptions / Triage

Shipment	Issue	Owner	Lane	Carrier	ETA Δ	Action
SHP-48211	LATE	–	ORD → DFW	Estes	+38h	Assign
SHP-48207	SHORT	JL	ATL → MEM	Saia	+4h	Triage
SHP-48198	MISROUTE	RM	LAX → PHX	Knight	+51h	Reroute
SHP-48187	LATE	JL	ORD → MSP	Dayton	+9h	Watch
SHP-48173	LATE	–	DFW → ELP	Averitt	+26h	Assign
SHP-48160	SHORT	AC	SAV → CLT	XPO	+2h	Resolve

[01 / detect]

Every feed, one tolerance model

Carrier APIs, EDI 214s, and forwarded status emails stream into a single feed. Anything outside lane tolerance is flagged in minutes, not at Friday's review.

5 min polling cycle on every connected feed

[02 / triage]

Rules in plain fields, not scripts

Lane, carrier, customer tier, dollar value: your rules assign each exception an owner and a deadline, or close it without ever paging one.

0 exceptions sitting unowned in the queue

[03 / resolve]

One thread per shipment, forever

The carrier contact, the customer notice, and the audit trail live in one thread. Close it once; the record stays queryable for the life of the account.

1 thread holding the whole paper trail

Six carriers, one queue. The highlighted row is 38 hours late out of Chicago and about to become a customer call. [illustrative data]

[seven days of throughput]

Detection runs ahead. Resolution catches up.

Volume peaks midweek; resolution keeps pace because triage never waits for someone to notice. The weekend crossover is the backlog clearing itself. By type, late is the volume: more than half of the week's 1,415 exceptions.

Exceptions detected versus resolved per day, last seven days
Day	Detected	Resolved
Monday	212	189
Tuesday	233	214
Wednesday	198	205
Thursday	247	231
Friday	226	240
Saturday	158	176
Sunday	141	168

Exceptions detected vs resolved, last 7 days. [illustrative data]

[same seven days · by type]

Exceptions by type, same seven days, 1,415 total
Type	Count	Share
Late	812	57.4%
Short-shipped	391	27.6%
Misrouted	212	15.0%

Exceptions by type across the same seven days, 1,415 total. [illustrative data]

[plumbing]

It connects to what you already run.

EDI 214
EDI 990
project44
FourKites
SAP
NetSuite
Snowflake
Email ingest
Slack
Microsoft Teams
Webhooks
CSV / Parquet

[illustrative integration set · vendors named as integrations only]

[built for the shipments that go wrong]

[trust center]

Built to pass your security review.

[review pack in procurement]

[soc 2]
SOC 2 Type II
Audited annually. Report available under NDA. Controls cover access, change management, and incident response. The trust center holds the full posture.
[sso]
SSO / SAML
Okta, Entra ID, and Google Workspace on Operations and up.
[rbac]
Queue-level roles
Read-only roles for finance and CS. Assign, resolve, and export are separate rights.
[residency]
US or EU
US by default. EU pinning available on Network.
[subprocessors]
Published list
The current list, updated with 30 days' notice.

[security review pack available in procurement]

[the math]

$58,339

[modeled first-year net · default case]

What does the status quo cost?

The status quo isn't free. It's just billed in hours instead of dollars.

That's the calculator's default case, 12,000 shipments a month at a 6% exception rate, not a promise. Every formula is on the page. Bring your own numbers; they follow you to the demo form below.

Open the ROI calculator

[pricing]

What does it cost?

Three tiers, priced by shipment volume, published in full. No sales call required to see a number.

See full pricing

[team]

Team

One facility finding out what its exceptions cost.

$1,500/mo
[operations]

Operations

Multi-site ops teams that own the carrier relationships.

$2,900/mo
[network]

Network

Networks that need EDI, residency control, and SQL.

$4,500/mo

[annual takes two months off · 14-day trial · no card · illustrative]

[faq]

What will the rest of the committee ask?

Six answers written to be forwarded, to people we will never meet.

[01]Do we need to connect our TMS or ERP first?

No. Carrier credentials or an EDI 214/990 feed is enough to go live; Throughline reads status data off the wire. SAP and NetSuite connectors exist for enrichment, and they are additive, never prerequisites.

[02]How long until it catches the first real exception?

Feeds connect in the first week and backfill 90 days of history; lane tolerances are tuned against that history in week two so day-one alerts aren't noise. Most teams triage their first live exception before the second weekly check-in.

[03]Where does shipment data live, and who can see it?

US residency by default, EU pinning on the Network tier. Queue-level roles separate assign, resolve, and export rights, with read-only seats for finance and CS. The SOC 2 Type II report is available under NDA via the trust center.

[04]What does it replace, and what does it not do?

It replaces the morning portal sweep, the exception spreadsheet, and the email thread. It is not a visibility map, a TMS, or a rating engine: shipments that are fine never appear, and nothing about how you tender freight changes.

[05]How is it priced as volume grows?

Three published tiers, $1,500 to $4,500 a month by shipment volume. At 80% of plan volume you get an alert; overage bills at $40 per additional 1,000 shipments, and two overage months in a row usually means the next tier is cheaper.

[06]What happens to our data if we leave?

You can export everything as CSV or Parquet at any time, not just at the end. On termination the workspace stays exportable for 30 days, then data is deleted with written confirmation. The DPA covers it in writing.

[next step]

See your lanes in it.

Twenty minutes with your carrier list. Bring credentials and we'll load a week of your own data live on the call.

Not ready for a call? Run the ROI calculator or read the platform tour. Both travel well in an email.