X12
Inbound

Dillard's Department Stores, Inc. X12 816 Organizational Relationships

Dillards Department Stores via InterTrade
The EDI 816 communicates Dillard's Department Stores, Inc.'s organizational hierarchy and relationships between divisions, departments, and locations. Suppliers use this data to maintain accurate routing and compliance mapping.
13segments
3loops
8mandatory

Schema Reference

13 segments · X12 816 Organizational Relationships

ISA ISA Interchange Control Header
Mandatory Max: 1
ISA01 Authorization Information Qualifier
M ID 2-2
ISA02 Authorization Information
M AN 10-10
ISA03 Security Information Qualifier
M ID 2-2
ISA04 Security Information
M AN 10-10
ISA05 Interchange ID Qualifier
M ID 2-2
ISA06 Interchange Sender ID
M AN 15-15
ISA07 Interchange ID Qualifier
M ID 2-2
ISA08 Interchange Receiver ID
M AN 15-15
ISA09 Interchange Date
M DT 6-6
ISA10 Interchange Time
M TM 4-4
ISA11 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator ISA12 Interchange Control Version Number
M ID 5-5
ISA13 Interchange Control Number
M N0 9-9
ISA14 Acknowledgment Requested
M ID 1-1
ISA15 Usage Indicator
M ID 1-1
GS GS Functional Group Header
Mandatory Max: 1
GS01 Functional Identifier Code
M ID 2-2
GS02 Application Sender's Code
M AN 2-15
GS03 Application Receiver's Code
M AN 2-15
GS04 Date
M DT 8-8
GS05 Time
M TM 4-8
GS06 Group Control Number
M N0 1-9
GS07 Responsible Agency Code
M ID 1-2
GS08 Version / Release / Industry Identifier Code
M AN 1-12
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
BHT Beginning of Hierarchical Transaction
Mandatory Max: 1
BHT01 Hierarchical Structure Code
M ID 4-4
BHT02 Transaction Set Purpose Code
M ID 2-2
BHT03 Reference Identification
O AN 1-50
BHT04 Date
O DT 8-8
N1 Loop
N1 Name
Mandatory Max: 1
N101 Entity Identifier Code
M ID 2-3
N102 Name
C AN 1-60
HL Loop
HL Hierarchical Level
Mandatory Max: 1
HL01 Hierarchical ID Number
M AN 1-12
HL02 Hierarchical Parent ID Number
O AN 1-12
HL03 Hierarchical Level Code
M ID 1-2
N1 Loop
N1 Name
Mandatory Max: 1
N101 Entity Identifier Code
M ID 2-3
N102 Name
C AN 1-60
N3 Address Information
Optional Max: 2
N301 Address Information
M AN 1-55
N4 Geographic Location
Optional Max: 1
N401 City Name
O AN 2-30
N402 State or Province Code
C ID 2-2
N403 Postal Code
O ID 3-15
REF Reference Identification
Optional Max: 12
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-50
DTM Date/Time Reference
Optional Max: 10
DTM01 Date/Time Qualifier
M ID 3-3
DTM02 Date
C DT 8-8
ASI Action or Status Indicator
Optional Max: 1
ASI01 Action Code
M ID 1-2
ASI02 Maintenance Type Code
M ID 3-3
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating Dillard's Department Stores, Inc. EDI 816

Stacksync validates, transforms, and delivers your 816 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate
Transform
Route
Monitor
Stacksync syncs Dillard's Department Stores, Inc. 816 Organizational Relationships into your system — keeping division-to-location mappings current as Dillard's Department Stores, Inc. updates its internal structure.

Business unit variations

Dillards Department Stores(Inovis VAN)
Stacksync syncs Dillard's Department Stores, Inc. 816 Organizational Relationships into your system — keeping division-to-location mappings current as Dillard's Department Stores, Inc. updates its internal structure.
Dillards Department Stores(TGMS Customers)
Stacksync syncs Dillard's Department Stores, Inc. 816 Organizational Relationships into your system — keeping division-to-location mappings current as Dillard's Department Stores, Inc. updates its internal structure.

Dillard's Department Stores, Inc. EDI 816 FAQ

Common questions about 816 Organizational Relationships transactions with Dillard's Department Stores, Inc..

What is a Dillard's Department Stores, Inc. EDI 816 Organizational Relationships?

The Dillard's Department Stores, Inc. EDI 816 Organizational Relationships is an X12 transaction set used to exchange Organizational Relationships data electronically between trading partners. As a inbound document, it standardizes the communication of Organizational Relationships information between Dillard's Department Stores, Inc. and their suppliers, carriers, or partners. Stacksync processes Dillard's Department Stores, Inc. 816 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with Dillard's Department Stores, Inc.'s requirements in real time.

How does Stacksync automate Dillard's Department Stores, Inc. EDI 816 Organizational Relationships transactions?

Stacksync handles Dillard's Department Stores, Inc. EDI 816 Organizational Relationships transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 816 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every Dillard's Department Stores, Inc. 816 document meets their specific formatting requirements before transmission or after receipt.

What are common Dillard's Department Stores, Inc. EDI 816 errors and how do I fix them?

Common errors in Dillard's Department Stores, Inc. EDI 816 Organizational Relationships transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates Dillard's Department Stores, Inc. 816 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

How long does it take to set up Dillard's Department Stores, Inc. EDI 816 with Stacksync?

Most Dillard's Department Stores, Inc. EDI 816 Organizational Relationships integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between Dillard's Department Stores, Inc.'s 816 format and your system, running test transactions, and completing Dillard's Department Stores, Inc.'s certification process if required. Stacksync includes pre-built mappings for Dillard's Department Stores, Inc.'s most common 816 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

Can I customize Dillard's Department Stores, Inc. EDI 816 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how Dillard's Department Stores, Inc. EDI 816 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If Dillard's Department Stores, Inc. updates their 816 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate Dillard's Department Stores, Inc. EDI?

a blue checkmark icon
POC from integration engineers
a blue checkmark icon
No-code EDI setup
a blue checkmark icon
Real-time compliance monitoring
a blue checkmark icon
White-glove onboarding