X12
Outbound

AAFES (Army and Air Force Exchange Service) X12 856 Ship Notice/Manifest

AAFES
The EDI 856 Advance Ship Notice notifies AAFES (Army and Air Force Exchange Service) that a shipment is in transit. It includes carton-level detail, pallet configurations, SSCC-18 barcodes, and carrier tracking information. Accurate ASNs are critical for receiving efficiency and compliance.
12segments
1loops
6mandatory

Schema Reference

12 segments · X12 856 Ship Notice/Manifest

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 Interchange Control Standards Identifier
M ID 1-1
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
BSN Beginning Segment for Ship Notice
Mandatory Max: 1
BSN01 Transaction Set Purpose Code
M ID 2-2
BSN02 Shipment Identification
M AN 2-30
BSN03 Date
M DT 8-8
BSN04 Time
M TM 4-8
BSN05 Hierarchical Structure Code
O ID 4-4
HL Loop Repeat: 200,000
HL Hierarchical Level
Mandatory Max: 1
HL01 Hierarchical ID Number
M AN 1-12
HL02 Hierarchical Parent ID Number
O AN 1-12
HL03 Hierarchical Level Code
M ID 1-2
LIN Item Identification
Optional Max: 1
LIN01 Assigned Identification
O AN 1-20
LIN02 Product/Service ID Qualifier
M ID 2-2
LIN03 Product/Service ID
M AN 1-48
LIN04 Product/Service ID Qualifier
C ID 2-2
LIN05 Product/Service ID
C AN 1-48
LIN06 Product/Service ID Qualifier
C ID 2-2
LIN07 Product/Service ID
C AN 1-48
SN1 Item Detail (Shipment)
Optional Max: 1
SN102 Number of Units Shipped
M R 1-10
SN103 Unit or Basis for Measurement Code
M ID 2-2
PRF Purchase Order Reference
Optional Max: 1
PRF01 Purchase Order Number
M AN 1-22
TD5 Carrier Details (Routing Sequence/Transit Time)
Optional Max: 12
TD503 Identification Code
C AN 2-80
TD505 Routing
C AN 1-35
MAN Marks and Numbers
MAN01 Marks and Numbers Qualifier
M ID 1-2
MAN02 Marks and Numbers
M AN 1-48
MAN03 Marks and Numbers
O AN 1-48
MAN04 Marks and Numbers Qualifier
C ID 1-2
MAN05 Marks and Numbers
C AN 1-48
DTM Date/Time Reference
Optional Max: 10
DTM01 Date/Time Qualifier
M ID 3-3
DTM02 Date
C DT 8-8
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 AAFES (Army and Air Force Exchange Service) EDI 856

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

Validate
Transform
Route
Monitor
Stacksync builds and transmits 856 ASNs automatically when shipments are created in your WMS. Carton contents, pallet labels, SSCC-18 codes, and tracking numbers are pulled from your warehouse data — eliminating manual EDI entry.

Business unit variations

AAFES Direct to Consumer through VendorNet(Radial)
Stacksync builds and transmits 856 ASNs automatically when shipments are created in your WMS. Carton contents, pallet labels, SSCC-18 codes, and tracking numbers are pulled from your warehouse data — eliminating manual EDI entry.
AAFES (via DSCO (dba Rithum))
Stacksync builds and transmits 856 ASNs automatically when shipments are created in your WMS. Carton contents, pallet labels, SSCC-18 codes, and tracking numbers are pulled from your warehouse data — eliminating manual EDI entry.

AAFES (Army and Air Force Exchange Service) EDI 856 FAQ

Common questions about 856 Ship Notice/Manifest transactions with AAFES (Army and Air Force Exchange Service).

How far in advance must a AAFES (Army and Air Force Exchange Service) EDI 856 ASN be sent before delivery?

AAFES (Army and Air Force Exchange Service) typically requires the EDI 856 Advance Ship Notice to be transmitted within hours of shipment — not days before delivery. The ASN must be sent after the carrier picks up the freight but before the shipment arrives at AAFES (Army and Air Force Exchange Service)'s receiving dock. Late or missing ASNs often result in compliance chargebacks and can cause receiving delays at the distribution center. Stacksync triggers 856 generation automatically when your WMS or shipping system confirms dispatch, ensuring the ASN reaches AAFES (Army and Air Force Exchange Service) within the required window without manual intervention from your logistics team.

How far in advance must a AAFES (Army and Air Force Exchange Service) EDI 856 ASN be sent before delivery?

AAFES (Army and Air Force Exchange Service) typically requires the EDI 856 Advance Ship Notice to be transmitted within hours of shipment — not days before delivery. The ASN must be sent after the carrier picks up the freight but before the shipment arrives at AAFES (Army and Air Force Exchange Service)'s receiving dock. Late or missing ASNs often result in compliance chargebacks and can cause receiving delays at the distribution center. Stacksync triggers 856 generation automatically when your WMS or shipping system confirms dispatch, ensuring the ASN reaches AAFES (Army and Air Force Exchange Service) within the required window without manual intervention from your logistics team.

What is the packaging hierarchy in a AAFES (Army and Air Force Exchange Service) EDI 856?

The AAFES (Army and Air Force Exchange Service) EDI 856 uses hierarchical levels (HL segments) to describe the shipment structure from top to bottom: shipment level, order level, pack level (cartons or pallets), and item level. Each level contains specific data — the shipment level holds carrier and BOL information, the pack level includes SSCC-18 barcodes and carton dimensions, and the item level lists UPCs and quantities per package. Stacksync builds this hierarchy automatically from your WMS packing data, mapping carton contents and pallet configurations into the correct HL structure required by AAFES (Army and Air Force Exchange Service).

