Trading Partner: Bealls
EDI IDs
Bealls 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 Bealls:
X12 Qualifier | EDI ID | Primary ID? |
ZZ | BEALLSINC | Yes |
12 | 8137472355 | No |
12 | 9417472355 | No |
Bealls 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 Bealls to determine the proper EDI ID to use.
Preliminary Steps
Before TrueCommerce is able to begin onboarding Bealls into Transaction Manager, you will need to perform the following actions to kick off your Trading Partner Implementation Project:
Bealls requires testing to be conducted through the OpenText testing portal.
Please email the Bealls team at [email protected] for assistance with obtaining access to the testing portal.
Note that you will need to schedule time with the Bealls team prior to testing to review scope and requirements
TrueCommerce will collaborate with your team to obtain any company specific details that are needed for this phase of the implementation.
Portal Testing
Bealls 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.
If so, please provide the following information:
URL for the OpenText testing portal
Username for the OpenText testing portal
Password for the OpenText testing portal
Commonly-Used Transactions
Invoice (810)
Purchase Order (850)
Purchase Order Acknowledgement (855)
Advanced Shipping Notice (856)
Purchase Order Change Request (860)
Next Steps
Once the purchase of the Bealls 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.
Important Information
The 753 and 754 transactions are optional as of February 2026, but they are expected to become mandatory within the next 1–2 years. Bealls has informed customers that they can either begin testing now or wait. However, please be aware that customers who choose to delay testing may incur additional re-testing fees from OpenText at a later date.
Related Documentation
rev. 06/02/26