Nordstrom
/
Ship Notice/Manifest
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Nordstrom. Contact Nordstrom for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Nordstrom 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
    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
    TD1
    110
    Carrier Details (Quantity and Weight)
    Max use 20
    Required
    TD5
    120
    Carrier Details (Routing Sequence/Transit Time)
    Max use 12
    Required
    REF
    150
    Reference Identification
    Max use 1
    Required
    PER
    151
    Administrative Communications Contact
    Max use 3
    Optional
    DTM
    200
    Date/Time Reference
    Max use 10
    Required
    N1 Loop Consolidator
    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
    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
    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
    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
    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
    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
    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
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    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
    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
    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
    Min 2Max 15

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

    GS-03
    124
    Application Receiver's Code
    Required
    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
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    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

    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
    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

    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

    Code identifying purpose of transaction set

    00
    Original
    BSN-02
    396
    Shipment Identification
    Required
    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
    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)

    • 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

    Pick and Pack Structure

    Detail

    HL Loop
    RequiredMax >1
    HL
    010

    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
    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.
    TD1
    110

    Carrier Details (Quantity and Weight)

    RequiredMax use 20

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

    Example
    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

    Usage notes

    Note: 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.
    Nordstrom is only concerned with Part 1 codes. Any legal code or spaces
    can be used for Part 2.

    CTN
    Carton
    CTN25
    Carton 25
    HRB
    On Hanger or Rack in Boxes

    Code used for GOH. HRB code is used ONLY when goods are shipped as a hanging packaging type. Use CTN code when goods are shipped on a hanger within a carton.

    TD1-02
    80
    Lading Quantity
    Required
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    Usage notes

    The number of packages in the shipment as described in TD101

    TD1-06
    187
    Weight Qualifier
    Required

    Code defining the type of weight

    G
    Gross Weight
    TD1-07
    81
    Weight
    Required
    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
    TD5
    120

    Carrier Details (Routing Sequence/Transit Time)

    RequiredMax use 12

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

    Example
    TD5-01
    133
    Routing Sequence Code
    Optional

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

    1
    1st Carrier after Origin Carrier
    2
    2nd Carrier after Origin Carrier
    3
    3rd Carrier after Origin Carrier
    4
    4th Carrier after Origin Carrier
    5
    5th Carrier after Origin Carrier
    6
    6th Carrier after Origin Carrier
    7
    7th Carrier after Origin Carrier
    8
    8th Carrier after Origin Carrier
    9
    9th Carrier after Origin Carrier
    A
    Origin Carrier, Agent's Routing (Rail)
    B
    Origin/Delivery Carrier (Any Mode)
    O
    Origin Carrier (Air, Motor, or Ocean)
    S
    Origin Carrier, Shipper's Routing (Rail)
    TD5-02
    66
    Identification Code Qualifier
    Required

    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
    Required
    Min 2Max 80

    Code identifying a party or other code

    TD5-04
    91
    Transportation Method/Type Code
    Optional

    Code specifying the method or type of transportation for the shipment

    A
    Air
    AE
    Air Express
    C
    Consolidation
    D
    Parcel Post
    E
    Expedited Truck
    H
    Customer Pickup
    L
    Contract Carrier
    M
    Motor (Common Carrier)
    R
    Rail
    S
    Ocean
    T
    Best Way (Shippers Option)
    U
    Private Parcel Service
    TD5-06
    368
    Shipment/Order Status Code
    Optional

    Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction

    BK
    Back Ordered from Previous Order
    BP
    Shipment Partial, Back Order to Ship on (Date)
    CC
    Shipment Complete on (Date)
    CM
    Shipment Complete with Additional Quantity
    CP
    Partial Shipment on (Date), Considered No Backorder
    CS
    Shipment Complete with Substitution
    DE
    Deleted Order
    IC
    Item Canceled
    IS
    Item Represents Substitution from Original Order
    PR
    Partial Shipment
    SS
    Split Shipment
    TD5-12
    284
    Service Level Code
    Optional

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

    DS
    Door Service
    ND
    Next Day Air
    PB
    Priority Mail
    PI
    Priority Mail Insured
    SC
    Second Day Air
    REF
    150

    Reference Identification

    RequiredMax use >1

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    BM
    Bill of Lading Number
    CN
    Carrier's Reference Number (PRO/Invoice)
    IA
    Internal Vendor Number
    MB
    Master Bill of Lading

    NOTE: Special characters such as dashes cannot be used in the BOL number. refer to the GS1 website (www.gs1us.org) for the complete GS1 US Bill of Lading Guidelines.

    REF-02
    127
    Reference Identification
    Required
    Min 1Max 30

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

    PER
    151

    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
    PER-01
    366
    Contact Function Code
    Optional

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

    DI
    Delivery Instructions Contact
    PER-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    TE
    Telephone
    PER-04
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable

    DTM
    200

    Date/Time Reference

    RequiredMax use 10

    To specify pertinent dates and times

    Example
    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
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    DTM-03
    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)

    N1 N1 Loop Consolidator
    OptionalMax >1
    Variants (all may be used)
    N1N1 Loop Ship FromN1N1 Loop Ship To
    N1
    220

    Name

    RequiredMax use 1

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

    Usage notes

    Note: Element is used to provide Consolidator SCAC in the CS (Consolidator) loop – 4/4 AN.

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    CS
    Consolidator
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N3
    240

    Address Information

    OptionalMax use 2

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 55

    Address information

    N4
    250

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Optional
    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
    Optional
    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
    Optional
    Min 3Max 15

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

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    N1 N1 Loop Ship From
    OptionalMax >1
    Variants (all may be used)
    N1N1 Loop ConsolidatorN1N1 Loop Ship To
    N1
    220

    Name

    RequiredMax use 1

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

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    SF
    Ship From
    N1-03
    66
    Identification Code Qualifier
    Required

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

    92
    Assigned by Buyer or Buyer's Agent
    N1-04
    67
    Identification Code
    Required
    Min 4Max 4

    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.
    Usage notes

    Element is used to provide the 4 digit Nordstrom Ship To location in the ST (Ship To) loop – Nordstrom ship to locations are 4 digits with leading 0’s (4/4 N0).

    N3
    240

    Address Information

    OptionalMax use 2

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 55

    Address information

    N4
    250

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Optional
    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
    Optional
    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
    Optional
    Min 3Max 15

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

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    N1 N1 Loop Ship To
    RequiredMax >1
    N1
    220

    Name

    RequiredMax use 1

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

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    ST
    Ship To
    N1-03
    66
    Identification Code Qualifier
    Required

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

    92
    Assigned by Buyer or Buyer's Agent
    N1-04
    67
    Identification Code
    Required
    Min 4Max 4

    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.
    Usage notes

    Element is used to provide the 4 digit Nordstrom Ship To location in the ST (Ship To) loop – Nordstrom ship to locations are 4 digits with leading 0’s (4/4 N0).

    N3
    240

    Address Information

    OptionalMax use 2

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 55

    Address information

    N4
    250

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Optional
    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
    Optional
    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
    Optional
    Min 3Max 15

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

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    HL Loop
    RequiredMax >1
    HL
    010

    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
    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
    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.
    1
    Additional Subordinate HL Data Segment in This Hierarchical Structure.
    PRF
    050

    Purchase Order Reference

    RequiredMax use 1

    To provide reference to a specific purchase order

    Example
    PRF-01
    324
    Purchase Order Number
    Required
    Min 8Max 8

    Identifying number for Purchase Order assigned by the orderer/purchaser

    Usage notes

    Note: Nordstrom's original 8 digit purchase order number. Please do not include dashes or any other special characters.

    PRF-04
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • PRF04 is the date assigned by the purchaser to purchase order.
    TD1
    110

    Carrier Details (Quantity and Weight)

    RequiredMax use 20

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

    Example
    If either Weight (TD1-07) or Unit or Basis for Measurement Code (TD1-08) is present, then the other 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

    Usage notes

    Note: 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.
    Nordstrom is only concerned with Part 1 codes. Any legal code or spaces
    can be used for Part 2.

    CTN
    Carton
    CTN25
    Carton 25
    HRB
    On Hanger or Rack in Boxes

    Code used for GOH. HRB code is used ONLY when goods are shipped as a hanging packaging type. Use CTN code when goods are shipped on a hanger within a carton.

    TD1-02
    80
    Lading Quantity
    Required
    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
    Required
    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
    REF
    150

    Reference Identification

    RequiredMax use >1

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    DP
    Department Number
    REF-02
    127
    Reference Identification
    Required
    Min 4Max 4

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

    Usage notes

    Note: Nordstrom's 4 digit department number. Nordstrom department numbers should be 4 digits with leading 0’s. For example, department 28 would be sent as 0028.

    N1 N1 Loop Buying Party
    RequiredMax >1
    N1
    220

    Name

    RequiredMax use 1

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

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    BY
    Buying Party (Purchaser)
    N1-03
    66
    Identification Code Qualifier
    Optional
    Min 1Max 2

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

    N1-04
    67
    Identification Code
    Required
    Min 4Max 4

    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.
    Usage notes

    Note: This is the mark-for location. Nordstrom's 4 digit store number. Nordstrom store numbers should be 4 digits with leading 0’s. For example, store 1 would be sent as 0001.

    HL Loop
    RequiredMax >1
    HL
    010

    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
    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
    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.
    MAN
    190

    Marks and Numbers

    RequiredMax use >1

    To indicate identifying marks and numbers for shipping containers

    Usage notes

    If the MAN segment is present, the LIN segment is required. If the LIN segment is present, the SN1 segment is required.

    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

    This is a twenty-character GS1-128 Serial Shipping Container Code (SSCC-18) that includes the two digit application identifier. The symbology code and the modulo 103 check digit are not included.
    The GS1-128 Serial Shipping Container Code (SSCC-18) must be a unique number and cannot be duplicated.

    MAN-02
    87
    Marks and Numbers
    Required
    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

    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
    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
    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

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

    Example
    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.
    EN
    European Article Number (EAN) (2-5-5-1)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    Note: 12 digit UPC or 13 digit EAN

    SN1
    030

    Item Detail (Shipment)

    RequiredMax use 1

    To specify line-item detail relative to shipment

    Usage notes

    This segment is used to specify the quantities associated with the item identified in the LIN at the item level.

    If the MAN segment is present, the LIN segment is required. If the LIN segment is present, the SN1 segment is required.

    Case Pack UPC’s – Please note that if Nordstrom sends your company a case pack UPC (unit of measure of ‘CA’ in PO103), we require the 856 back at the individual component level (an individual UPC for each item).

    Example
    SN1-02
    382
    Number of Units Shipped
    Required
    Min 1Max 10

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

    Usage notes

    Note: A numerical value greater than 0 is required. Do not send 0 or negative quantities.

    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.
    EA
    Each

    Summary

    CTT
    010

    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
    Min 1Max 6

    Total number of line items in the transaction set

    SE
    020

    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
    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
    Min 4Max 9

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

    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
    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
    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
    Min 1Max 5

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

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Consolidated ASN example

    ISA*00* *00* *12*999999999 *12*2062336664 *100401*2039*U*00401*000000180*0*P*>~
    GS*SH*999999999*2062336664*20100401*2039*180*X*004010VICS~
    ST*856*0001~
    BSN*00*040120102036*20100401*2036*0001~
    HL*1**S~
    TD1*CTN*21****G*105.00*LB~
    TD5**2*CAIE*M~
    REF*BM*CTEP7590662356124~
    REF*CN*CTEP7590662356124~
    REF*MB*CTEP7590662356124~
    PER*DI*ANN SMITH*TE*2062335525~
    DTM*011*20100405~
    N1*ST**92*0089~
    N1*SF**92*1234~
    N3*444 MAIN DRIVE~
    N4*FREMONT*CA*11111~
    HL*2*1*O~
    PRF*11133333***20100330~
    TD1*CTN*6****G*30*LB~
    REF*DP*0276~
    N1*BY**92*0002~
    HL*3*2*P~
    MAN*GM*00089175300100067087~
    HL*4*3*I~
    LIN**UP*891111111111~
    SN1**1*EA~
    HL*5*2*P~
    MAN*GM*00089175300100067094~
    HL*6*5*I~
    LIN**UP*891111111112~
    SN1**1*EA~
    HL*7*2*P~
    MAN*GM*00089175300100067100~
    HL*8*7*I~
    LIN**UP*891111111113~
    SN1**1*EA~
    HL*9*2*P~
    MAN*GM*00089175300100067117~
    HL*10*9*I~
    LIN**UP*891111111114~
    SN1**1*EA~
    HL*11*2*P~
    MAN*GM*00089175300100067124~
    HL*12*11*I~
    LIN**UP*891111111115~
    SN1**1*EA~
    HL*13*2*P~
    MAN*GM*00089175300100067131~
    HL*14*13*I~
    LIN**UP*891111111116~
    SN1**1*EA~
    HL*15*1*O~
    PRF*13621032***20100330~
    TD1*CTN*9****G*45*LB~
    REF*DP*0276~
    N1*BY**92*0005~
    HL*16*15*P~
    MAN*GM*00089175300100067148~
    HL*17*16*I~
    LIN**UP*891111111111~
    SN1**1*EA~
    HL*18*15*P~
    MAN*GM*00089175300100067155~
    HL*19*18*I~
    LIN**UP*891111111112~
    SN1**1*EA~
    HL*20*15*P~
    MAN*GM*00089175300100067162~
    HL*21*20*I~
    LIN**UP*891111111113~
    SN1**1*EA~
    HL*22*15*P~
    MAN*GM*00089175300100067179~
    HL*23*22*I~
    LIN**UP*891111111114~
    SN1**1*EA~
    HL*24*15*P~
    MAN*GM*00089175300100067186~
    HL*25*24*I~
    LIN**UP*891111111115~
    SN1**1*EA~
    HL*26*15*P~
    MAN*GM*00089175300100067193~
    HL*27*26*I~
    LIN**UP*891111111116~
    SN1**1*EA~
    HL*28*15*P~
    MAN*GM*00089175300100067209~
    HL*29*28*I~
    LIN**UP*891111111117~
    SN1**1*EA~
    HL*30*15*P~
    MAN*GM*00089175300100067216~
    HL*31*30*I~
    LIN**UP*891111111118~
    SN1**1*EA~
    HL*32*15*P~
    MAN*GM*00089175300100067223~
    HL*33*32*I~
    LIN**UP*891111111119~
    SN1**1*EA~
    HL*34*1*O~
    PRF*13621032***20100330~
    TD1*CTN*6****G*30*LB~
    REF*DP*0276~
    N1*BY**92*0024~
    HL*35*34*P~
    MAN*GM*00089175300100067230~
    HL*36*35*I~
    LIN**UP*891111111111~
    SN1**1*EA~
    HL*37*34*P~
    MAN*GM*00089175300100067247~
    HL*38*37*I~
    LIN**UP*891111111112~
    SN1**1*EA~
    HL*39*34*P~
    MAN*GM*00089175300100067254~
    HL*40*39*I~
    LIN**UP*891111111113~
    SN1**1*EA~
    HL*41*34*P~
    MAN*GM*00089175300100067261~
    HL*42*41*I~
    LIN**UP*891111111114~
    SN1**1*EA~
    HL*43*34*P~
    MAN*GM*00089175300100067278~
    HL*44*43*I~
    LIN**UP*891111111115~
    SN1**1*EA~
    HL*45*34*P~
    MAN*GM*00089175300100067285~
    HL*46*45*I~
    LIN**UP*891111111116~
    SN1**1*EA~
    CTT*46~
    SE*135*0001~
    GE*1*180~
    IEA*1*000000180~

    Small package ASN example

    ISA*00* *00* *12*9999999999 *12*2062336664 *100402*0110*U*00401*100004475*0*P*>~
    GS*SH*999999999999*2062336664*20100402*0110*200004475*X*004010VICS~
    ST*856*300032643~
    BSN*00*P286113*20100402*0110*0001~
    HL*1**S~
    TD1*CTN25*1****G*1*LB~
    TD5**2*UPSN~
    REF*BM*1Z3909820314009185~
    REF*CN*1Z3909820314009185~
    REF*MB*1Z3909820314009185~
    PER*DI*ANN SMITH*TE*2062335525~
    DTM*011*20100402~
    N1*SF**92*1234~
    N3*1234 MAIN ST.~
    N4*SEATTLE*WA*98111~
    N1*ST**92*0399~
    HL*2*1*O~
    PRF*13222222***20100331~
    TD1*CTN25*1****G*1*LB~
    REF*DP*0180~
    N1*BY**92*0342~
    HL*3*2*P~
    MAN*GM*00007471220030172642~
    HL*4*3*I~
    LIN**EN*1233333333333~
    SN1**1*EA~
    CTT*4~
    SE*25*300032643~
    ST*856*300032644~
    BSN*00*P286116*20100402*0110*0001~
    HL*1**S~
    TD1*CTN25*1****G*7*LB~
    TD5**2*UPSN~
    REF*BM*1Z3909820314009247~
    REF*CN*1Z3909820314009247~
    REF*MB*1Z3909820314009247~
    PER*DI*ANN SMITH*TE*2062335525~
    DTM*011*20100402~
    N1*SF**92*1234~
    N3*1234 MAIN ST.~
    N4*SEATTLE*WA*98111~
    N1*ST**92*0399~
    HL*2*1*O~
    PRF*13222222***20100331~
    TD1*CTN25*1****G*7*LB~
    REF*DP*0180~
    N1*BY**92*0323~
    HL*3*2*P~
    MAN*GM*00007471220030172659~
    HL*4*3*I~
    LIN**EN*4022222222222~
    SN1**2*EA~
    CTT*4~
    SE*25*300032644~
    GE*1*200004475~
    IEA*1*100004475~

    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.