Written and maintained by CASRAI Editorial Board
Last updated
Short answer: An EDI 856 is the electronic advance ship notice (ASN): the message a shipper sends before a delivery arrives so the receiver knows what is coming. In the ASC X12 standard the 856 is titled Ship Notice/Manifest. An 850 is the order that starts the exchange; the 856 describes the shipment that results. For receiving staff the useful link is the SSCC, the 18-digit number on the pallet or carton label, which points to the matching ASN.
Definition and scope
ASC X12 is the family of electronic data interchange (EDI) standards used in US business-to-business messaging. Transaction set 856 is named Ship Notice/Manifest. The US federal implementation guideline for version 003050, published by NIST in 1998 (NIST SP 881-66), describes it as the federal government’s interpretation of the use of the X12 003050 standards, written to help developers build the interface between a business application and an X12 translator. That guideline is old and covers one version only; trading partners today publish their own implementation guides for the 856, so treat it as a definition of the set rather than a current specification.
For the wider picture of how EDI replaces paper and PDF documents between a facility and a distributor, see the CASRAI term electronic data interchange (EDI).
How the ASN works at the receiving dock
GS1 US, the standards body behind the Serial Shipping Container Code (SSCC), explains the pairing in its SSCC introduction:
- An SSCC identifies one logistic unit, such as a case, carton, pallet or air cargo container. It is an 18-digit number including the check digit.
- Because each SSCC is unique to the delivery, it can serve as a lookup number for the contents of the load as part of the ASN process.
- One scan of the SSCC at a receiving bay can be linked to a pre-received electronic ASN for that unit, which GS1 US says supports faster receiving, reconciliation and put-away.
- GS1 US describes the SSCC as a license plate for the shipment: it tracks the logistic unit through the supply chain, while the GTIN identifies the trade items inside.
Why the product codes are in the ASN and not in the SSCC
GS1 US answers this directly: the GTIN should not be included in the SSCC. GTIN information travels in the ASN sent to the receiver before shipment, and the SSCC is linked to that ASN, which gives access to the GTIN data. The SSCC is used in distribution and warehouse environments, never at the point of sale.
850 vs 856: what is the difference?
An 850 is the purchase order a buyer sends; an 856 is the shipment notice the seller or shipper sends back after goods are prepared, before they arrive (see the EDI term for the full order-to-invoice sequence). They are different messages with different senders and different jobs.
| Question | 850 | 856 |
|---|---|---|
| What it is | Purchase order | Ship Notice/Manifest (advance ship notice) |
| Who sends it | Buyer | Shipper or seller |
| When | At ordering | Before the shipment arrives |
| Link to the physical unit | Not covered by the GS1 US SSCC guide | The SSCC on each logistic unit is linked to the ASN, and GTINs sit in the ASN, not in the SSCC (GS1 US) |
Where it matters for labs, clinics and supply decisions
In pharmaceutical distribution, the Healthcare Distribution Alliance (HDA) published EDI guidelines for the 856 in July 2014 to support compliance with the Drug Supply Chain Security Act (DSCSA). Its stated purpose is to give manufacturers a standard way to send distributors advance shipment information for planning and for automating receiving; the guideline covers ship-to, buyer, ship-from and seller details as well as direct purchase and transaction statements. Labs and clinics buying through distributors are on the receiving end of that data flow even when they never read the message itself.
A checklist for anyone documenting a receiving process, drawn from the GS1 US guidance above:
- Is an electronic ASN sent for each shipment, and does it arrive before the goods?
- Does each carton or pallet carry a scannable SSCC label?
- Is the SSCC linked to the ASN so one scan retrieves the contents?
- Are product identifiers (GTINs) read from the ASN rather than expected inside the SSCC?
Which fields, label formats and timing a given customer requires is set in that trading partner’s own guideline. For supplier documentation more generally, see the vendor onboarding documentation checklist, the goods receipt note guide and the hospital supply chain overview.
Common misunderstandings
- The 856 is not an invoice. It describes what is being shipped; billing is a separate message.
- The SSCC is not a product code. It identifies the logistic unit; the GTIN identifies the trade item.
- The SSCC is not for retail scanning. GS1 US limits it to distribution and warehouse use.
- The 856 is not one fixed layout everywhere. The X12 set has a standard name, but partners and sectors publish their own guidelines, such as the HDA guideline for pharmaceuticals.
FAQ
What is an 850 vs 856 transaction?
The 850 is the purchase order from the buyer. The 856 is the advance ship notice from the shipper, sent before delivery, describing the shipment so the receiver can plan and reconcile on arrival.
What does ASN stand for in EDI?
Advance Ship Notice. In ASC X12 it is transaction set 856, named Ship Notice/Manifest.
How does the SSCC relate to the 856?
The SSCC on the physical unit is the lookup key. Scanning it at receiving can be linked to the ASN received earlier (GS1 US).
Sources
- GS1 US, An Introduction to the Serial Shipping Container Code (SSCC), checked 2026-10-31.
- Healthcare Distribution Alliance, EDI Guidelines For 856 Advance Ship Notice to Support Implementation of DSCSA (July 2014), checked 2026-10-31.
- NIST, Federal Implementation Guideline for ASC X12 003050 Transaction Set 856 Ship Notice/Manifest (SP 881-66, 1998), checked 2026-10-31.
