Amazon
/
Direct Fulfillment Ship Notice/Manifest
  • Specification
  • EDI Inspector
Import guide into your account
Amazon logo

X12 856 Direct Fulfillment Ship Notice/Manifest

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.

The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
  • Full Floor Denial
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/amazon/direct-fulfillment-ship-noticemanifest/01GWHTBZ4226RFRMT0S60D8VSA
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
detail
HL Loop
HL
010
Hierarchical Level
Max use 1
Required
PRF
050
Purchase Order Reference
Max use 1
Required
HL Loop
HL
010
Hierarchical Level
Max use 1
Required
LIN
020
Item Identification
Max use 1
Required
SN1
030
Item Detail (Shipment)
Max use 1
Required
SLN
040
Subline Item Detail
Max use 1000
Optional
MAN
190
Marks and Numbers
Max use 1
Optional
HL Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

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

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

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

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

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

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

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

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

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

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

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

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

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

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

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

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

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

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

This version number covers the interchange control segments

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

A control number assigned by the interchange sender

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

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

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

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

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

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

>
Component Element Separator

Functional Group Header

RequiredMax use 1

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

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

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

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

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

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

GS-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

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

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

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

Assigned number originated and maintained by the sender

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

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

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

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

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

Heading

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

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

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

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

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

BSN
020
Heading > BSN

Beginning Segment for Ship Notice

RequiredMax use 1

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

Usage notes

BSN00S123456201502062006ZZZZAS~

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

Code identifying purpose of transaction set

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

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

Usage notes

Vendor's internal shipment identification number.

BSN-03
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

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

Date format CCYYMMDD expressed in UTC format.

BSN-04
337
Time
Required
Time (TM)
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

Time format HHMMSS expressed in UTC Format.

BSN-05
1005
Hierarchical Structure Code
Optional
Identifier (ID)

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

Usage notes

Amazon.com HL Segment Usage:

The looping structure in this 856 is Order, Item, Pack. Items that are shipped will have an item and Pack loop for each carton. If one line item is shipped in two cartons the looping structure will be Item, Pack, Item, Pack- NOT Item, Pack, Pack. Both Item loops will have the same Line Item ID Number, however, Package ID's and Tracking Numbers must be unique per carton.

Items that are not shipped will not have a Pack loop or any associated Package ID's.

ZZZZ
Mutually Defined
BSN-06
640
Transaction Type Code
Required
Identifier (ID)

Code specifying the type of transaction

  • BSN06 is limited to shipment related codes.
  • BSN06 and BSN07 differentiate the functionality of use for the transaction set.
Usage notes

If the entire shipment has been sent, use "AS".
If the entire shipment has been cancelled, use "72"
Partial shipment is not allowed.

72
Termination

If the entire shipment has been rejected then use '72'

AS
Shipment Advice

If the all of the shipment has been sent then use 'AS'

BSN-07
641
Status Reason Code
Optional
Identifier (ID)

Code indicating the status reason

NOR
Normal
REJ
Rejected - Insufficient or Incorrect Information
Heading end

Detail

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

Hierarchical Level

RequiredMax use 1

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

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

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

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

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
Identifier (ID)

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

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

Purchase Order Reference

RequiredMax use 1

To provide reference to a specific purchase order

Usage notes

PRF*D2abC12PN*****5547416~

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

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

Same as 850 BEG03
Same as 855 BAK04
*This number is unique

PRF-04
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • PRF04 is the date assigned by the purchaser to purchase order.
PRF-06
367
Contract Number
Required
String (AN)
Min 1Max 30

Contract number

Usage notes

Vendor Order Reference Number.

N1 Loop
RequiredMax >1
N1
220
Detail > HL Loop > N1 Loop > N1

Name

RequiredMax use 1

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

Usage notes

Vendor's ship from warehouse.
N1SFABCD92ABCD~

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

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

Free-form name

Usage notes

This will be the Amazon code representing the warehouse that the order should ship from or the Warehouse name.
This is usually a four character alpha code (e.g. ABCD or ABC Warehouse).

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

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

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Usage notes

