Trading Partner: Hy-Vee Inc
If you are looking to implement Hy-Vee Inc 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.
EDI IDs
Hy-Vee Inc 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 Hy-Vee Inc
X12 Qualifier | EDI ID | Primary ID? |
08 | 9264350000 | Yes |
08 | 9264350000RX | No |
08 | 5157742121 | No |
ZZ | 9264350000T | No |
Hy-Vee Inc 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 Hy-Vee Inc to determine the proper EDI ID to use.
Preliminary Steps
In order to begin the EDI process, Hy-Vee vendors will need to contact Hy-Vee Inc directly at [email protected] and provide the following details:
Compliance version (4010 or 5010)
EDI Provider = TrueCommerce
VAN = Liaison
EDI / Support Contact Details from your company
Direct Trading Partner Testing
Hy-Vee Inc requires you to complete compliance testing before Go-Live. Please refer to the below Next Steps section for detailed instructions and expectations. If you prefer, TrueCommerce can conduct and complete compliance testing on your behalf.
Commonly Used Transactions
Below is a list of most commonly used EDI transactions with Hy-Vee Inc:
Next Steps
Once the purchase of the Hy-Vee Inc 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
rev: 7/30/2026