What is the packaging hierarchy in a AAFES (Army and Air Force Exchange Service) EDI 856?

The AAFES (Army and Air Force Exchange Service) EDI 856 uses hierarchical levels (HL segments) to describe the shipment structure from top to bottom: shipment level, order level, pack level (cartons or pallets), and item level. Each level contains specific data — the shipment level holds carrier and BOL information, the pack level includes SSCC-18 barcodes and carton dimensions, and the item level lists UPCs and quantities per package. Stacksync builds this hierarchy automatically from your WMS packing data, mapping carton contents and pallet configurations into the correct HL structure required by AAFES (Army and Air Force Exchange Service).

What penalties does AAFES (Army and Air Force Exchange Service) charge for EDI 856 ASN errors?

Penalties for AAFES (Army and Air Force Exchange Service) ASN errors vary by the type of mistake and your compliance scorecard tier. Common chargeable errors include missing or late ASNs, incorrect carton counts, wrong item quantities, invalid SSCC-18 labels, and mismatches between the ASN and actual received goods. These penalties can range from flat fees per incident to percentage-based fines on the shipment value. Stacksync validates every 856 against the original PO data and your shipping records before transmission, catching errors that would otherwise result in AAFES (Army and Air Force Exchange Service) chargebacks. The platform maintains an audit trail for dispute resolution.

What penalties does AAFES (Army and Air Force Exchange Service) charge for EDI 856 ASN errors?

Penalties for AAFES (Army and Air Force Exchange Service) ASN errors vary by the type of mistake and your compliance scorecard tier. Common chargeable errors include missing or late ASNs, incorrect carton counts, wrong item quantities, invalid SSCC-18 labels, and mismatches between the ASN and actual received goods. These penalties can range from flat fees per incident to percentage-based fines on the shipment value. Stacksync validates every 856 against the original PO data and your shipping records before transmission, catching errors that would otherwise result in AAFES (Army and Air Force Exchange Service) chargebacks. The platform maintains an audit trail for dispute resolution.

Are SSCC-18 labels required for AAFES (Army and Air Force Exchange Service) EDI 856 shipments?

Most AAFES (Army and Air Force Exchange Service) programs require SSCC-18 (Serial Shipping Container Code) labels on every carton and pallet, with the corresponding barcodes referenced in the 856 ASN's MAN (Marks and Numbers) segment. The SSCC-18 is a unique 18-digit identifier that links the physical package to the electronic ASN data, enabling AAFES (Army and Air Force Exchange Service)'s receiving dock to scan and verify shipments against the advance notice. Stacksync generates SSCC-18 numbers that comply with GS1 standards and embeds them in the 856 automatically. If your WMS already assigns SSCC-18s, Stacksync pulls those values directly from your packing records.

Are SSCC-18 labels required for AAFES (Army and Air Force Exchange Service) EDI 856 shipments?

Most AAFES (Army and Air Force Exchange Service) programs require SSCC-18 (Serial Shipping Container Code) labels on every carton and pallet, with the corresponding barcodes referenced in the 856 ASN's MAN (Marks and Numbers) segment. The SSCC-18 is a unique 18-digit identifier that links the physical package to the electronic ASN data, enabling AAFES (Army and Air Force Exchange Service)'s receiving dock to scan and verify shipments against the advance notice. Stacksync generates SSCC-18 numbers that comply with GS1 standards and embeds them in the 856 automatically. If your WMS already assigns SSCC-18s, Stacksync pulls those values directly from your packing records.

How does Stacksync generate AAFES (Army and Air Force Exchange Service) EDI 856 ASNs from my warehouse system?

Stacksync connects to your WMS, ERP, or shipping platform and monitors for shipment confirmations. When an order is marked as shipped, Stacksync extracts the packing details — carton contents, weights, dimensions, carrier information, tracking numbers, and SSCC-18 labels — and constructs the 856 ASN document automatically. The platform maps your warehouse data to AAFES (Army and Air Force Exchange Service)'s required HL hierarchy, populates the BSN, TD1, and REF segments, and validates the complete document before transmitting it. The entire process runs without manual EDI formatting, reducing ASN errors and keeping your AAFES (Army and Air Force Exchange Service) compliance scores high.

How does Stacksync generate AAFES (Army and Air Force Exchange Service) EDI 856 ASNs from my warehouse system?

Stacksync connects to your WMS, ERP, or shipping platform and monitors for shipment confirmations. When an order is marked as shipped, Stacksync extracts the packing details — carton contents, weights, dimensions, carrier information, tracking numbers, and SSCC-18 labels — and constructs the 856 ASN document automatically. The platform maps your warehouse data to AAFES (Army and Air Force Exchange Service)'s required HL hierarchy, populates the BSN, TD1, and REF segments, and validates the complete document before transmitting it. The entire process runs without manual EDI formatting, reducing ASN errors and keeping your AAFES (Army and Air Force Exchange Service) compliance scores high.

Ready to automate AAFES (Army and Air Force Exchange Service) EDI?

a blue checkmark icon
POC from integration engineers
a blue checkmark icon
No-code EDI setup
a blue checkmark icon
Real-time compliance monitoring
a blue checkmark icon
White-glove onboarding