[integrations]

Starts at the carrier feed. Everything else is additive.

Throughline reads carrier feeds and EDI 214/990 directly. No TMS or ERP integration is required to start; the connectors below deepen what it sees, they never gate it.

Book a demo Browse the directory

[real vendor names for realism · all entries illustrative · no partnership implied]

[day one]

[tms or erp integrations required to start]

The feed is the integration. Everything with a vendor name on this page is optional depth, not a prerequisite.

What does day one actually require?

[01]
Carrier credentials or an EDI 214/990 feed
Either works. That is the whole integration surface on day one.
[02]
90 days of history, backfilled in week one
Lane tolerances are tuned against that history in week two, so day-one alerts are not noise.
[03]
First live exception before the second check-in
Alerts land in email and Slack from the first flagged shipment. Implementation runs 2 to 3 weeks end to end.

The rest of the product is on the platform tour. What the feed replaces is on Throughline vs. spreadsheets and email.

[the directory]

What connects, and how?

Grouped by kind. Each row states the protocol, the payload, and the plan it ships on, because those are the three things an IT reviewer checks against the contract.

[01 / carrier feeds]

Carrier feeds

Carrier feeds · the day-one surface · illustrative
Source	Mode	Cadence	Payload
Carrier APIs: Estes, Saia, XPO, Knight, Averitt, Dayton	Poll with credentials	5 min cycle	Status events, ETA revisions, delivery scans
project44	Aggregated visibility feed, push	As published	Normalized status events across contracted carriers
FourKites	Aggregated visibility feed, push	As published	Normalized status events across contracted carriers
Forwarded status email	Parse on receipt	On arrival	Carrier status emails parsed into structured events

Carrier feeds ship on every plan; the carrier count is set by tier, 2 on Team, unlimited on Operations and Network.

[02 / edi transaction sets]

EDI transaction sets

EDI transaction sets · X12 and EDIFACT · illustrative
Set	Standard	Carries	Direction	Plan
214	X12	Shipment status message, the primary tracking signal	Inbound	Network
990	X12	Response to a load tender, accept or decline	Inbound	Network
204	X12	Load tender, read to pair each 990 with its tender	Inbound	Network
IFTSTA	EDIFACT	International transport status, the 214 analog	Inbound	Network
997	X12	Functional acknowledgment, returned for every received set	Outbound	Network

EDI ingest ships on the Network plan. 214/990 is the pair that lets Throughline start without touching your TMS.

[03 / tms and erp]

TMS and ERP

TMS and ERP connectors · additive, never prerequisites · illustrative
System	Interface	Reads	Writes	Required to start
SAP S/4HANA	IDoc / OData	Order and delivery master data	Nothing without a rule	No
NetSuite	SuiteTalk REST	Sales orders, item fulfillments	Nothing without a rule	No
Any TMS with an API	REST ingest + webhooks	Shipment references	Exception events out	No

Connectors add order context to exceptions. They are additive, not prerequisites; the last column is the point.

[04 / data warehouse and export]

Data warehouse and export

Data warehouse and export · your data, queryable where you work · illustrative
Destination	Method	Contents	Plan
Snowflake	Secure data share	Exception history and the event log	Network
CSV / Parquet	Export from any queue	Whatever the queue holds, attachments included	All plans
Direct SQL	Read-only workspace	The full exception schema	Network

[05 / notification channels]

Notification channels

Notification channels · where exceptions find their owner · illustrative
Channel	Trigger	Plan
Email	Assignment, deadline, escalation	All plans
Slack	Same events, to a channel or a DM	All plans
Microsoft Teams	Same events	Operations and up
Webhooks	Every state change, signed payload	Operations and up

Book a demo

[bring your carrier list and your edi setup]

[document repository]

Where do the documents live?

On the shipment.

Every exception thread holds its BOL, its POD, the carrier correspondence, and the customer notice, attached to the shipment they belong to. The thread stays queryable for the life of the account, and exports carry the attachments with the record. There is no second filing system to maintain.

[one thread per shipment · the whole paper trail]

[a note on logos]

Where are the partner badges?

There are none, on purpose.

Partner-tier badges go stale: Microsoft retired its Gold and Silver competencies and asks partners to stop citing them. A row that names the protocol, the payload, the direction, and the plan can be checked against a contract; a logo wall cannot. Vendor names on this page identify file formats and APIs, not partnerships.

[protocol · payload · direction · plan]

[next step]

Bring the carrier list.

Twenty minutes, your carriers, your EDI setup. The demo loads a week of your own feed data live on the call.

Book a demo Read the trust center