EDI 856 Ship Notice/Manifest
Functional Group SH
X12M Supply Chain Subcommittee
This standard provides the standardized format and establishes the data contents of a ship notice/manifest transaction set within the context of an electronic data interchange (EDI) environment. A ship notice/manifest lists the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information. The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.
What is an EDI 856?
An EDI 856 Ship Notice/Manifest communicates Purchase Order shipment details from a supplier to a buyer. It contains information about packaging details (HL Segment), UCC/SSCC numbers (MAN Segment), and tracking numbers (REF Segment).
How is an EDI 856 used?
For example, after fulfilling the 850 Purchase Order, Vendor B will send Retailer A an 856 Ship Notice/Manifest to communicate that the order has been shipped. Once the order has shipped, an 810 Invoice will follow.
Heading
- 2Transaction Set HeaderMandatoryMax 1
To indicate the start of a transaction set and to assign a control number
- 3Beginning Segment for Ship NoticeMandatoryMax 1
To transmit identifying numbers, dates and other basic data relating to the transaction set
- 4Note/Special InstructionFMax 100
To transmit information in a free-form format, if necessary, for comment or special instruction
- 5Date/Time ReferenceOptionalMax 10
To specify pertinent dates and times
Detail
- HL Loop MandatoryRepeat 200000
- 7Hierarchical LevelMandatoryMax 1
To identify dependencies among and the content of hierarchically related groups of data segments.
At least one occurrence of loop HL is required. The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning. - 8Item Identification DetailOptionalMax 1
To specify basic item identification data.
- 10Item Detail (Shipment)OptionalMax 1
To specify line item detail relative to shipment
- 11Subline Item DetailOptionalMax 100
To specify product subline detail item data
- 12Purchase Order ReferenceOptionalMax 1
To provide reference to a specific purchase order
- 13Item Physical DetailsOptionalMax 1
To specify the physical qualities, packaging, weights and dimensions relating to the item.
- 14Product/Item DescriptionOptionalMax 200
To describe a product in coded or free-form format
- 15MeasurementsOptionalMax 40
To specify physical measurements, including dimensions, tolerances, weights and counts.
- 16PaperworkOptionalMax 25
To specify the type and transmission of paperwork relating to product or order.
- 17Marking, Packaging, LoadingOptionalMax 25
To describe marking, packaging, loading and unloading requirements.
- 18Carrier Details (Quantity and Weight)OptionalMax 20
To specify the transportation details relative to commodity, weight and quantity.
- 19Carrier Details (Routing Sequence/Transit Time)OptionalMax 12
To specify the carrier, sequence of routing and to provide transit time information
- 20Carrier Details (Equipment)OptionalMax 12
To specify transportation details relating to the equipment used by the carrier.
- 21Carrier Details (Special Handling/Hazardous Materials)OptionalMax 5
To specify transportation special handling requirements and hazardous materials information
- 22Reference NumbersOptionalMax 200
To transmit identifying numbers
- 23Administrative Communications ContactOptionalMax 1
To identify a person or office to whom administrative communications should be directed
- CLD Loop OptionalRepeat 200
- 24Load DetailMandatoryMax 1
To specify the number of material loads shipped.
Loop CLD is optional, but, if used, segment CLD is mandatory. - 25Reference NumbersOptionalMax 200
To transmit identifying numbers
- 24Load DetailMandatoryMax 1
- 26Marks and NumbersOptionalMax 10
To indicate identifying marks and numbers for shipping containers
- 27Date/Time ReferenceOptionalMax 10
To specify pertinent dates and times
- 28F.O.B. Related InstructionsOptionalMax 1
To specify transportation instructions relating to shipment
- N1 Loop OptionalRepeat 200
- 29NameMandatoryMax 1
To identify a party by type of organization, name and code
Loop N1 is optional, but, if used, segment N1 is mandatory. - 30Additional Name InformationOptionalMax 2
To specify additional names or those longer than 35 characters in length
- 31Address InformationOptionalMax 2
To specify the location of the named party
- 32Geographic LocationOptionalMax 1
To specify the geographic place of the named party
- 33Reference NumbersOptionalMax 12
To transmit identifying numbers
- 34Administrative Communications ContactOptionalMax 3
To identify a person or office to whom administrative communications should be directed
- 35F.O.B. Related InstructionsOptionalMax 1
To specify transportation instructions relating to shipment
- 29NameMandatoryMax 1
- 36Destination QuantityOptionalMax 50
To specify destination and quantity detail.
- 37Excess Transportation DetailOptionalMax 1
To specify information relating to premium transportation.
- 38CurrencyOptionalMax 1
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
- 39Allowance, Charge or ServiceOptionalMax 10
To specify allowances, charges or services
- 7Hierarchical LevelMandatoryMax 1
Summary
- 41Transaction TotalsMandatoryMax 1
To transmit a hash total for a specific element in the transaction set
Number of line items (CTT01) is the accumulation of the number of HL segments. Hash total (CTT02) is the accumulation of the value of units shipped (SN102) for each SN1 segment. - 42Transaction Set TrailerMandatoryMax 1
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).