Skip to main content

Trading Partner Onboarding - Hub Group

If you are looking to implement Hub Group as a new Trading Partner within your EDI network, this article will provide you with an understanding of the requirements, preliminary and next steps, as well as commonly used transaction types.

S
Written by Stacie McGee

Trading Partner: Hub Group


EDI IDs


Hub Group utilizes the following Electronic Data Interface (EDI) IDs for identification purposes. These EDI IDs are made up of a Qualifier and an ID which will be sent within their Interchange Control Header, ISA segment, on your inbound transactions. This allows Transaction Manager to be able to identify the Sender and Receiver of any EDI transaction that is sent or received.

Below is a list of the most common EDI IDs typically used by Hub Group:

X12 Qualifier

EDI ID

Primary ID?

02

HUBG

Yes

ZZ

HUBGTEST

No

ZZ

HUBCFS

No

ZZ

HUBCFST

No

Hub Group will expect a specific EDI ID based on your business relationship with them. Selecting the wrong EDI ID will result in EDI Transactions not being sent or received.

You will need to work with Hub Group to determine the proper EDI ID to use.


Preliminary Steps


To establish an EDI relationship with HubGroup, their team recommends that their suppliers contact their Customer Success Team.

Please complete the attached TrueCommerce Warehouse Setup form and provide to your Account Manager (located under the Related Documentation Section of this guide).


Direct Trading Partner Testing


Hub Group requires you to complete compliance testing before Go-Live. Please refer to the below Next Steps section for detailed instructions and expectations.


Commonly Used Transactions

Below is a list of most commonly used EDI transactions with Hub Group:


Next Steps


Once the purchase of the Hub Group plug-in is complete, your Implementation Specialist will reach out to schedule time to complete and/or coordinate a plan for compliance testing and/or Enterprise Resource Planning (ERP) system integration testing.


Related Documentation


Did this answer your question?