X12 856 Drop Ship Ship Notice/Manifest
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.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
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
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
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- SH
- Ship Notice/Manifest (856)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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)
Assigned number originated and maintained by the sender
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
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
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Ship Notice
To transmit identifying numbers, dates, and other basic data relating to the transaction set
BSN00234567200908010142*0004
Code identifying purpose of transaction set
- 00
- Original
- 14
- Advance Notification
A unique control number assigned by the original shipper to identify a specific shipment
Note: EDI Standards state that this should be a unique number.
Unique per vendor in a given year.
Date expressed as CCYYMMDD
- BSN03 is the date the shipment transaction set is created.
Date this shipment transaction was created
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.
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
- 0004
- Shipment, Order, Item
Detail
Hierarchical Level
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.
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.
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
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.
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Information for this segment should be returned as received in TD5 on the 850.
Sample TD5 Segment
TD5B2UPSNUNS*****SD3*G2
Code describing the relationship of a carrier to a specific shipment movement
- B
- Origin/Delivery Carrier (Any Mode)
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)
Code identifying a party or other code
SCAC Code
See list of DVS Shipping Setup | EDI Routing Codes on Partners Online.
Code specifying the method or type of transportation for the shipment
The mode of transportation determines both the transportation method type code (TD504) and the REF segment qualifier (REF01).
The mode of transportation determines the transportation method type
code (TD504)
- A
- Air
- M
- Motor (Common Carrier)
TL or LTL
Used for larger quantity shipments Truckload or LTL.
SCAC code EFWW should be used with "M". - U
- Private Parcel Service
Parcel Package used for small package or small quantities.
SCAC codes UPSN, UPSM, USPS, FDE, FDEG and FXSP should be used with "U".
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Use only codes from this list. Send the code only. The description is present for information only
- AS
- White Glove Assembly with Signature Required LTL
- HD
- Home Delivery with No Signatured Required FedEx
- HDS
- Home Delivery with Signature Required FedEx
- IS
- Through the Door with Signature Required LTL
- MI
- Mail Innovations/MIP/MM UPS
- NDS
- Next Day Air with No Signature Required UPS/FedEx
- NDSS
- Next Day Air with Signature Required UPS/FedEx
- NS
- No Signature Required UPS / FedEx
- PON
- Priority Overnight FedEx
- PONS
- Priority Signature FedEx
- RS
- Room of Choice with Signature Required LTL
- SG
- Signature Required UPS / FedEx
- SMP
- SmartPost with No Signature Required FedEx
- SMPU
- Signature FedEx
- SP
- SurePost UPS
- TD
- To the Door LTL
- WS
- White Glove with Signature Required LTL
Code specifying the value of time used to measure the transit time
- SD
- Surface Days
The numeric amount of transit time
Time in transit in days.
Code indicating the level of transportation service or the billing service offered by the transportation carrier
A code must be sent. Use only codes listed. Unless previously negotiated with Target.com, DS will represent LTL and G2, ND, and SC will represent
UPS/FedEx.
- DS
- Door Service
- G2
- Standard Service
- ND
- Next Day Air
Delivery during business day hours of next business day
- NS
- Not Served
- PO
- P.O. Box/Zip Code
- SC
- Second Day Air
Delivery during business day hours no later than second business day
- SS
- 2 Day Saturday
Reference Identification
To specify identifying information
REFVR12345
Code qualifying the Reference Identification
- VR
- Vendor ID Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Target.com assigned vendor number (minimum of 4 digits).
Date/Time Reference
To specify pertinent dates and times
DTM01120090801
Name
To identify a party by type of organization, name, and code
N1SF**93TTTT
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
- 93
- Code assigned by the organization originating the transaction set
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.
A code which identifies a vendor's specific Warehouse location. A minimum of 4 characters, an EDC is an alpha and/or numeric code that may start with a 'T'.
Alpha characters must be sent in upper case.
Hierarchical Level
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.
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.
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.
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
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.
Purchase Order Reference
To provide reference to a specific purchase order
PRF*1234567890
Identifying number for Purchase Order assigned by the orderer/purchaser
Contains the Release ID. This value will be 10 digits.
Hierarchical Level
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.
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.
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.
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
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.
Item Identification
To specify basic item identification data
Note: The manufacturer style number is required to be sent on the 856.
LIN01 cannot be duplicated in the 856 - only one line 1, line 2, etc.
Vendors should not use the 856 to communicate rejected items by use of a zero quantity in the SN1. The 855 must be used to indicate rejected items. The 856 is to be used to indicate items being shipped.
If a line item is not being shipped, do NOT send an LIN and SN1 for that item.
Sample LIN Segment
LIN1SK*821927~
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
LIN01 must reflect what is received in PO101 of the 850
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN/UCC 8
- IB
- International Standard Book Number (ISBN)
- IN
- Buyer's Item Number
- SK
- Stock Keeping Unit (SKU)
- UA
- U.P.C./EAN Case Code (2-5-5)
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
A 14-digit code that uniquely identifies the manufacturer's shipping unit, including the packaging indicator and check digit; the first digit is the packaging indicator, the next two digits are the number system characters, the next five digits are the manufacturer ID number, the second five digits are the item code, and the final digit is the check digit
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
When LIN02 = SK, this contains the Manufacturer's style number
When LIN02 = IN, this contains the Target.com item number (6 - 8 digits)
When LIN02 = UP, this contains the UPC (12 digits)
When LIN02 = EO, this value is the 8 digit EAN
When LIN02 = EN, this value is the 13 digit EAN
When LIN02= IB, this value is the ISBN
When LIN02 = UK, this value is the 14 digit barcode
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN/UCC 8
- IB
- International Standard Book Number (ISBN)
- IN
- Buyer's Item Number
- SK
- Stock Keeping Unit (SKU)
- UA
- U.P.C./EAN Case Code (2-5-5)
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
A 14-digit code that uniquely identifies the manufacturer's shipping unit, including the packaging indicator and check digit; the first digit is the packaging indicator, the next two digits are the number system characters, the next five digits are the manufacturer ID number, the second five digits are the item code, and the final digit is the check digit
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
When LIN04 = SK, this contains the Manufacturer's style number
When LIN04 = IN, this contains the Target.com item number (6 - 8 digits)
When LIN04 = UP, this contains the UPC (12 digits)
When LIN04 = EO, this value is the 8 digit EAN
When LIN04 = EN, this value is the 13 digit EAN
When LIN04= IB, this value is the ISBN
When LIN04 = UK, this value is the 14 digit barcode
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN/UCC 8
- IB
- International Standard Book Number (ISBN)
- IN
- Buyer's Item Number
- SK
- Stock Keeping Unit (SKU)
- UA
- U.P.C./EAN Case Code (2-5-5)
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
A 14-digit code that uniquely identifies the manufacturer's shipping unit, including the packaging indicator and check digit; the first digit is the packaging indicator, the next two digits are the number system characters, the next five digits are the manufacturer ID number, the second five digits are the item code, and the final digit is the check digit
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
When LIN06 = SK, this contains the Manufacturer's style number
When LIN06 = IN, this contains the Target.com item number (6 - 8 digits)
When LIN06 = UP, this contains the UPC (12 digits)
When LIN06 = EO, this value is the 8 digit EAN
When LIN06 = EN, this value is the 13 digit EAN
When LIN06= IB, this value is the ISBN
When LIN06 = UK, this value is the 14 digit barcode
Item Detail (Shipment)
To specify line-item detail relative to shipment
Vendors should not use the 856 to communicate rejected items by use of a zero quantity in the SN1. The 855 must be used to indicate rejected items. The 856 is to be used to indicate items being shipped.
If a line item is not being shipped, do NOT send an LIN and SN1 for that item.
Sample SN1 Segment
SN1*2EA
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
This quantity must be greater than zero. A quantity of zero will not be accepted by Target.com.
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
Number of units shipped to date
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Product/Item Description
To describe a product or process in coded or free-form format
NOTE: The PID segment is optional, but for some vendors it needs to be included for packing slip printing.
PID Segment Example
PIDF***Description
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
A free-form description to clarify the related data elements and their content
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
In most instances there will be only one MAN segment per line.
There could be multiple if the item shipped in separate cartons or if there are multiple items on one line that shipped in separate cartons.
If multiple MAN segments are needed for 1 line number, these can be listed in the next segment below the first MAN segment.
For example, where a lamp base and shade are considered one item and the lamp base is in one carton and the lamp shade in a second.
Sample MAN Segments
MANZZ123456789876751
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.
- ZZ
- Mutually Defined
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.
Tracking Number
Summary
Transaction Totals
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.
CTT*4
Total number of line items in the transaction set
The number of HL segments present in the transaction set
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample 856
GS*SH*1112001111*AABBCC*20230802*2001*1111*X*004010~
ST*856*1111~
BSN*00*123123*20230802*1959*0004~
HL*1**S~
TD5*B*2*AAAA*M*NS*******G2~
REF*VR*345116~
DTM*011*20230802~
N1*SF*ABC Corp*93*XYZW~
HL*2*1*O~
PRF*789789789~
HL*3*2*I~
LIN*1*SK*AA-BB-CCC-C*IN*789789789*UP*789890890~
SN1**1*EA**1*EA~
PID*F****Red T-shirts~
MAN*ZZ*0809809809808~
CTT*3~
SE*16*1111~
GE*1*1111~
IEA*1*100000111~
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.