Skip to main content

Trading Partner Onboarding - B and H Photo & Video

If you are looking to implement B and H Photo & Video 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: B and H Photo & Video


EDI IDs


B and H Photo & Video utilizes the following Electronic Data Interface (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 EDI transaction that is sent or received.

Below is a list of the most common EDI ID typically used by B and H Photo & Video:

X12 Qualifier

EDI ID

Primary ID?

01

116012659

Yes

B and H Photo & Video 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 B and H Photo & Video to determine the proper EDI ID to use.


Preliminary Steps


To initiate the EDI Setup process, B and H Photo & Video requires vendors to complete their vendor form located on their website. The EDI details required for the form are:


Test Exempt Relationship


B and H Photo & Video does not conduct compliance testing. Once the vendor form is submitted, the relationship will be moved into production.


Commonly Used Transactions


Below is a list of most commonly used EDI transactions with B and H Photo & Video

Note: the transaction scope will be determined when the Vendor form is completed on the B and H Photo & Video website.


Next Steps


Once the purchase of the B and H Photo & Video plug-in is complete, your Implementation Specialist will reach out to schedule time to coordinate a plan for go-live and/or Enterprise Resource Planning (ERP) system integration setup.


Related Documentation


rev: 10/20/2026

Did this answer your question?