Overstock
/
Ship Notice/Manifest
  • Specification
  • EDI Inspector
Import
Stedi maintains this guide based on public documentation from Overstock. Contact Overstock for official EDI specifications. To report any errors in this guide, please contact us.
Go to EDI Guide Catalog
Overstock 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 free 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
    Warehouse
    Max use 1
    Required
    REF
    150
    Retailer Name
    Max use 1
    Required
    REF
    150
    Invoice
    Max use 1
    Optional
    DTM
    200
    Date/Time Reference
    Max use 10
    Required
    SAC Loop
    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

    Usage notes

    Packing slip number assigned by original shipper

    BSN-03
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BSN03 is the date the shipment transaction set is created.
    Usage notes

    Date this shipment transaction set was 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

    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
    Optional

    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
    PKG
    Package
    TD1-02
    80
    Lading Quantity
    Required
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    Usage notes

    Number of units

    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
    Required

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

    O
    Origin Carrier (Air, Motor, or Ocean)
    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
    Service Level Code
    Required

    Code identifying a party or other code

    Usage notes

    Service Level Code

    CURB
    LTL shipping, curbside
    DOCK
    LTL Shipping B2B, dock to dock
    DOCK_TO_DOCK
    LTL Shipping B2B, dock to dock
    FIRSTCLASS
    First class mail
    FIRST_CLASS_MAIL
    First class mail
    FRDRPLUS
    Outside Home with Signature
    FRNTDOOR
    Outside Home
    GROUND
    Shipping by Ground
    GROUND_PARCEL
    Standard post ground parcel
    GROUND_PARCEL_SELECT
    Ground parcel select
    INHOME
    In Home
    LIGHTWEIGHT_LB_GROUND
    Light weight pound ground day shipping
    LIGHTWEIGHT_LB_NEXT_DAY
    Light weight pound one day shipping
    LIGHTWEIGHT_LB_THREE_DAY
    Light weight pound three day shipping
    LIGHTWEIGHT_LB_TWO_DAY
    Light weight pound two day shipping
    LIGHTWEIGHT_OZ_GROUND
    Light weight ounce ground day shipping
    LIGHTWEIGHT_OZ_NEXT_DAY
    Light weight ounce one day shipping
    LIGHTWEIGHT_OZ_THREE_DAY
    Light weight ounce three day shipping
    LIGHTWEIGHT_OZ_TWO_DAY
    Light weight ounce two day shipping
    MEDIA_MAIL
    Media mail
    NEXT_DAY
    One day shipping
    PARCEL
    Standard post ground parcel
    PARCEL_SEL
    Ground parcel select
    PRIORITY
    Priority mail
    PRIORITY_MAIL
    Priority mail
    RMCHOICE
    Room of Choice
    RMDEBRIS
    Room of choice with debris removed and light assembly under 30 minutes (no tools)
    THREE_DAY
    Three day shipping
    THRESHOLD
    Outside Home
    TWO_DAY
    Two day shipping
    WHITE_GLOVE
    LTL Shipping with White Glove installation
    TD5-06
    368
    Shipment/Order Status Code
    Required

    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

    CC
    Shipment Complete on (Date)
    TD5-08
    310
    Transportation Method/Type Code
    Required
    Min 1Max 30

    Code which identifies a specific location

    Usage notes

    Transportation Method/Type Code

    Supplier Oasis Shipping Codes (TD508 Element must contain the carrier code)

    *Please go to the Supplier Oasis UI to retrieve the most current list of Accepted Carrier Codes. Found under Tools > Template Documentation > Import > Ship Orders.

    REF
    150

    Warehouse

    RequiredMax use >1

    To specify identifying information

    Example
    Variants (all may be used)
    REFRetailer NameREFInvoice
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    WH
    Master Reference (Link) Number
    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

    Usage notes

    Warehouse Name

    REF
    150

    Retailer Name

    RequiredMax use >1

    To specify identifying information

    Example
    Variants (all may be used)
    REFWarehouseREFInvoice
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    RN
    Retailer Name
    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

    Usage notes

    Retailer Name

    REF
    150

    Invoice

    OptionalMax use >1

    To specify identifying information

    Example
    Variants (all may be used)
    REFWarehouseREFRetailer Name
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    IV
    Seller's Invoice Number
    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

    Usage notes

    Invoice Number (Suppliers internal Invoice number)

    DTM
    200

    Date/Time Reference

    RequiredMax use 10

    To specify pertinent dates and times

    Example
    If Time Code (DTM-04) is present, then Time (DTM-03) is required
    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)

    DTM-04
    623
    Time Code
    Optional

    Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow

    Usage notes

    Standard time:
    CT=America/Chicago
    ET=America/New_York,
    MT=America/Denver,
    PT=America/Los_Angeles,

    Daylight saving:
    CD=America/Chicago
    ED=America/New_York
    MD=America/Denver
    PD=America/Los_Angeles

    CD
    Central Daylight Time
    CT
    Central Time
    ED
    Eastern Daylight Time
    ET
    Eastern Time
    MD
    Mountain Daylight Time
    MT
    Mountain Time
    PD
    Pacific Daylight Time
    PT
    Pacific Time
    N1 Ship To
    RequiredMax >1
    Variants (all may be used)
    N1Ship From
    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-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    Usage notes

    Customer’s Name

    N3
    240

    Address Information

    RequiredMax use 2

    To specify the location of the named party

    Usage notes

    Customer’s Address Information

    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

    RequiredMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Required
    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

    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.
    AB
    Alberta
    AK
    Alaska
    AL
    Alabama
    AR
    Arkansas
    AZ
    Arizona
    BC
    British Columbia
    CA
    California
    CO
    Colorado
    CT
    Connecticut
    DC
    District of Columbia
    DE
    Delaware
    FL
    Florida
    GA
    Georgia
    HI
    Hawaii
    IA
    Iowa
    ID
    Idaho
    IL
    Illinois
    IN
    Indiana
    KS
    Kansas
    KY
    Kentucky
    LA
    Louisiana
    MA
    Massachusetts
    MB
    Manitoba
    MD
    Maryland
    ME
    Maine
    MI
    Michigan
    MN
    Minnesota
    MO
    Missouri
    MS
    Mississippi
    MT
    Montana
    NB
    New Brunswick
    NC
    North Carolina
    ND
    North Dakota
    NE
    Nebraska
    NH
    New Hampshire
    NJ
    New Jersey
    NL
    Newfoundland and Labrador
    NM
    New Mexico
    NS
    Nova Scotia
    NT
    Northwest Territories
    NU
    Nunavut
    NV
    Nevada
    NY
    New York
    OH
    Ohio
    OK
    Oklahoma
    ON
    Ontario
    OR
    Oregon
    PA
    Pennsylvania
    PE
    Prince Edward Island
    QC
    Quebec
    RI
    Rhode Island
    SC
    South Carolina
    SD
    South Dakota
    SK
    Saskatchewan
    TN
    Tennessee
    TX
    Texas
    UT
    Utah
    VA
    Virginia
    VT
    Vermont
    WA
    Washington
    WI
    Wisconsin
    WV
    West Virginia
    WY
    Wyoming
    YT
    Yukon
    N4-03
    116
    Postal Code
    Required
    Min 3Max 15

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

    Usage notes

    Zip Code for addresses in the US.
    Postal Code for addresses outside the US.

    N4-04
    26
    Country Code
    Required
    Min 2Max 3

    Code identifying the country

    Usage notes

    ISO Country Codes

    N1 Ship From
    RequiredMax >1
    Variants (all may be used)
    N1Ship To
    N1
    220

    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
    Required
    Min 1Max 60

    Free-form name

    Usage notes

    Customer’s Name

    N1-03
    66
    Identification Code Qualifier
    Optional

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

    91
    Assigned by Seller or Seller's Agent
    N1-04
    67
    Identification Code
    Optional
    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

    Address Information

    OptionalMax use 2

    To specify the location of the named party

    Usage notes

    Customer’s Address Information

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

    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.
    AB
    Alberta
    AK
    Alaska
    AL
    Alabama
    AR
    Arkansas
    AZ
    Arizona
    BC
    British Columbia
    CA
    California
    CO
    Colorado
    CT
    Connecticut
    DC
    District of Columbia
    DE
    Delaware
    FL
    Florida
    GA
    Georgia
    HI
    Hawaii
    IA
    Iowa
    ID
    Idaho
    IL
    Illinois
    IN
    Indiana
    KS
    Kansas
    KY
    Kentucky
    LA
    Louisiana
    MA
    Massachusetts
    MB
    Manitoba
    MD
    Maryland
    ME
    Maine
    MI
    Michigan
    MN
    Minnesota
    MO
    Missouri
    MS
    Mississippi
    MT
    Montana
    NB
    New Brunswick
    NC
    North Carolina
    ND
    North Dakota
    NE
    Nebraska
    NH
    New Hampshire
    NJ
    New Jersey
    NL
    Newfoundland and Labrador
    NM
    New Mexico
    NS
    Nova Scotia
    NT
    Northwest Territories
    NU
    Nunavut
    NV
    Nevada
    NY
    New York
    OH
    Ohio
    OK
    Oklahoma
    ON
    Ontario
    OR
    Oregon
    PA
    Pennsylvania
    PE
    Prince Edward Island
    QC
    Quebec
    RI
    Rhode Island
    SC
    South Carolina
    SD
    South Dakota
    SK
    Saskatchewan
    TN
    Tennessee
    TX
    Texas
    UT
    Utah
    VA
    Virginia
    VT
    Vermont
    WA
    Washington
    WI
    Wisconsin
    WV
    West Virginia
    WY
    Wyoming
    YT
    Yukon
    N4-03
    116
    Postal Code
    Required
    Min 3Max 15

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

    Usage notes

    Zip Code for addresses in the US.
    Postal Code for addresses outside the US.

    N4-04
    26
    Country Code
    Required
    Min 2Max 3

    Code identifying the country

    Usage notes

    ISO Country Codes

    SAC Loop
    OptionalMax >1
    SAC
    320

    Service, Promotion, Allowance, or Charge Information

    RequiredMax use 1

    To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge

    Example
    SAC-01
    248
    Allowance or Charge Indicator
    Required

    Code which indicates an allowance or charge for the service specified

    • If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
    C
    Charge
    SAC-02
    1300
    Service, Promotion, Allowance, or Charge Code
    Required

    Code identifying the service, promotion, allowance, or charge

    D240
    Freight
    SAC-05
    610
    Amount
    Required
    Min 1Max 15

    Monetary amount

    • SAC05 is the total amount for the service, promotion, allowance, or charge.
    • If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
    Usage notes

    Implied Decimal point two position, for example $8.29 would be transmitted as 829. $0.00 would be transmitted as 000

    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 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    Usage notes

    Supplier Oasis Order Number

    PRF-02
    328
    Release Number
    Required
    Min 1Max 30

    Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction

    Usage notes

    Retailer Order Number

    PRF-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • PRF04 is the date assigned by the purchaser to purchase order.
    PRF-07
    92
    Purchase Order Type Code
    Optional

    Code specifying the type of Purchase Order

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

    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.
    CP
    Carrier-Assigned Package ID Number
    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.
    Usage notes

    Tracking Number

    Arkansas-Best Freight / ABF:

    • Must consist of '9' characters

    Airborne / ARBN

    • Begin with '8', must consist of '10' or '11' characters

    United Parcel Services / UPS

    • Begin with '1Z' or '1z', must consist of '18 to 24' characters OR
    • Begin with ‘1’, must consist of 10 characters OR
    • Begin with '9', must consist of 11 to 13 characters OR
    • Begin with Alpha character, must consist of 11 to 13 characters
    • Do not include dashes '-'

    United States Postal Service / USPS

    • Begin with '42', must consist of 30 characters OR
    • Begin with '9', must consist of 20 to 27 characters OR
    • Begin with '0', must consist of 20 to 24 characters OR
    • Any combination of #'s, spaces, must consist 9 to 11 digits in length
    • Begin with ‘E’, must consist of 13 characters

    Federal Express / FEDEX

    • Must consist of 9, 12, 15 or 22 characters
    • Should not start with an alpha character
    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
    If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required
    LIN-01
    350
    Assigned Identification
    Required
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • LIN01 is the line item identification
    Usage notes

    Supplier Oasis Order Line Number

    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.
    SK
    Stock Keeping Unit (SKU)
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    Supplier SKU Number

    LIN-04
    235
    Product/Service ID Qualifier
    Optional

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

    BP
    Buyer's Part Number
    LIN-05
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    Supplier Oasis SKU Number

    SN1
    030

    Item Detail (Shipment)

    RequiredMax use 1

    To specify line-item detail relative to shipment

    Example
    If either Quantity Ordered (SN1-05) or Unit or Basis for Measurement Code (SN1-06) is present, then the other is required
    SN1-01
    350
    Assigned Identification
    Optional
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • SN101 is the ship notice line-item identification.
    Usage notes

    Shipment notice or packing slip number

    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

    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
    SN1-05
    330
    Quantity Ordered
    Optional
    Min 1Max 15

    Quantity ordered

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

    EA
    Each
    SN1-08
    668
    Line Item Status Code
    Required

    Code specifying the action taken by the seller on a line item requested by the buyer

    AC
    Item Accepted and Shipped

    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

    Usage notes

    Number of line item segments in ST/SE block

    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

    Multiple Pack, Multiple Items

    ST*856*000002445~
    BSN*00*123456*20160606*13574122*0001~
    HL*1**S~
    TD1*CTN*1****G*30*LB~
    TD5*O*2*GROUND***CC**UPS~
    REF*WH*WarehouseName~
    REF*RN*OSTK~
    DTM*011*20160506~
    N1*SF*Shipper Name*91*12345~
    N1*ST*Customer Contact~
    N3*555 Name Rd~
    N4*Salt Lake City*UT*84111*US~
    HL*2*1*O~
    PRF*12346578-1*234567890**20160501~
    HL*3*2*P~
    MAN*CP*123456789012345~
    HL*4*3*I~
    LIN*1*SK*OS5200GP*BP*12345678-000-000~
    SN1**1*EA*****AC~
    HL*5*2*P~
    MAN*CP*234567890123456~
    HL*6*5*I~
    LIN*2*SK*OS7101GP*BP*23456789-000-000~
    SN1**1*EA*****AC~
    HL*7*2*P~
    MAN*CP*345678901234567~
    HL*8*7*I~
    LIN*3*SK*OS8102GP*BP*34567890-000-000~
    SN1**1*EA*****AC~
    CTT*12~
    SE*17*000002445~

    Overstock Fulfillment Ship Confirmations (Overstock to Supplier)

    ST*856*048690145~
    BSN*00*41295960*20190207*1338*0001~
    HL*000000000001*000000000000*S~
    TD1**1****G*1.25*LB~
    TD5*O*2*GROUND***CC**UPS~
    REF*WH*castle~
    REF*RN*OSTK~
    DTM*011*20190207~
    N1*SF*castle*91*21~
    N1*ST*Customer Name~
    N3*1234 Anywhere St~
    N4*Ellensburg*WA*98926*US~
    HL*000000000002*000000000001*O~
    PRF*12345678-1*234567890**20190207***DS~
    HL*000000000003*000000000002*P~
    MAN*CP*1Z2870WV0300077099~
    HL*000000000004*000000000003*I~
    LIN*1*SK*9098 Cream 8x10*BP*18924477-000-000~
    SN1**1*EA*****AC~
    CTT*1~
    SE*21*048690145~

    Single Pack, Multiple Items

    ST*856*000002445~
    BSN*00*123456*20160606*13574122*0001~
    HL*1**S~
    TD1*CTN*1****G*30*LB~
    TD5*O*2*GROUND***CC**UPS~
    REF*WH*WarehouseName~
    REF*RN*OSTK~
    DTM*011*20160506~
    N1*SF*Shipper Name*91*12345~
    N1*ST*Customer Contact~
    N3*555 Name Rd~
    N4*Salt Lake City*UT*84111*US~
    HL*2*1*O~
    PRF*12346578-1*234567890**20160501~
    HL*3*2*P~
    MAN*CP*123456789012345~
    HL*4*3*I~
    LIN*1*SK*OS5200GP*BP*12345678-000-000~
    SN1**1*EA*****AC~
    HL*5*3*I~
    LIN*2*SK*OS7101GP*BP*23456789-000-000~
    SN1**1*EA*****AC~
    HL*6*3*I~
    LIN*3*SK*OS8102GP*BP*34567890-000-000~
    SN1**1*EA*****AC~
    CTT*12~
    SE*17*000002445~

    Single Pack, Single Item, Single Quantity

    ST*856*1234~
    BSN*00*12345*20160121*104010*0001~
    HL*1**S~
    TD1**1****G*5*LB~
    TD5*O*2*TWO_DAY***CC**FEDEX~
    REF*WH*WarehouseName~
    REF*RN*OSTK~
    DTM*011*20160121~
    N1*SF*WarehouseName*91*83772~
    N1*ST*Joe Customer~
    N3*1234 Anywhere St~
    N4*Bloomington*IL*61701*US~
    HL*2*1*O~
    PRF*12345678-1*234567890**20160121~
    HL*3*2*P~
    MAN*CP*123465789012345~
    HL*4*3*I~
    LIN*1*SK*WF-MNT-1050*BP*345678901-000-000~
    SN1**1*EA*****AC~
    CTT*1~
    SE*8*000001081~

    Single Pack, Single Line, Multiple Quantities, Different tracking numbers

    ST*856*000002445~
    BSN*00*123456*20160606*13574122*0001~
    HL*1**S~
    TD1*CTN*1****G*30*LB~
    TD5*O*2*GROUND***CC**UPS~
    REF*WH*WarehouseName~
    REF*RN*OSTK~
    DTM*011*20160506~
    N1*SF*Shipper Name*91*12345~
    N1*ST*Customer Contact~
    N3*555 Name Rd~
    N4*Salt Lake City*UT*84111*US~
    HL*2*1*O~
    PRF*12346578-1*234567890**20160501~
    HL*3*2*P~
    MAN*CP*12345678901234567~
    HL*4*3*I~
    LIN*1*SK*OS5200GP*BP*12345678-000-000~
    SN1**1*EA*****AC~
    HL*5*2*P~
    MAN*CP*23456789012345678~
    HL*6*5*I~
    LIN*1*SK*OS5200GP*BP*12345678-000-000~
    SN1**1*EA*****AC~
    HL*7*2*P~
    MAN*CP*34567890123456789~
    HL*8*7*I~
    LIN*1*SK*OS5200GP*BP*12345678-000-000~
    SN1**1*EA*****AC~
    CTT*12~
    SE*17*000002445~

    Single Pack, Single Line, Single Quantity, Multi box

    ST*856*000002445~
    BSN*00*123456*20160606*13574122*0001~
    HL*1**S~
    TD1*CTN*1****G*30*LB~
    TD5*O*2*GROUND***CC**UPS~
    REF*WH*WarehouseName~
    REF*RN*OSTK~
    DTM*011*20160506~
    N1*SF*Shipper Name*91*12345~
    N1*ST*Customer Contact~
    N3*555 Name Rd~
    N4*Salt Lake City*UT*84111*US~
    HL*2*1*O~
    PRF*12346578-1*234567890**20160501~
    HL*3*2*P~
    MAN*CP*12345678901234567~
    HL*4*3*I~
    LIN*1*SK*OS5200GP*BP*12345678-000-000~
    SN1**1*EA*****AC~
    HL*5*2*P~
    MAN*CP*23456789012345678~
    HL*6*5*I~
    LIN*1*SK*OS5200GP*BP*12345678-000-000~
    SN1**0*EA*****AC~
    HL*7*2*P~
    MAN*CP*34567890123456789~
    HL*8*7*I~
    LIN*1*SK*OS5200GP*BP*12345678-000-000~
    SN1**0*EA*****AC~
    CTT*12~
    SE*17*000002445~

    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.