To start and identify an interchange of zero or more functional groups and interchange-related control segments
Dillard's Department Stores, Inc. X12 816 Organizational Relationships
X12 816 (Organizational Relationships) is the EDI transaction exchanged between Dillard's Department Stores, Inc. (Dillards Department Stores(Inovis VAN)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 12
- Loops
- 2
- X12 816
- All partners ↗
Transaction context
Where 816 Organizational Relationships fits on Dillards Department Stores(Inovis VAN)
- Dillard's Department Stores, Inc. channels
- 3 of 3
- Trading partners
- 4
- Channels
- 6
3 of Dillard's Department Stores, Inc.'s 3 channels carry 816
partners across the Stacksync network trade 816
channels network-wide carry 816
Most common alongside 816
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.
When it fires: 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.
Common 816 rejection causes
- Location codes not loaded or updated in the supplier's system, so later purchase orders and ASNs reference store or DC codes the receiver cannot resolve.
- Stale or incomplete address data after a store opens, closes, or relocates, causing shipments to be routed to the wrong facility.
- Errors in the relationship data linking buying, bill-to, ship-to, and mark-for locations, which corrupts how downstream documents are addressed.
- Updates applied without confirmation when the receiving supplier fails to return a 997 functional acknowledgment, leaving the sender unsure the change took effect.
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 |
Key identifiers in 816
- Hierarchical Structure Code
- Transaction Set Purpose Code
- Entity Identifier Code
- Hierarchical ID Number
- Hierarchical Level Code
- Address Information
- Contact Function Code
- Reference Identification Qualifier
Full segment guideline — 12 segments 2 loops · X12 816 Organizational Relationships
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To define the business hierarchical structure of the transaction set and identify the business application purpose and reference data, i.e., number, date, and time
N1 Loop
To identify a party by type of organization, name, and code
HL Loop
To identify dependencies among and the content of hierarchically related groups of data segments
To specify the location of the named party
To specify the geographic place of the named party
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To specify identifying information
To specify pertinent dates and times
To indicate the action to be taken with the information provided or the status of the entity described
Trading partners
2+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
No trading partner matches your search.
Browse the full directory
Trading partners
9+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
Dillard's Department Stores, Inc. Dillards Department Stores(Inovis VAN) EDI 816 FAQ
Common questions about 816 Organizational Relationships on the Dillards Department Stores(Inovis VAN) channel.
What is X12 816 Organizational Relationships?
X12 816 (Organizational Relationships) is the EDI transaction set used to exchange organizational relationships data. Dillard's Department Stores, Inc.'s Dillards Department Stores(Inovis VAN) channel requires it from trading partners.
Does Dillard's Department Stores, Inc. Dillards Department Stores(Inovis VAN) require 816 for trading partners?
Yes, Dillard's Department Stores, Inc. (Dillards Department Stores(Inovis VAN)) supports X12 816 Organizational Relationships. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Dillard's Department Stores, Inc. 816 with Stacksync?
Most companies go live with Dillard's Department Stores, Inc. 816 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which other Dillard's Department Stores, Inc. channels accept 816?
X12 816 runs on 3 of Dillard's Department Stores, Inc.'s 3 channels. Besides Dillards Department Stores(Inovis VAN), it is accepted on Dillards Department Stores(TGMS Customers), Dillards Department Stores via InterTrade. Each channel carries its own implementation guideline; Stacksync validates outbound documents against the correct guideline automatically.
Ready to automate your Dillard's Department Stores, Inc. EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
