Logic Broker
/
Ship Notice/Manifest
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Logic Broker. Contact Logic Broker for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Logic Broker logo

X12 856 Ship Notice/Manifest

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list 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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
    View the latest version of this implementation guide as an interactive webpage
    https://www.stedi.com/app/guides/view/logic-broker/ship-noticemanifest/01HCEAVZAJV0VK50AEY1HFMA5M
    Powered by
    Build EDI implementation guides at stedi.com
    Overview
    ISA
    -
    Interchange Control Header
    Max use 1
    Required
    GS
    -
    Functional Group Header
    Max use 1
    Required
    heading
    detail
    HL Loop
    HL
    010
    Hierarchical Level
    Max use 1
    Required
    TD5
    120
    Carrier Details (Routing Sequence/Transit Time)
    Max use 12
    Required
    REF
    150
    Bill of Lading Number
    Max use 1
    Optional
    REF
    150
    Carrier's Reference Number (PRO/Invoice)
    Max use 1
    Optional
    REF
    150
    Carrier's Reference Number (PRO/Invoice)
    Max use 1
    Optional
    DTM
    200
    Current Schedule Delivery
    Max use 10
    Optional
    DTM
    200
    Shipped
    Max use 10
    Required
    N1 Loop Bill-to-Party
    GE
    -
    Functional Group Trailer
    Max use 1
    Required
    IEA
    -
    Interchange Control Trailer
    Max use 1
    Required
    ISA

    Interchange Control Header

    RequiredMax use 1

    To start and identify an interchange of zero or more functional groups and interchange-related control segments

    Example
    ISA-01
    I01
    Authorization Information Qualifier
    Required

    Code to identify the type of information in the Authorization Information

    00
    No Authorization Information Present (No Meaningful Information in I02)
    ISA-02
    I02
    Authorization Information
    Required
    String (AN)
    Min 10Max 10

    Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

    ISA-03
    I03
    Security Information Qualifier
    Required

    Code to identify the type of information in the Security Information

    00
    No Security Information Present (No Meaningful Information in I04)
    ISA-04
    I04
    Security Information
    Required
    String (AN)
    Min 10Max 10

    This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

    ISA-05
    I05
    Interchange ID Qualifier
    Required
    Identifier (ID)
    Min 2Max 2

    Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

    Codes
    ISA-06
    I06
    Interchange Sender ID
    Required
    String (AN)
    Min 15Max 15

    Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

    ISA-07
    I05
    Interchange ID Qualifier
    Required
    Identifier (ID)
    Min 2Max 2

    Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

    Codes
    ISA-08
    I07
    Interchange Receiver ID
    Required
    String (AN)
    Min 15Max 15

    Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

    ISA-09
    I08
    Interchange Date
    Required
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I10
    Interchange Control Standards Identifier
    Required

    Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

    U
    U.S. EDI Community of ASC X12, TDCC, and UCS
    ISA-12
    I11
    Interchange Control Version Number
    Required

    This version number covers the interchange control segments

    00401
    Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
    ISA-13
    I12
    Interchange Control Number
    Required
    Numeric (N0)
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    Identifier (ID)
    Min 1Max 1

    Code sent by the sender to request an interchange acknowledgment (TA1)

    0
    No Acknowledgment Requested
    1
    Interchange Acknowledgment Requested
    ISA-15
    I14
    Usage Indicator
    Required
    Identifier (ID)
    Min 1Max 1

    Code to indicate whether data enclosed by this interchange envelope is test, production or information

    I
    Information
    P
    Production Data
    T
    Test Data
    ISA-16
    I15
    Component Element Separator
    Required
    String (AN)
    Min 1Max 1

    Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

    >
    Component Element Separator

    Functional Group Header

    RequiredMax use 1

    To indicate the beginning of a functional group and to provide control information

    Example
    GS-01
    479
    Functional Identifier Code
    Required

    Code identifying a group of application related transaction sets

    SH
    Ship Notice/Manifest (856)
    GS-02
    142
    Application Sender's Code
    Required
    String (AN)
    Min 2Max 15

    Code identifying party sending transmission; codes agreed to by trading partners

    GS-03
    124
    Application Receiver's Code
    Required
    String (AN)
    Min 2Max 15

    Code identifying party receiving transmission. Codes agreed to by trading partners

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    GS-05
    337
    Time
    Required
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

    GS-06
    28
    Group Control Number
    Required
    Numeric (N0)
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    Identifier (ID)
    Min 1Max 2

    Code used in conjunction with Data Element 480 to identify the issuer of the standard

    T
    Transportation Data Coordinating Committee (TDCC)
    X
    Accredited Standards Committee X12
    GS-08
    480
    Version / Release / Industry Identifier Code
    Required

    Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

    004010
    Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

    Heading

    ST
    010
    Heading > ST

    Transaction Set Header

    RequiredMax use 1

    To indicate the start of a transaction set and to assign a control number

    Example
    ST-01
    143
    Transaction Set Identifier Code
    Required

    Code uniquely identifying a Transaction Set

    • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
    856
    Ship Notice/Manifest
    ST-02
    329
    Transaction Set Control Number
    Required
    Numeric (N)
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    BSN
    020
    Heading > BSN

    Beginning Segment for Ship Notice

    RequiredMax use 1

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

    Example
    BSN-01
    353
    Transaction Set Purpose Code
    Required
    Identifier (ID)
    Min 2Max 2

    Code identifying purpose of transaction set

    BSN-02
    396
    Shipment Identification
    Required
    String (AN)
    Min 2Max 30

    A unique control number assigned by the original shipper to identify a specific shipment

    BSN-03
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BSN03 is the date the shipment transaction set is created.
    BSN-04
    337
    Time
    Optional
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

    • BSN04 is the time the shipment transaction set is created.
    BSN-05
    1005
    Hierarchical Structure Code
    Required

    Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set

    0001
    Shipment, Order, Packaging, Item
    Heading end

    Detail

    HL Loop
    RequiredMax >1
    HL
    010
    Detail > HL Loop > HL

    Hierarchical Level

    RequiredMax use 1

    To identify dependencies among and the content of hierarchically related groups of data segments

    • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    String (AN)
    Min 1Max 12

    A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

    • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
    HL-03
    735
    Hierarchical Level Code
    Required

    Code defining the characteristic of a level in a hierarchical structure

    • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
    S
    Shipment
    HL-04
    736
    Hierarchical Child Code
    Optional

    Code indicating if there are hierarchical child data segments subordinate to the level being described

    • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
    1
    Additional Subordinate HL Data Segment in This Hierarchical Structure.
    TD5
    120
    Detail > HL Loop > TD5

    Carrier Details (Routing Sequence/Transit Time)

    RequiredMax use 12

    To specify the carrier and sequence of routing and provide transit time information

    Usage notes

    TD503 Identification (Carrier Code) - this is the Standard Carrier Alpha Code (SCAC). If you are using your own custom shipping methods, these are set-up on the "Shipment Settings" page in the portal, the Carrier Code will automatically populate based on the Class Code (TD505) submitted.

    TD505 Routing (Class code) - This is the field that will be a combination of both SCAC and Service Level. If you map this to your partner's, the Carrier Code (TD503) and the Service Level Code (TD512) will automatically populate accordingly. This will allow you to only keep track of one code (Class Code) rather then 3.

    TD512 Service Level Code (Service Level Code) - If you are using your own custom shipping methods, these are set-up on the "Shipment Settings" page in the portal, the Service Level Code (TD512) will automatically populate based on the Class Code (TD505) submitted.

    Example
    If Identification Code Qualifier (TD5-02) is present, then Identification Code (TD5-03) is required
    TD5-01
    133
    Routing Sequence Code
    Optional

    Code describing the relationship of a carrier to a specific shipment movement

    B
    Origin/Delivery Carrier (Any Mode)
    TD5-02
    66
    Identification Code Qualifier
    Optional

    Code designating the system/method of code structure used for Identification Code (67)

    • When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
    2
    Standard Carrier Alpha Code (SCAC)
    TD5-03
    67
    Identification Code
    Optional
    String (AN)
    Min 2Max 80

    Code identifying a party or other code

    TD5-05
    387
    Routing
    Required
    String (AN)
    Min 1Max 35

    Free-form description of the routing or requested routing for shipment, or the originating carrier's identity

    TD5-12
    284
    Service Level Code
    Optional

    Code indicating the level of transportation service or the billing service offered by the transportation carrier

    CG
    Ground
    ND
    Next Day Air
    ON
    Overnight
    SA
    Same Day
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    BM
    Bill of Lading Number
    REF-02
    127
    Reference Identification
    Optional
    String (AN)
    Min 1Max 30

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    REF
    150
    Detail > HL Loop > REF

    Carrier's Reference Number (PRO/Invoice)

    OptionalMax use >1

    To specify identifying information

    Usage notes

    CN (Carrier Reference/PRO Number) - If your shipment has a PRO number, please enter it here. This field is optional.

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    CN
    Carrier's Reference Number (PRO/Invoice)
    REF-02
    127
    Reference Identification
    Optional
    String (AN)
    Min 1Max 30

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    REF
    150
    Detail > HL Loop > REF

    Carrier's Reference Number (PRO/Invoice)

    OptionalMax use 1

    To specify identifying information

    Usage notes

    CN (Carrier Reference/PRO Number) - If your shipment has a PRO number, please enter it here. This field is optional.

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    IL
    Internal Order Number
    REF-02
    127
    Reference Identification
    Optional
    String (AN)
    Min 1Max 30

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    DTM
    200
    Detail > HL Loop > DTM

    Current Schedule Delivery

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    Date the shipment is expected to be delivered.

    Example
    Variants (all may be used)
    DTM Shipped
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time

    067
    Current Schedule Delivery
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    DTM
    200
    Detail > HL Loop > DTM

    Shipped

    RequiredMax use 10

    To specify pertinent dates and times

    Usage notes

    Date the shipment is getting picked up.

    Example
    Variants (all may be used)
    DTMCurrent Schedule Delivery
    DTM-01
    374
    Date/Time Qualifier
    Required

    Code specifying type of date or time, or both date and time

    011
    Shipped
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    N1 Loop Bill-to-Party
    OptionalMax 1
    Variants (all may be used)
    N1 Loop Ship FromN1 Loop Ship To
    N1
    220
    Detail > HL Loop > N1 Loop Bill-to-Party > N1

    Name

    RequiredMax use 1

    To identify a party by type of organization, name, and code

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, property or an individual

    BT
    Bill-to-Party
    N1-02
    93
    Name
    Optional
    String (AN)
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

    Code designating the system/method of code structure used for Identification Code (67)

    93
    Code assigned by the organization originating the transaction set
    N1-04
    67
    Identification Code
    Optional
    String (AN)
    Min 2Max 80

    Code identifying a party or other code

    • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
    N3
    240
    Detail > HL Loop > N1 Loop Bill-to-Party > N3

    Address Information

    RequiredMax use 2

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    String (AN)
    Min 1Max 55

    Address information

    N3-02
    166
    Address Information
    Optional
    String (AN)
    Min 1Max 55

    Address information

    N4
    250
    Detail > HL Loop > N1 Loop Bill-to-Party > N4

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Required
    String (AN)
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Required
    Identifier (ID)
    Min 2Max 2

    Code (Standard State/Province) as defined by appropriate government agency

    • N402 is required only if city name (N401) is in the U.S. or Canada.
    N4-03
    116
    Postal Code
    Required
    Identifier (ID)
    Min 3Max 15

    Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

    N4-04
    26
    Country Code
    Optional
    Identifier (ID)
    Min 2Max 3

    Code identifying the country

    PER
    270
    Detail > HL Loop > N1 Loop Bill-to-Party > PER

    Administrative Communications Contact

    OptionalMax use 3

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

    Example
    If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
    If either Communication Number Qualifier (PER-05) or Communication Number (PER-06) is present, then the other is required
    PER-01
    366
    Contact Function Code
    Required

    Code identifying the major duty or responsibility of the person or group named

    IC
    Information Contact
    PER-02
    93
    Name
    Optional
    String (AN)
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    EM
    Electronic Mail
    PER-04
    364
    Communication Number
    Optional
    String (AN)
    Min 1Max 80

    Complete communications number including country or area code when applicable

    PER-05
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    TE
    Telephone
    PER-06
    364
    Communication Number
    Optional
    String (AN)
    Min 1Max 80

    Complete communications number including country or area code when applicable

    N1 Loop Bill-to-Party end
    N1 Loop Ship From
    RequiredMax 1
    Variants (all may be used)
    N1 Loop Bill-to-PartyN1 Loop Ship To
    N1
    220
    Detail > HL Loop > N1 Loop Ship From > N1

    Name

    RequiredMax use 1

    To identify a party by type of organization, name, and code

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, property or an individual

    SF
    Ship From
    N1-02
    93
    Name
    Optional
    String (AN)
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

    Code designating the system/method of code structure used for Identification Code (67)

    93
    Code assigned by the organization originating the transaction set
    N1-04
    67
    Identification Code
    Optional
    String (AN)
    Min 2Max 80

    Code identifying a party or other code

    • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
    N3
    240
    Detail > HL Loop > N1 Loop Ship From > N3

    Address Information

    RequiredMax use 2

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    String (AN)
    Min 1Max 55

    Address information

    N3-02
    166
    Address Information
    Optional
    String (AN)
    Min 1Max 55

    Address information

    N4
    250
    Detail > HL Loop > N1 Loop Ship From > N4

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Required
    String (AN)
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Required
    Identifier (ID)
    Min 2Max 2

    Code (Standard State/Province) as defined by appropriate government agency

    • N402 is required only if city name (N401) is in the U.S. or Canada.
    N4-03
    116
    Postal Code
    Required
    Identifier (ID)
    Min 3Max 15

    Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

    N4-04
    26
    Country Code
    Optional
    Identifier (ID)
    Min 2Max 3

    Code identifying the country

    PER
    270
    Detail > HL Loop > N1 Loop Ship From > PER

    Administrative Communications Contact

    OptionalMax use 3

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

    Example
    If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
    If either Communication Number Qualifier (PER-05) or Communication Number (PER-06) is present, then the other is required
    PER-01
    366
    Contact Function Code
    Required

    Code identifying the major duty or responsibility of the person or group named

    IC
    Information Contact
    PER-02
    93
    Name
    Optional
    String (AN)
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    EM
    Electronic Mail
    PER-04
    364
    Communication Number
    Optional
    String (AN)
    Min 1Max 80

    Complete communications number including country or area code when applicable

    PER-05
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    TE
    Telephone
    PER-06
    364
    Communication Number
    Optional
    String (AN)
    Min 1Max 80

    Complete communications number including country or area code when applicable

    N1 Loop Ship From end
    N1 Loop Ship To
    OptionalMax 1
    Variants (all may be used)
    N1 Loop Bill-to-PartyN1 Loop Ship From
    N1
    220
    Detail > HL Loop > N1 Loop Ship To > N1

    Name

    RequiredMax use 1

    To identify a party by type of organization, name, and code

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, property or an individual

    ST
    Ship To
    N1-02
    93
    Name
    Optional
    String (AN)
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

    Code designating the system/method of code structure used for Identification Code (67)

    93
    Code assigned by the organization originating the transaction set
    N1-04
    67
    Identification Code
    Optional
    String (AN)
    Min 2Max 80

    Code identifying a party or other code

    • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
    N3
    240
    Detail > HL Loop > N1 Loop Ship To > N3

    Address Information

    RequiredMax use 2

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    String (AN)
    Min 1Max 55

    Address information

    N3-02
    166
    Address Information
    Optional
    String (AN)
    Min 1Max 55

    Address information

    N4
    250
    Detail > HL Loop > N1 Loop Ship To > N4

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Required
    String (AN)
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Required
    Identifier (ID)
    Min 2Max 2

    Code (Standard State/Province) as defined by appropriate government agency

    • N402 is required only if city name (N401) is in the U.S. or Canada.
    N4-03
    116
    Postal Code
    Required
    Identifier (ID)
    Min 3Max 15

    Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

    N4-04
    26
    Country Code
    Optional
    Identifier (ID)
    Min 2Max 3

    Code identifying the country

    PER
    270
    Detail > HL Loop > N1 Loop Ship To > PER

    Administrative Communications Contact

    OptionalMax use 3

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

    Example
    If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
    If either Communication Number Qualifier (PER-05) or Communication Number (PER-06) is present, then the other is required
    PER-01
    366
    Contact Function Code
    Required

    Code identifying the major duty or responsibility of the person or group named

    IC
    Information Contact
    PER-02
    93
    Name
    Optional
    String (AN)
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    EM
    Electronic Mail
    PER-04
    364
    Communication Number
    Optional
    String (AN)
    Min 1Max 80

    Complete communications number including country or area code when applicable

    PER-05
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    TE
    Telephone
    PER-06
    364
    Communication Number
    Optional
    String (AN)
    Min 1Max 80

    Complete communications number including country or area code when applicable

    N1 Loop Ship To end
    HL Loop
    RequiredMax >1
    HL
    010
    Detail > HL Loop > HL Loop > HL

    Hierarchical Level

    RequiredMax use 1

    To identify dependencies among and the content of hierarchically related groups of data segments

    • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    String (AN)
    Min 1Max 12

    A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

    • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
    HL-02
    734
    Hierarchical Parent ID Number
    Required
    String (AN)
    Min 1Max 12

    Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

    • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
    HL-03
    735
    Hierarchical Level Code
    Required

    Code defining the characteristic of a level in a hierarchical structure

    • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
    O
    Order
    HL-04
    736
    Hierarchical Child Code
    Optional

    Code indicating if there are hierarchical child data segments subordinate to the level being described

    • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
    0
    No Subordinate HL Segment in This Hierarchical Structure.
    1
    Additional Subordinate HL Data Segment in This Hierarchical Structure.
    PRF
    050
    Detail > HL Loop > HL Loop > PRF

    Purchase Order Reference

    RequiredMax use 1

    To provide reference to a specific purchase order

    Usage notes

    PRF01 (Purchase Order Number) - this is the same number that was sent on the 850. This will always need to match.

    Example
    PRF-01
    324
    Purchase Order Number
    Required
    String (AN)
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    HL Pack
    OptionalMax >1
    Variants (all may be used)
    Shipping Tare
    HL
    010
    Detail > HL Loop > HL Loop > Pack > HL

    Hierarchical Level

    RequiredMax use 1

    To identify dependencies among and the content of hierarchically related groups of data segments

    • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    String (AN)
    Min 1Max 12

    A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

    • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
    HL-02
    734
    Hierarchical Parent ID Number
    Required
    String (AN)
    Min 1Max 12

    Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

    • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
    HL-03
    735
    Hierarchical Level Code
    Required

    Code defining the characteristic of a level in a hierarchical structure

    • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
    P
    Pack
    HL-04
    736
    Hierarchical Child Code
    Optional

    Code indicating if there are hierarchical child data segments subordinate to the level being described

    • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
    1
    Additional Subordinate HL Data Segment in This Hierarchical Structure.
    PO4
    060
    Detail > HL Loop > HL Loop > Pack > PO4

    Item Physical Details

    RequiredMax use 1

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

    Usage notes

    Dimensions for each carton/pack.

    Example
    PO4-10
    82
    Length
    Required
    Decimal number (R)
    Min 1Max 8

    Largest horizontal dimension of an object measured when the object is in the upright position

    PO4-11
    189
    Width
    Required
    Decimal number (R)
    Min 1Max 8

    Shorter measurement of the two horizontal dimensions measured with the object in the upright position

    PO4-12
    65
    Height
    Required
    Decimal number (R)
    Min 1Max 8

    Vertical dimension of an object measured when the object is in the upright position

    PO4-13
    355
    Unit or Basis for Measurement Code
    Optional

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    • PO413 defines the unit of measure for PO410, PO411, and PO412.
    IN
    Inch
    TD1
    110
    Detail > HL Loop > HL Loop > Pack > TD1

    Carrier Details (Quantity and Weight)

    RequiredMax use 20

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

    Usage notes

    TD101 (Packaging Code) - CTN will always be used to specify that this is a carton or box.

    TD102 (Lading Quantity) - Total number of Items (Item Level) that are in the carton or box.

    TD107 (Weight) - Gross weight of the carton or box.

    Example
    If Packaging Code (TD1-01) is present, then Lading Quantity (TD1-02) is required
    TD1-01
    103
    Packaging Code
    Required

    Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required

    CTN
    Carton
    TD1-02
    80
    Lading Quantity
    Optional
    Numeric (N0)
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    TD1-06
    187
    Weight Qualifier
    Required

    Code defining the type of weight

    G
    Gross Weight
    TD1-07
    81
    Weight
    Required
    Decimal number (R)
    Min 1Max 10

    Numeric value of weight

    TD1-08
    355
    Unit or Basis for Measurement Code
    Required

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    LB
    Pound
    MAN
    190
    Detail > HL Loop > HL Loop > Pack > MAN

    Marks and Numbers

    RequiredMax use >1

    To indicate identifying marks and numbers for shipping containers

    Usage notes

    CP (Carrier-Assigned Package ID Number) - This is the tracking number assigned by your carrier for the carton or box shipment.

    GM (SSCC-18 and Application Identifier) - This needs to be a GS1 formatted SSCC18 code and will need to match the label that is being put on the physical carton or box.

    **CP is always required for dropship. GM will only be required for direct to store or replenishment orders.

    Example
    MAN-01
    88
    Marks and Numbers Qualifier
    Required

    Code specifying the application or source of Marks and Numbers (87)

    • MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
    • When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
    CP
    Carrier-Assigned Package ID Number
    GM
    SSCC-18 and Application Identifier
    MAN-02
    87
    Marks and Numbers
    Required
    String (AN)
    Min 1Max 48

    Marks and numbers used to identify a shipment or parts of a shipment

    • When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
    HL Loop
    RequiredMax >1
    HL
    010
    Detail > HL Loop > HL Loop > Pack > HL Loop > HL

    Hierarchical Level

    RequiredMax use 1

    To identify dependencies among and the content of hierarchically related groups of data segments

    • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    String (AN)
    Min 1Max 12

    A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

    • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
    HL-02
    734
    Hierarchical Parent ID Number
    Required
    String (AN)
    Min 1Max 12

    Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

    • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
    HL-03
    735
    Hierarchical Level Code
    Required

    Code defining the characteristic of a level in a hierarchical structure

    • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
    I
    Item
    HL-04
    736
    Hierarchical Child Code
    Optional

    Code indicating if there are hierarchical child data segments subordinate to the level being described

    • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
    0
    No Subordinate HL Segment in This Hierarchical Structure.
    LIN
    020
    Detail > HL Loop > HL Loop > Pack > HL Loop > LIN

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

    Example
    If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required
    If either Product/Service ID Qualifier (LIN-06) or Product/Service ID (LIN-07) is present, then the other is required
    LIN-01
    350
    Assigned Identification
    Required
    String (AN)
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • LIN01 is the line item identification
    Usage notes

    This should match PO101 from the original item line on the 850 Purchase Order.

    LIN-02
    235
    Product/Service ID Qualifier
    Required

    Code identifying the type/source of the descriptive number used in Product/Service ID (234)

    • LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
    VN
    Vendor's (Seller's) Item Number
    LIN-03
    234
    Product/Service ID
    Required
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    LIN-04
    235
    Product/Service ID Qualifier
    Optional

    Code identifying the type/source of the descriptive number used in Product/Service ID (234)

    IN
    Buyer's Item Number
    LIN-05
    234
    Product/Service ID
    Optional
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    LIN-06
    235
    Product/Service ID Qualifier
    Optional

    Code identifying the type/source of the descriptive number used in Product/Service ID (234)

    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    LIN-07
    234
    Product/Service ID
    Optional
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    SN1
    030
    Detail > HL Loop > HL Loop > Pack > HL Loop > SN1

    Item Detail (Shipment)

    RequiredMax use 1

    To specify line-item detail relative to shipment

    Example
    SN1-02
    382
    Number of Units Shipped
    Required
    Decimal number (R)
    Min 1Max 10

    Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

    SN1-03
    355
    Unit or Basis for Measurement Code
    Required

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    • SN103 defines the unit of measurement for both SN102 and SN104.
    CA
    Case
    EA
    Each
    PID
    070
    Detail > HL Loop > HL Loop > Pack > HL Loop > PID

    Product/Item Description

    OptionalMax use 200

    To describe a product or process in coded or free-form format

    Example
    PID-01
    349
    Item Description Type
    Required

    Code indicating the format of a description

    • If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
    F
    Free-form
    PID-02
    750
    Product/Process Characteristic Code
    Optional

    Code identifying the general class of a product or process characteristic

    08
    Product
    35
    Color
    SIZ
    Sizing
    PID-05
    352
    Description
    Required
    String (AN)
    Min 1Max 80

    A free-form description to clarify the related data elements and their content

    HL Loop end
    HL Pack end
    HL Shipping Tare
    OptionalMax >1
    Usage notes

    This level will be used only to specify pallet. If you are not sending pallets, please ignore this level.

    Variants (all may be used)
    Pack
    HL
    010
    Detail > HL Loop > HL Loop > Shipping Tare > HL

    Hierarchical Level

    RequiredMax use 1

    To identify dependencies among and the content of hierarchically related groups of data segments

    • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    String (AN)
    Min 1Max 12

    A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

    • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
    HL-02
    734
    Hierarchical Parent ID Number
    Required
    String (AN)
    Min 1Max 12

    Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

    • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
    HL-03
    735
    Hierarchical Level Code
    Required

    Code defining the characteristic of a level in a hierarchical structure

    • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
    T
    Shipping Tare
    HL-04
    736
    Hierarchical Child Code
    Optional

    Code indicating if there are hierarchical child data segments subordinate to the level being described

    • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
    1
    Additional Subordinate HL Data Segment in This Hierarchical Structure.
    TD1
    110
    Detail > HL Loop > HL Loop > Shipping Tare > TD1

    Carrier Details (Quantity and Weight)

    OptionalMax use 20

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

    Usage notes

    TD101 (Packaging Code) - PLT will always be used to specify that this is a pallet.

    TD102 (Lading Quantity) - Total number of cartons (Pack Level) that are on the pallet.

    TD107 (Weight) - Gross weight of the pallet.

    TD109 (Volume) - total volume measurement of the pallet.

    Example
    If Weight Qualifier (TD1-06) is present, then Weight (TD1-07) is required
    If either Weight (TD1-07) or Unit or Basis for Measurement Code (TD1-08) is present, then the other is required
    If either Volume (TD1-09) or Unit or Basis for Measurement Code (TD1-10) is present, then the other is required
    TD1-01
    103
    Packaging Code
    Required
    String (AN)
    Min 3Max 5

    Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required

    Usage notes

    PLT will always be used to specify that this is a pallet.

    TD1-02
    80
    Lading Quantity
    Optional
    Numeric (N0)
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    TD1-06
    187
    Weight Qualifier
    Optional

    Code defining the type of weight

    G
    Gross Weight
    TD1-07
    81
    Weight
    Optional
    Decimal number (R)
    Min 1Max 10

    Numeric value of weight

    TD1-08
    355
    Unit or Basis for Measurement Code
    Optional

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    LB
    Pound
    TD1-09
    183
    Volume
    Optional
    Decimal number (R)
    Min 1Max 8

    Value of volumetric measure

    TD1-10
    355
    Unit or Basis for Measurement Code
    Optional

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    IN
    Inch
    REF
    150
    Detail > HL Loop > HL Loop > Shipping Tare > REF

    Reference Identification

    OptionalMax use >1

    To specify identifying information

    Usage notes

    ZH (Carrier Assigned Reference Number) - This will be a tracking number for the specific pallet.

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    ZH
    Carrier Assigned Reference Number
    REF-02
    127
    Reference Identification
    Optional
    String (AN)
    Min 1Max 30

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    MAN
    190
    Detail > HL Loop > HL Loop > Shipping Tare > MAN

    Marks and Numbers

    OptionalMax use >1

    To indicate identifying marks and numbers for shipping containers

    Example
    MAN-01
    88
    Marks and Numbers Qualifier
    Required

    Code specifying the application or source of Marks and Numbers (87)

    • MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
    • When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
    GM
    SSCC-18 and Application Identifier
    MAN-02
    87
    Marks and Numbers
    Required
    String (AN)
    Min 1Max 48

    Marks and numbers used to identify a shipment or parts of a shipment

    • When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
    HL Loop
    RequiredMax >1
    HL
    010
    Detail > HL Loop > HL Loop > Shipping Tare > HL Loop > HL

    Hierarchical Level

    RequiredMax use 1

    To identify dependencies among and the content of hierarchically related groups of data segments

    • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    String (AN)
    Min 1Max 12

    A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

    • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
    HL-02
    734
    Hierarchical Parent ID Number
    Required
    String (AN)
    Min 1Max 12

    Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

    • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
    HL-03
    735
    Hierarchical Level Code
    Required

    Code defining the characteristic of a level in a hierarchical structure

    • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
    P
    Pack
    HL-04
    736
    Hierarchical Child Code
    Optional

    Code indicating if there are hierarchical child data segments subordinate to the level being described

    • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
    1
    Additional Subordinate HL Data Segment in This Hierarchical Structure.
    PO4
    060
    Detail > HL Loop > HL Loop > Shipping Tare > HL Loop > PO4

    Item Physical Details

    RequiredMax use 1

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

    Usage notes

    Dimensions for each carton/pack.

    Example
    PO4-10
    82
    Length
    Required
    Decimal number (R)
    Min 1Max 8

    Largest horizontal dimension of an object measured when the object is in the upright position

    PO4-11
    189
    Width
    Required
    Decimal number (R)
    Min 1Max 8

    Shorter measurement of the two horizontal dimensions measured with the object in the upright position

    PO4-12
    65
    Height
    Required
    Decimal number (R)
    Min 1Max 8

    Vertical dimension of an object measured when the object is in the upright position

    PO4-13
    355
    Unit or Basis for Measurement Code
    Optional

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    • PO413 defines the unit of measure for PO410, PO411, and PO412.
    IN
    Inch
    TD1
    110
    Detail > HL Loop > HL Loop > Shipping Tare > HL Loop > TD1

    Carrier Details (Quantity and Weight)

    RequiredMax use 20

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

    Usage notes

    TD101 (Packaging Code) - CTN will always be used to specify that this is a carton or box.

    TD102 (Lading Quantity) - Total number of Items (Item Level) that are in the carton or box.

    TD107 (Weight) - Gross weight of the carton or box.

    Example
    If Packaging Code (TD1-01) is present, then Lading Quantity (TD1-02) is required
    TD1-01
    103
    Packaging Code
    Required

    Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required

    CTN
    Carton
    TD1-02
    80
    Lading Quantity
    Optional
    Numeric (N0)
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    TD1-06
    187
    Weight Qualifier
    Required

    Code defining the type of weight

    G
    Gross Weight
    TD1-07
    81
    Weight
    Required
    Decimal number (R)
    Min 1Max 10

    Numeric value of weight

    TD1-08
    355
    Unit or Basis for Measurement Code
    Required

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    LB
    Pound
    MAN
    190
    Detail > HL Loop > HL Loop > Shipping Tare > HL Loop > MAN

    Marks and Numbers

    RequiredMax use >1

    To indicate identifying marks and numbers for shipping containers

    Usage notes

    CP (Carrier-Assigned Package ID Number) - This is the tracking number assigned by your carrier for the carton or box shipment.

    GM (SSCC-18 and Application Identifier) - This needs to be a GS1 formatted SSCC18 code and will need to match the label that is being put on the physical carton or box.

    **CP is always required for dropship. GM will only be required for direct to store or replenishment orders.

    Example
    MAN-01
    88
    Marks and Numbers Qualifier
    Required

    Code specifying the application or source of Marks and Numbers (87)

    • MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
    • When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
    CP
    Carrier-Assigned Package ID Number
    GM
    SSCC-18 and Application Identifier
    MAN-02
    87
    Marks and Numbers
    Required
    String (AN)
    Min 1Max 48

    Marks and numbers used to identify a shipment or parts of a shipment

    • When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
    HL Loop
    RequiredMax >1
    HL
    010
    Detail > HL Loop > HL Loop > Shipping Tare > HL Loop > HL Loop > HL

    Hierarchical Level

    RequiredMax use 1

    To identify dependencies among and the content of hierarchically related groups of data segments

    • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    String (AN)
    Min 1Max 12

    A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

    • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
    HL-02
    734
    Hierarchical Parent ID Number
    Required
    String (AN)
    Min 1Max 12

    Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

    • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
    HL-03
    735
    Hierarchical Level Code
    Required

    Code defining the characteristic of a level in a hierarchical structure

    • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
    I
    Item
    HL-04
    736
    Hierarchical Child Code
    Optional

    Code indicating if there are hierarchical child data segments subordinate to the level being described

    • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
    0
    No Subordinate HL Segment in This Hierarchical Structure.
    LIN
    020
    Detail > HL Loop > HL Loop > Shipping Tare > HL Loop > HL Loop > LIN

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

    Example
    If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required
    If either Product/Service ID Qualifier (LIN-06) or Product/Service ID (LIN-07) is present, then the other is required
    LIN-01
    350
    Assigned Identification
    Required
    String (AN)
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • LIN01 is the line item identification
    Usage notes

    This should match PO101 from the original item line on the 850 Purchase Order.

    LIN-02
    235
    Product/Service ID Qualifier
    Required

    Code identifying the type/source of the descriptive number used in Product/Service ID (234)

    • LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
    VN
    Vendor's (Seller's) Item Number
    LIN-03
    234
    Product/Service ID
    Required
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    LIN-04
    235
    Product/Service ID Qualifier
    Optional

    Code identifying the type/source of the descriptive number used in Product/Service ID (234)

    IN
    Buyer's Item Number
    LIN-05
    234
    Product/Service ID
    Optional
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    LIN-06
    235
    Product/Service ID Qualifier
    Optional

    Code identifying the type/source of the descriptive number used in Product/Service ID (234)

    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    LIN-07
    234
    Product/Service ID
    Optional
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    SN1
    030
    Detail > HL Loop > HL Loop > Shipping Tare > HL Loop > HL Loop > SN1

    Item Detail (Shipment)

    RequiredMax use 1

    To specify line-item detail relative to shipment

    Example
    SN1-02
    382
    Number of Units Shipped
    Required
    Decimal number (R)
    Min 1Max 10

    Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

    SN1-03
    355
    Unit or Basis for Measurement Code
    Required

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    • SN103 defines the unit of measurement for both SN102 and SN104.
    CA
    Case
    EA
    Each
    PID
    070
    Detail > HL Loop > HL Loop > Shipping Tare > HL Loop > HL Loop > PID

    Product/Item Description

    OptionalMax use 200

    To describe a product or process in coded or free-form format

    Example
    PID-01
    349
    Item Description Type
    Required

    Code indicating the format of a description

    • If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
    F
    Free-form
    PID-02
    750
    Product/Process Characteristic Code
    Optional

    Code identifying the general class of a product or process characteristic

    08
    Product
    35
    Color
    SIZ
    Sizing
    PID-05
    352
    Description
    Required
    String (AN)
    Min 1Max 80

    A free-form description to clarify the related data elements and their content

    HL Loop end
    HL Loop end
    HL Shipping Tare end
    HL Loop end
    HL Loop end
    Detail end

    Summary

    CTT
    010
    Summary > CTT

    Transaction Totals

    RequiredMax 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.
      If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
    Example
    CTT-01
    354
    Number of Line Items
    Required
    Numeric (N0)
    Min 1Max 6

    Total number of line items in the transaction set

    CTT-02
    347
    Hash Total
    Optional
    Decimal number (R)
    Min 1Max 10

    Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.

    ## Example:
    -.0018 First occurrence of value being hashed.
    .18 Second occurrence of value being hashed.
    1.8 Third occurrence of value being hashed.
    18.01 Fourth occurrence of value being hashed.

    1855 Hash total prior to truncation.
    855 Hash total after truncation to three-digit field.

    SE
    020
    Summary > SE

    Transaction Set Trailer

    RequiredMax use 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)

    Example
    SE-01
    96
    Number of Included Segments
    Required
    Numeric (N0)
    Min 1Max 10

    Total number of segments included in a transaction set including ST and SE segments

    SE-02
    329
    Transaction Set Control Number
    Required
    Numeric (N)
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    Summary end

    Functional Group Trailer

    RequiredMax use 1

    To indicate the end of a functional group and to provide control information

    Example
    GE-01
    97
    Number of Transaction Sets Included
    Required
    Numeric (N0)
    Min 1Max 6

    Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

    GE-02
    28
    Group Control Number
    Required
    Numeric (N0)
    Min 1Max 9

    Assigned number originated and maintained by the sender

    Interchange Control Trailer

    RequiredMax use 1

    To define the end of an interchange of zero or more functional groups and interchange-related control segments

    Example
    IEA-01
    I16
    Number of Included Functional Groups
    Required
    Numeric (N0)
    Min 1Max 5

    A count of the number of functional groups included in an interchange

    IEA-02
    I12
    Interchange Control Number
    Required
    Numeric (N0)
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    856 Sample (Pack Only)

    ISA*00* *00* *ZZ*EDI *ZZ*LBEDI2 *160711*2048*U*00401*071120006*0*P*>~
    GS*SH*EDI*LBEDI2*20160711*2048*071120007*X*004010~
    ST*856*071120008~
    BSN*00*1599999999*20160711*16485319*0001~
    HL*1**S~
    TD5*B*2*UNSP**UPS Ground*******CG~
    REF*BM*BOL987456~
    REF*CN*PRO987456~
    DTM*011*20161112~
    DTM*067*20161115~
    N1*SF*Test Company Address~
    N3*Street 123*Street 321~
    N4*Shelton*CT*06484*USA~
    HL*2*1*O~
    PRF*15999999878~
    HL*3*2*P~
    PO4**********4*3*2*IN~
    TD1*CTN*1****G*20*LB~
    MAN*CP*564564654654~
    MAN*GM*081034001000008795~
    HL*4*3*I~
    LIN*3*VN*49-98760*IN*J07874*UP*123456789012~
    SN1**298*EA~
    PID*F*08***Green Mustard~
    PID*F*35***Red~
    PID*F*SIZ***Large~
    HL*5*2*P~
    PO4**********4*3*2*IN~
    TD1*CTN*1****G*20*LB~
    MAN*CP*854545488888~
    MAN*GM*081034001000008818~
    HL*6*5*I~
    LIN*1*VN*J07874*IN*J07874*UP*123456789012~
    SN1**1*EA~
    PID*F****BLOUSE~
    PID*F*35***Red~
    PID*F*SIZ***Large~
    HL*7*5*I~
    LIN*2*VN*J-10-1011*IN*J-10-1011*UP*129876543210~
    SN1**1*CA~
    PID*F*08***Large Pack of Chocolate~
    HL*8*5*I~
    LIN*3*VN*LO78787*IN*LO78787*UP*9801234567890~
    SN1**200*EA~
    PID*F*08***Green Mustard~
    PID*F*35***Red~
    PID*F*SIZ***Large~
    CTT*11*513~
    SE*47*071120008~
    GE*1*071120007~
    IEA*1*071120006~

    856 Sample (with Pallet)

    ISA*00* *00* *ZZ*EDI *ZZ*LBEDI2 *160711*2048*U*00401*071120006*0*P*>~
    GS*SH*EDI*LBEDI2*20160711*2048*071120007*X*004010~
    ST*856*071120008~
    BSN*00*1599999999*20160711*16485319*0001~
    HL*1**S~
    TD5*B*2*UNSP**UPS Ground*******CG~
    REF*BM*BOL987456~
    REF*CN*PRO987456~
    DTM*011*20161112~
    DTM*067*20161115~
    N1*SF*Test Company Address~
    N3*Street 123*Street 321~
    N4*Shelton*CT*06484*USA~
    HL*2*1*O~
    PRF*15999999878~
    HL*3*2*T~
    TD1*PLT*1****G*400*LB*1000*IN~
    REF*ZH*1Z324323~
    MAN*GM*181034001000008808~
    HL*4*3*P~
    PO4**********4*3*2*IN~
    TD1*CTN*1****G*20*LB~
    MAN*CP*564564654654~
    MAN*GM*081034001000008795~
    HL*5*4*I~
    LIN*3*VN*49-98760*IN*J07874*UP*123456789012~
    SN1**298*EA~
    PID*F*08***Green Mustard~
    PID*F*35***Red~
    PID*F*SIZ***Large~
    HL*6*3*P~
    PO4**********4*3*2*IN~
    TD1*CTN*1****G*20*LB~
    MAN*CP*854545488888~
    MAN*GM*081034001000008818~
    HL*9*6*I~
    LIN*1*VN*J07874*IN*J07874*UP*123456789012~
    SN1**1*EA~
    PID*F****BLOUSE~
    PID*F*35***Red~
    PID*F*SIZ***Large~
    HL*10*6*I~
    LIN*2*VN*J-10-1011*IN*J-10-1011*UP*129876543210~
    SN1**1*CA~
    PID*F*08***Large Pack of Chocolate~
    HL*11*6*I~
    LIN*3*VN*LO78787*IN*LO78787*UP*9801234567890~
    SN1**200*EA~
    PID*F*08***Green Mustard~
    PID*F*35***Red~
    PID*F*SIZ***Large~
    CTT*11*513~
    SE*51*071120008~
    GE*1*071120007~
    IEA*1*071120006~

    Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page 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. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.