Trading Partner: Cardinal Health
If you are looking to implement Cardinal Health as a new Trading Partner within your Electronic Data Interchange (EDI) network, this article will provide you with an understanding of the requirements, preliminary and next steps, as well as commonly used transaction types.
EDI IDs
Cardinal Health utilizes the following 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 sent/received EDI transaction.
The table, below, lists the most common EDI IDs used by Cardinal Health.
X12 Qualifier | EDI ID | Primary ID? |
ZZ | CARDINAL | Yes |
01 | RB0130586 | No |
ZZ | CARDINALCSOS | No |
ZZ | 255047102 | No |
Cardinal Health 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 Cardinal Health to determine the proper EDI ID to use.
Preliminary Steps
Vendors of Cardinal Health must contact [email protected] to begin the EDI setup process. During this time, confirm what transactions scope Cardinal Health would require with your organization.
Test Exempt Relationship
Cardinal Health does not require TrueCommerce customers to complete compliance testing prior to exchanging live orders via EDI. Cardinal Health will establish the relationship in production and will issue live orders.
Commonly used Transactions
The table, below, lists the most commonly used EDI Transactions from Cardinal Health.
EDI Transaction |
Each Cardinal Health vendor should discuss with the trading partner directly on which transactions will be required once the EDI relationship is setup. The type of transaction sets may vary per vendor.
Next Steps
Once the purchase of the Cardinal Health plug-in is complete, your Implementation Specialist will reach out to schedule time to coordinate Enterprise Resource Planning (ERP) system integration setup (as applicable) and production readiness.
Related Documentation
rev. 8/10/2026