**These specifications are a base model. All customers are responsible for ensuring their map or EDI is compliant with their trading partner's most current specifications.
![]()
X12 856 Retail Ship Notice/Manifest
Revised March 4, 2024
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
Pick and Pack Structure for Bulk / Casepack Order
Pick and Pack Structure for Compound Multiple Prepack Order
Pick and Pack Structure for Inner Prepack Order
Pick and Pack Structure for Multiple Prepack Order 1
Pick and Pack Structure for Multiple Prepack Order 2
Pick and Pack Structure-Direct to Store
Pick and Pack Structure-Mark for store, ship to DC
Standard Structure for Bulk / Casepack Order
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*00* *00* *XX*XXXXXXXXXXXXXXX*12*14147844480 *231004*0500*U*00401*000000000*X*X*>~
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)
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)
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)
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)
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
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
Interchange ID Qualifier
Required
Identifier (ID)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
12
Phone (Telephone Companies)
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
Interchange Date
Required
Date (DT)
YYMMDD format
Date of the interchange
Interchange Time
Required
Time (TM)
HHMM format
Time of the interchange
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
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
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9
A control number assigned by the interchange sender
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
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
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*SH*XX*14147844480*20231004*0409*000000000*XX*004010VICS~
Functional Identifier Code
Required
Identifier (ID)
Code identifying a group of application related transaction sets
SH
Ship Notice/Manifest (856)
Application Sender's Code
Required
String (AN)
Min 2Max 15
Code identifying party sending transmission; codes agreed to by trading partners
Application Receiver's Code
Required
String (AN)
Min 2Max 15
Code identifying party receiving transmission. Codes agreed to by trading partners
Date
Required
Date (DT)
CCYYMMDD format
Date expressed as CCYYMMDD
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)
Group Control Number
Required
Numeric (N0)
Min 1Max 9
Assigned number originated and maintained by the sender
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
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
004010VICS
Heading
010
Transaction Set Header
RequiredMax use 1
To indicate the start of a transaction set and to assign a control number
Example
ST*856*0001~
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
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
020
Beginning Segment for Ship Notice
RequiredMax use 1
To transmit identifying numbers, dates, and other basic data relating to the transaction set
Usage notes
The BSN02 must be unique for each ASN sent or the entire document will be rejected.
Example
BSN*00*XXXXXX*20231004*0804*0002~
Transaction Set Purpose Code
Required
Identifier (ID)
Code identifying purpose of transaction set
00
Original
Shipment Identification
Required
String (AN)
Min 2Max 30
A unique control number assigned by the original shipper to identify a specific shipment
Date
Required
Date (DT)
CCYYMMDD format
Date expressed as CCYYMMDD
- BSN03 is the date the shipment transaction set is created.
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.
Hierarchical Structure Code
Required
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
0001
Shipment, Order, Packaging, Item
0002
Shipment, Order, Item, Packaging
Detail
HL Loop
RequiredMax >1
010
Hierarchical Level
RequiredMax use 1
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
Example
HL*1**S*1~
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.
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.
S
Shipment
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.
110
Carrier Details (Quantity and Weight)
RequiredMax use 20
To specify the transportation details relative to commodity, weight, and quantity
Example
TD1*CTN25*0000000****G*00*LB~
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
Packaging Code
Required
String (AN)
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
Part 1/2
CTN
Carton
Part 2/2
25
Corrugated or Solid
Lading Quantity
Required
Numeric (N0)
Min 1Max 7
Number of units (pieces) of the lading commodity
Weight Qualifier
Optional
Identifier (ID)
Code defining the type of weight
G
Gross Weight
Weight
Optional
Decimal number (R)
Min 1Max 10
Numeric value of weight
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
LB
Pound
120
Carrier Details (Routing Sequence/Transit Time)
RequiredMax use 12
To specify the carrier and sequence of routing and provide transit time information
Usage notes
When using a small package service provider as the carrier, TD504 should contain code U.
Example
TD5*O*2*XXXXXX*D~
If Identification Code Qualifier (TD5-02) is present, then Identification Code (TD5-03) is required
Routing Sequence Code
Optional
Identifier (ID)
Code describing the relationship of a carrier to a specific shipment movement
O
Origin Carrier (Air, Motor, or Ocean)
Identification Code Qualifier
Optional
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)
Identification Code
Optional
String (AN)
Min 2Max 80
Code identifying a party or other code
Transportation Method/Type Code
Optional
Identifier (ID)
Code specifying the method or type of transportation for the shipment
AE
Air Express
BU
Bus
C
Consolidation
CE
Customer Pickup / Customer's Expense
D
Parcel Post
E
Expedited Truck
H
Customer Pickup
L
Contract Carrier
M
Motor (Common Carrier)
R
Rail
T
Best Way (Shippers Option)
U
Private Parcel Service
130
Carrier Details (Equipment)
OptionalMax use 12
To specify transportation details relating to the equipment used by the carrier
Usage notes
This segment is only mandatory for deconsolidators that send ASNs for Import and Landed shipments.
Example
TD3*CN*XXXX*XXXXX~
If Equipment Initial (TD3-02) is present, then Equipment Number (TD3-03) is required
Equipment Description Code
Optional
Identifier (ID)
Code identifying type of equipment used for shipment
CN
Container
Equipment Initial
Optional
String (AN)
Min 1Max 4
Prefix or alphabetic part of an equipment unit's identifying number
Usage notes
Container SCAC Code (Alpha Characters of Container ID)
Equipment Number
Optional
String (AN)
Min 1Max 10
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Usage notes
Unique Container ID (Numeric Characters of Container ID)
150
Bill of Lading Number
RequiredMax use 1
To specify identifying information
Usage notes
Kohl’s requires that the Bill of Lading Number and the TP Load Number are transmitted.
The Bill of Lading number must match the number on the physical Bill of Lading that is tendered to the carrier.
Example: REFBM12345678912345678
Example
REF*BM*XXXXXX~
Variants (all may be used)
REFCarrier's Reference Number (PRO/Invoice)REFSystem Number
Reference Identification Qualifier
Required
Identifier (ID)
Code qualifying the Reference Identification
BM
Bill of Lading Number
Reference Identification
Required
String (AN)
Min 1Max 30
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
150
Carrier's Reference Number (PRO/Invoice)
OptionalMax use 1
To specify identifying information
Usage notes
The Carrier’s Reference Number is optional but preferred.
Example: REFCN293010
Example
REF*CN*XXXXXX~
Variants (all may be used)
REFBill of Lading NumberREFSystem Number
Reference Identification Qualifier
Required
Identifier (ID)
Code qualifying the Reference Identification
CN
Carrier's Reference Number (PRO/Invoice)
Reference Identification
Required
String (AN)
Min 1Max 30
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
150
System Number
OptionalMax use 1
To specify identifying information
Usage notes
Kohl’s requires that the Bill of Lading Number and the TP Load Number are transmitted.
The TP Load Number is also referred to as the ME (Mode Execution) ID in Transplace.
The ME/TP Load Number should be 9 digits. The TP load number should not contain leading zeros.
The TP load number should contain numeric values only (do not include a leading "TP").
Example: REF06706869401
Example
REF*06*XXX~
Variants (all may be used)
REFBill of Lading NumberREFCarrier's Reference Number (PRO/Invoice)
Reference Identification Qualifier
Required
Identifier (ID)
Code qualifying the Reference Identification
06
System Number
System Number / TP Load Number
Reference Identification
Required
String (AN)
Min 1Max 30
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
151
Administrative Communications Contact
RequiredMax use 3
To identify a person or office to whom administrative communications should be directed
Example
PER*IC**EM*X~
If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
Contact Function Code
Required
Identifier (ID)
Code identifying the major duty or responsibility of the person or group named
IC
Information Contact
Communication Number Qualifier
Optional
Identifier (ID)
Code identifying the type of communication number
EM
Electronic Mail
Communication Number
Optional
String (AN)
Min 1Max 80
Complete communications number including country or area code when applicable
200
Date/Time Reference
RequiredMax use 1
To specify pertinent dates and times
Example
DTM*011*20231006*0353~
Date/Time Qualifier
Required
Identifier (ID)
Code specifying type of date or time, or both date and time
011
Shipped
Date
Required
Date (DT)
CCYYMMDD format
Date expressed as CCYYMMDD
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)
N1 Ship From
RequiredMax 1
Variants (all may be used)
220
Name
RequiredMax use 1
To identify a party by type of organization, name, and code
Usage notes
Kohl’s has multiple Distribution Centers. Store to Distribution Center relationships are transmitted via the 816 - Organizational Relationship
document.
When N101 = SF,
N102 should be the vendor/consolidator name
N103 should be 91
N104 should be the Vendor Location ID if there is more than one shipping location. If there is only one shipping location, this field can contain the vendor name.
Example
N1*SF*XXXXXX*91*XXX~
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
Entity Identifier Code
Required
Identifier (ID)
Code identifying an organizational entity, a physical location, property or an individual
SF
Ship From
Name
Optional
String (AN)
Min 1Max 60
Free-form name
Usage notes
Kohl’s Vendor Name
Identification Code Qualifier
Optional
Identifier (ID)
Code designating the system/method of code structure used for Identification Code (67)
91
Assigned by Seller or Seller's Agent
92
Assigned by Buyer or Buyer's Agent
Identification Code
Optional
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
Kohl’s 5-digit DC Number
Kohl’s 5-digit Store Number
Vendor’s Location ID or Vendor/Consolidator Name
240
Address Information
RequiredMax use 2
To specify the location of the named party
Usage notes
The N3 segment needs to be sent if the previous N1 segment contains Ship From information.
Example
N3*XXX*XXXXX~
Address Information
Required
String (AN)
Min 1Max 55
Address information
Address Information
Optional
String (AN)
Min 1Max 55
Address information
250
Geographic Location
RequiredMax use 1
To specify the geographic place of the named party
Usage notes
The N3 segment needs to be sent if the previous N1 segment contains Ship From information.
Example
N4*XXXXXX*XX*XXXX~
City Name
Optional
String (AN)
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.
State or Province Code
Optional
Identifier (ID)
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.
Postal Code
Optional
Identifier (ID)
Min 3Max 15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
N1 Ship To
RequiredMax 1
Variants (all may be used)
220
Name
RequiredMax use 1
To identify a party by type of organization, name, and code
Usage notes
The N104 field may contain a store number only if the ASN is for a direct to store shipment. Mark for store shipments need to be sent with the DC
number.
When N101 = ST,
N102 should be Kohl’s
N103 should be 92
N104 should be a Kohl’s 5-digit Distribution Center number or 5-digit Store number
Example
N1*ST*XXX*91*XXX~
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
Entity Identifier Code
Required
Identifier (ID)
Code identifying an organizational entity, a physical location, property or an individual
ST
Ship To
Name
Optional
String (AN)
Min 1Max 60
Free-form name
Identification Code Qualifier
Optional
Identifier (ID)
Code designating the system/method of code structure used for Identification Code (67)
91
Assigned by Seller or Seller's Agent
92
Assigned by Buyer or Buyer's Agent
Identification Code
Optional
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
Kohl’s 5-digit DC Number
Kohl’s 5-digit Store Number
Vendor’s Location ID or Vendor/Consolidator Name
240
Address Information
OptionalMax use 2
To specify the location of the named party
Example
N3*XXXXX*XXXXX~
Address Information
Required
String (AN)
Min 1Max 55
Address information
Address Information
Optional
String (AN)
Min 1Max 55
Address information
250
Geographic Location
OptionalMax use 1
To specify the geographic place of the named party
Example
N4*XXXXXX*XX*XXX~
City Name
Optional
String (AN)
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.
State or Province Code
Optional
Identifier (ID)
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.
Postal Code
Optional
Identifier (ID)
Min 3Max 15
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
HL Loop
RequiredMax >1
010
Hierarchical Level
RequiredMax use 1
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
Example
HL*2*1*O*1~
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.
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.
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
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.
050
Purchase Order Reference
RequiredMax use 1
To provide reference to a specific purchase order
Usage notes
The Purchase Order number is required and must match the number transmitted on Kohl’s 850 or vendor’s 855.
Example
PRF*XX~
Purchase Order Number
Required
String (AN)
Min 1Max 22
Identifying number for Purchase Order assigned by the orderer/purchaser
110
Carrier Details (Quantity and Weight)
RequiredMax use 20
To specify the transportation details relative to commodity, weight, and quantity
Usage notes
The TD102 field should contain the store’s carton count if the ASN is for a mark for store order. The TD102 field should contain the purchase
order’s carton count if the ASN is for a non mark for store order.
Example
TD1*CTN25*00~
Packaging Code
Required
String (AN)
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
Part 1/2
CTN
Carton
Part 2/2
25
Corrugated or Solid
Lading Quantity
Required
Numeric (N0)
Min 1Max 7
Number of units (pieces) of the lading commodity
150
Reference Identification
OptionalMax use >1
To specify identifying information
Example
REF*DP*XX~
Reference Identification Qualifier
Required
Identifier (ID)
Code qualifying the Reference Identification
DP
Department Number
Reference Identification
Required
String (AN)
Min 1Max 30
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
N1 Loop
RequiredMax >1
220
Name
RequiredMax use 1
To identify a party by type of organization, name, and code
Usage notes
Kohl’s has multiple Distribution Centers. Store to Distribution Center associations are transmitted via the 816 - Organizational Relationship
document.
When N101 = BY,
N102 should be KOHLS
N103 should be 92
N104 should be a Kohl’s 5-digit Distribution Center number for bulk and prepack shipments or 5-digit Store number for mark for store
shipments.
Example
N1*BY**92*XXXXXX~
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
Entity Identifier Code
Required
Identifier (ID)
Code identifying an organizational entity, a physical location, property or an individual
BY
Buying Party (Purchaser)
Identification Code Qualifier
Optional
Identifier (ID)
Code designating the system/method of code structure used for Identification Code (67)
92
Assigned by Buyer or Buyer's Agent
Identification Code
Optional
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
Kohl’s 5-Digit DC Number
Kohl’s 5-Digit Store Number
HL Item
OptionalMax >1
Variants (all may be used)
010
Hierarchical Level
RequiredMax use 1
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
Example
HL*3*2*I*1~
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.
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.
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
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.
020
Item Identification
RequiredMax use 1
To specify basic item identification data
Usage notes
The UPC or EAN is required and must match the UPC or EAN on Kohl’s 850 or vendor’s 855.
Kohl’s recommends when shipping an assortment that the LIN03 reflect the pack UPC number. The SN103 needs to be AS for assortment. The
SLN/Item loops would contain the item UPC numbers or EANs.
Example
LIN**UP*XXXXXX~
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.
EN
European Article Number (EAN) (2-5-5-1)
UP
U.P.C. Consumer Package Code (1-5-5-1)
Product/Service ID
Required
String (AN)
Min 1Max 48
Identifying number for a product or service
030
Item Detail (Shipment)
RequiredMax use 1
To specify line-item detail relative to shipment
Usage notes
For the Standard Carton Structure, the SN102 should be the total number of eaches per UPC shipped.
Example
SN1**000*EA~
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
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.
AS
Assortment
EA
Each
040
Subline Item Detail
OptionalMax use 1000
To specify product subline detail item data
Usage notes
The SLN10 must contain the item UPC numbers or EAN’s within the pack.
Example
SLN*X**S*0000000000000*EA****UP*XXX~
If either Product/Service ID Qualifier (SLN-09) or Product/Service ID (SLN-10) is present, then the other is required
Assigned Identification
Required
String (AN)
Min 1Max 20
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Relationship Code
Required
Identifier (ID)
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
I
Included
S
Substituted
Quantity
Optional
Decimal number (R)
Min 1Max 15
Numeric value of quantity
Composite Unit of Measure
RequiredMax use 1
To identify a composite unit of measure (See Figures Appendix for examples of use)
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
EA
Each
Product/Service ID Qualifier
Optional
Identifier (ID)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
EN
European Article Number (EAN) (2-5-5-1)
UP
U.P.C. Consumer Package Code (1-5-5-1)
Product/Service ID
Optional
String (AN)
Min 1Max 48
Identifying number for a product or service
HL Loop
RequiredMax >1
010
Hierarchical Level
RequiredMax use 1
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
Example
HL*4*3*P*0~
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.
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.
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
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.
060
Item Physical Details
RequiredMax use 1
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Usage notes
Kohl’s does not require the PO4 segment if the ASN is in the Pick and Pack Structure.
The PO4 segment is mandatory if the ASN is in the Standard Structure.
The PO414 is required if there are inner containers in each outer carton. If there are no inner containers, send only the PO401.
Examples of an inner container can be bundles, polybags or inner cartons.
Example:
The carton contains 2 inner containers, each of which has 4 items
PO42************4
Example
PO4*00*********00000*00*0000000*EA*00000~
If Length (PO4-10) is present, then Unit or Basis for Measurement Code (PO4-13) is required
If Width (PO4-11) is present, then Unit or Basis for Measurement Code (PO4-13) is required
If Height (PO4-12) is present, then Unit or Basis for Measurement Code (PO4-13) is required
If Unit or Basis for Measurement Code (PO4-13) is present, then at least one of Length (PO4-10), Width (PO4-11) or Height (PO4-12) is required
Pack
Optional
Numeric (N0)
Min 1Max 6
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Length
Optional
Decimal number (R)
Min 1Max 8
Largest horizontal dimension of an object measured when the object is in the upright position
Width
Optional
Decimal number (R)
Min 1Max 8
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Height
Optional
Decimal number (R)
Min 1Max 8
Vertical dimension of an object measured when the object is in the upright position
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
- PO413 defines the unit of measure for PO410, PO411, and PO412.
EA
Each
Inner Pack
Optional
Numeric (N0)
Min 1Max 6
The number of eaches per inner container
100
Marking, Packaging, Loading
OptionalMax use 25
To describe marking, packaging, loading, and unloading requirements
Example
PKG*S*36*VI*XXXXXX~
If Packaging Description Code (PKG-04) is present, then Agency Qualifier Code (PKG-03) is required
Item Description Type
Optional
Identifier (ID)
Code indicating the format of a description
- If PKG01 equals "F", then PKG05 is used. If PKG01 equals "S", then PKG04 is used. If PKG01 equals "X", then both PKG04 and PKG05 are used.
S
Structured (From Industry Code List)
Packaging Characteristic Code
Optional
Identifier (ID)
Code specifying the marking, packaging, loading and related characteristics being described
36
Package Specifications
Agency Qualifier Code
Optional
Identifier (ID)
Code identifying the agency assigning the code values
- Use PKG03 to indicate the organization that publishes the code list being referred to.
VI
Voluntary Inter-Industry Commerce Standard (VICS) EDI
Packaging Description Code
Optional
String (AN)
Min 1Max 7
A code from an industry code list which provides specific data about the marking, packaging or loading and unloading of a product
- PKG04 should be used for industry-specific packaging description codes.
Usage notes
First character:
L Logical Container
P Physical Container
Last 2 characters:
01 Carton
02 Carton, Hanging Garments
03 Carton, With Hangers (not hanging)
04 Carton, With Identifiable Inner Packs
05 Carton, With Unidentifiable Inner Packs
190
Marks and Numbers
RequiredMax use >1
To indicate identifying marks and numbers for shipping containers
Usage notes
The MAN04 and MAN05 fields only need to be sent for Outlet store shipments.
Example
MAN*GM*X**CP*XXXXXX~
If either Marks and Numbers Qualifier (MAN-04) or Marks and Numbers (MAN-05) is present, then the other is required
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.
GM
SSCC-18 and Application Identifier
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.
Marks and Numbers Qualifier
Optional
Identifier (ID)
Code specifying the application or source of Marks and Numbers (87)
CP
Carrier-Assigned Package ID Number
Marks and Numbers
Optional
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.
HL Pack
OptionalMax >1
Variants (all may be used)
010
Hierarchical Level
RequiredMax use 1
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
Example
HL*3*2*P*1~
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.
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.
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
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.
100
Marking, Packaging, Loading
OptionalMax use 25
To describe marking, packaging, loading, and unloading requirements
Example
PKG*S*36*VI*XXXXXX*XXXXXX~
If Packaging Description Code (PKG-04) is present, then Agency Qualifier Code (PKG-03) is required
If Description (PKG-05) is present, then Item Description Type (PKG-01) is required
At least one of Packaging Description Code (PKG-04) or Description (PKG-05) is required
Item Description Type
Optional
Identifier (ID)
Code indicating the format of a description
- If PKG01 equals "F", then PKG05 is used. If PKG01 equals "S", then PKG04 is used. If PKG01 equals "X", then both PKG04 and PKG05 are used.
S
Structured (From Industry Code List)
Packaging Characteristic Code
Optional
Identifier (ID)
Code specifying the marking, packaging, loading and related characteristics being described
36
Package Specifications
Agency Qualifier Code
Optional
Identifier (ID)
Code identifying the agency assigning the code values
- Use PKG03 to indicate the organization that publishes the code list being referred to.
VI
Voluntary Inter-Industry Commerce Standard (VICS) EDI
Packaging Description Code
Optional
String (AN)
Min 1Max 7
A code from an industry code list which provides specific data about the marking, packaging or loading and unloading of a product
- PKG04 should be used for industry-specific packaging description codes.
Description
Optional
String (AN)
Min 1Max 80
A free-form description to clarify the related data elements and their content
- Special marking or tagging data can be given in PKG05 (description).
190
Marks and Numbers
RequiredMax use >1
To indicate identifying marks and numbers for shipping containers
Usage notes
The MAN04 and MAN05 fields only need to be sent for Outlet store shipments.
Example
MAN*GM*XXXX**CP*XXX~
If either Marks and Numbers Qualifier (MAN-04) or Marks and Numbers (MAN-05) is present, then the other is required
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.
GM
SSCC-18 and Application Identifier
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.
Marks and Numbers Qualifier
Optional
Identifier (ID)
Code specifying the application or source of Marks and Numbers (87)
CP
Carrier-Assigned Package ID Number
Marks and Numbers
Optional
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.
HL Loop
RequiredMax >1
010
Hierarchical Level
RequiredMax use 1
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
Example
HL*4*3*I*0~
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.
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.
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
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.
020
Item Identification
RequiredMax use 1
To specify basic item identification data
Usage notes
The UPC or EAN is required and must match the UPC or EAN on Kohl’s 850 or vendor’s 855.
Kohl’s recommends when shipping an assortment that the LIN03 reflect the pack UPC number. The SN103 needs to be AS for assortment. The
SLN/Item loops would contain the item UPC numbers or EANs.
Example
LIN**UP*XXXX~
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.
EN
European Article Number (EAN) (2-5-5-1)
UP
U.P.C. Consumer Package Code (1-5-5-1)
Product/Service ID
Required
String (AN)
Min 1Max 48
Identifying number for a product or service
030
Item Detail (Shipment)
RequiredMax use 1
To specify line-item detail relative to shipment
Usage notes
For the Pick and Pack Structure, when the SN103 is AS the SN102 must be the total number of packs in the carton.
For the Pick and Pack Structure, when the SN103 is EA the SN102 must be the total number of units per carton.
Example
SN1**000*EA~
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
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.
AS
Assortment
EA
Each
040
Subline Item Detail
OptionalMax use 1000
To specify product subline detail item data
Usage notes
The SLN10 must contain the item UPC numbers or EAN’s within the pack.
Example
SLN*XX**S*000000000*EA****EN*XXXX~
If either Product/Service ID Qualifier (SLN-09) or Product/Service ID (SLN-10) is present, then the other is required
Assigned Identification
Required
String (AN)
Min 1Max 20
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Relationship Code
Required
Identifier (ID)
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
I
Included
S
Substituted
Quantity
Optional
Decimal number (R)
Min 1Max 15
Numeric value of quantity
Composite Unit of Measure
RequiredMax use 1
To identify a composite unit of measure (See Figures Appendix for examples of use)
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
EA
Each
Product/Service ID Qualifier
Optional
Identifier (ID)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
EN
European Article Number (EAN) (2-5-5-1)
UP
U.P.C. Consumer Package Code (1-5-5-1)
Product/Service ID
Optional
String (AN)
Min 1Max 48
Identifying number for a product or service
060
Item Physical Details
OptionalMax use 1
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Usage notes
This segment can be sent only for the Pick and Pack Structure.
The PO414 is required if there are inner containers in each outer carton. If there are no inner containers, send only the PO401.
Examples of an inner container can be bundles, polybags or inner cartons.
Example:
The carton contains 2 inner containers, each of which has 4 items
PO42************4
Example
PO4*0*************000~
Pack
Optional
Numeric (N0)
Min 1Max 6
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Inner Pack
Optional
Numeric (N0)
Min 1Max 6
The number of eaches per inner container
Summary
010
Transaction Totals
RequiredMax use 1
To transmit a hash total for a specific element in the transaction set
- Number of line items (CTT01) is the accumulation of the number of HL segments.
If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
Example
CTT*0~
Number of Line Items
Required
Numeric (N0)
Min 1Max 6
Total number of line items in the transaction set
Usage notes
The number of HL segments present in the transaction set.
020
Transaction Set Trailer
RequiredMax use 1
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Example
SE*0000000*0001~
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10
Total number of segments included in a transaction set including ST and SE segments
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
Functional Group Trailer
RequiredMax use 1
To indicate the end of a functional group and to provide control information
Example
GE*00000*0000000~
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
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*00000*000000000~
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5
A count of the number of functional groups included in an interchange
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9
A control number assigned by the interchange sender
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article