Short answer
In this dated review of 47 approved SupplyWolf TMS listings, the reviewed official public pages documented integration/API/EDI information for 40, a specific data-retrieval or export example for 19, and customer implementation/onboarding information for 25. These are counts of published evidence found in the reviewed sources, not estimates of which products have a capability. “Not verified” does not mean a feature is absent.
Download the reviewed evidence as CSV (also available in the table below).
What was reviewed
The study records product-specific official public documentation about three buyer questions: (1) integration mechanisms such as APIs, EDI, and named system connections; (2) a published example of retrieving or exporting data, with its scope stated; and (3) customer implementation or onboarding guidance. A developer API quickstart alone is not counted as customer implementation documentation.
Method
The snapshot contains the 47 approved listings returned by SupplyWolf’s /api/products/category/tms catalog endpoint on 2026-09-29. It is a snapshot of SupplyWolf’s catalog, not a representative sample of the overall TMS market. Distinct catalog products remain separate rows, including products from the same parent company. For each listing, the review checked public vendor-controlled sources and recorded a finding only where a linked official page supported it. The table includes source links, a short paraphrase, and limitations or product-identity caveats where relevant. No product was tested or ranked.
Findings by product listing
“Not verified in reviewed sources” means the review did not verify a qualifying public document for that dimension. It is not a statement that the product lacks the feature or service.
| Catalog product | Integration / API / EDI information | Data retrieval / export example | Customer implementation / onboarding | Scope notes |
|---|---|---|---|---|
| Descartes 3Gtms | The Descartes 3G TMS product directory lists integration categories including ERP/accounting and Supply Chain/EDI; the page does not specify protocols or provide an API specification. |
Not verified in reviewed sources. |
Not verified in reviewed sources. |
Checked the official 3G TMS integration directory and homepage. No product-specific export/portability or customer implementation process was verified. Do not transfer evidence from Descartes Aljex or general Descartes TMS pages to 3Gtms. |
| Alvys | Alvys advertises in-house EDI, a self-serve API, and integrations with named industry tools. |
The official guide uses the Alvys Public API to pull live operational records, including loads, trips, customers, drivers, carriers, and invoices, into Google Sheets. This is a documented external retrieval example, not proof of full-account portability. |
Alvys describes a dedicated team guiding customers through onboarding, training, and data migration. |
The Google Sheets example documents selected live data retrieval; a complete customer-account export or exit procedure was not verified. |
| AscendTMS | Not verified in reviewed sources. |
Not verified in reviewed sources. |
Not verified in reviewed sources. |
Checked https://www.ascendtms.com/api, which showed a login/restricted-page gate rather than public API documentation, and https://support.ascendtms.com/help, which provided support contact options. No public product integration, outbound data retrieval/export example, or customer onboarding/deployment process was verified. |
| Axon Software | Axon says its fleet management software integrates with satellite trucking interfaces, naming Omnitracs, Shaw Tracking, and PeopleNet for real-time driver communication and shipment-status/GPS updates. |
Not verified in reviewed sources. |
Axon's process describes collecting records from a prior system for import, followed by live online training with a dedicated trainer using the customer's data. |
The described migration is into Axon; no outbound customer data export or portability example was verified. |
| Banyan Technology LIVE Connect | LIVE Connect v3 web-services documentation covers authentication and shipment, tracking, and invoice operations. |
The API documentation includes retrieval operations for shipments/invoices and operations to mark records as exported. This documents API-level record handling, not a full-account portability facility. |
Not verified in reviewed sources. |
The fetched documentation is developer integration/API guidance; a customer onboarding or deployment process was not verified. |
| BEYOND TRUCKS TMS | BeyondTrucks' official legacy-route content describes Orderful EDI embedded in BeyondTrucks, converting EDI data via API and synchronizing transaction data. |
Not verified in reviewed sources. |
Not verified in reviewed sources. |
The integration evidence was fetched from an official URL under /drafts/old/; it is a legacy-route product claim, not a public API specification. No outbound export example or customer implementation process was verified. |
| Blue Yonder TMS | Blue Yonder's Transportation Execution product page describes interoperability, EDI/tracking-provider integrations, and APIs for coordinating carrier and supplier relationships. |
Not verified in reviewed sources. |
Blue Yonder's TMS-specific SaaS resource describes a template-based implementation methodology intended to improve consistency and supportability. |
No documented outbound data retrieval/export example was verified; interoperability and API references are not evidence of customer data portability. |
| CXT Software | CXT describes partner and custom integrations that send and receive data between its solution and shipper systems. |
The official pricing/features page lists an “Own Your Data” feature for importing, exporting, and updating data, and describes API access to driver, shipment, and business-intelligence information. Export scope is not specified. |
CXT describes an onboarding team, project roadmap, implementation planning, and training as part of customer implementation. |
The pricing page points to API documentation, but public API reference details were not verified. |
| Descartes Aljex TMS | Aljex Live documents a REST API for creating, updating, processing, and retrieving shipments, with GLN SSO session-token authentication. |
The API documentation says shipment data can be retrieved during the shipment lifecycle; returned fields may be limited by customer configuration and user role. This is record-level API retrieval, not a full-account export guarantee. |
Not verified in reviewed sources. |
Public API documentation was verified, but it is developer guidance rather than a customer onboarding/deployment process. No comprehensive account export was verified. Do not transfer Aljex evidence to Descartes 3Gtms. |
| Dispatch Science | DataBridge advertises API and EDI connectivity, including ANSI X12 support and configurable processing. |
DataBridge explicitly supports file import/export and FTP file downloads. This is a documented integration-platform mechanism, not proof of full-account portability. |
Not verified in reviewed sources. |
The API reference at https://api.dispatchscience.com/reference documents developer integration setup only; it is not a customer onboarding/deployment process. No separate customer implementation process or full-account export was verified. |
| DispatchTrack | DispatchTrack says its extensible APIs receive order data from ERP systems to create delivery plans and send completed-delivery information back to the ERP. |
For the billing and settlement feature, users can export generated billing/settlement reports to accounting software as CSV; this is a scoped report export, not full-account portability. |
DispatchTrack describes customer onboarding experience, data integration, documented processes, and change-management expertise. |
The CSV example is limited to billing and settlement reports; no broader account-data portability claim was verified. |
| E2open BluJay TMS | The current E2open Transportation Management page says the TMS supports standard and custom EDI and API integrations with ERP, WMS, and other supply-chain platforms. |
Not verified in reviewed sources. |
The TMS FAQ says implementation timelines depend on network, carrier/mode, and integration complexity, and that E2open's implementation team configures the platform to customer workflows. |
The fetched product page names current E2open Transportation Management, not BluJay TMS; this does not establish that every legacy BluJay version has the same capabilities. No outbound data retrieval/export example was verified. |
| Eka TMS | EKA Omni-TMS describes native EDI and API connectors, API-first connections, webhooks, and a partner sandbox. |
Not verified in reviewed sources. |
The EKA support article describes DAT customer integration setup, including DAT coordination, credential configuration in Omni-TMS, and completion by EKA Customer Success. |
The implementation evidence is specifically for the DAT integration process; no outbound data retrieval/export example was verified. |
| FarEye | FarEye's Delivery Platform API reference documents endpoints for consignments, slots, routes, tracking/status updates, and reference data. |
Not verified in reviewed sources. |
FarEye's customer integration guide describes setup paths for outsourced or insourced fleets and parcel, bulky, or freight use cases, including order, checkout, slot, and tracking integration steps. |
The carrier onboarding guide says endpoint and authentication specifics are supplied by the FarEye implementation contact; no outbound data retrieval/export example was verified. |
| Fleet Enable | Fleet Enable says orders can be accepted through EDI, API, PDF scanning, or manual entry and describes scalable TMS integrations. |
Not verified in reviewed sources. |
Fleet Enable says it builds and tests forwarder EDI connections, trains customer teams before go-live, and reports average onboarding of about 10 weeks with customer-controlled cutover. |
No outbound data retrieval/export example was verified. |
| FreightPOP | FreightPOP describes a unified freight API connecting ERP, WMS, and e-commerce systems to carrier rating, booking, labels, tracking, and invoice auditing. |
FreightPOP says approved invoices, with GL codes, can be exported automatically to an accounting system/ERP; this is a scoped invoice-data export, not full-account portability. |
The API page says prebuilt connectors accelerate go-live and describes expert onboarding and ongoing support. |
The data export example is specifically approved freight invoice data. No broader account-data portability claim was verified. |
| Freightview | Freightview's official API v2 documentation describes a REST/JSON API using OAuth 2.0, with shipment workflows, webhooks, sandbox, and workflow guides. |
The API documents GET shipment search, shipment detail, quote, and tracking-history endpoints, providing retrieval of shipment records; this is API-level access, not a full-account portability guarantee. |
Not verified in reviewed sources. |
The supplied C.H. Robinson Freightview path https://www.chrobinson.com/en-us/technology/freightview/ returned 404 when checked. The Freightview-branded API site was used; its getting-started and developer guides are API documentation only, not customer onboarding/deployment process evidence. |
| Infios TMS | Infios Transportation Management's product FAQ says it integrates with common ERP, WMS, and OMS platforms plus EDI, APIs, SFTP, webhooks, tracking platforms, and accounting tools. |
Not verified in reviewed sources. |
The TMS FAQ says implementation timelines vary with network and integration complexity and that Infios's implementation team configures the platform to customer workflows. |
Evidence is from the Infios TM product page, which identifies MercuryGate TMS as now Infios Transportation Management. No outbound data retrieval/export example was verified. |
| IntelliTrans TMS | The IntelliTrans API portal describes Truck and Rail/Ocean APIs and guides for exchanging shipment, status, financial-workflow, and partner-connectivity data. |
Not verified in reviewed sources. |
Not verified in reviewed sources. |
The fetched portal provides API/developer guides and quickstarts only; no customer onboarding or deployment process, or outbound data retrieval/export example, was verified. |
| Kuebix TMS | The Kuebix/FreightWise integrations page lists SFTP, AS2, and API/web-service protocols, and EDI X12, JSON, CSV/TSV, XML, fixed-length, and custom flat-file formats. |
Not verified in reviewed sources. |
Not verified in reviewed sources. |
Kuebix is presented under FreightWise; cited integration evidence explicitly names Kuebix or Kuebix/FreightWise TMS. No outbound data retrieval/export example was verified. |
| Loadsmart TMS | The official developer portal identifies ShipperGuide API as the API for integrating ShipperGuide TMS capabilities into applications; API access requires an active Shipper account and credentials requested through an account manager. |
Not verified in reviewed sources. |
Not verified in reviewed sources. |
The official portal identifies ShipperGuide TMS as the TMS product; if the assigned name refers to another Loadsmart offering, that mapping is unverified. The checked setup material is a developer API quickstart, not customer onboarding/deployment documentation. Data export or portability was not verified in the ShipperGuide API documentation reviewed. |
| Magaya | Not verified in reviewed sources. |
Not verified in reviewed sources. |
Not verified in reviewed sources. |
The Magaya Open API page describes an API for Magaya's logistics technology ecosystem but does not establish that it belongs to a specific product named simply “Magaya”; product scope is ambiguous, so this ecosystem evidence is not assigned to the product. Data export/portability and customer implementation documentation were not verified in the official Magaya Open API page or the Magaya Supply Chain documentation portal reviewed. |
| Manhattan TMS | Not verified in reviewed sources. |
Not verified in reviewed sources. |
Not verified in reviewed sources. |
The Manhattan TMS product page was checked alongside generic Manhattan REST API guidance and the Developer Hub reference index. The index mentions Transportation Management in API-rate-limit guidance, but the REST guide points to solution-specific references and the reviewed sources do not establish a TMS-specific integration endpoint or customer implementation process. Generic Manhattan API/data tooling evidence is not attributed to this product. |
| McLeod LoadMaster | McLeod's LoadMaster Enterprise page lists off-the-shelf, tested and supported integrations for LoadMaster. The separately checked McLeod Innovation Hub also specifically describes its Symphony API as serving telematics and ELD partners integrating with LoadMaster for Truckload Carriers. |
Not verified in reviewed sources. |
McLeod describes implementation project management, configuration/process design, training, change management, and onsite go-live support; the page's product selector explicitly includes LoadMaster. |
No product-scoped data export or portability example was verified in the LoadMaster integration page or McLeod API material reviewed. |
| McLeod PowerBroker | This official product URL serves McLeod's “Standard Integration Solutions for PowerBroker” page, which describes tested and supported integrations available for PowerBroker. |
Not verified in reviewed sources. |
McLeod describes implementation project management, configuration/process design, training, change management, and onsite go-live support; the page's product selector explicitly includes PowerBroker. |
The checked McLeod API catalog does not establish a PowerBroker-specific outbound data export/retrieval example or API contract. LoadMaster-specific Symphony API evidence was not transferred to PowerBroker. |
| MyCarrierTMS | The official MyCarrier Help Center Integrations collection lists API documentation and FTP/SFTP integration collections, as well as named platform integrations. |
Not verified in reviewed sources. |
The official Getting Started collection is for customers after registration and links account-setup guidance, including third-party setup, adding locations, and adding carriers. |
The integration collection verifies that API and FTP/SFTP documentation is published, but the reviewed collection did not provide an outbound data retrieval/export example. No product data export/portability example was verified. |
| OnTime 360 | OnTime says its API connects an OnTime account with other systems and supports real-time order creation, updates, and tracking through REST and SOAP web services. |
Not verified in reviewed sources. |
The guide describes OnTime Advisory Services for installation/configuration and deployment/migration support. |
The guide's table of contents mentions an Exporting Data section, but the reviewed extract did not establish the records or scope exported. Data retrieval/export was therefore not verified for this study. |
| Oracle TMS | Oracle's Transportation and Global Trade Management API catalog links REST API references for business-object resources and data export. |
The API catalog explicitly links “REST API for Fusion Cloud Transportation and Global Trade Management Data Export,” documenting outbound data export through REST APIs. |
Oracle's Transportation and Global Trade Management Get Started portal links implementation guides and integration guides for the product. |
The cited API catalog is release 25C and the cited Get Started portal is release 26B; the documentation is for Oracle Transportation and Global Trade Management. |
| PCS Software | PCS says its Open API supports bidirectional data sharing with proprietary and third-party systems, initially for Loads, Invoices, and Locations; it describes the Loads API as a way to receive load offers directly in the TMS instead of EDI. |
PCS describes customer access to platform data through business intelligence and data extractors; this is documented data retrieval, not a claim of full-account portability. |
PCS describes customer onboarding with a dedicated implementation specialist, Excel import of customers/drivers/vehicles/delivery addresses, system configuration, role-based training, integration setup, and go-live planning. |
The data-access evidence is scoped to PCS business intelligence and data extractors; no full-system export/exit guarantee was verified. |
| Qargo | Qargo TMS API documentation describes OAuth2 client-credential authentication and tenant-level operational integrations; the API documentation also describes event visibility messages delivered through webhooks or EDI. |
Qargo documents an API operation to export a manually created order in order-creation format, for reuse as a template. |
Qargo describes a customer onboarding process with kickoff, discovery, implementation checklist, environment setup, user training, and user testing; it also describes migration support for customer information and records. |
The documented API export is an existing order-as-template operation, not evidence of full-account data portability. |
| Revenova TMS | Official release describes an upgraded SMC³ LTL API integration and EDI enhancements for 204, 214, and 990 documents. |
Not verified in reviewed sources. |
Not verified in reviewed sources. |
Export or portability and customer implementation/onboarding documentation were not verified in the reviewed official sources: https://revenova.com/ and https://revenova.com/tms-solutions/platform. Null means not verified, not absent. |
| Rose Rocket | Official API guide documents account setup, OAuth application credentials, bearer-token authorization, and API requests. |
The API guide includes a Retrieve customer information example, documenting retrieval of an individual customer's information; this is not evidence of bulk account export. |
The official guide describes CSV imports of historical/bulk orders, quotes, manifests, customers, partners, and assets to support account setup and preserve legacy records. |
The reviewed data-import guide documents inbound CSV imports, not outbound bulk portability. API evidence is individual customer retrieval. |
| Routific | Official Platform API documentation describes REST endpoints for creating orders, routes, and schedules to automate delivery planning from external systems. |
The API documents GET retrieval of a completed schedule solution and route timelines, including order completion statuses and planned-versus-actual ETA data. |
Not verified in reviewed sources. |
No customer onboarding/deployment process was verified; the reviewed getting-started material is developer API setup and does not meet the requested implementation scope. The API documentation distinguishes the new Platform API from the standalone Routing Engine API; evidence is limited to the explicitly cited Platform API. |
| Rygen Corsair TMS | Corsair connects ERP/WMS and other systems through Rygen's X1 platform, using EDI, API integrations, or custom data flows. |
The Corsair TMS page documents exportable reports, including operational KPIs and carrier scorecards; this is report export, not verified full-account portability. |
The product FAQ says Rygen's implementation team handles configuration and onboarding, with deployments sequenced according to carrier-network and integration complexity. |
Data-access evidence is limited to exportable reports; no full-account or bulk portability mechanism was verified. |
| SAP TMS | The SAP Transportation Management technical page links product integration guides and directs custom-app developers to SAP Business Accelerator Hub APIs and integration packages. |
Not verified in reviewed sources. |
The product page links installation guidance for SAP Transportation Management and describes implementation/configuration information and implementation services. |
Product-data export or portability was not verified in the reviewed product pages. The linked API catalog presented a sign-in page, so no specific public endpoint was verified. This evidence concerns SAP Transportation Management, not the separate Cloud Transport Management service. |
| Sennder | Not verified in reviewed sources. |
Not verified in reviewed sources. |
Not verified in reviewed sources. |
The fetched page describes sennder's digital freight platform and FMCG shipping service, not a distinct product named Sennder TMS. It provides no API specification or customer deployment process; evidence must not be generalized to an unidentified TMS product. |
| Shipium Platform | Shipium describes an API-first, modular integration framework with flexible APIs for customizing data flows across existing systems. |
The Shipium Console provides downloadable shipment-data exports configured by carrier, tenant, and date range; the documented range is six weeks and no more than 100 days back. |
Shipium describes a dedicated customer implementation team and a managed migration journey with kickoff, API integration, testing, and go-live stages. |
The documented export is time-bounded; older shipment data requires a support request, so unrestricted historical portability was not verified. |
| Shipsy TMS | The TMS product page describes prebuilt ERP connectors and open APIs/webhooks for integration with systems including SAP, Oracle, Microsoft Dynamics, and custom ERPs. |
The TMS page says open APIs and webhooks push shipment, rate, and exception data to downstream systems; this verifies those outbound data flows, not a bulk export. |
Not verified in reviewed sources. |
No bulk data-export facility or detailed public deployment manual was verified. The supplied shipsy.io TMS URL resolves to the Shipsy.ai TMS page; evidence is from that TMS page only, not Shipsy's separate WMS material. |
| Shipwell | Shipwell documents EDI connectivity through supported VANs Orderful and Kleinschmidt, connection options including FTP, AS2, and HTTP, and supported transactions such as 204, 990, 214, and 210. |
Not verified in reviewed sources. |
Not verified in reviewed sources. |
No customer onboarding/deployment process or data export/portability example was verified. The reviewed getting-started guide is developer API and sandbox setup, which is not customer implementation evidence. |
| Tai TMS | Tai's developer portal documents REST APIs and webhooks for synchronizing supply-chain, order, and shipment data with internal systems. |
The portal explicitly describes pushing and pulling supply-chain, order, and shipment data between Tai and internal systems; this verifies API-level data retrieval, not a full-account or bulk export. |
Tai describes a customer onboarding path covering kickoff, process discovery, migration of address books/carriers/shipment history, training, integration setup, testing, and go-live. |
Data access is documented as API push/pull and shipment-data synchronization; no full-account or bulk export facility was verified. |
| Trimble Transporeon TMS | Not verified in reviewed sources. |
Not verified in reviewed sources. |
Not verified in reviewed sources. |
The reviewed official pages describe Transporeon platform integrations with a carrier's in-house TMS and a general platform API onboarding process, but do not verify a product specifically named Transporeon TMS. Those adjacent-product/platform claims are not attributed to this named product. |
| Transport Pro | The TMS features page describes in-house native EDI and a public API for connecting data with other tools. |
Transport Pro says built-in reports can be exported to Excel or CSV; this verifies report export, not full-account portability. |
Not verified in reviewed sources. |
An official integration-partners page was reviewed, but no customer deployment or onboarding process was verified in the sources reviewed. |
| Trimble TMW Suite | The TMW.Suite product page describes connecting TMW.Suite with popular tools, including fuel-card and asset-tracking tools. |
Not verified in reviewed sources. |
Trimble's SaaS onboarding article explicitly names TMW.Suite and outlines a customer conversion process from an on-premise Trimble TMS installation to its SaaS offering. |
The reviewed official sources did not verify a TMW.Suite outbound data retrieval or export example. |
| Turvo Collaboration Hub | Not verified in reviewed sources. |
Not verified in reviewed sources. |
Not verified in reviewed sources. |
Turvo's official pages describe a Turvo Integration Hub and collaborative platform, but do not verify a distinct product named Turvo Collaboration Hub. Integration Hub evidence is not attributed to this ambiguously named product. |
| Turvo TMS | Turvo's transportation-management-system page describes open APIs connecting Turvo TMS with its Partner Network and Integration Hub. |
Not verified in reviewed sources. |
Not verified in reviewed sources. |
The reviewed official pages did not verify an outbound retrieval/export example or a customer TMS deployment/onboarding process; API documentation and developer/API onboarding material alone are not treated as implementation evidence. |
| Uber Freight TMS | Not verified in reviewed sources. |
Not verified in reviewed sources. |
Not verified in reviewed sources. |
The reviewed Uber Freight developer sources document API products and their technical integration onboarding, but do not establish those APIs as integration or customer implementation evidence for the named Uber Freight TMS product. |
| Wise Systems | Wise Systems describes an API-based Encompass integration that loads inventory and stop-address data into Wise Systems. |
In the Encompass integration example, planned routes are exported back to Encompass for picking and packing; this is a scoped route-data export, not full-account portability. |
Wise Systems describes customer deployment with platform configuration, connection to existing ERP/OMS/telematics systems, and hands-on dispatcher and driver training. |
The data-access evidence is specifically the documented Encompass route-export workflow. |
Limitations
- This is a review of public documentation, not a product test, security audit, feature certification, or assessment of the quality of an integration.
- A named integration, API endpoint, report export, or data-retrieval example does not establish that every customer can use it, that it is included in a contract, or that it provides complete account portability.
- Vendor pages can change, require a login, or describe a parent platform rather than the exact catalog product. Product-specific scope is noted in the table where the reviewed source made that distinction unclear.
- The counts describe only this SupplyWolf catalog snapshot and review date. They should not be generalized to all TMS vendors.
Review date: 2026-09-29. Please confirm current product scope and documentation directly with each vendor.