Third-Party Logistics integration
Hub Group EDI integration
A guide for shippers and carriers connecting with Hub Group, covering transportation EDI, warehouse shipping orders and ERP or TMS integration.
Overview
Understanding Hub Group integration
Who this is for: Shippers using Hub Group for intermodal, managed transportation or fulfillment, and carriers hauling freight on Hub Group's managed transportation channel.
Hub Group provides intermodal, truckload, managed transportation, logistics and fulfillment services. Because it acts as a transportation provider, a managed transportation provider and a warehouse operator, the EDI documents a company exchanges with Hub Group depend on which service it uses.
Third-party directories list two Hub Group channels. The managed transportation channel, listed under the Unyson name, carries the standard tender cycle: the 204 load tender, the 990 tender response, 214 shipment status messages and the 210 freight invoice. A second channel, listed under CaseStack, carries the 940 warehouse shipping order used to release inventory from a warehouse.
Directory listings show what has been exchanged, not every requirement. Companies starting with Hub Group should request the implementation guides for their service, confirm identifiers and versions, and test each document before production. Shippers usually also want status messages to update their ERP or TMS automatically and freight invoices to reconcile against tendered rates.
Workflows
Typical Hub Group business workflows
Managed transportation tender cycle
- 1Receive 204 load tender
- 2Send 990 response
- 3Send 214 status updates
- 4Send 210 freight invoice
Warehouse fulfillment
- 1Send 940 shipping order
- 2Warehouse picks and ships
- 3Receive shipment confirmation
- 4Invoice the customer
Documents and APIs
Common Hub Group transactions
Documents commonly exchanged with Hub Group, based on the public sources listed below. Exact requirements depend on your program, so always confirm against Hub Group's current implementation guide.
| Document | Name | Direction | Purpose |
|---|---|---|---|
| 204 | Motor Carrier Load Tender | Both directions | Offers a load; direction depends on whether you are a shipper or carrier. |
| 990 | Response to a Load Tender | Both directions | Accepts or declines a tender. |
| 214 | Shipment Status Message | Both directions | Reports pickup, in-transit and delivery events. |
| 210 | Motor Carrier Freight Details and Invoice | Both directions | Bills freight charges for a load. |
| 940 | Warehouse Shipping Order | To Hub Group | Instructs the warehouse to ship inventory. |
Connectivity
How companies connect
EDI by service
Transportation and warehouse services use different channels, identifiers and document sets.
Testing per channel
Each channel's documents, versions and identifiers should be confirmed and tested with Hub Group.
Challenges
Common integration challenges
Different documents by service
Transportation and fulfillment services use different documents, so setups must be planned per service.
Status timeliness
Status messages must be sent promptly with correct event codes so shippers see accurate visibility.
Freight invoice matching
Freight invoices must reference the right load and agreed charges to avoid payment delays.
How ECOM helps
How ECOM can support your Hub Group integration
Logistics Automation
Automate tenders, status updates and freight invoices between your systems and Hub Group.
Industry3PL and Warehousing
See how ECOM supports warehouse and fulfillment integrations.
ProductPRISM-SCV
Monitor tender responses, status gaps and warehouse orders in one place.
ERP integration options
ECOM integrates Hub Group tenders, status messages, freight invoices and warehouse orders with ERP, TMS and WMS platforms, keeping each service's channel and identifiers separate.
Visibility and exception management
PRISM-SCV, ECOM's supply chain visibility product, is designed to follow each Hub Group document from receipt to response and flag late or missing documents and mismatches, so your team can resolve exceptions before they affect the relationship.
Explore PRISM-SCVHub Group integration FAQs
Which EDI documents are used with Hub Group?
Third-party directories list the 204, 990, 214 and 210 on Hub Group's managed transportation channel and the 940 on a warehouse channel. Confirm the exact set with Hub Group.
Why do Hub Group channels differ?
Hub Group offers transportation and fulfillment services, and each service exchanges different documents through its own channel.
Do carriers and shippers use the same documents?
They use the same tender cycle documents in opposite directions. Shippers send tenders and receive status and invoices; carriers do the reverse.
Is ECOM a Hub Group partner?
This page is an integration guide and does not indicate a partnership with Hub Group. ECOM builds integrations to the specifications Hub Group provides.
Sources and accuracy
This guide summarizes publicly available information as of October 2026. Hub Group sets its own requirements and can change them at any time; your Hub Group implementation guide, supplier portal or account contact is the authoritative source for your program.
- Stacksync, Hub Group EDI channels Third-party source
Hub Group is a trademark of its owner. Its mention does not imply endorsement of, or a partnership with, ECOM Specialist.
Related integrations
More third-party logistics integration guides
C.H. Robinson EDI
A guide for carriers and shippers connecting with C.H. Robinson, covering load tenders, status updates, invoicing and API options.
J.B. Hunt EDI
A guide for shippers connecting their ERP or TMS with J.B. Hunt, covering EDI load tenders and status updates and J.B. Hunt 360 APIs.
Ryder EDI
A guide for carriers tendered freight by Ryder and for companies using Ryder logistics services, covering EDI documents and onboarding.
Request Hub Group integration assistance
Tell us about your Hub Group program, documents and ERP. We will outline the connection, mapping and testing plan.