The Amazon Vendor Central 856 Ship Notice / ASN, explained

What Amazon Vendor Central expects in the 856

Amazon Vendor Central trades on X12 4010 + EDIFACT (EU) over API + AS2. Beyond the base standard, watch these:

How EDISQ maps it

The certified Amazon Vendor Central 856 map loads when you enable the partner — fields auto-map from NetSuite, QuickBooks, Dynamics, and 33 other systems, validation runs against Amazon Vendor Central's spec before transmission, and the sandbox replays Amazon Vendor Central test scenarios until everything passes.

Common rejection reasons

Nearly all 856 rejections trace to reference data, not syntax: identifiers that don't match Amazon Vendor Central's cross-references, echoed fields dropped from the original PO, or timing that misses the program window. EDISQ flags each before Amazon Vendor Central ever sees the document.

Sample Amazon Vendor Central 856

A representative 856 interchange addressed to Amazon Vendor Central — envelope, shipment→order→pack→item hierarchy, and control totals:

1ISA*00*          *00*          *ZZ*ACMESUPPLY     *ZZ*AMAZON         *260101*1200*U*00401*000000001*0*P*>~
2GS*SH*ACMESUPPLY*AMAZON*20260101*1200*1*X*004010~
3ST*856*0001~
4BSN*00*SHIP0001*20260101*1200*0001~
5HL*1**S~
6TD1*CTN25*3****G*180*LB~
7TD5*B*2*UPSN*M~
8REF*BM*BOL000123~
9DTM*011*20260105~
10N1*ST*AMAZON VENDOR CENTRAL DC 5093*92*5093~
11HL*2*1*O~
12PRF*PO12345~
13HL*3*2*P~
14MAN*GM*00000123450000000017~
15HL*4*3*I~
16LIN**UP*012345678905~
17SN1**24*EA~
18CTT*4~
19SE*17*0001~
20GE*1*1~
21IEA*1*000000001~

FAQ