855 Purchase Order Acknowledgment
Gander Mountain · X12 004010
Gander Mountain’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
12 of 12 segments
HEADING
ST
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
pos 010
Required
max —
BAK
Beginning Segment for Purchase Order Acknowledgment
To indicate the beginning of the Purchase Order Acknowledgment
pos 020
Required
max —
REF
Reference Identification
To specify identifying information
pos 050
Required
max —
FOB
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
pos 080
Optional
max —
ITD
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
pos 130
Optional
max —
DTM
Date/Time Reference
To specify pertinent dates and times
pos 150
Optional
max 2
N9 Looprepeats 1
N9
Reference Identification
pos 280
Optional
max —
DETAIL
PO1 Looprepeats 650required
PO1
Baseline Item Data
pos 010
Optional
max —
PID Looprepeats 3
PID
Product/Item Description
To describe a product or process in coded or free- form format
pos 050
Optional
max —
ACK Looprepeats 104required
ACK
Line Item Acknowledgment
To acknowledge the ordered quantities and specify the ready date for a
pos 270
Required
max —
SUMMARY
CTT Looprepeats 1required
CTT
Transaction Totals
To transmit a hash total for a specific element in the transaction set
pos 010
Required
max —
SE
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the
pos 030
Required
max —
Validate a 855
Paste or upload a document and check it against Gander Mountain’s published rules — segment order and repetition, required elements, field lengths, data types and accepted codes. Nothing is stored.
Go live on Gander Mountain’s 855 in days, not months
Weredi maps this guide to your ERP, runs the test cycle with Gander Mountain, and keeps the spec current as it changes.