X12
Outbound

Elliotts Boots X12 855 Purchase Order Acknowledgment

Elliotts Boots
The EDI 855 confirms receipt and acceptance of a Elliotts Boots Purchase Order. Suppliers must respond promptly indicating whether the order is accepted, rejected, or accepted with changes to maintain compliance standing.
8segments
2loops
5mandatory

Schema Reference

8 segments · X12 855 Purchase Order Acknowledgment

ISA ISA Interchange Control Header
Mandatory Max: 1
ISA01 Authorization Information Qualifier
M ID 2-2
ISA02 Authorization Information
M AN 10-10
ISA03 Security Information Qualifier
M ID 2-2
ISA04 Security Information
M AN 10-10
ISA05 Interchange ID Qualifier
M ID 2-2
ISA06 Interchange Sender ID
M AN 15-15
ISA07 Interchange ID Qualifier
M ID 2-2
ISA08 Interchange Receiver ID
M AN 15-15
ISA09 Interchange Date
M DT 6-6
ISA10 Interchange Time
M TM 4-4
ISA11 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator ISA12 Interchange Control Version Number
M ID 5-5
ISA13 Interchange Control Number
M N0 9-9
ISA14 Acknowledgment Requested
M ID 1-1
ISA15 Usage Indicator
M ID 1-1
GS GS Functional Group Header
Mandatory Max: 1
GS01 Functional Identifier Code
M ID 2-2
GS02 Application Sender's Code
M AN 2-15
GS03 Application Receiver's Code
M AN 2-15
GS04 Date
M DT 8-8
GS05 Time
M TM 4-8
GS06 Group Control Number
M N0 1-9
GS07 Responsible Agency Code
M ID 1-2
GS08 Version / Release / Industry Identifier Code
M AN 1-12
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
BAK Beginning Segment for Purchase Order Acknowledgment
Mandatory Max: 1
BAK01 Transaction Set Purpose Code
M ID 2-2
BAK02 Acknowledgment Type
M ID 2-2
BAK03 Purchase Order Number
M AN 1-22
BAK04 Date
M DT 8-8
BAK05 Release Number
O AN 1-30
BAK06 Request Reference Number
O AN 1-45
BAK07 Contract Number
O AN 1-30
BAK08 Reference Identification
O AN 1-50
BAK09 Date
O DT 8-8
BAK10 Transaction Type Code
O ID 2-2
REF Reference Identification
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-50
REF03 Description
C AN 1-80
PO1 Loop Repeat: 100,000
PO1 Baseline Item Data
Optional Max: 1
PO101 Assigned Identification
O AN 1-20
PO102 Quantity Ordered
C R 1-15
PO103 Unit or Basis for Measurement Code
O ID 2-2
PO104 Unit Price
C R 1-17
PO105 Basis of Unit Price Code
O ID 2-2
PO106 Product/Service ID Qualifier
C ID 2-2
PO107 Product/Service ID
C AN 1-48
PO108 Product/Service ID Qualifier
C ID 2-2
PO109 Product/Service ID
C AN 1-48
PO110 Product/Service ID Qualifier
C ID 2-2
PO111 Product/Service ID
C AN 1-48
PO112 Product/Service ID Qualifier
C ID 2-2
PO113 Product/Service ID
C AN 1-48
PO114 Product/Service ID Qualifier
C ID 2-2
PO115 Product/Service ID
C AN 1-48
PO116 Product/Service ID Qualifier
C ID 2-2
PO117 Product/Service ID
C AN 1-48
PO118 Product/Service ID Qualifier
C ID 2-2
PO119 Product/Service ID
C AN 1-48
PO120 Product/Service ID Qualifier
C ID 2-2
PO121 Product/Service ID
C AN 1-48
PO122 Product/Service ID Qualifier
C ID 2-2
PO123 Product/Service ID
C AN 1-48
PO124 Product/Service ID Qualifier
C ID 2-2
PO125 Product/Service ID
C AN 1-48
ACK Loop Repeat: 104
ACK Line Item Acknowledgment
Optional Max: 1
ACK01 Line Item Status Code
M ID 2-2
ACK02 Quantity
C R 1-15
ACK03 Unit or Basis for Measurement Code
C ID 2-2
ACK04 Date/Time Qualifier
O ID 3-3
ACK05 Date
C DT 8-8
ACK06 Request Reference Number
O AN 1-45
ACK07 Product/Service ID Qualifier
C ID 2-2
ACK08 Product/Service ID
C AN 1-48
ACK09 Product/Service ID Qualifier
C ID 2-2
ACK10 Product/Service ID
C AN 1-48
ACK11 Product/Service ID Qualifier
C ID 2-2
ACK12 Product/Service ID
C AN 1-48
ACK13 Product/Service ID Qualifier
C ID 2-2
ACK14 Product/Service ID
C AN 1-48
ACK15 Product/Service ID Qualifier
C ID 2-2
ACK16 Product/Service ID
C AN 1-48
ACK17 Product/Service ID Qualifier
C ID 2-2
ACK18 Product/Service ID
C AN 1-48
ACK19 Product/Service ID Qualifier
C ID 2-2
ACK20 Product/Service ID
C AN 1-48
ACK21 Product/Service ID Qualifier
C ID 2-2
ACK22 Product/Service ID
C AN 1-48
ACK23 Product/Service ID Qualifier
C ID 2-2
ACK24 Product/Service ID
C AN 1-48
ACK25 Product/Service ID Qualifier
C ID 2-2
ACK26 Product/Service ID
C AN 1-48
ACK27 Agency Qualifier Code
C ID 2-2
ACK28 Source Subqualifier
C AN 1-15
ACK29 Industry Code
C AN 1-30
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating Elliotts Boots EDI 855

Stacksync validates, transforms, and delivers your 855 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate
Transform
Route
Monitor
Stacksync generates and sends 855 Purchase Order Acknowledgments automatically when your system confirms an order. Accept, reject, or modify line items through your ERP — Stacksync handles the EDI formatting and transmission.

Elliotts Boots EDI 855 FAQ

Common questions about 855 Purchase Order Acknowledgment transactions with Elliotts Boots.

How long does it take to set up Elliotts Boots EDI with Stacksync?

Most suppliers are fully connected and processing live Elliotts Boots EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with Elliotts Boots?

No. Stacksync handles the entire EDI transport layer. We connect directly to Elliotts Boots's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with Elliotts Boots compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for Elliotts Boots?

Stacksync supports all EDI document types required by Elliotts Boots — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect Elliotts Boots EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Elliotts Boots's EDI network and your system in real time.

What happens when Elliotts Boots updates their EDI specifications?

Stacksync monitors Elliotts Boots's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.