X12 856 Retail 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
*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
Pick Pack format is typically used when different SKUs are packed.
Standard Pack format used when identical SKUs are packed.
See Business Examples on POL (www.partnersonline.com) for formatting differences between pick/pack and standard pack.
Sample BSN Segment
BSN002345672000060101420001 (Pick Pack Format)
BSN003456782000060512340002 (Standard Pack Format)
Code identifying purpose of transaction set
- 00
- Original
- 07
- Duplicate
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. Target
applications have been written based on that.
This number will be used to differentiate multiple 856s received from a
supplier.
This number should be different than the Purchase Order or Bill of Lading number.
Date expressed as CCYYMMDD
- BSN03 is the date the shipment transaction set is 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
- 0001
- Shipment, Order, Packaging, Item
Pick & Pack Format - allows for multiple SKUs on pallet
- 0002
- Shipment, Order, Item, Packaging
Standard Pack Format - used when identical SKUs are packed
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
Correct information is necessary for matching to the corresponding EDI 214 Carrier Shipment Status Message.
Sample TD5 Segments
TD5B2SOCSCConsolidator Name (consolidator example)
TD5B2MIIWM (truckload or LTL carrier example)
TD5B2UPSNUUPS (private parcel example)
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
Target requires the 4-character alpha code.
The SCAC code must be sent in upper case.
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).
Mode of Transportation:
Air:
TD504 = A
REF01 = CN
REF02 = Carrier Ref.# (Carrier Tracking Number)Consolidation:
TD504 = C
REF01 = MB (Mandatory)
REF02 = Master Bill of Lading#
REF01 = BM (Optional)
REF02 = Underlying (When used with MB)
TL or LTL:
TD504 = M
REF01 = BM
REF02 = Bill of Lading #Private Parcel:
TD504 = U
REF01 = CN
REF02 = Carrier Ref.# (Carrier Tracking Number)
- A
- Air
- C
- Consolidation
- M
- Motor (Common Carrier)
Truckload or LTL
- U
- Private Parcel Service
Small Package Shipments
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Reference Identification
To specify identifying information
*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
This segment is critical for matching the Carrier's EDI 214 Carrier Status Message with your EDI 856 Ship Notice Message.
Target requires:
A UNIQUE Bill of Lading (BOL) number for each shipment. Use the GS1 US (VICS) standard Bill of Lading document. Target strongly recommends the use of the GS1 US (VICS) standard 17-digit Bill of Lading number format.
- When routing via Truckload (TL) or Less than Truckload (LTL) carrier, one unique BOL # is required per Target ship to location. If constraints require BOL per Purchase Order, then a Master BOL must be used to summarize the underlying bills of lading.
When a Master BOL# is used, be sure to transmit this number on the 856. The Master BOL# must be passed to the carrier as the Shipment BOL # for the corresponding Carrier EDI transmission.
- When routing to a Target consolidator, a Master BOL# must be used and sent on all 856's created per Purchase Order ship to location. The Master BOL# must reflect the actual BOL# given to the carrier on the GS1 US (VICS) BOL. Do not transmit the individual (underlying) Bill of Lading numbers on the 856.
Sample REF Segment
REFBM06141411234567890 (GS1 17-digit Bill of Lading number)
Does your shipment require a Master Bill of Lading#? Read and review above notes for proper Bill of Lading usage.
Code qualifying the Reference Identification
The mode of transportation determines both the transportation method type code (TD504) and the REF segment qualifier (REF01).
Mode of Transportation:
Air:
TD504 = A
REF01 = CN
REF02 = Carrier Ref.# (Carrier Tracking Number)Consolidation:
TD504 = C
REF01 = MB (Mandatory)
REF02 = Master Bill of Lading#
REF01 = BM (Optional)
REF02 = Underlying (When used with MB)
TL or LTL:
TD504 = M
REF01 = BM
REF02 = Bill of Lading #Private Parcel:
TD504 = U
REF01 = CN
REF02 = Carrier Ref.# (Carrier Tracking Number)
- BM
- Bill of Lading Number
Required when shipping via motor carrier (TD504 equals "M").
- CN
- Carrier's Reference Number (PRO/Invoice)
Required when shipping parcel package shipments (TD504 equals "U" or "A").
- MB
- Master Bill of Lading
Master Bill of Lading required for all consolidated shipments (TD504 equals "C").
Note: if the Master Bill of Lading (MB) and Bill of Lading (BM) are both sent, Target will only use the Master Bill of Lading (MB) number.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A unique Bill of Lading (BOL) number for each shipment is required. When the mode of transportation is for Consolidation, a unique Master BOL# is required for all ship to locations on that shipment.
Name
To identify a party by type of organization, name, and code
At least one N1 segment, containing an N101 of ST, is required.
Sample N1 Segment
N1ST**920552
N1ST**929998 (Direct Ship to Guest)
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
Four digit location number.
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.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
NOTE: Starting in Dec 2017, Target will start phasing in a new PO format. The new format removes the 4 digit department number prefix and the purchase order number will be moving from 7 digits to 11 digits. No changes are being made to the location number.
During this transition, your company needs to be able to receive both PO formats, as both may be received during transition. The same PO format received from Target will need to be returned on all EDI related documents for that PO to ensure no business interruption.
New Purchase Order Number Format:
12345678901-1234
Target Stores:
Sample PRF Segment
PRF0040-0434720
PRF0040-0434720-0551
PRF12345678909
PRF12345678909-0551
Identifying number for Purchase Order assigned by the orderer/purchaser
Identifying number sent on 850 Purchase Order in the BEG03 segment. Send back what was received in the BEG03 segment on 850 Purchase Order.
Product/Item Description
To describe a product or process in coded or free-form format
PIDS**VIFL
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.
- S
- Structured (From Industry Code List)
Code identifying the agency assigning the code values
- Use PID03 to indicate the organization that publishes the code list being referred to.
- VI
- Voluntary Inter-Industry Commerce Standard (VICS) EDI
A code from an industry code list which provides specific data about a product characteristic
- PID04 should be used for industry-specific product description codes.
- FL
- Compliant with Fair Labor Standards Act
- ZZ
- FLSA Non-Compliance or Not applicable.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Note: TD101 must be 5 characters. If only CTN is sent, it should be followed by 2 spaces.
Sample TD1 Segments
TD1CTN 60
TD1CTN2560
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
This data element contains 2 parts:
Part 1 is comprised of the first 3 positions. For Target, Part 1 must always contain the alpha code CTN.
Part 2 is comprised of the final 2 positions and must always be numeric. For Target, the three valid codes for Part 2 are listed below. Spaces may also be used in place of the valid codes. See Sample TD1 segments above.
CTN Carton
25 - Carton Corrugated
31 - Carton Fiber
76 - Carton Paper
Number of units (pieces) of the lading commodity
Name
To identify a party by type of organization, name, and code
Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
Sample N1 Segment
N1BY**920552
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
This will be a four digit location number.
*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
The Tare level must be used when the Pack level MAN segment contains the 'UC' (GTIN-14, SCC-14) or 'UP'/'EN' (GTIN-12/13 or U.P.C./EAN).
The Tare level is optional when MAN01=GM or AA at the pack level.
Sample HL (Tare level) Segment
HL32*T
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.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data
*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
NOTE: IN will be used as an item identifier for Target in the future. When this item identifier is sent by Target, your system must be capable of sending it back on inbound EDI documents to Target.
Target Stores:
Always send either the Target DPCI number with a CB qualifier or the corresponding UPC number with a UP qualifier for item.
Sample LIN Segments
LINCB019060025UP*039800088628
LINUP039800088628
LIN**CB019060025
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
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.
- CB
- Buyer's Catalog Number
Target 9 digit DPCI number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN-8
- IN
- Buyer's Item Number
Target Corporation Item Number (TCIN)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CB
- Buyer's Catalog Number
Target 9 digit DPCI number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN-8
- IN
- Buyer's Item Number
Target Corporation Item Number (TCIN)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CB
- Buyer's Catalog Number
Target 9 digit DPCI number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN-8
- IN
- Buyer's Item Number
Target Corporation Item Number (TCIN)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Item Detail (Shipment)
To specify line-item detail relative to shipment
*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
Sample SN1 Segment
SN1*75EA
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
The value stated in SN102 is dependent upon the 856 structure (Standard or Pick Pack) and the type of carton identification number being sent in the MAN segment at the Pack level.
Pick Pack Structure:
When a SSCC is sent for every carton, the value is equal to the total number of eaches tied to the unique SSCC sent at the corresponding Pack level. If the unit of measure is cases (CA), then the value is one.
When a GTIN-14 (SCC 14 digit) is sent at the Pack level, then the value is equal to the total number of eaches or cases shipped for the line item.
Do not repeat Pack/Item loops for each carton shipped that is tied to the GTIN referenced in the Pack level.
When doing MAN segment ranges at the Pack level, then the value is equal to the total number of eaches shipped within the range.
Standard Structure:
The value is equal to the total number of eaches or cases shipped for a line item where the respective bar code will report to the parent item level.
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.
If the product was ordered in pounds, Target will only accept the LB qualifier.
If the product was ordered in eaches, Target will accept EA qualifier.
If the product was ordered in cases, Target will accept CA qualifier.
- CA
- Case
- EA
- Each
- LB
- Pound
Pound is only allowed on Food Distribution Center shipments. The LB qualifier is interchangeable with the EA qualifier within Target's application systems for non-random weight food items.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
NOTE: This segment is required for Standard Pack Structure.
If sending Pick and Pack Structure, Target prefers to receive the PO4 at the Pack Level.
If it's not possible to send the PO4 at the Pack Level, the PO4 must be sent at the Item Level.
PO401 =
The number of total units within the carton - OR -
The number of inner packs within the outer carton.
(The latter applies if PO414 was sent on the PO.)
PO414 = The number of units within an inner pack.
If the PO414 is sent on the PO, it is required to be sent back/returned on the EDI 856.
If the PO414 is not sent on the PO, do not send back/return a PO4*14 on the EDI 856.
Sample PO4 Segments:
PO412 (no inner packs) - Casepack = 12 individual units
PO44*************6 - (inner packs, within a carton) Casepack = 24, with 4 inner packs of 6 units each
The number of inner containers, or number of eaches if there are no inner containers, per outer container
The number of eaches per inner container
If inner cartons are being sent, this must represent the number of selling units within one inner pack.
If the PO414 element is received on the PO, then it is required to be sent back on the 856.
Reference Identification
To specify identifying information
Sample REF Segment
REFLT123456789
Standard Pack Format:
Lot number accepted at item level only.
Pick Pack Format:
Prefer lot number at pack level, will accept at item level.
Code qualifying the Reference Identification
- LT
- Lot Number
Lot number required based on Food Distribution Center Shipments, as these are designated by Target as lot number controlled product.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time Reference
To specify pertinent dates and times
Sample DTM Segment
DTM03620070430
Standard Pack Format:
Expiration date accepted at item level only.
Pick Pack Format:
Prefer expiration date at pack level, will accept at item level.
Code specifying type of date or time, or both date and time
- 036
- Expiration
Expiration date required based on Food Distribution Center Shipments, as these are designated by Target as expiration date controlled product.
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.
- P
- Pack
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 Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
NOTE: Target prefers receiving the PO4 at the pack level for the pick/pack structure.
If it's not possible to send at the pack level, the PO4 must be sent at the Item Level.
If using standard structure, the PO4 is required at the Item Level.
PO401 =
The number of total units within the carton - OR -
The number of inner packs within the outer carton.
(The latter applies if PO414 was sent on the PO.)
PO414 = The number of units within an inner pack.
If the PO414 is sent on the PO, it is required to be sent back/returned on the EDI 856.
If the PO414 is not sent on the PO, do not send back/return a PO414 on the EDI 856.
Sample PO4 Segments:
PO412 (no inner packs) - Casepack = 12 individual units
PO44*************6 - (inner packs, within a carton) Casepack = 24, with 4 inner packs of 6 units each
The number of inner containers, or number of eaches if there are no inner containers, per outer container
The number of eaches per inner container
If inner cartons are being sent, this must represent the number of selling units within one inner pack.
If the PO414 element is received on the PO, then it is required to be sent back on the 856.
Reference Identification
To specify identifying information
Sample REF Segment
REFLT123456789
Standard Pack Format:
Lot number accepted at item level only.
Pick Pack Format:
Prefer lot number at pack level, will accept at item level.
Code qualifying the Reference Identification
- LT
- Lot Number
Lot number required based on Food Distribution Center Shipments, as these are designated by Target as lot number controlled product.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
MAN01 or MAN04 must be 'GM' or 'AA' at Pack Level when a Tare Segment is not present.
When used together, MAN01 and MAN04 CANNOT be the same (i.e. if MAN01 is 'GM', MAN04 cannot be GM).
Sample MAN Segments:
MANGM00000123456789876754 (Must be a unique # per shipping container)
MANAA000123456789876754 (Must be a unique # per shipping container)
GTIN-14: 14 digit Product Identification Code (aka SCC-14)
MANUC10012345655668 (14-digit carton case code)
GTIN-12/13: U.P.C./EAN on selling unit. Only valid if selling unit is shipping unit and case-pack equals 1
MANUP000123456784 (12-digit selling unit UPC code)
Ranging MAN Segments
MANGM00000123456789987659*00000123456789988756
MAN02 = First carton barcode of an item
MAN03 = Last carton barcode of same item
MANAA000001234567899876*000001234567899887
MAN02 = First carton barcode of an item
MAN03 = Last carton barcode of same item
See "Ship Carton and Pallet Markings Domestic" on POL (www.partnersonline.com) for labeling requirements.
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.
- AA
- SSCC-18
- GM
- SSCC-18 and Application Identifier
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.
When GM is present in MAN01, the value in this field must be 20 digits.
When AA is present in MAN01, the value in this field must be 18 digits.
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.
Code specifying the application or source of Marks and Numbers (87)
- AA
- SSCC-18
- GM
- SSCC-18 and Application Identifier
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.
Marks and numbers used to identify a shipment or parts of a shipment
Date/Time Reference
To specify pertinent dates and times
Sample DTM Segment
DTM03620070430
Standard Pack Format:
Expiration date accepted at item level only.
Pick Pack Format:
Prefer expiration date at pack level, will accept at item level.
Code specifying type of date or time, or both date and time
- 036
- Expiration
Expiration date required based on Food Distribution Center Shipments, as these are designated by Target as expiration date controlled product.
*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
The Tare level must be used when the Pack level MAN segment contains the 'UC' (GTIN-14, SCC-14) or 'UP'/'EN' (GTIN-12/13 or U.P.C./EAN).
The Tare level is optional when MAN01=GM or AA at the pack level.
Sample HL (Tare level) Segment
HL32*T
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.
- P
- Pack
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.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
NOTE: Target prefers receiving the PO4 at the pack level for the pick/pack structure.
If it's not possible to send at the pack level, the PO4 must be sent at the Item Level.
If using standard structure, the PO4 is required at the Item Level.
PO401 =
The number of total units within the carton - OR -
The number of inner packs within the outer carton.
(The latter applies if PO414 was sent on the PO.)
PO414 = The number of units within an inner pack.
If the PO414 is sent on the PO, it is required to be sent back/returned on the EDI 856.
If the PO414 is not sent on the PO, do not send back/return a PO414 on the EDI 856.
Sample PO4 Segments:
PO412 (no inner packs) - Casepack = 12 individual units
PO44*************6 - (inner packs, within a carton) Casepack = 24, with 4 inner packs of 6 units each
The number of inner containers, or number of eaches if there are no inner containers, per outer container
A generic number
- PO418 is the number of packages in this layer.
If inner cartons are being sent, this must represent the number of selling units within one inner pack.
If the PO414 element is received on the PO, then it is required to be sent back on the 856.
Reference Identification
To specify identifying information
Sample REF Segment
REFLT123456789
Standard Pack Format:
Lot number accepted at item level only.
Pick Pack Format:
Prefer lot number at pack level, will accept at item level.
Code qualifying the Reference Identification
- LT
- Lot Number
Lot number required based on Food Distribution Center Shipments, as these are designated by Target as lot number controlled product.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
MAN01 or MAN04 must be 'GM' or 'AA' at Pack Level when a Tare Segment is not present.
When used together, MAN01 and MAN04 CANNOT be the same (i.e. if MAN01 is 'GM', MAN04 cannot be GM).
Sample MAN Segments:
MANGM00000123456789876754 (Must be a unique # per shipping container)
MANAA000123456789876754 (Must be a unique # per shipping container)
GTIN-14: 14 digit Product Identification Code (aka SCC-14)
MANUC10012345655668 (14-digit carton case code)
GTIN-12/13: U.P.C./EAN on selling unit. Only valid if selling unit is shipping unit and case-pack equals 1
MANUP000123456784 (12-digit selling unit UPC code)
Ranging MAN Segments
MANGM00000123456789987659*00000123456789988756
MAN02 = First carton barcode of an item
MAN03 = Last carton barcode of same item
MANAA000001234567899876*000001234567899887
MAN02 = First carton barcode of an item
MAN03 = Last carton barcode of same item
See "Ship Carton and Pallet Markings Domestic" on POL (www.partnersonline.com) for labeling requirements.
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.
- AA
- SSCC-18
- GM
- SSCC-18 and Application Identifier
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.
When GM is present in MAN01, the value in this field must be 20 digits.
When AA is present in MAN01, the value in this field must be 18 digits.
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.
Code specifying the application or source of Marks and Numbers (87)
- AA
- SSCC-18
- GM
- SSCC-18 and Application Identifier
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.
Marks and numbers used to identify a shipment or parts of a shipment
Date/Time Reference
To specify pertinent dates and times
Sample DTM Segment
DTM03620070430
Standard Pack Format:
Expiration date accepted at item level only.
Pick Pack Format:
Prefer expiration date at pack level, will accept at item level.
Code specifying type of date or time, or both date and time
- 036
- Expiration
Expiration date required based on Food Distribution Center Shipments, as these are designated by Target as expiration date controlled product.
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
*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
NOTE: IN will be used as an item identifier for Target in the future. When this item identifier is sent by Target, your system must be capable of sending it back on inbound EDI documents to Target.
Target Stores:
Always send either the Target DPCI number with a CB qualifier or the corresponding UPC number with a UP qualifier for item.
Sample LIN Segments
LINCB019060025UP*039800088628
LINUP039800088628
LIN**CB019060025
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
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.
- CB
- Buyer's Catalog Number
Target 9 digit DPCI number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN-8
- IN
- Buyer's Item Number
Target Corporation Item Number (TCIN)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CB
- Buyer's Catalog Number
Target 9 digit DPCI number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN-8
- IN
- Buyer's Item Number
Target Corporation Item Number (TCIN)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CB
- Buyer's Catalog Number
Target 9 digit DPCI number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN-8
- IN
- Buyer's Item Number
Target Corporation Item Number (TCIN)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Item Detail (Shipment)
To specify line-item detail relative to shipment
*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
Sample SN1 Segment
SN1*75EA
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
The value stated in SN102 is dependent upon the 856 structure (Standard or Pick Pack) and the type of carton identification number being sent in the MAN segment at the Pack level.
Pick Pack Structure:
When a SSCC is sent for every carton, the value is equal to the total number of eaches tied to the unique SSCC sent at the corresponding Pack level. If the unit of measure is cases (CA), then the value is one.
When a GTIN-14 (SCC 14 digit) is sent at the Pack level, then the value is equal to the total number of eaches or cases shipped for the line item.
Do not repeat Pack/Item loops for each carton shipped that is tied to the GTIN referenced in the Pack level.
When doing MAN segment ranges at the Pack level, then the value is equal to the total number of eaches shipped within the range.
Standard Structure:
The value is equal to the total number of eaches or cases shipped for a line item where the respective bar code will report to the parent item level.
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.
If the product was ordered in pounds, Target will only accept the LB qualifier.
If the product was ordered in eaches, Target will accept EA qualifier.
If the product was ordered in cases, Target will accept CA qualifier.
- CA
- Case
- EA
- Each
- LB
- Pound
Pound is only allowed on Food Distribution Center shipments. The LB qualifier is interchangeable with the EA qualifier within Target's application systems for non-random weight food items.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
NOTE: This segment is required for Standard Pack Structure.
If sending Pick and Pack Structure, Target prefers to receive the PO4 at the Pack Level.
If it's not possible to send the PO4 at the Pack Level, the PO4 must be sent at the Item Level.
PO401 =
The number of total units within the carton - OR -
The number of inner packs within the outer carton.
(The latter applies if PO414 was sent on the PO.)
PO414 = The number of units within an inner pack.
If the PO414 is sent on the PO, it is required to be sent back/returned on the EDI 856.
If the PO414 is not sent on the PO, do not send back/return a PO4*14 on the EDI 856.
Sample PO4 Segments:
PO412 (no inner packs) - Casepack = 12 individual units
PO44*************6 - (inner packs, within a carton) Casepack = 24, with 4 inner packs of 6 units each
The number of inner containers, or number of eaches if there are no inner containers, per outer container
The number of eaches per inner container
If inner cartons are being sent, this must represent the number of selling units within one inner pack.
If the PO414 element is received on the PO, then it is required to be sent back on the 856.
Reference Identification
To specify identifying information
Sample REF Segment
REFLT123456789
Standard Pack Format:
Lot number accepted at item level only.
Pick Pack Format:
Prefer lot number at pack level, will accept at item level.
Code qualifying the Reference Identification
- LT
- Lot Number
Lot number required based on Food Distribution Center Shipments, as these are designated by Target as lot number controlled product.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time Reference
To specify pertinent dates and times
Sample DTM Segment
DTM03620070430
Standard Pack Format:
Expiration date accepted at item level only.
Pick Pack Format:
Prefer expiration date at pack level, will accept at item level.
Code specifying type of date or time, or both date and time
- 036
- Expiration
Expiration date required based on Food Distribution Center Shipments, as these are designated by Target as expiration date controlled product.
*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
The Tare level must be used when the Pack level MAN segment contains the 'UC' (GTIN-14, SCC-14) or 'UP'/'EN' (GTIN-12/13 or U.P.C./EAN).
The Tare level is optional when MAN01=GM or AA at the pack level.
Sample HL (Tare level) Segment
HL32*T
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.
- T
- Shipping Tare
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.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
NOTE: If sending HL Tare Level, this Segment is required.
The Tare level must be used when the Pack level MAN segment contains the 'UC' (GTIN-14, SCC-14) or 'UP'/'EN' (GTIN-12/13 or U.P.C./EAN).
Sample MAN Segments
MANGM00123456789876543217
MANAA123456789876543217
See "Ship Carton and Pallet Markings Domestic" on POL (www.partnersonline.com) for labeling requirements.
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.
- AA
- SSCC-18
- GM
- SSCC-18 and Application Identifier
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.
When GM is present in MAN01, the value in this field must be 20 digits.
When AA is present in MAN01, the value in this field must be 18 digits.
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.
Code specifying the application or source of Marks and Numbers (87)
- AA
- SSCC-18
This code is not commonly used.
- GM
- SSCC-18 and Application Identifier
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.
When GM is present in MAN01, the value in this field must be 20 digits.
When AA is present in MAN01, the value in this field must be 18 digits.
Marks and numbers used to identify a shipment or parts of a shipment
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.
- P
- Pack
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.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
NOTE: Target prefers receiving the PO4 at the pack level for the pick/pack structure.
If it's not possible to send at the pack level, the PO4 must be sent at the Item Level.
If using standard structure, the PO4 is required at the Item Level.
PO401 =
The number of total units within the carton - OR -
The number of inner packs within the outer carton.
(The latter applies if PO414 was sent on the PO.)
PO414 = The number of units within an inner pack.
If the PO414 is sent on the PO, it is required to be sent back/returned on the EDI 856.
If the PO414 is not sent on the PO, do not send back/return a PO414 on the EDI 856.
Sample PO4 Segments:
PO412 (no inner packs) - Casepack = 12 individual units
PO44*************6 - (inner packs, within a carton) Casepack = 24, with 4 inner packs of 6 units each
The number of inner containers, or number of eaches if there are no inner containers, per outer container
The number of eaches per inner container
If inner cartons are being sent, this must represent the number of selling units within one inner pack.
If the PO414 element is received on the PO, then it is required to be sent back on the 856.
Reference Identification
To specify identifying information
Sample REF Segment
REFLT123456789
Standard Pack Format:
Lot number accepted at item level only.
Pick Pack Format:
Prefer lot number at pack level, will accept at item level.
Code qualifying the Reference Identification
- LT
- Lot Number
Lot number required based on Food Distribution Center Shipments, as these are designated by Target as lot number controlled product.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
MAN01 or MAN04 must be 'GM' or 'AA' at Pack Level when a Tare Segment is not present.
When used together, MAN01 and MAN04 CANNOT be the same (i.e. if MAN01 is 'GM', MAN04 cannot be GM).
Sample MAN Segments:
MANGM00000123456789876754 (Must be a unique # per shipping container)
MANAA000123456789876754 (Must be a unique # per shipping container)
GTIN-14: 14 digit Product Identification Code (aka SCC-14)
MANUC10012345655668 (14-digit carton case code)
GTIN-12/13: U.P.C./EAN on selling unit. Only valid if selling unit is shipping unit and case-pack equals 1
MANUP000123456784 (12-digit selling unit UPC code)
Ranging MAN Segments
MANGM00000123456789987659*00000123456789988756
MAN02 = First carton barcode of an item
MAN03 = Last carton barcode of same item
MANAA000001234567899876*000001234567899887
MAN02 = First carton barcode of an item
MAN03 = Last carton barcode of same item
See "Ship Carton and Pallet Markings Domestic" on POL (www.partnersonline.com) for labeling requirements.
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.
- AA
- SSCC-18
- EN
- EAN European Article Number (2-5-5-1)
Used when case pack is one and selling unit is shipping unit
- GM
- SSCC-18 and Application Identifier
- UC
- U.P.C. Shipping Container Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Used when case pack is one and selling unit is shipping unit.
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.
When GM is present in MAN01, the value in this field must be 20 digits.
When AA is present in MAN01, the value in this field must be 18 digits.
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.
Code specifying the application or source of Marks and Numbers (87)
- AA
- SSCC-18
- EN
- EAN European Article Number (2-5-5-1)
Used when case pack is one and selling unit is shipping unit.
- GM
- SSCC-18 and Application Identifier
- UC
- U.P.C. Shipping Container Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Used when case pack is one and selling unit it shipping unit.
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.
Marks and numbers used to identify a shipment or parts of a shipment
Date/Time Reference
To specify pertinent dates and times
Sample DTM Segment
DTM03620070430
Standard Pack Format:
Expiration date accepted at item level only.
Pick Pack Format:
Prefer expiration date at pack level, will accept at item level.
Code specifying type of date or time, or both date and time
- 036
- Expiration
Expiration date required based on Food Distribution Center Shipments, as these are designated by Target as expiration date controlled product.
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
*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
NOTE: IN will be used as an item identifier for Target in the future. When this item identifier is sent by Target, your system must be capable of sending it back on inbound EDI documents to Target.
Target Stores:
Always send either the Target DPCI number with a CB qualifier or the corresponding UPC number with a UP qualifier for item.
Sample LIN Segments
LINCB019060025UP*039800088628
LINUP039800088628
LIN**CB019060025
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
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.
- CB
- Buyer's Catalog Number
Target 9 digit DPCI number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN-8
- IN
- Buyer's Item Number
Target Corporation Item Number (TCIN)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CB
- Buyer's Catalog Number
Target 9 digit DPCI number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN-8
- IN
- Buyer's Item Number
Target Corporation Item Number (TCIN)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CB
- Buyer's Catalog Number
Target 9 digit DPCI number
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN-8
- IN
- Buyer's Item Number
Target Corporation Item Number (TCIN)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Item Detail (Shipment)
To specify line-item detail relative to shipment
*Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data.
Sample SN1 Segment
SN1*75EA
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
The value stated in SN102 is dependent upon the 856 structure (Standard or Pick Pack) and the type of carton identification number being sent in the MAN segment at the Pack level.
Pick Pack Structure:
When a SSCC is sent for every carton, the value is equal to the total number of eaches tied to the unique SSCC sent at the corresponding Pack level. If the unit of measure is cases (CA), then the value is one.
When a GTIN-14 (SCC 14 digit) is sent at the Pack level, then the value is equal to the total number of eaches or cases shipped for the line item.
Do not repeat Pack/Item loops for each carton shipped that is tied to the GTIN referenced in the Pack level.
When doing MAN segment ranges at the Pack level, then the value is equal to the total number of eaches shipped within the range.
Standard Structure:
The value is equal to the total number of eaches or cases shipped for a line item where the respective bar code will report to the parent item level.
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.
If the product was ordered in pounds, Target will only accept the LB qualifier.
If the product was ordered in eaches, Target will accept EA qualifier.
If the product was ordered in cases, Target will accept CA qualifier.
- CA
- Case
- EA
- Each
- LB
- Pound
Pound is only allowed on Food Distribution Center shipments. The LB qualifier is interchangeable with the EA qualifier within Target's application systems for non-random weight food items.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
NOTE: This segment is required for Standard Pack Structure.
If sending Pick and Pack Structure, Target prefers to receive the PO4 at the Pack Level.
If it's not possible to send the PO4 at the Pack Level, the PO4 must be sent at the Item Level.
PO401 =
The number of total units within the carton - OR -
The number of inner packs within the outer carton.
(The latter applies if PO414 was sent on the PO.)
PO414 = The number of units within an inner pack.
If the PO414 is sent on the PO, it is required to be sent back/returned on the EDI 856.
If the PO414 is not sent on the PO, do not send back/return a PO4*14 on the EDI 856.
Sample PO4 Segments:
PO412 (no inner packs) - Casepack = 12 individual units
PO44*************6 - (inner packs, within a carton) Casepack = 24, with 4 inner packs of 6 units each
The number of inner containers, or number of eaches if there are no inner containers, per outer container
The number of eaches per inner container
If inner cartons are being sent, this must represent the number of selling units within one inner pack.
If the PO414 element is received on the PO, then it is required to be sent back on the 856.
Reference Identification
To specify identifying information
Sample REF Segment
REFLT123456789
Standard Pack Format:
Lot number accepted at item level only.
Pick Pack Format:
Prefer lot number at pack level, will accept at item level.
Code qualifying the Reference Identification
- LT
- Lot Number
Lot number required based on Food Distribution Center Shipments, as these are designated by Target as lot number controlled product.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time Reference
To specify pertinent dates and times
Sample DTM Segment
DTM03620070430
Standard Pack Format:
Expiration date accepted at item level only.
Pick Pack Format:
Prefer expiration date at pack level, will accept at item level.
Code specifying type of date or time, or both date and time
- 036
- Expiration
Expiration date required based on Food Distribution Center Shipments, as these are designated by Target as expiration date controlled product.
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.
Total number of line items 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*1111991111*1111471111*20230702*1543*1283*X*004010~
ST*856*1283~
BSN*00*123456*20230702*1328*0001~
HL*1**S~
TD5*B*2*ABCD*U*FedEx Ground~
REF*CN*9988776655~
N1*ST**92*1234~
HL*2*1*O~
PRF*1111-22222222-3333~
PID*S**VI*FL~
TD1*CTN25*1~
N1*BY**92*1234~
HL*3*2*P~
MAN*GM*00001234567890123456~
HL*4*3*I~
LIN*1*CB*111111111*UP*2222222222~
SN1**6*EA~
PO4*6*************1~
CTT*4~
SE*19*1283~
GE*1*1283~
IEA*1*100000283~
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.