X12
Outbound

Ingram Micro X12 856 Ship Notice/Manifest

Ingram Micro (US)
The EDI 856 Advance Ship Notice notifies Ingram Micro 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.
22segments
2loops
6mandatory

Schema Reference

22 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
BSN06 Transaction Type Code
C ID 2-2
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
SN101 Assigned Identification
O AN 1-20
SN102 Number of Units Shipped
M R 1-10
SN103 Unit or Basis for Measurement Code
M ID 2-2
SN104 Quantity Shipped to Date
O R 1-15
SN105 Quantity Ordered
C R 1-15
SN106 Unit or Basis for Measurement Code
C ID 2-2
SN107 Returnable Container Load Make-Up Code
O ID 1-2
SN108 Line Item Status Code
O ID 2-2
PRF Purchase Order Reference
Optional Max: 1
PRF01 Purchase Order Number
M AN 1-22
PRF02 Release Number
O AN 1-30
PRF03 Change Order Sequence Number
O AN 1-8
PRF04 Date
O DT 8-8
PRF05 Assigned Identification
O AN 1-20
PRF06 Contract Number
O AN 1-30
PO4 Item Physical Details
Optional Max: 1
PO401 Pack
O N0 1-6
PO402 Size
C R 1-8
PO403 Unit or Basis for Measurement Code
C ID 2-2
PO404 Packaging Code
C AN 3-5
PO405 Weight Qualifier
O ID 1-2
PO406 Gross Weight per Pack
C R 1-9
PO407 Unit or Basis for Measurement Code
C ID 2-2
PO408 Gross Volume per Pack
C R 1-9
PO409 Unit or Basis for Measurement Code
C ID 2-2
PO410 Length
C R 1-8
PO411 Width
C R 1-8
PO412 Height
C R 1-8
PO413 Unit or Basis for Measurement Code
C ID 2-2
PID Product/Item Description
Optional Max: 200
PID01 Item Description Type
M ID 1-1
PID05 Description
C AN 1-80
PID09 Language Code
O ID 2-3
TD1 Carrier Details (Quantity and Weight)
Optional Max: 20
TD101 Packaging Code
O AN 3-5
TD102 Lading Quantity
C N0 1-7
TD103 Commodity Code Qualifier
O ID 1-1
TD104 Commodity Code
C AN 1-30
TD105 Lading Description
O AN 1-50
TD106 Weight Qualifier
O ID 1-2
TD107 Weight
C R 1-10
TD108 Unit or Basis for Measurement Code
C ID 2-2
TD5 Carrier Details (Routing Sequence/Transit Time)
Optional Max: 12
TD501 Routing Sequence Code
O ID 1-2
TD502 Identification Code Qualifier
C ID 1-2
TD503 Identification Code
C AN 2-80
TD504 Transportation Method/Type Code
C ID 1-2
TD505 Routing
C AN 1-35
TD506 Shipment/Order Status Code
C ID 2-2
TD507 Location Qualifier
O ID 1-2
TD508 Location Identifier
C AN 1-30
TD509 Transit Direction Code
O ID 2-2
TD510 Transit Time Direction Qualifier
O ID 2-2
TD511 Transit Time
C R 1-4
TD3 Carrier Details (Equipment)
Optional Max: 12
TD301 Equipment Description Code
C ID 2-2
TD302 Equipment Initial
O AN 1-4
TD303 Equipment Number
C AN 1-10
TD310 Equipment Type
C ID 4-4
REF Reference Identification
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-30
MAN Marks and Numbers
MAN01 Marks and Numbers Qualifier
M ID 1-2
MAN02 Marks and Numbers
M 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
DTM03 Time
C TM 4-8
DTM04 Time Code
O ID 2-2
FOB F.O.B. Related Instructions
Optional Max: 1
FOB01 Shipment Method of Payment
M ID 2-2
N1 Loop Repeat: 200
N1 Name
Optional Max: 1
N101 Entity Identifier Code
M ID 2-3
N103 Identification Code Qualifier
C ID 1-2
N104 Identification Code
C AN 2-80
N3 Address Information
Optional Max: 2
N301 Address Information
M AN 1-55
N302 Address Information
O AN 1-55
N4 Geographic Location
Optional Max: 1
N401 City Name
O AN 2-30
N402 State or Province Code
O ID 2-2
N403 Postal Code
O ID 3-15
N404 Country Code
O ID 2-3
CTT Transaction Totals
Optional Max: 1
CTT01 Number of Line Items
M N0 1-6
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 Ingram Micro 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.

Ingram Micro EDI 856 FAQ

Common questions about 856 Ship Notice/Manifest transactions with Ingram Micro.

How long does it take to set up Ingram Micro EDI with Stacksync?

Most suppliers are fully connected and processing live Ingram Micro 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 Ingram Micro?

No. Stacksync handles the entire EDI transport layer. We connect directly to Ingram Micro'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 Ingram Micro 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 Ingram Micro?

Stacksync supports all EDI document types required by Ingram Micro — 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 Ingram Micro 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 Ingram Micro's EDI network and your system in real time.

What happens when Ingram Micro updates their EDI specifications?

Stacksync monitors Ingram Micro'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.