855 Purchase Order Acknowledgment
Lowe's · X12 004010
Lowe'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
10 of 10 segments
HEADING
ST
Transaction Set Header ST
pos 010
Optional
max —
BAK
Beginning Segment For Purchase Order Acknowledgment BAK
Example:
BAK*00*AP*123456789*19981001\
BAK*05*AP*123456789*19981001\
BAK*01*AP*123456789*19981001\
pos 020
Required
max —
REF
Reference Identification REF
Example:
REF*WO*22222\
REF*AN*123456789\
pos 050
Required
max —
PER
Administrative Communications Contact PER
This segment should be used to communicate the name of the individual at our retail locations who placed the order. In case of a change, it should contain the name at the vendor location who is requesting the change.
Example:
PER*OC*JOHN DOE\
pos 060
Required
max 3
DTM
Date Time Reference DTM
Example:
DTM*067*19980826\
DTM*068*19980825\
pos 150
Required
max 10
N1 LoopParty for whom Item is Ultimately Intendedvariant 1 of 2
N1
Name N1
Example:
N1*ST**94*960\
N1*MA**94*465\
pos 300
Required
max —
N1 LoopShip Tovariant 2 of 2required
N1
Name N1
Example:
N1*ST**94*960\
N1*MA**94*465\
pos 300
Required
max —
DETAIL
PO1 Looprequired
PO1
Baseline Item Data PO1
Example:
PO1**25*EA*2.5**CB*12345\
pos 010
Required
max —
SUMMARY
CTT Looprequired
CTT
Transaction Totals CTT
Example:
CTT*1\
pos 010
Required
max —
SE
Transaction Set Trailer SE
pos 030
Optional
max —
Validate a 855
Paste or upload a document and check it against Lowe's’ published rules — segment order and repetition, required elements, field lengths, data types and accepted codes. Nothing is stored.
Go live on Lowe's’ 855 in days, not months
Weredi maps this guide to your ERP, runs the test cycle with Lowe's, and keeps the spec current as it changes.