Amazon.com assigned code representing the warehouse order should ship from. This is usually a four character alpha code (e.g. ABCD).

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

Hierarchical Level

RequiredMax use 1

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

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

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

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

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

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

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
Identifier (ID)

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.
LIN
020
Detail > HL Loop > HL Loop > LIN

Item Identification

RequiredMax use 1

To specify basic item identification data

Usage notes

LIN1SK*123456789~

Example
LIN-01
350
Assigned Identification
Required
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • LIN01 is the line item identification
Usage notes

Same as PO101 in the 850
Same as PO101 in the 855

LIN-02
235
Product/Service ID Qualifier
Required
Identifier (ID)

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

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

Identifying number for a product or service

Usage notes

Item or production number. Should match LIN03 from 850/855.

SN1
030
Detail > HL Loop > HL Loop > SN1

Item Detail (Shipment)

RequiredMax use 1

To specify line-item detail relative to shipment

Usage notes

SN111EA**1EA**IA~

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

Alphanumeric characters assigned for differentiation within a transaction set

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

Same as PO101 in the 850
Same as PO101 in the 855
Same as LIN01 in this 856

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

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

Usage notes

Quantity Shipped.

SN1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

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

  • SN103 defines the unit of measurement for both SN102 and SN104.
EA
Each
SN1-05
330
Quantity Ordered
Optional
Decimal number (R)
Min 1Max 15

Quantity ordered

Usage notes

Original Order Qty.

SN1-06
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

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

EA
Each
SN1-08
668
Line Item Status Code
Required
Identifier (ID)

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

Usage notes

Use 'IA' if all the items in order are accepted.

IA
Item Accepted

IA - Item Accepted, if all the items are sent.

IR
Item Rejected

IR - Item Rejected if all of the items are cancelled or unavailable for shipment.

SLN
040
Detail > HL Loop > HL Loop > SLN

Subline Item Detail

OptionalMax use 1000

To specify product subline detail item data

Usage notes

This segment is only present when an item is either partially or entirely cancelled (i.e. item is not shipped). Due to no partial shipment allowed, all items in the order should be cancelled.

SLN****2~

Example
SLN-04
380
Quantity
Required
Decimal number (R)
Min 1Max 15

Numeric value of quantity

Usage notes

Quantity of item that is cancelled. Since partial order fulfillment is not allowed, you need to cancel/reject the whole order.

MAN
190
Detail > HL Loop > HL Loop > MAN

Marks and Numbers

OptionalMax use >1

To indicate identifying marks and numbers for shipping containers

Usage notes

This segment is used to communicate the ID of the package that the order was shipped in.

MANR01111178760019599973~

Example
MAN-01
88
Marks and Numbers Qualifier
Required
Identifier (ID)

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.
R
Originator Assigned
MAN-02
87
Marks and Numbers
Required
String (AN)
Min 1Max 48

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

  • When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
Usage notes

Vendor assigned unique package ID. MAN02 at Package Level must equal the MAN02 at Line Item Level.

HL Loop
OptionalMax >1
Usage notes

Not used when item is rejected

HL
010
Detail > HL Loop > HL Loop > HL Loop > HL

Hierarchical Level

RequiredMax use 1

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

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

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

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

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

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

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
Identifier (ID)

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.
TD1
110
Detail > HL Loop > HL Loop > HL Loop > TD1

Carrier Details (Quantity and Weight)

RequiredMax use 20

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

Usage notes

Segment used to communicate package weight.

TD1*****Z25.35*LB~

Example
TD1-06
187
Weight Qualifier
Optional
Identifier (ID)

Code defining the type of weight

Z
Mutually Defined
TD1-07
81
Weight
Required
Decimal number (R)
Min 1Max 10

Numeric value of weight

Usage notes

Weight expressed with two decimals (i.e. 1.88).

TD1-08
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

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

LB
Pound
TD5
120
Detail > HL Loop > HL Loop > HL Loop > TD5

Amazon.com ship-to method code

RequiredMax use 12

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

Usage notes

Segment used to communicate Amazon.com ship-to method codes.

TD5*92UPS_GR_RES~

