To start and identify an interchange of zero or more functional groups and interchange-related control segments
Lumens, Inc. X12 855 Purchase Order Acknowledgment
X12 855 (Purchase Order Acknowledgment) is the EDI transaction exchanged between Lumens, Inc. (Lumens (via SPS Commerce)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 20
- Loops
- 7
- X12 855
- All partners ↗
Transaction context
Where 855 Purchase Order Acknowledgment fits on Lumens (via SPS Commerce)
On Lumens (via SPS Commerce), the X12 855 Purchase Order Acknowledgment follows the 850 Purchase Order and precedes the 856 Ship Notice Manifest and 810 Invoice in the Order-to-cash cycle.
- Lumens, Inc. channels
- 1 of 1
- Trading partners
- 269
- Channels
- 328
1 of Lumens, Inc.'s 1 channel carries 855
partners across the Stacksync network trade 855
channels network-wide carry 855
Most common alongside 855
On SPS Commerce, 855 runs on 87 channels.
The 855 is the seller's formal response to an 850 purchase order: accept as submitted, accept with changes to price, quantity, dates, or items, or reject. Buyers require it to confirm the order is committed before shipment and to surface availability, pricing, and item discrepancies while there is still time to correct them. Many retail compliance programs mandate it within a defined window, commonly 24 to 48 hours of PO receipt, and failure to send required response documents on time can result in financial penalties under vendor compliance programs. Sent by the supplier or vendor to the buyer that issued the purchase order.
When it fires: A supplier's order management system finishes validating an inbound purchase order against its item master, pricing, and available inventory.
Common 855 rejection causes
- Acknowledgments sent after the buyer's required response window, commonly 24 to 48 hours, exposing the supplier to compliance penalties.
- PO number or line references that do not match the original 850, so the buyer's system cannot tie the acknowledgment back to the order.
- Inaccurate product identifiers or prices echoed back on the acknowledgment, creating discrepancies that persist into the ship notice and invoice.
- Missing or inconsistent acknowledgment status codes, leaving the buyer unsure whether changed quantities, dates, or backorders were actually committed.
Specification summary
X12 855 Purchase Order Acknowledgment at the element level
The X12 855 specification defines 54 segments carrying 204 data elements, 72 of which are mandatory.
- Segments
- 54
- Data elements
- 204
- Mandatory elements
- 72
| Segment | Elements | Mandatory |
|---|---|---|
| BAK | 6 | 4 |
| CUR | 2 | 2 |
| REF | 3 | 1 |
| FOB | 3 | 1 |
| SAC | 10 | 1 |
| DTM | 4 | 1 |
| TXI | 7 | 1 |
| N9 | 3 | 1 |
| MSG | 2 | 1 |
| N1 | 4 | 1 |
| N2 | 2 | 1 |
Key identifiers in 855
- Transaction Set Purpose Code
- Acknowledgment Type
- Purchase Order Number
- Date
- Entity Identifier Code
- Currency Code
- Reference Identification Qualifier
- Shipment Method of Payment
Full segment guideline — 20 segments 7 loops · X12 855 Purchase Order Acknowledgment
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates
To specify identifying information
To specify terms of sale
To specify pertinent dates and times
To specify the carrier and sequence of routing and provide transit time information
N1 Loop Repeat: 200
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
To specify textual data
PO1 Loop Repeat: 100,000
To specify basic and most frequently used line item data
To specify pricing information
PID Loop Repeat: 1,000
To describe a product or process in coded or free-form format
SAC Loop Repeat: 25
CTT Loop Repeat: 1
To transmit a hash total for a specific element in the transaction set
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
ACK Loop Repeat: 104
To acknowledge the ordered quantities and specify the ready date for a specific line item
N9 Loop Repeat: 1,000
To transmit identifying information as specified by the Reference Identification Qualifier
Trading partners
4+ 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.
No trading partner matches your search.
Browse the full directory
Lumens, Inc. Lumens (via SPS Commerce) EDI 855 FAQ
Common questions about 855 Purchase Order Acknowledgment on the Lumens (via SPS Commerce) channel.
What is X12 855 Purchase Order Acknowledgment?
X12 855 (Purchase Order Acknowledgment) is the EDI transaction set used to exchange purchase order acknowledgment data. Lumens, Inc.'s Lumens (via SPS Commerce) channel requires it from trading partners.
Does Lumens, Inc. Lumens (via SPS Commerce) require 855 for trading partners?
Yes, Lumens, Inc. (Lumens (via SPS Commerce)) supports X12 855 Purchase Order Acknowledgment. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Lumens, Inc. 855 with Stacksync?
Most companies go live with Lumens, Inc. 855 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 855 on Lumens (via SPS Commerce)?
On Lumens (via SPS Commerce), X12 855 is typically exchanged alongside 850 Purchase Order, 810 Invoice, 856 Ship Notice Manifest, 846 Inventory Inquiry Advice. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Lumens, Inc. EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
