855 Purchase Order Acknowledgment
Doordash · X12 005010
Doordash’s published 855 specification, rendered as an interactive guide. Expand any segment to see its elements, data types, lengths and accepted codes — then validate your own document against it below.
Specification
13 of 13 segments
HEADING
ST
Transaction Set Header ST
pos 0100
Optional
max —
BAK
Beginning Segment For Purchase Order Acknowledgment BAK
pos 0200
Required
max —
REF
Reference Information REF
pos 0500
Required
max —
DTM
Date Time Reference DTM
Only send this segment if changing for the entire order. Else, if only the scheduled ship date for certain items is changing, use the ACK segment to indicate this.
pos 1500
Optional
max 10
N9 Loop
N9
Extended Reference Information N9
pos 2800
Required
max —
MTX
Text MTX
pos 2900
Required
max —
DETAIL
PO1 Loop
PO1
Baseline Item Data PO1
pos 0100
Required
max —
PID Looprequired
PID
Product Item Description PID
pos 0500
Required
max —
ACK Looprequired
ACK
Line Item Acknowledgment ACK
pos 2700
Required
max —
N9 Loop
N9
Extended Reference Information N9
pos 3500
Required
max —
MTX
Text MTX
pos 3600
Required
max —
SUMMARY
CTT Loop
CTT
Transaction Totals CTT
pos 0100
Required
max —
SE
Transaction Set Trailer SE
pos 0300
Optional
max —
Validate a 855
Paste or upload a document and check it against Doordash’s published rules — segment order and repetition, required elements, field lengths, data types and accepted codes. Nothing is stored.
Go live on Doordash’s 855 in days, not months
Weredi maps this guide to your ERP, runs the test cycle with Doordash, and keeps the spec current as it changes.