Example
Variants (all may be used)
TD5Standard Carrier Alpha Code (SCAC)
If Identification Code Qualifier (TD5-02) is present, then Identification Code (TD5-03) is required
TD5-02
66
Identification Code Qualifier
Required
Identifier (ID)

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.
92
Assigned by Buyer or Buyer's Agent
TD5-03
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

Usage notes

Amazon.com defined codes indicating shipping carrier and shipment service level. These ship methods have to be returned verbatim.
Amazon.com defined codes indicating shipping carrier and shipment service level.

The value in this field is case sensitive and format sensitive. The value sent in the 850 should be the value returned in the corresponding 856. The value in the 856 will be to be the 'exact' value as reflected in the 850.

To see the full list of ship methods in use -- including both the code and the friendly name -- search theHelp section on 'ship methods

TD5
120
Detail > HL Loop > HL Loop > HL Loop > TD5

Standard Carrier Alpha Code (SCAC)

OptionalMax use 12

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

Usage notes

This TD5 segment is only required for Vendor Own Carrier (VOC) Vendors.

TD5*2PGLI~

Example
Variants (all may be used)
TD5Amazon.com ship-to method code
If Identification Code Qualifier (TD5-02) is present, then Identification Code (TD5-03) is required
TD5-02
66
Identification Code Qualifier
Required
Identifier (ID)

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

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

Code identifying a party or other code

Usage notes

Amazon expects the SCAC code in this field.

MAN
190
Detail > HL Loop > HL Loop > HL Loop > MAN

Marks and Numbers

RequiredMax use >1

To indicate identifying marks and numbers for shipping containers

Usage notes

Segment is used to communicate vendor package ID, manifest number and carrier shipment tracking number.

MANR1111187876001959997311187601112907239CP*1LA1111M0399059008~

Example
MAN-01
88
Marks and Numbers Qualifier
Required
Identifier (ID)

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.
R
Originator Assigned
MAN-02
87
Marks and Numbers
Required
String (AN)
Min 1Max 48

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

  • When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
Usage notes

Vendor assigned package ID.MAN02 at Package Level must equal the MAN02 at Line Item Level.

MAN-03
87
Marks and Numbers
Optional
String (AN)
Min 1Max 48

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

  • MAN03 and/or MAN06 are only used when sending a range(s) of ID numbers.
  • When both MAN02/MAN03 and MAN05/MAN06 are used to send ranges of ID numbers, the integrity of the two ID numbers must be maintained.
Usage notes

Manifest Number.

MAN-04
88
Marks and Numbers Qualifier
Required
Identifier (ID)

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

CP
Carrier-Assigned Package ID Number

CP if Carrier-Assigned.
CP is for small parcel tracking numbers (e.g. UPS, FedEx).

SM
Shipper Assigned

SM if Shipper-Assigned.
SM is the vendor’s BOL ID for LTL shipments.

MAN-05
87
Marks and Numbers
Required
String (AN)
Min 1Max 48

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

  • When both MAN05 and MAN06 are used, MAN05 is the starting number of a sequential range, and MAN06 is the ending number of that range.
Usage notes

Carrier assigned package tracking ID. This number should be unique per carton.

DTM
200
Detail > HL Loop > HL Loop > HL Loop > DTM

Date/Time that order was processed and 'ready to ship"

RequiredMax use 10

To specify pertinent dates and times

Usage notes

Date/Time that order was processed and 'ready to ship'.

DTMZZZ20150206120000GM~

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
Identifier (ID)

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

ZZZ
Mutually Defined
DTM-02
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

Date expressed CCYYMMDD.

DTM-03
337
Time
Optional
Time (TM)
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)

Usage notes

Time expressed HHMM.

DTM-04
623
Time Code
Optional
Identifier (ID)

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
DTM
200
Detail > HL Loop > HL Loop > HL Loop > DTM

Shipped

RequiredMax use 10

To specify pertinent dates and times

Usage notes

Date/Time that shipment was manifested.

DTM01120150206120000GM~

Example
If Time Code (DTM-04) is present, then Time (DTM-03) is required
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

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

011
Shipped
DTM-02
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

Date shipped expressed CCYYMMDD.

