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

X12 856 Retail Ship Notice/Manifest

X12 Release 5010

This X12 Transaction Set 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
  • ^ Repetition
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
    0100
    Hierarchical Level
    Max use 1
    Required
    TD1
    1100
    Carrier Details (Quantity and Weight)
    Max use 20
    Required
    TD5
    1200
    Carrier Details (Routing Sequence/Transit Time)
    Max use 12
    Required
    TD3 Loop
    REF
    1500
    Bill of Lading Number
    Max use 1
    Optional
    REF
    1500
    Buyer's Shipment Mark Number
    Max use 1
    Optional
    REF
    1500
    Carrier's Tracking/Airbill Number
    Max use 1
    Optional
    REF
    1500
    Seal Number
    Max use 1
    Optional
    DTM
    2000
    Estimated Delivery
    Max use 10
    Required
    DTM
    2000
    Shipped
    Max use 10
    Required
    FOB
    2100
    F.O.B. Related Instructions
    Max use 1
    Optional
    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 identifying 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 identifying 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

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

    Code indicating 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
    I65
    Repetition Separator
    Required
    Min 1Max 1

    Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

    ^
    Repetition Separator
    ISA-12
    I11
    Interchange Control Version Number
    Required

    Code specifying the version number of the interchange control segments

    00501
    Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
    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 indicating sender's request for an interchange acknowledgment

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

    Code indicating 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 where CC represents the first two digits of the calendar year

    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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480

    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

    005010
    Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003

    Heading

    ST
    0100

    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) is 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
    0200

    Beginning Segment for Ship Notice

    RequiredMax use 1

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

    Usage notes

    Example: BSN00030514090720140101011111*0001

    Example
    BSN-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    05
    Replace
    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

    This field will be a unique ID which represents this ASN. Note that failure to use a unique ID for each shipment will result in ASN data being overwritten and chargebacks for missing ASN data. Please only use the same ASN ID and BGN01 code "05" if you would like to replace the information provided via the earlier ASN message. Please verify the business requirements document for the locale you are shipping into.

    BSN-03
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

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

    This field will list the date that the ASN information was created. The ASN creation date should be no earlier than one day before the ASN was sent or it should be the same day the ASN was sent.

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

    This field will list the time that the ASN information was created.

    The format must be reported in hours, minutes and seconds.

    Local time must be converted to either Greenwich Mean Time or Universal Time Coordinates.

    BSN-05
    1005
    Hierarchical Structure Code
    Optional

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

    0001
    Pick and Pack Structure

    Shipment, Order, Tare, Packaging,Item (Pallet)
    Shipment, Order, Packaging, Item (Carton)

    Detail

    HL Loop
    RequiredMax >1
    Usage notes

    Per ASN only one Shipment HL Loop should be sent. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Example: HL*1**S

    HL
    0100

    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
    1100

    Carrier Details (Quantity and Weight)

    RequiredMax use 20

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

    Usage notes

    Carton count is mandatory information in the ASN for all shipments. Carton count is the total number of shipping packages (not including tares/pallets) making up the shipment. The carton count needs to match the number of package loops contained in the ASN.

    Pallet count is the total number of pallets making up a shipment. This segment is required if pallets are being sent. Pallet count needs to match the number of tare/ pallet loops in the ASN.

    Examples:
    TD1CTN45*G1297.03*LB
    TD1
    CTN
    45*PLTG*1297.03LB
    TD1CTN4*FLRG*12.03LB

    TD1PLT6

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

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

    Number of units (pieces) of the lading commodity

    Usage notes

    This field will be the total number of cartons making up a shipment.

    This field can be the total number of pallets making up the shipment.

    TD1-04
    22
    Commodity Code
    Optional
    Min 1Max 30

    Code describing a commodity or group of commodities

    Usage notes

    Code describing a commodity or group of commodities.

    Not used when TD1-01 is PLT

    TD1-05
    79
    Lading Description
    Optional
    Min 1Max 50

    Description of an item as required for rating and billing purposes

    Usage notes

    All non-small parcel shipments must be palletized.

    This field is used to indicate whether a shipment is floor loaded or not. A value of FLR indicates that the shipment is floor loaded. A value of PLT indicates a shipment of pallets.

    Not used when TD1-01 is PLT

    TD1-06
    187
    Weight Qualifier
    Optional

    Code defining the type of weight

    Usage notes

    Not used when TD1-01 is PLT

    G
    Gross Weight
    TD1-07
    81
    Weight
    Optional
    Min 1Max 10

    Numeric value of weight

    Usage notes

    This field will be the gross weight of the shipment.

    Not used when TD1-01 is PLT

    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

    Usage notes

    Not used when TD1-01 is PLT

    GR
    Gram
    KG
    Kilogram
    LB
    Pound
    OZ
    Ounce - Av
    TD1-09
    183
    Volume
    Optional
    Min 1Max 8

    Value of volumetric measure

    Usage notes

    Not used when TD1-01 is PLT

    TD1-10
    355
    Unit or Basis for Measurement Code
    Optional

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

    Usage notes

    Not used when TD1-01 is PLT

    CF
    Cubic Feet
    CI
    Cubic Inches
    CR
    Cubic Meter
    CY
    Cubic Yard
    TD5
    1200

    Carrier Details (Routing Sequence/Transit Time)

    RequiredMax use 12

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

    Usage notes

    SCAC is dependent on business requirements. These might differ per region you are operating in. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Examples:
    TD52*ABFS
    TD5
    2*UPSN

    Example
    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

    Usage notes

    The Standard Carrier Alpha Code (SCAC) is a unique code used to identify the carrier. In United States it is assigned and maintained by NMFTA (National Motor Freight Association).

    Formatting: AAAA

    TD3 Loop
    OptionalMax >1
    Usage notes

    This segment is only used for import ASNs. Not used for domestic messaging.

    TD3
    1300

    Carrier Details (Equipment)

    RequiredMax use 1

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

    Usage notes

    This is only in use for import ASNs. Not for usage within domestic messaging.

    Example: TD3TL*B5834.54*KG

    Example
    If Weight Qualifier (TD3-04) is present, then Weight (TD3-05) is required
    If either Weight (TD3-05) or Unit or Basis for Measurement Code (TD3-06) is present, then the other is required
    TD3-01
    40
    Equipment Description Code
    Optional
    Min 2Max 2

    Code identifying type of equipment used for shipment

    TD3-04
    187
    Weight Qualifier
    Required

    Code defining the type of weight

    B
    Billed Weight
    TD3-05
    81
    Weight
    Optional
    Min 1Max 10

    Numeric value of weight

    TD3-06
    355
    Unit or Basis for Measurement Code
    Optional
    Min 2Max 2

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

    REF
    1500

    Bill of Lading Number

    OptionalMax use >1

    To specify identifying information

    Usage notes

    Bill of Lading is required for LTL/ TL shipments. Bill of Lading identification needs to be provided via the REF*BM segment.

    Example: REFBM600305100059

    Example
    Variants (all may be used)
    REFBuyer's Shipment Mark NumberREFCarrier's Tracking/Airbill NumberREFSeal Number
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    BM
    Bill of Lading Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 50

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

    Usage notes

    The Bill of Lading in the ASN depends on business requirements. These might differ per region you are operating in. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    REF
    1500

    Buyer's Shipment Mark Number

    OptionalMax use >1

    To specify identifying information

    Usage notes

    Amazon Reference Number in the ASN depends on business requirements. These might differ per region you are operating in. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Example: REFBX2860010031

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    BX
    Buyer's Shipment Mark Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 50

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

    Usage notes

    This field will be contain the Amazon Reference Number provided via Routing Instructions for a Collect shipment.

    This field contains the Amazon Reference Number (ARN) associated with a Routing Request. The segment is only required if the ARN was provided by Amazon via the BGN06 element in the corresponding Routing Instructions (EDI X12 754), via the Routing Request feature in Vendor Central, or via a Routing Instructions email.

    REF
    1500

    Carrier's Tracking/Airbill Number

    OptionalMax use >1

    To specify identifying information

    Usage notes

    The Shipment level REF*CN segment with Air/PRO/TrackingNumber is required for all LTL, TL, and small parcel shipments.

    For multi carton small parcel shipments (carton count > 1), a unique Air/PRO/TrackingNumber is required for each carton at the Package level.

    For single carton small parcel shipments (carton count = 1), the Air/PRO/TrackingNumber is not required at the Package level if it's present at theShipment level.

    Examples:
    REFCN009447616 (example of valid Pro Number from trucking company)
    REFCN1ZE1628E0340236740 (example of valid tracking number from small parcel carrier)

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    CN
    Carrier's Tracking/Airbill Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 50

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

    Usage notes

    The ASN PRO must be unique for a shipment and can't be repeated within the last 90 days.

    The Air/PRO/TrackingNumber in the ASN depends on business requirements. These might differ per region you are operating in. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    REF
    1500

    Seal Number

    OptionalMax use >1

    To specify identifying information

    Usage notes

    If the shipment does contain a seal number, this seal number needs to be provided through the REF*SN segment for identification.

    Example: REFSNSEAL123

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    SN
    Seal Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 50

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

    Usage notes

    This field will be the container's seal number.

    DTM
    2000

    Estimated Delivery

    RequiredMax use 10

    To specify pertinent dates and times

    Usage notes

    Shipped Date and Estimated Delivery Dates are mandatory information in the ASN message.

    DTM04 Time Code has to correspond with all DTM segments in the ASN. Different Time Codes are not allowed.

    If any of DTM03 or DTM04 are present then both are required.

    Example: DTM017201402100915GM

    Example
    Variants (all may be used)
    DTMShipped
    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

    017
    Estimated Delivery
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    Usage notes

    This field lists the date/time that the shipment departed from your warehouse location.

    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

    GM
    Greenwich Mean Time
    UT
    Universal Time Coordinate
    DTM
    2000

    Shipped

    RequiredMax use 10

    To specify pertinent dates and times

    Usage notes

    Shipped Date and Estimated Delivery Dates are mandatory information in the ASN message.

    DTM04 Time Code has to correspond with all DTM segments in the ASN. Different Time Codes are not allowed.

    If any of DTM03 or DTM04 are present then both are required.

    Example: DTM011201402050915GM

    Example
    Variants (all may be used)
    DTMEstimated Delivery
    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 where CC represents the first two digits of the calendar year

    Usage notes

    This field lists the date/time that the shipment departed from your warehouse location.

    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

    GM
    Greenwich Mean Time
    UT
    Universal Time Coordinate
    FOB
    2100

    F.O.B. Related Instructions

    OptionalMax use 1

    To specify transportation instructions relating to shipment

    Usage notes

    FOB01 indicates which party will pay the carrier.

    Examples:
    FOBCC
    FOB
    PP

    Example
    FOB-01
    146
    Shipment Method of Payment
    Required
    Min 2Max 2

    Code identifying payment terms for transportation charges

    • FOB01 indicates which party will pay the carrier.
    N1 Ship From
    RequiredMax >1
    Usage notes

    Examples:
    N1SFSUPPLIER151234567
    N4NASHVILLETN37214US

    Variants (all may be used)
    N1Ship To
    N1
    2200

    Party Identification

    RequiredMax use 1

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

    Usage notes

    Examples:
    N1SFSUPPLIER151234567
    N1SFSUPPLIER92AmazonVendorCode

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    N1-01
    98
    Entity Identifier Code
    Required

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

    SF
    Ship From
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Required

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

    1
    D-U-N-S Number, Dun & Bradstreet
    15
    Standard Address Number (SAN)
    92
    Assigned by Buyer or Buyer's Agent
    UL
    Global Location Number (GLN)
    ZZ
    Mutually Defined
    N1-04
    67
    Identification Code
    Required
    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.
    Usage notes

    This field will contain the unique ID code representing the vendor's or 3PL's warehouse from where this shipment originated from. Unless otherwise notified, the vendor or 3PL can choose which ID code to use to identify their warehouse.

    N3
    2400

    Party Location

    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
    2500

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Usage notes

    Examples:
    N4NASHVILLETN37214US
    N4TORONTO**36573594CA
    N4SWANSEA**SA1 8QXGB

    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
    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
    Required
    Min 3Max 15

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

    N4-04
    26
    Country Code
    Required
    Min 2Max 3

    Code identifying the country

    Usage notes

    Amazon is expecting the country to be provided in ISO 3166-1 alpha-2 code (2 digits).

    N1 Ship To
    RequiredMax >1
    Usage notes

    Examples:
    N1ST**92RNO1
    N1ST**151566008
    N1ST**UL5450534000116

    Variants (all may be used)
    N1Ship From
    N1
    2200

    Party Identification

    RequiredMax use 1

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

    Usage notes

    The ship-to code needs to match the code used in the corresponding purchase order.

    Examples:
    N1ST**92RNO1
    N1ST**151566008
    N1ST**UL5450534000116

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    N1-01
    98
    Entity Identifier Code
    Required

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

    ST
    Ship To
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Required

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

    15
    Standard Address Number (SAN)
    92
    Assigned by Buyer or Buyer's Agent
    UL
    Global Location Number (GLN)
    N1-04
    67
    Identification Code
    Required
    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.
    Usage notes

    This field will be a unique ID representing the Amazon FC where this shipment will be delivered. This should match the vale which was transmitted through the Amazon purchase order.

    Please see the list of Amazon Ship-To locations and their corresponding FC codes and SAN's in the "Technical" section of the Resource Center in Vendor Central.

    N3
    2400

    Party Location

    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
    2500

    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

    V1 Loop
    OptionalMax >1
    Usage notes

    This segment is only used for import ASNs. Not used for domestic messaging.

    V1
    3600

    Vessel Identification

    RequiredMax use 1

    To provide vessel details and voyage number

    Usage notes

    This is only in use for import ASNs, not in use within domestic messaging.

    Example: V19349617ITAL MILIONEUS0370-008EEGLV***O

    Example
    At least one of Vessel Code (V1-01) or Vessel Name (V1-02) is required
    If Vessel Code Qualifier (V1-08) is present, then Vessel Code (V1-01) is required
    V1-01
    597
    Vessel Code
    Optional
    Min 1Max 8

    Code identifying vessel

    V1-02
    182
    Vessel Name
    Optional
    Min 2Max 28

    Name of ship as documented in "Lloyd's Register of Ships"

    V1-03
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    • V103 is the code identifying the country in which the ship (vessel) is registered.
    V1-04
    55
    Flight/Voyage Number
    Optional
    Min 2Max 10

    Identifying designator for the particular flight or voyage on which the cargo travels

    V1-05
    140
    Standard Carrier Alpha Code
    Optional
    Min 2Max 4

    Standard Carrier Alpha Code

    • V105 identifies the ocean carrier.
    V1-06
    249
    Vessel Requirement Code
    Optional
    Min 1Max 1

    Code specifying options for satisfying vessel requirements

    V1-07
    854
    Vessel Type Code
    Optional
    Min 2Max 2

    Code to determine type of vessel

    V1-08
    897
    Vessel Code Qualifier
    Optional
    Min 1Max 1

    Code specifying vessel code source

    V1-09
    91
    Transportation Method/Type Code
    Optional
    Min 1Max 2

    Code specifying the method or type of transportation for the shipment

    R4
    3700

    Port or Terminal

    OptionalMax use >1

    Contractual or operational port or point relevant to the movement of the cargo

    Usage notes

    This is only in use for import ASNs, not in use within domestic messaging.

    Example: R4DUN*USTIW**CN

    Example
    If either Location Qualifier (R4-02) or Location Identifier (R4-03) is present, then the other is required
    R4-01
    115
    Port or Terminal Function Code
    Required

    Code defining function performed at the port or terminal with respect to a shipment

    D
    Port of Discharge (Operational)
    F
    Freight Payable At (Contractual)
    L
    Port of Loading (Operational)
    R4-02
    309
    Location Qualifier
    Optional

    Code identifying type of location

    UN
    United Nations Location Code (UNLOCODE)
    R4-03
    310
    Location Identifier
    Optional
    Min 1Max 30

    Code which identifies a specific location

    R4-04
    114
    Port Name
    Optional
    Min 2Max 24

    Free-form name for the place at which an offshore carrier originates or terminates (by transshipment or otherwise) its actual ocean carriage of property

    R4-05
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    R4-06
    174
    Terminal Name
    Optional
    Min 2Max 30

    Free-form field for terminal name

    R4-07
    113
    Pier Number
    Optional
    Min 1Max 4

    Identifying number for the pier

    R4-08
    156
    State or Province Code
    Optional
    Min 2Max 2

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

    DTM
    3800

    Date/Time Reference

    OptionalMax use >1

    To specify pertinent dates and times

    Usage notes

    This segment is only used for import ASNs. Not used for domestic messaging.

    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

    AAA
    Arrival in Country
    DFS
    Departure From Specification
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

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

    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

    HL Loop
    RequiredMax >1
    Usage notes

    Per ASN multiple Order HL Loops can be sent. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Example: HL21*O

    HL
    0100

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

    Purchase Order Reference

    RequiredMax use 1

    To provide reference to a specific purchase order

    Usage notes

    This is the Amazon Purchase Order number you received via EDI or Vendor Central PO Managment Application.

    Example: PRF*S3993317

    Example
    PRF-01
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    Usage notes

    This field will contain the Amazon purchase order number. It will be supplied for all Amazon purchase order numbers relevant to each shipment and that shipment's paper bill of lading (BOL).

    HL Loop
    OptionalMax >1
    Usage notes

    Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Please do not include items (HL Item loop) at the Tare (Pallet) Level without an associated package level, as this will cause processing errors. When providing the Tare (Pallet) Level information, Amazon requires the SSCC code to be sent on the Tare (Pallet) Level and prefers SSCC also at the Pack Level.

    If the vendor provides Tare (Pallet) Level information with SSCC and Pack Level (with/without SSCC) Amazon will treat the Pack Level as Cartons, even if the vendor does not declare the TD1 on Pack Level.

    Example: HL32*T

    Variants (all may be used)
    HLHL Loop
    HL
    0100

    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.
    T
    Shipping Tare
    HL-04
    736
    Hierarchical Child Code
    Optional

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

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

    Carrier Details (Quantity and Weight)

    OptionalMax use 20

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

    Usage notes

    Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    This section is needed if you can provide pallet level carton count and pallet weight details. The number of cartons (CTN) mentioned in the TD102 element refers to the count of shipping cartons/ packages in the pallet (not the packaged items inside the cartons).

    If the vendor provides Tare Level information with SSCC and Pack Level (with/without SSCC) Amazon will treat the Pack level as Cartons, even if the vendor does not declare the TD1 on Pack level.

    Example
    If Commodity Code Qualifier (TD1-03) is present, then Commodity Code (TD1-04) is required
    If Weight Qualifier (TD1-06) is present, then Weight (TD1-07) is required
    If either Weight (TD1-07) or Unit or Basis for Measurement Code (TD1-08) is present, then the other is required
    If either Volume (TD1-09) or Unit or Basis for Measurement Code (TD1-10) is present, then the other is required
    TD1-01
    103
    Packaging Code
    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
    TD1-02
    80
    Lading Quantity
    Optional
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    TD1-03
    23
    Commodity Code Qualifier
    Optional
    Min 1Max 1

    Code identifying the commodity coding system used for Commodity Code

    TD1-04
    22
    Commodity Code
    Optional
    Min 1Max 30

    Code describing a commodity or group of commodities

    TD1-05
    79
    Lading Description
    Optional
    Min 1Max 50

    Description of an item as required for rating and billing purposes

    TD1-06
    187
    Weight Qualifier
    Optional
    Min 1Max 2

    Code defining the type of weight

    TD1-07
    81
    Weight
    Optional
    Min 1Max 10

    Numeric value of weight

    TD1-08
    355
    Unit or Basis for Measurement Code
    Optional
    Min 2Max 2

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

    TD1-09
    183
    Volume
    Optional
    Min 1Max 8

    Value of volumetric measure

    TD1-10
    355
    Unit or Basis for Measurement Code
    Optional
    Min 2Max 2

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

    MAN
    1900

    Marks and Numbers Information

    RequiredMax use >1

    To indicate identifying marks and numbers for shipping containers

    Usage notes

    This segment is required when sending pallets in the shipment and including the tare loop.The SSCC has to be unique per pallet and can't be reused within 90 days.

    Example: MANGM00000388080758591512

    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
    EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier
    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

    Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    HL Loop
    OptionalMax >1
    Usage notes

    Per ASN multiple Package HL Loops can be sent. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Example: HL32*P

    Variants (all may be used)
    HLHL Loop
    HL
    0100

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

    Carrier Details (Quantity and Weight)

    OptionalMax use 20

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

    Usage notes

    This segment should be used if you send the MAN segment and can provide package level weight details.

    If the vendor provides Tare Level information with SSCC and Pack Level (with/without SSCC), Amazon will treat the Pack level as Cartons, even if the vendor does not declare the TD1 on Pack level.

    Example: TD1CTN1***G2.5*LB

    Example
    If Commodity Code Qualifier (TD1-03) is present, then Commodity Code (TD1-04) is required
    TD1-01
    103
    Packaging Code
    Required

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

    CTN
    Carton
    TD1-02
    80
    Lading Quantity
    Required
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    TD1-03
    23
    Commodity Code Qualifier
    Optional
    Min 1Max 1

    Code identifying the commodity coding system used for Commodity Code

    TD1-04
    22
    Commodity Code
    Optional
    Min 1Max 30

    Code describing a commodity or group of commodities

    TD1-05
    79
    Lading Description
    Optional
    Min 1Max 50

    Description of an item as required for rating and billing purposes

    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

    GR
    Gram
    KG
    Kilogram
    LB
    Pound
    OZ
    Ounce - Av
    REF
    1500

    Reference Information

    OptionalMax use >1

    To specify identifying information

    Usage notes

    Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    For multi carton small parcel shipments, it is required to provide the carrier tracking number per package.The tracking number needs to be unique per package and can't be reused from previous ASN's.

    For single carton small parcel shipments (carton count = 1), the Air/PRO/TrackingNumber is not required at the Package level if it's present at the Shipment level.

    It is not required to provide this segment and package level tracking for LTL/ TL shipments, as long as tracking exists at the shipment level.

    Example: REFCN1ZE1628E0340236740

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    A value of CN is used to qualify the following values:

    • Carrier tracking number for small parcel carriers
    • Carrier Airbill number for air freight
    CN
    Carrier's Tracking/Airbill Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 50

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

    MAN
    1900

    Marks and Numbers Information

    OptionalMax use >1

    To indicate identifying marks and numbers for shipping containers

    Usage notes

    This segment is required for small parcel shipments. The SSCC needs to be unique per package and can't be repeated across multiple shipments/ ASN's. This segment is desired, but not required for LTL/ TL shipments if the pallet level SSCC is provided at the tare level.

    Example: MANGM00000388080758591512

    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
    EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier
    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

    Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    HL Loop
    RequiredMax >1
    Usage notes

    Example: HL43*I

    HL
    0100

    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
    0200

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

    Usage notes

    Example: LIN1EN4260333470017LT*23141345

    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
    Optional
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • LIN01 is the line item identification
    Usage notes

    This will be a unique line number representing this item.

    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.
    BP
    Buyer's Part Number
    EN
    EAN/UCC - 13
    IB
    International Standard Book Number (ISBN)
    UA
    U.P.C./EAN Case Code (2-5-5)
    UK
    GTIN 14-digit Data Structure
    UP
    UCC - 12
    VN
    Vendor's (Seller's) Item Number
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    The value in this field needs to match the product ID supplied by Amazon when the order was placed either via EDI or Vendor Central.

    LIN-04
    235
    Product/Service ID Qualifier
    Optional

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

    LT
    Lot Number
    LIN-05
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    The value in this field will be the Lot Number in GS-128 code format. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    SN1
    0300

    Item Detail (Shipment)

    RequiredMax use 1

    To specify line-item detail relative to shipment

    Usage notes

    Example: SN1*1EA

    Example
    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

    This element should contain the same number as the corresponding LIN01.

    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

    This field will be the number of units shipped for this item related to the package in this order.

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

    The same unit of measurement should be used as was provided via the Amazon purchase order.

    CA
    Case
    EA
    Each
    MEA
    0800

    Measurements

    OptionalMax use 40

    To specify physical measurements or counts, including dimensions, tolerances, variances, and weights

    (See Figures Appendix for example of use of C001)

    Usage notes

    Shelf Life can be provided here. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Examples:
    MEASFSHA12MO - Item has a shelf life of 12 months
    MEASFSHA10DA - Item has a shelf life of 10 days

    Example
    MEA-01
    737
    Measurement Reference ID Code
    Optional

    Code identifying the broad category to which a measurement applies

    SF
    Shelf Life
    MEA-02
    738
    Measurement Qualifier
    Optional

    Code identifying a specific product or process characteristic to which a measurement applies

    SHA
    Shelf Life
    MEA-03
    739
    Measurement Value
    Optional
    Min 1Max 15

    The value of the measurement

    MEA-04
    C001
    Composite Unit of Measure
    To identify a composite unit of measure (See Figures Appendix for examples of use)
    C001-01
    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

    DA
    Days
    MO
    Months
    DTM
    2000

    Expiration

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    Item specific dates can be provided via the DTM segment. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Example: DTM03620140725

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

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

    036
    Expiration
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    DTM
    2000

    Manufacture

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    Item specific dates can be provided via the DTM segment. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Example: DTM09420140815

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

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

    094
    Manufacture
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    HL Loop
    OptionalMax >1
    Usage notes

    Example: HL43*I

    Variants (all may be used)
    HLHL Loop
    HL
    0100

    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
    0200

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

    Usage notes

    Example: LIN1EN4260333470017LT*23141345

    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
    Optional
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • LIN01 is the line item identification
    Usage notes

    This will be a unique line number representing this item.

    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.
    BP
    Buyer's Part Number
    EN
    EAN/UCC - 13
    IB
    International Standard Book Number (ISBN)
    UA
    U.P.C./EAN Case Code (2-5-5)
    UK
    GTIN 14-digit Data Structure
    UP
    UCC - 12
    VN
    Vendor's (Seller's) Item Number
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    The value in this field needs to match the product ID supplied by Amazon when the order was placed either via EDI or Vendor Central.

    LIN-04
    235
    Product/Service ID Qualifier
    Optional

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

    LT
    Lot Number
    LIN-05
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    The value in this field will be the Lot Number in GS-128 code format. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    SN1
    0300

    Item Detail (Shipment)

    RequiredMax use 1

    To specify line-item detail relative to shipment

    Usage notes

    Example: SN1*1EA

    Example
    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

    This element should contain the same number as the corresponding LIN01.

    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

    This field will be the number of units shipped for this item related to the package in this order.

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

    The same unit of measurement should be used as was provided via the Amazon purchase order.

    CA
    Case
    EA
    Each
    MEA
    0800

    Measurements

    OptionalMax use 40

    To specify physical measurements or counts, including dimensions, tolerances, variances, and weights

    (See Figures Appendix for example of use of C001)

    Usage notes

    Shelf Life can be provided here. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Example:
    MEASFSHA12MO - Item has a shelf life of 12 months
    MEASFSHA10DA - Item has a shelf life of 10 days

    Example
    MEA-01
    737
    Measurement Reference ID Code
    Optional

    Code identifying the broad category to which a measurement applies

    SF
    Shelf Life
    MEA-02
    738
    Measurement Qualifier
    Optional

    Code identifying a specific product or process characteristic to which a measurement applies

    SHA
    Shelf Life
    MEA-03
    739
    Measurement Value
    Optional
    Min 1Max 15

    The value of the measurement

    MEA-04
    C001
    Composite Unit of Measure
    To identify a composite unit of measure (See Figures Appendix for examples of use)
    C001-01
    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

    DA
    Days
    MO
    Months
    DTM
    2000

    Expiration

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    Item specific dates can be provided via the DTM segment. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Example: DTM03620140725

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

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

    036
    Expiration
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    DTM
    2000

    Manufacture

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    Item specific dates can be provided via the DTM segment. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Example: DTM09420140815

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

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

    094
    Manufacture
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    HL Loop
    OptionalMax >1
    Usage notes

    Per ASN multiple Package HL Loops can be sent. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Example: HL32*P

    Variants (all may be used)
    HLHL Loop
    HL
    0100

    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.
    0
    No Subordinate HL Segment in This Hierarchical Structure.
    1
    Additional Subordinate HL Data Segment in This Hierarchical Structure.
    TD1
    1100

    Carrier Details (Quantity and Weight)

    OptionalMax use 20

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

    Usage notes

    This segment should be used if you send the MAN segment and can provide package level weight details.

    If the vendor provides Tare Level information with SSCC and Pack Level (with/without SSCC), Amazon will treat the Pack level as Cartons, even if the vendor does not declare the TD1 on Pack level.

    Example: TD1CTN1***G2.5*LB

    Example
    If Commodity Code Qualifier (TD1-03) is present, then Commodity Code (TD1-04) is required
    TD1-01
    103
    Packaging Code
    Required

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

    CTN
    Carton
    TD1-02
    80
    Lading Quantity
    Required
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    TD1-03
    23
    Commodity Code Qualifier
    Optional
    Min 1Max 1

    Code identifying the commodity coding system used for Commodity Code

    TD1-04
    22
    Commodity Code
    Optional
    Min 1Max 30

    Code describing a commodity or group of commodities

    TD1-05
    79
    Lading Description
    Optional
    Min 1Max 50

    Description of an item as required for rating and billing purposes

    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

    GR
    Gram
    KG
    Kilogram
    LB
    Pound
    OZ
    Ounce - Av
    REF
    1500

    Reference Information

    OptionalMax use >1

    To specify identifying information

    Usage notes

    Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    For multi carton small parcel shipments, it is required to provide the carrier tracking number per package.The tracking number needs to be unique per package and can't be reused from previous ASN's.

    For single carton small parcel shipments (carton count = 1), the Air/PRO/TrackingNumber is not required at the Package level if it's present at the Shipment level.

    It is not required to provide this segment and package level tracking for LTL/ TL shipments, as long as tracking exists at the shipment level.

    Example: REFCN1ZE1628E0340236740

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    A value of CN is used to qualify the following values:

    • Carrier tracking number for small parcel carriers
    • Carrier Airbill number for air freight
    CN
    Carrier's Tracking/Airbill Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 50

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

    MAN
    1900

    Marks and Numbers Information

    OptionalMax use >1

    To indicate identifying marks and numbers for shipping containers

    Usage notes

    This segment is required for small parcel shipments. The SSCC needs to be unique per package and can't be repeated across multiple shipments/ ASN's. This segment is desired, but not required for LTL/ TL shipments if the pallet level SSCC is provided at the tare level.

    Example: MANGM00000388080758591512

    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
    EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier
    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

    Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    HL Loop
    OptionalMax >1
    Usage notes

    Example: HL43*I

    HL
    0100

    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
    0200

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

    Usage notes

    Example: LIN1EN4260333470017LT*23141345

    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
    Optional
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • LIN01 is the line item identification
    Usage notes

    This will be a unique line number representing this item.

    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.
    BP
    Buyer's Part Number
    EN
    EAN/UCC - 13
    IB
    International Standard Book Number (ISBN)
    UA
    U.P.C./EAN Case Code (2-5-5)
    UK
    GTIN 14-digit Data Structure
    UP
    UCC - 12
    VN
    Vendor's (Seller's) Item Number
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    The value in this field needs to match the product ID supplied by Amazon when the order was placed either via EDI or Vendor Central.

    LIN-04
    235
    Product/Service ID Qualifier
    Optional

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

    LT
    Lot Number
    LIN-05
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    The value in this field will be the Lot Number in GS-128 code format. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    SN1
    0300

    Item Detail (Shipment)

    RequiredMax use 1

    To specify line-item detail relative to shipment

    Usage notes

    Example: SN1*1EA

    Example
    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

    This element should contain the same number as the corresponding LIN01.

    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

    This field will be the number of units shipped for this item related to the package in this order.

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

    The same unit of measurement should be used as was provided via the Amazon purchase order.

    CA
    Case
    EA
    Each
    MEA
    0800

    Measurements

    OptionalMax use 40

    To specify physical measurements or counts, including dimensions, tolerances, variances, and weights

    (See Figures Appendix for example of use of C001)

    Usage notes

    Shelf Life can be provided here. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Example:
    MEASFSHA12MO - Item has a shelf life of 12 months
    MEASFSHA10DA - Item has a shelf life of 10 days

    Example
    MEA-01
    737
    Measurement Reference ID Code
    Optional

    Code identifying the broad category to which a measurement applies

    SF
    Shelf Life
    MEA-02
    738
    Measurement Qualifier
    Optional

    Code identifying a specific product or process characteristic to which a measurement applies

    SHA
    Shelf Life
    MEA-03
    739
    Measurement Value
    Optional
    Min 1Max 15

    The value of the measurement

    MEA-04
    C001
    Composite Unit of Measure
    To identify a composite unit of measure (See Figures Appendix for examples of use)
    C001-01
    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

    DA
    Days
    MO
    Months
    DTM
    2000

    Expiration

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    Item specific dates can be provided via the DTM segment. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Example: DTM03620140725

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

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

    036
    Expiration
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    DTM
    2000

    Manufacture

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    Item specific dates can be provided via the DTM segment. Please refer to the Business Requirement Document for the specific locale you are sending a shipment to.

    Example: DTM09420140815

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

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

    094
    Manufacture
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    Summary

    CTT
    0100

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

    Example: CTT5372426

    Example
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    Usage notes

    Logical count of all HL loops in the message.

    CTT-02
    347
    Hash Total
    Required
    Min 1Max 10

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

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

    1873 Hash Total

    Usage notes

    Sum of all SN102 elements (number of units shipped).

    SE
    0200

    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

    Carton with SSCC

    ISA*00* *00* *ZZ*VENDOR ID *ZZ*AMAZON *140223*0111*^*00501*000143657*0*T*>~
    GS*SH*VENDOR ID*AMAZON*20140223*0111*20642*X*005010~
    ST*856*0001~
    BSN*00*UNIQUE ASN ID*20140223*011147*0001~
    HL*1**S~
    TD1*CTN*2****G*30*LB~
    TD5**2*UPSN~
    REF*BM*BOL NUMBER~
    REF*CN*PRO NUMBER~
    REF*BX*ARN NUMBER~
    DTM*011*20140223~
    DTM*017*20140228~
    FOB*CC~
    N1*SF*VENDOR NAME*15*LOCCODE~
    N4*City*ST*NNNNN*US~
    N1*ST*AMAZON.COM*15*1553992~
    N4*NEW CASTLE*DE*19720*US~
    HL*2*1*O~
    PRF*P3618661~
    HL*3*2*P~
    REF*CN*UPS TRACKING NUMBER~
    MAN*GM*00100746460944048555~
    HL*4*3*I~
    LIN*1*UP*ITEM NUMBER~
    SN1**30*EA~
    HL*5*3*I~
    LIN*2*UP*ITEM NUMBER~
    SN1**98*EA~
    HL*6*2*P~
    REF*CN*UPS TRACKING NUMBER~
    MAN*GM*00100746460944048565~
    HL*7*6*I~
    LIN*1*UP*ITEM NUMBER~
    SN1**50*EA~
    HL*8*6*I~
    LIN*2*UP*ITEM NUMBER~
    SN1**50*EA~
    CTT*8*228~
    SE*34*0001~
    GE*1*20642~
    IEA*1*000143657~

    CollectASN - Small Parcel with Expiration and Lot Numbers

    ISA*00* *00* *ZZ*VENDOR ID *ZZ*AMAZON *140223*0111*^*00501*000143657*0*T*>~
    GS*SH*VENDOR ID*AMAZON*20140223*0111*20642*X*005010~
    ST*856*0001~
    BSN*00*UNIQUE ASN ID*20140223*011147*0001~
    HL*1**S~
    TD1*CTN*2****G*30*LB~
    TD5**2*UPSN~
    REF*BX*ARN NUMBER~
    DTM*011*20140223~
    DTM*017*20140228~
    FOB*CC~
    N1*SF*VENDOR NAME*15*LOCCODE~
    N4*City*ST*NNNNN*US~
    N1*ST*AMAZON.COM*15*1553992~
    N4*NEW CASTLE*DE*19720*US~
    HL*2*1*O~
    PRF*P3618661~
    HL*3*2*P~
    REF*CN*UPS TRACKING NUMBER~
    MAN*GM*SSCC CODE~
    HL*4*3*I~
    LIN*1*UP*ITEM NUMBER*LT*12345~
    SN1**30*EA~
    DTM*036*20140725~
    HL*5*3*I~
    LIN*2*UP*ITEM NUMBER*LT*12345~
    SN1**98*EA~
    DTM*036*20140725~
    HL*6*2*P~
    REF*CN*UPS TRACKING NUMBER~
    MAN*GM*SSCC CODE~
    HL*7*6*I~
    LIN*1*UP*ITEM NUMBER*LT*12345~
    SN1**50*EA~
    DTM*036*20140725~
    HL*8*6*I~
    LIN*2*UP*ITEM NUMBER*LT*12345~
    SN1**50*EA~
    DTM*036*20140725~
    CTT*8*228~
    SE*32*0001~
    GE*1*20642~
    IEA*1*000143657~

    Expiration and Lot Numbers

    ISA*00* *00* *ZZ*VENDOR ID *ZZ*AMAZON *140223*0111*^*00501*000143657*0*T*>~
    GS*SH*VENDOR ID*AMAZON*20140223*0111*20642*X*005010~
    ST*856*0001~
    BSN*00*UNIQUE ASN ID*20140223*011147*0001~
    HL*1**S~
    TD1*CTN*2****G*30*LB~
    TD5**2*UPSN~
    REF*BM*BOL NUMBER~
    REF*CN*PRO NUMBER~
    REF*BX*ARN NUMBER~
    DTM*011*20140223~
    DTM*017*20140228~
    FOB*CC~
    N1*SF*VENDOR NAME*15*LOCCODE~
    N4*City*ST*NNNNN*US~
    N1*ST*AMAZON.COM*15*1553992~
    N4*NEW CASTLE*DE*19720*US~
    HL*2*1*O~
    PRF*P3618661~
    HL*3*2*P~
    REF*CN*UPS TRACKING NUMBER~
    MAN*GM*00100746460944048555~
    HL*4*3*I~
    LIN*1*UP*ITEM NUMBER*LT*12345~
    SN1**30*EA~
    DTM*036*20140725~
    HL*5*3*I~
    LIN*2*UP*ITEM NUMBER*LT*12345~
    SN1**98*EA~
    DTM*036*20140725~
    HL*6*2*P~
    REF*CN*UPS TRACKING NUMBER~
    MAN*GM*00100746460944048565~
    HL*7*6*I~
    LIN*1*UP*ITEM NUMBER*LT*12345~
    SN1**50*EA~
    DTM*036*20140725~
    HL*8*6*I~
    LIN*2*UP*ITEM NUMBER*LT*12345~
    SN1**50*EA~
    DTM*036*20140725~
    CTT*8*228~
    SE*34*0001~
    GE*1*20642~
    IEA*1*000143657~

    Pallet with SSCC at Tare and Pack

    ISA*00* *00* *ZZ*VENDOR ID *ZZ*AMAZON *140223*0111*^*00501*000143657*0*T*>~
    GS*SH*VENDOR ID*AMAZON*20140223*0111*20642*X*005010~
    ST*856*0001~
    BSN*00*UNIQUE ASN ID*20140223*011147*0001~
    HL*1**S~
    TD1*CTN*2****G*30*LB~
    TD1*PLT*2~
    TD5**2*ABFS~
    REF*BM*BOL NUMBER~
    REF*CN*PRO NUMBER~
    REF*BX*ARN NUMBER~
    DTM*011*20140223~
    DTM*017*20140228~
    FOB*CC~
    N1*SF*VENDOR NAME*15*LOCCODE~
    N4*City*ST*NNNNN*US~
    N1*ST*AMAZON.COM*15*1553992~
    N4*NEW CASTLE*DE*19720*US~
    HL*2*1*O~
    PRF*P3618661~
    HL*3*2*T~
    MAN*GM*00100746460944048575~
    HL*4*3*P~
    MAN*GM*00100746460944048577~
    HL*5*4*I~
    LIN*1*UP*ITEM NUMBER~
    SN1**30*EA~
    HL*6*4*I~
    LIN*2*UP*ITEM NUMBER~
    SN1**98*EA~
    HL*7*2*T~
    MAN*GM*00100746460944048576~
    HL*8*7*P~
    MAN*GM*00100746460944048578~
    HL*9*8*I~
    LIN*1*UP*ITEM NUMBER~
    SN1**50*EA~
    HL*10*8*I~
    LIN*2*UP*ITEM NUMBER~
    SN1**50*EA~
    CTT*10*228~
    SE*37*0001~
    GE*1*20642~
    IEA*1*000143657

    Pallet with SSCC at Tare level Only (Amazon Authorization Required)

    ISA*00* *00* *ZZ*VENDOR ID *ZZ*AMAZON *140223*0111*^*00501*000143657*0*T*>~
    GS*SH*VENDOR ID*AMAZON*20140223*0111*20642*X*005010~
    ST*856*0001~
    BSN*00*UNIQUE ASN ID*20140223*011147*0001~
    HL*1**S~
    TD1*CTN*2****G*30*LB~
    TD1*PLT*2~
    TD5**2*ABFS~
    REF*BM*BOL NUMBER~
    REF*CN*PRO NUMBER~
    REF*BX*ARN NUMBER~
    DTM*011*20140223~
    DTM*017*20140228~
    FOB*CC~
    N1*SF*VENDOR NAME*15*LOCCODE~
    N4*City*ST*NNNNN*US~
    N1*ST*AMAZON.COM*15*1553992~
    N4*NEW CASTLE*DE*19720*US~
    HL*2*1*O~
    PRF*P3618661~
    HL*3*2*T~
    MAN*GM*00100746460944048575~
    HL*4*3*P~
    HL*5*4*I~
    LIN*1*UP*ITEM NUMBER~
    SN1**30*EA~
    HL*6*2*T~
    MAN*GM*00100746460944048576~
    HL*7*6*P~
    HL*8*7*I~
    LIN*1*UP*ITEM NUMBER~
    SN1**50*EA~
    CTT*10*80~
    SE*32*0001~
    GE*1*20642~
    IEA*1*000143657

    Pallet with SSCC at Tare Only SOTI Hierarchy

    ISA*00* *00* *ZZ*VENDOR ID *ZZ*AMAZON *140223*0111*^*00501*000143657*0*T*>~
    GS*SH*VENDOR ID*AMAZON*20140223*0111*20642*X*005010~
    ST*856*0001~
    BSN*00*UNIQUE ASN ID*20140223*011147*0001~
    HL*1**S~
    TD1*CTN*20****G*30*LB~
    TD1*PLT*2~
    TD5**2*ABFS~
    REF*BM*BOL NUMBER~
    REF*CN*PRO NUMBER~
    DTM*011*20140223~
    DTM*017*20140228~
    FOB*CC~
    N1*SF*VENDOR NAME*15*LOCCODE~
    N4*City*ST*NNNNN*US~
    N1*ST*AMAZON.COM*15*1553992~
    N4*NEW CASTLE*DE*19720*US~
    HL*2*1*O~
    PRF*P3618661~
    HL*3*2*T~
    TD1*CTN*10~
    MAN*GM*00100746460944048575~
    HL*4*3*I~
    LIN**UK*10037000725692*LT*11241505N1~
    SN1**10*CA~
    DTM*036*20230407~
    DTM*094*20220115~
    HL*5*2*T~
    TD1*CTN*10~
    MAN*GM*00100746460944048543~
    HL*6*5*I~
    LIN**UK*10037000726541*LT*11241505N1~
    SN1**10*CA~
    DTM*036*20230807~
    DTM*094*20220215~
    CTT*6*20~
    SE*43*0001~
    GE*1*20642~
    IEA*1*000143657

    Small Parcel

    ISA*00* *00* *ZZ*VENDOR ID *ZZ*AMAZON *140223*0111*^*00501*000143657*0*T*>~
    GS*SH*VENDOR ID*AMAZON*20140223*0111*20642*X*005010~
    ST*856*0001~
    BSN*00*UNIQUE ASN ID*20140223*011147*0001~
    HL*1**S~
    TD1*CTN*2****G*30*LB~
    TD5**2*UPSN~
    REF*BX*ARN NUMBER~
    DTM*011*20140223~
    DTM*017*20140228~
    FOB*CC~
    N1*SF*VENDOR NAME*15*LOCCODE~
    N4*City*ST*NNNNN*US~
    N1*ST*AMAZON.COM*15*1553992~
    N4*NEW CASTLE*DE*19720*US~
    HL*2*1*O~
    PRF*P3618661~
    HL*3*2*P~
    REF*CN*UPS TRACKING NUMBER~
    MAN*GM*SSCC CODE~
    HL*4*3*I~
    LIN*1*UP*ITEM NUMBER~
    SN1**30*EA~
    HL*5*3*I~
    LIN*2*UP*ITEM NUMBER~
    SN1**98*EA~
    HL*6*2*P~
    REF*CN*UPS TRACKING NUMBER~
    MAN*GM*SSCC CODE~
    HL*7*6*I~
    LIN*1*UP*ITEM NUMBER~
    SN1**50*EA~
    HL*8*6*I~
    LIN*2*UP*ITEM NUMBER~
    SN1**50*EA~
    CTT*8*228~
    SE*32*0001~
    GE*1*20642~
    IEA*1*000143657~

    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.