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

Position
Segment
Name
Max use
  1. To indicate the start of a transaction set and to assign a control number

  2. To transmit identifying numbers, dates and other basic data relating to the transaction set

  3. To transmit information in a free-form format, if necessary, for comment or special instruction

  4. To specify pertinent dates and times

Detail

Position
Segment
Name
Max use
  1. HL Loop Mandatory
    Repeat 200000
    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.
    2. To specify basic item identification data.

    3. To specify line item detail relative to shipment

    4. To specify product subline detail item data

    5. To provide reference to a specific purchase order

    6. To specify the physical qualities, packaging, weights and dimensions relating to the item.

    7. To describe a product in coded or free-form format

    8. To specify physical measurements, including dimensions, tolerances, weights and counts.

    9. To specify the type and transmission of paperwork relating to product or order.

    10. To describe marking, packaging, loading and unloading requirements.

    11. To specify the transportation details relative to commodity, weight and quantity.

    12. To specify the carrier, sequence of routing and to provide transit time information

    13. To specify transportation details relating to the equipment used by the carrier.

    14. To specify transportation special handling requirements and hazardous materials information

    15. To transmit identifying numbers

    16. To identify a person or office to whom administrative communications should be directed

    17. CLD Loop Optional
      Repeat 200
      1. To specify the number of material loads shipped.

        Loop CLD is optional, but, if used, segment CLD is mandatory.
      2. To transmit identifying numbers

    18. To indicate identifying marks and numbers for shipping containers

    19. To specify pertinent dates and times

    20. To specify transportation instructions relating to shipment

    21. N1 Loop Optional
      Repeat 200
      1. To identify a party by type of organization, name and code

        Loop N1 is optional, but, if used, segment N1 is mandatory.
      2. To specify additional names or those longer than 35 characters in length

      3. To specify the location of the named party

      4. To specify the geographic place of the named party

      5. To transmit identifying numbers

      6. To identify a person or office to whom administrative communications should be directed

      7. To specify transportation instructions relating to shipment

    22. To specify destination and quantity detail.

    23. To specify information relating to premium transportation.

    24. To specify the currency (dollars, pounds, francs, etc.) used in a transaction

    25. To specify allowances, charges or services

Summary

Position
Segment
Name
Max use
  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.
  2. To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.