X12 transaction code
X12 816 Organizational Relationships
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 816
- Trading partners
- 4
Specification summary
X12 816 Organizational Relationships at the element level
The X12 816 specification defines 17 segments carrying 79 data elements, 38 of which are mandatory.
- Segments
- 17
- Data elements
- 79
- Mandatory elements
- 38
| Segment | Elements | Mandatory |
|---|---|---|
| BHT | 6 | 2 |
| N1 | 6 | 1 |
| HL | 4 | 2 |
| N3 | 2 | 1 |
| PER | 9 | 1 |
| REF | 3 | 1 |
| DTM | 6 | 1 |
| ASI | 3 | 2 |
- Hierarchical Structure Code
- Transaction Set Purpose Code
- Entity Identifier Code
- Hierarchical ID Number
- Hierarchical Level Code
- Address Information
- Contact Function Code
- Reference Identification Qualifier
Trading partners that support X12 816
4 partners, 6 channels. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 816 Organizational Relationships
816 is used most heavily in apparel & footwear and retail.
The 816 communicates organizational structure and location information: store, warehouse, and distribution center addresses, their identifying codes, and the relationships between buying, bill-to, ship-to, and mark-for locations. Trading partners require it because most other EDI documents identify locations only by code, so both sides need a shared, current location master to route orders and shipments correctly. Typically sent by the buyer (a retailer or distributor) to its suppliers to publish and maintain the location codes that purchase orders and shipping documents will reference. A retailer opens a new store or distribution center, closes one, or changes a location's address, and needs every supplier's system updated before orders reference the new location codes.
By industry
- apparel & footwear 5 channels
- retail 1 channel
By network
- InterTrade 1 channel
FAQ
X12 816 questions
What is X12 816 Organizational Relationships?
X12 816 (Organizational Relationships) is an EDI transaction set defined by ANSI ASC X12 for exchanging organizational relationships between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 4 Stacksync trading partners support this code across 6 channels.
Which trading partners use X12 816?
4 Stacksync partners accept X12 816: Dillard's Department Stores, Inc., FootLocker, Shoe Carnival, Walmart. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 816 with my ERP?
Stacksync handles the full X12 816 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
