X12
Inbound

Walmart X12 816 Organizational Relationships

Walmart (Goods Not For Resale)
The EDI 816 communicates Walmart's organizational hierarchy and relationships between divisions, departments, and locations. Suppliers use this data to maintain accurate routing and compliance mapping.
14segments
3loops
8mandatory

Schema Reference

14 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 Interchange 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
ST03 Implementation Convention Reference
O AN 1-35
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
BHT05 Time
O TM 4-8
BHT06 Transaction Type Code
O ID 2-2
N1 Loop
N1 Party Identification
Mandatory Max: 1
N101 Entity Identifier Code
M ID 2-3
N102 Name
C AN 1-60
N103 Identification Code Qualifier
C ID 1-2
N104 Identification Code
C AN 2-80
N105 Entity Relationship Code
O ID 2-2
N106 Entity Identifier Code
O ID 2-3
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
HL04 Hierarchical Child Code
O ID 1-1
N1 Loop
N1 Party Identification
Mandatory Max: 1
N101 Entity Identifier Code
M ID 2-3
N102 Name
C AN 1-60
N103 Identification Code Qualifier
C ID 1-2
N104 Identification Code
C AN 2-80
N105 Entity Relationship Code
O ID 2-2
N106 Entity Identifier Code
O ID 2-3
N3 Party Location
Optional Max: 2
N301 Address Information
M AN 1-55
N302 Address Information
O 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
N404 Country Code
C ID 2-3
N405 Location Qualifier
C ID 1-2
N406 Location Identifier
O AN 1-30
N407 Country Subdivision Code
C ID 1-3
PER Administrative Communications Contact
PER01 Contact Function Code
M ID 2-2
PER02 Name
O AN 1-60
PER03 Communication Number Qualifier
C ID 2-2
PER04 Communication Number
C AN 1-256
PER05 Communication Number Qualifier
C ID 2-2
PER06 Communication Number
C AN 1-256
PER07 Communication Number Qualifier
C ID 2-2
PER08 Communication Number
C AN 1-256
PER09 Contact Inquiry Reference
O AN 1-20
REF Reference Information
Optional Max: 12
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-50
REF03 Description
C AN 1-80
DTM Date/Time Reference
Optional Max: 10
DTM01 Date/Time Qualifier
M ID 3-3
DTM02 Date
C DT 8-8
DTM03 Time
C TM 4-8
DTM04 Time Code
O ID 2-2
DTM05 Date Time Period Format Qualifier
C ID 2-3
DTM06 Date Time Period
C AN 1-35
ASI Action or Status Indicator
Optional Max: 1
ASI01 Action Code
M ID 1-2
ASI02 Maintenance Type Code
M ID 3-3
ASI03 Status Reason Code
O 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 Walmart 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 Walmart 816 Organizational Relationships into your system — keeping division-to-location mappings current as Walmart updates its internal structure.

Walmart EDI 816 FAQ

Common questions about 816 Organizational Relationships transactions with Walmart.

How long does it take to set up Walmart EDI with Stacksync?

Most suppliers are fully connected and processing live Walmart EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with Walmart?

No. Stacksync handles the entire EDI transport layer. We connect directly to Walmart's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with Walmart compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for Walmart?

Stacksync supports all EDI document types required by Walmart — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect Walmart EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Walmart's EDI network and your system in real time.

What happens when Walmart updates their EDI specifications?

Stacksync monitors Walmart's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.