Sent by a trading partner to communicate detailed profile information about business capabilities, operational parameters, and trading conditions, the 838 transaction set enables organizations to establish or update their trading partner agreements. Typically transmitted in response to a request or proactively to establish new business relationships, this transaction uses the BTP (Beginning Segment for Trading Partner Profile) segment to initiate the profile submission, the TPD (Trading Partner Detail) segment to describe specific capabilities and business rules, and the TXN (Transaction Capabilities) segment to specify which EDI transactions the sender can support. Additional segments such as N1 (Name) and N4 (Geographic Location) identify parties and locations involved in the trading relationship, while operational details are captured through segments like DTM (Date/Time Reference), ITD (Terms of Sale), and TD5 (Carrier Details).

For example, suppose ABC Manufacturing requests that XYZ Logistics submit a trading partner profile to establish a logistics partnership. XYZ Logistics responds by sending an 838 transaction set that includes a TPD segment identifying XYZ as a third-party logistics provider, TXN segments indicating support for 856 (Advance Ship Notice), 810 (Invoice), and 997 (Functional Acknowledgment) transactions, N1 and N4 segments specifying XYZ’s corporate address and regional warehousing locations, an ITD segment detailing payment terms, and a TD5 segment describing their preferred routing capabilities. This comprehensive profile allows ABC Manufacturing to validate XYZ’s operational fit before integrating them into their supply chain network.