Skip to content
EDI Walmart Walmart (Goods Not For Resale) 864
X12 EDI

Walmart X12 864 Text Message

X12 864 (Text Message) is the EDI transaction exchanged between Walmart (Walmart (Goods Not For Resale)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.

Segments
9
Loops
2
X12 864
All partners ↗
Book a demo ← All Walmart (Goods Not For Resale) transactions

Transaction context

Where 864 Text Message fits on Walmart (Goods Not For Resale)

Walmart channels
2 of 8

2 of Walmart's 8 channels carry 864

Trading partners
15

partners across the Stacksync network trade 864

Channels
25

channels network-wide carry 864

Most common alongside 864

The 864 transmits free-form, human-readable text such as one-time notices, error explanations, and policy or system announcements through the same audited EDI channel as structured documents. A common production use in retail supply chains is a buyer telling a supplier that a previously submitted document, often an invoice or ASN, failed validation and must be corrected. Because the content has no machine-processable schema, it is written for people rather than for automated posting. Either party can originate one, but in practice it is usually sent by the retailer, buyer, or 3PL to the supplier's EDI or accounting team.

When it fires: A buyer's system rejects a supplier document, for example an invoice that fails validation rules, and issues an 864 explaining the errors and requesting a corrected retransmission.

Common 864 rejection causes
  • Messages go unread because they require human review; rejection notices sit in the mailbox while the flawed invoice or ASN is never corrected.
  • Used to carry structured business data that belongs in a dedicated transaction set such as the 824 Application Advice, so the receiver cannot process it automatically.
  • MSG and MTX text segments mixed inconsistently within a message loop, which X12 usage notes warn will confuse receivers.
  • No reference identification linking the text to the failed document, forcing the supplier to guess which transaction the notice concerns.

Specification summary

X12 864 Text Message at the element level

The X12 864 specification defines 16 segments carrying 52 data elements, 35 of which are mandatory.

Segments
16
Data elements
52
Mandatory elements
35
Segments with mandatory elements
Segment Elements Mandatory
BMG 3 1
N1 4 1
MIT 1 1
N3 2 1
REF 2 1
PER 4 1
MSG 1 1
Key identifiers in 864
  • Transaction Set Purpose Code
  • Entity Identifier Code
  • Reference Identification
  • Address Information
  • Reference Identification Qualifier
  • Contact Function Code
  • Free-Form Message Text
Full segment guideline — 9 segments 2 loops · X12 864 Text Message
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 3 elements

To indicate the start of a transaction set and to assign a control number

BMG Beginning Segment For Text Message 3 elements

To indicate the beginning of a Text Message Transaction Set

N1 Loop Repeat: 200
N1 Party Identification 6 elements

To identify a party by type of organization, name, and code

REF Reference Information 9 elements

To specify identifying information

MIT Loop
MIT Message Identification 4 elements

To identify the beginning of a specific message and to allow the identification of a subject for the message

MSG Message Text 3 elements

To provide a free-form format that allows the transmission of text information

SE Transaction Set Trailer 2 elements

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Trading partners

1+ 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.

Browse the full directory

Trading partners

3+ 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.

Browse the full directory

Walmart Walmart (Goods Not For Resale) EDI 864 FAQ

Common questions about 864 Text Message on the Walmart (Goods Not For Resale) channel.

What is X12 864 Text Message?
X12 864 (Text Message) is the EDI transaction set used to exchange text message data. Walmart's Walmart (Goods Not For Resale) channel requires it from trading partners.
Does Walmart Walmart (Goods Not For Resale) require 864 for trading partners?
Yes, Walmart (Walmart (Goods Not For Resale)) supports X12 864 Text Message. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Walmart 864 with Stacksync?
Most companies go live with Walmart 864 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which other Walmart channels accept 864?
X12 864 runs on 2 of Walmart's 8 channels. Besides Walmart (Goods Not For Resale), it is accepted on Walmart US (Goods for Resale). Each channel carries its own implementation guideline; Stacksync validates outbound documents against the correct guideline automatically.

Ready to automate your Walmart EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.

Book a Walmart EDI demo Tour the platform on your own