Why we publish integration matrices
Most TMS shopping is done by feature comparison. But the moment you sign, the question is no longer "what features does the TMS have" — it's "does this TMS actually talk to my Samsara devices, my QuickBooks file, my factor's API, my preferred load board." A working integration is operationally invisible. A broken one means three months of dispatchers and bookkeepers manually double-keying data while the integration roadmap "ships next quarter."
These matrices are designed to be the page you screenshot before a demo. Every cell flagged Native links to a primary source — usually the partner's own marketplace listing or a vendor integration article. Cells flagged Listed mean we found marketing language but couldn't confirm depth. Cells flagged Unverified mean we don't have evidence either direction; we don't claim "supported" without it.
All 7 matrices
The largest connected-fleet platform in trucking. ~1.2M devices, ~$1.3B TTM revenue. The default ELD assumption past 10 trucks.
View matrixFormerly KeepTruckin. Samsara's closest competitor with deeper owner-op and small-fleet penetration. Open Marketplace, developer API.
View matrixThe third major ELD — reseller-channel-distributed, mixed-fleet (trucking + utility + government). Strong at scale but uneven TMS support.
View matrixThe dominant carrier accounting tool. Real depth varies between QBO (Online) and QBD (Desktop) — and which TMS supports which.
View matrixThe largest freight load board in North America. DAT One, DAT Power, RateView. Native integration is the difference between a half-FTE.
View matrixDAT's main competitor — and uniquely owns ITS Dispatch (a vertically integrated freight platform). Book It Now and RMIS layer.
View matrixApex, RTS, OTR, TBS, Triumph, Bobtail, eCapital — TMS integration collapses the daily portal-upload chore into a one-click submission.
View matrixHow we mark cells
- Native. Documented integration with depth — partner's marketplace lists the TMS, or vendor docs describe the bidirectional flow. The page links to the source.
- Listed. Vendor mentions the partner in marketing or an integrations page, but we couldn't confirm depth (is it GPS only? Bidirectional? Webhook-driven?). Pressure-test in demo.
- Marketplace. Partner-side confirms it (e.g., a Samsara KB article exists for this TMS). Like Native but the source is the partner not the TMS.
- Partial. Integration exists but is meaningfully limited — one-direction-only, single feature, or with documented friction (e.g. Alvys's QuickBooks "heavy lift").
- Not supported. Explicit no per vendor positioning or reviewer evidence (e.g. McLeod replaces QuickBooks rather than integrating; Axon's no-loadboard stance).
- Unverified. No evidence either way. Default for cells we couldn't confirm.
Methodology: every cell verified against either the TMS vendor's docs or the partner's own marketplace. Read the editorial methodology. Last updated May 2026.