Trading Partner: Rona
If you are looking to implement Rona 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
Rona utilizes the following EDI ID for identification purposes. This EDI ID is 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 ID used by Rona.
X12 Qualifier | EDI ID | Primary ID? |
01 | 204197800 | Yes |
01 | 254979594 | No |
ZZ | TST1RONAINC | No |
Rona 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 Rona to determine the proper EDI ID to use.
Preliminary Steps
To initiate the EDI Setup, Rona vendors will need to contact Rona directly at [email protected]. The EDI Onboarding Form will need to be completed and sent back to Bashas. Below is the EDI information required for the form:
EDI Version: 4010
Network: VAN - GXS (through the TrueCommerce mailbox)
Direct Trading Partner Testing
Rona requires you to complete compliance testing before Go-Live. Refer to the Next Steps section in this article for detailed instructions and expectations. If you prefer, TrueCommerce can conduct and complete compliance testing on your behalf.
Commonly Used Transactions
The table, below, lists the most commonly used EDI transactions with Rona.
EDI Transaction |
Next Steps
Once the purchase of the Rona 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. 8/12/2026