DTM-03
337
Time
Optional
Time (TM)
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)

Usage notes

Time shipped expressed in HHMM.

DTM-04
623
Time Code
Optional
Identifier (ID)

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
HL Loop end
HL Loop end
HL Loop end
Detail end

Summary

CTT
010
Summary > CTT

Transaction Totals

RequiredMax use 1

To transmit a hash total for a specific element in the transaction set

  • Number of line items (CTT01) is the accumulation of the number of HL segments.
    If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
Usage notes

CTT13~

Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

Usage notes

Always the number of line items.

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

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

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

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

Usage notes

Always Qty shipped.

SE
020
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

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

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

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

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

Summary end

Functional Group Trailer

RequiredMax use 1

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

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

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

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

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

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

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

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

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

A control number assigned by the interchange sender

EDI Samples

Full Floor Denial

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231101*0121*U*00401*000000001*0*T*>~
GS*SH*SENDERGS*RECEIVERGS*20231101*012106*000000001*X*004010~
ST*856*0001~
BSN*00*VendorShipID*20220524*1850*ZZZZ*72~
HL*1**O~
PRF*T7Fd9Zn55*****VendorOrderNumber~
N1*SF*WHSE*92*WHSE~
HL*2*1*I~
LIN*1*SK*1617~
SN1*1*0*EA**1*EA**IR~
SLN****1~
CTT*1*0~
SE*11*0001~
GE*1*000000001~
IEA*1*000000001~

Multiple Item Shipment Three Items Five Cartons

ISA*00* *00* *ZZ*SENDERID *ZZ*AMAZONDS *220524*2001*U*00401*000000044*0*P*>~
GS*SH*SENDERID*AMAZONDS*20220524*2001*99*X*004010~
ST*856*0001~
BSN*00*VendorShipID*20220524*2001*ZZZZ*AS~
HL*1**O~
PRF*Tx22HNv4d*****VendorOrderNumber~
N1*SF*WHSE*92*WHSE~
HL*2*1*I~
LIN*1*SK*1617~
SN1*1*3*EA**3*EA**IA~
MAN*R*0001~
HL*3*2*P~
TD1******Z*23*LB~
TD5**92*UPS_GR_RES~
MAN*R*0001*99999*SM*1ZXR28900300000001~
DTM*ZZZ*20220524*1200*GM~
DTM*011*20220524*1200*GM~
HL*3*2*P~
TD1******Z*23*LB~
TD5**92*UPS_GR_RES~
MAN*R*0002*99999*SM*1ZXR28900300000002~
DTM*ZZZ*20220524*1200*GM~
DTM*011*20220524*1200*GM~
HL*3*2*P~
TD1******Z*23*LB~
TD5**92*UPS_GR_RES~
MAN*R*0003*99999*SM*1ZXR28900300000003~
DTM*ZZZ*20220524*1200*GM~
DTM*011*20220524*1200*GM~
HL*4*1*I~
LIN*2*SK*4927~
SN1*2*2*EA**2*EA**IA~
MAN*R*0004~
HL*5*4*P~
TD1******Z*23*LB~
TD5**92*UPS_GR_RES~
MAN*R*0004*99999*SM*1ZXR28900300000004~
DTM*ZZZ*20220524*1200*GM~
DTM*011*20220524*1200*GM~
HL*6*1*I~
LIN*3*SK*9876~
SN1*3*1*EA**1*EA**IA~
MAN*R*0005~
HL*7*6*P~
TD1******Z*23*LB~
TD5**92*UPS_GR_RES~
MAN*R*0005*99999*SM*1ZXR28900300000005~
DTM*ZZZ*20220524*1200*GM~
DTM*011*20220524*1200*GM~
CTT*2*5~
SE*49*0001~
GE*1*99~
IEA*1*000000044~

Multiple Item Shipment Three Items One Carton

