In a standard built entirely on structure — coded segments, qualified elements, validated everything — there's one transaction whose payload is just... words. The EDI 864 Text Message carries free-form, human-readable text between trading partners, and its persistence says something true about supply chains: not every message fits a code list, but partners still want the unstructured ones flowing through the same audited channel as the orders and invoices.
Structure around the unstructured
The document itself is minimal. BMG opens it and states its purpose; MIT identifies each message with a reference and subject; MSG segments carry the actual text, line by line. References can tie a message to a specific document or PO when the text is about something — which is common, because a large share of 864 traffic is partners explaining, in prose, a situation their structured documents can't express.
What arrives this way in practice: cutover and maintenance notices from a partner's EDI operations team, explanations accompanying a rejection or a data problem, program announcements ("effective next quarter, all vendors must..."), dock closures and revised holiday schedules, and occasional per-order notes on unusual situations. Some partners also use the 864 as the wrapper for error notifications where they don't implement the structured 824 Application Advice.
The failure mode is silence
Nothing about an 864 demands processing — no order to fill, no invoice to match — so untended, it lands in an archive folder and is never seen by a human. That's the entire risk profile of this document: it is only ever as valuable as your process for reading it. And the misses are asymmetric. A holiday-schedule notice you skip costs nothing until your freight arrives at a closed DC; a program-change announcement you skip costs nothing until documents start failing next quarter; an explanation of why your 850s are erroring costs nothing until you've spent a week diagnosing what the partner already told you. The exposure compounds with partner count, since each new relationship adds another voice that may only ever speak through this channel.
The 997 acknowledges receipt automatically, which creates a small trap: the partner's system shows you received the message. "We notified you via EDI" is a sentence you don't want to hear first in a dispute about a change you never read.
Handling: route text like it matters
The fix is unglamorous: treat 864s as a notification feed, not document traffic. Parse them on arrival, extract subject and references, and surface them where people actually look — a monitored queue, a Slack or email relay, a dashboard. Link referenced documents so a message about PO 12345 appears attached to PO 12345. Flag senders and keywords that historically mean action (cutover, mandatory, reject, closure) for priority. EDISQ does this out of the box: inbound 864s render as readable notices tied to their references, with nothing left to rot in a mailbox directory.
Outbound is worth remembering too — the 864 runs both directions, and sending a structured-channel note to a partner's EDI operations desk occasionally beats hunting for the right email address. A few conventions keep outbound text useful: one topic per message, references to the documents you're writing about, and no requests that properly belong in a structured transaction — a quantity change buried in prose is a change nobody's system will apply.
Cost of the words
Text messages bill like any document at EDISQ — the pricing model doesn't distinguish payloads. First 25 documents in a month free; beyond them, from $0.50 per document easing to $0.10 at the highest tier, marginally applied, with connectivity included and no mapping or setup fees. The 864 will never be a meaningful line on that bill. Its entire economics live on the other side: what one unread notice can cost, and how little it takes to make sure that never happens.
FAQ
What is the EDI 864 used for?
Free-form text between trading partners over the EDI channel: system maintenance notices, error explanations, program announcements, holiday schedule changes — anything without a dedicated structured document.
Is the 864 a replacement for email?
More like email that arrives through EDI. Partners use it because it reaches the EDI operations side directly and rides the same audited, acknowledged channel as business documents.
Do I need to respond to an 864?
A 997 acknowledges receipt automatically. Beyond that, response depends on content — some messages are informational, some describe problems that need action. The risk is never reading them at all.
What do 864s cost to receive?
One document each under EDISQ pricing — free within your 25 monthly, then from $0.50 with volume tiers. The cost is trivial; missing one that mattered is not.