Skip to main content

Trading Partner Onboarding - Sonepar

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


EDI IDs


Sonepar 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 Sonepar:
​

X12 Qualifier

EDI ID

Primary ID?

ZZ

SONEPARIDXP

Yes

ZZ

SONEPARIDXT

No

ZZ

SONEPAR2IDXP

No

ZZ

SONEPAR2IDXT

No

01

006928931IDX

No

01

006928931IDX

No

ZZ

006964324

No

ZZ

006964324

No

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


Preliminary Steps


To initiate the EDI Setup process, Sonepar vendors will be required to email [email protected] and supply the following details:


Direct Trading Partner Testing


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


Next Steps


Once the purchase of the Sonepar 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: 9/24/2026


​


​

Did this answer your question?