Skip to main content

Trading Partner Onboarding - Bashas

If you are looking to implement Bashas 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: Bashas


EDI IDs


Bashas utilizes the following Electronic Data Interchange (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 Bashas.

X12 Qualifier

EDI ID

Primary ID?

08

9289850000

Yes

12

6028955234

No

Bashas 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 Bashas to determine the proper EDI ID to use.


Preliminary Steps


To initiate the EDI Setup, Bashas vendors will need to contact Bashas directly at [email protected]. The Bashas Trading Partner EDI Communication Sheet will need to be completed and sent back to Bashas. Below is the EDI information required for the form:


Direct Trading Partner Testing


Bashas 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 Bashas:


Next Steps


Once the purchase of the Bashas 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/7/2026

Did this answer your question?