ISA*00* *00* *ZZ*SENDERID *ZZ*AMAZONDS *220524*2001*U*00401*000000082*0*P*>~
GS*SH*SENDERID*AMAZONDS*20220524*2001*96*X*004010~
ST*856*0001~
BSN*00*VendorShipID*20220524*2001*ZZZZ*AS~
HL*1**O~
PRF*T4Kd9Zn64*****VendorOrderNumber~
N1*SF*WHSE*92*WHSE~
HL*2*1*I~
LIN*1*SK*1617~
SN1*1*3*EA**3*EA**IA~
MAN*R*0001~
HL*3*1*I~
LIN*2*SK*4927~
SN1*2*2*EA**2*EA**IA~
MAN*R*0001~
HL*4*1*I~
LIN*3*SK*9876~
SN1*3*1*EA**1*EA**IA~
MAN*R*0001~
HL*5*4*P~
TD1******Z*23*LB~
TD5**92*UPS_GR_RES~
MAN*R*0001*99999*SM*1ZXR28900300000001~
DTM*ZZZ*20220524*1200*GM~
DTM*011*20220524*1200*GM~
CTT*3*6~
SE*25*0001~
GE*1*96~
IEA*1*000000082~

Multiple Item Shipment Three Items Three Cartons

ISA*00* *00* *ZZ*SENDERID *ZZ*AMAZONDS *220524*2001*U*00401*000000081*0*P*>~
GS*SH*SENDERID*AMAZONDS*20220524*2001*95*X*004010~
ST*856*0001~
BSN*00*VendorShipID*20220524*2001*ZZZZ*AS~
HL*1**O~
PRF*T7sd9Zn60*****VendorOrderNumber~
N1*SF*WHSE*92*WHSE~
HL*2*1*I~
LIN*1*SK*1617~
SN1*1*3*EA**3*EA**IA~
MAN*R*0001~
HL*3*2*P~
TD1******Z*23*LB~
TD5**92*UPS_GR_RES~
MAN*R*0001*99999*SM*1ZXR28900300000001~
DTM*ZZZ*20220524*1200*GM~
DTM*011*20220524*1200*GM~
HL*4*1*I~
LIN*2*SK*4927~
SN1*2*2*EA**2*EA**IA~
MAN*R*0002~
HL*5*4*P~
TD1******Z*23*LB~
TD5**92*UPS_GR_RES~
MAN*R*0002*99999*SM*1ZXR28900300000002~
DTM*ZZZ*20220524*1200*GM~
DTM*011*20220524*1200*GM~
HL*6*1*I~
LIN*3*SK*9876~
SN1*3*1*EA**1*EA**IA~
MAN*R*0003~
HL*7*6*P~
TD1******Z*23*LB~
TD5**92*UPS_GR_RES~
MAN*R*0003*99999*SM*1ZXR28900300000003~
DTM*ZZZ*20220524*1200*GM~
DTM*011*20220524*1200*GM~
CTT*3*6~
SE*37*0001~
GE*1*95~
IEA*1*000000081~

Single Item Shipment Two Cartons

ISA*00* *00* *ZZ*SENDERID *ZZ*AMAZONDS *220524*2001*U*00401*000000093*0*P*>~
GS*SH*SENDERID*AMAZONDS*20220524*2001*97*X*004010~
ST*856*0001~
BSN*00*VendorShipID*20220524*2001*ZZZZ*AS~
HL*1**O~
PRF*Tx22HNv4d*****VendorOrderNumber~
N1*SF*WHSE*92*WHSE~
HL*2*1*I~
LIN*1*SK*1617~
SN1*1*1*EA**1*EA**IA~
MAN*R*0001~
HL*3*2*P~
TD1******Z*5.5*LB~
TD5**92*UPS_GR_COM~
MAN*R*0001*9999*CP*1ZXR28900300000001~
DTM*ZZZ*20220524*1200*GM~
DTM*011*20220524*1200*GM~
HL*4*1*I~
LIN*1*SK*1617~
SN1*1*1*EA**1*EA**IA~
MAN*R*0002~
HL*5*4*P~
TD1******Z*5.5*LB~
TD5**92*UPS_GR_COM~
MAN*R*0002*9999*CP*1ZXR28900300000002~
DTM*ZZZ*20220524*1200*GM~
DTM*011*20220524*1200*GM~
CTT*1*2~
SE*27*0001~
GE*1*97~
IEA*1*000000093~

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.