X12 856 Drop Ship Ship Notice/Manifest
This X12 Transaction Set contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment.
The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.
The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.
- ~ Segment
- * Element
- > Component
- ^ Repetition
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying 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 identifying 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)
Code indicating 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
Code indicating 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
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00501
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Interchange Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested (TA1)
Code indicating 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
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 005010
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
Heading
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) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 856
- Ship Notice/Manifest
Beginning Segment for Ship Notice
To transmit identifying numbers, dates, and other basic data relating to the transaction set
Code identifying purpose of transaction set
- 00
- Original
A unique control number assigned by the original shipper to identify a specific shipment
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BSN03 is the date the shipment transaction set is created.
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.
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 (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
See trading partner specific guides
Numeric value of weight
Shipment weight, numeric values only, must include decimal.
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Code describing the relationship of a carrier to a specific shipment movement
- Z
- Mutually Defined
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.
- ZZ
- Mutually Defined
Code identifying a party or other code
Ship Carrier - Examples: FedEx, UPS, USPS
Code specifying the method or type of transportation for the shipment
- A
- Air
- J
- Motor
- R
- Rail
- S
- Ocean
- ZZ
- Mutually defined
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Ship Method - Examples: Ground, SmartPost, Overnight
Code identifying type of location
- ZZ
- Mutually Defined
Code which identifies a specific location
Shipping Service Level Code
- AECO
- Allied Express Courier
- APEP
- Aus. Post eParcel
- APEX
- Aus. Post Express Post eParcel
- CEVC
- CEVA Curbside Service
- CEVR
- CEVA Room of Choice Service
- CEVT
- CEVA Threshold Service
- CEVW
- CEVA White Glove Service
- CPDO
- Couriers Please Domestic
- CPIN
- Couriers Please International
- F2DA
- FedEx 2Day A.M.
- FAST
- Fastway Australia Standard
- FE2D
- FedEx 2Day
- FECG
- FedEx Ground
- FEDT
- FedEx Territory
- FEES
- FedEx Express Saver
- FEFO
- FedEx First Overnight
- FEHD
- FedEx Home Delivery
- FEIE
- FedEx International Economy
- FEIP
- FedEx International Priority
- FEPO
- FedEx Priority Overnight
- FESD
- FedEx SameDay
- FESO
- FedEx Standard Overnight
- FESP
- FedEx SmartPost
- FSDC
- FedEx SameDay City
- G3D
- Generic Three Day
- GCG
- Generic Ground
- GCX
- Generic Express Saver
- GIX
- Generic International
- GND
- Generic Next Day
- GNM
- Generic Priority
- GON
- Generic 1st Overnight
- GSA
- Generic Same Day
- GSD
- Generic Saturday
- GSE
- Generic Second Day
- HEAE
- Hunter Express Air Express
- HEER
- Hunter Express Economy Road
- HERE
- Hunter Express Road Express
- HESD
- Hunter Express Same Day Courier
- LTLC
- LTL Curbside Service
- LTLD
- LTL Vendor Delivered
- LTLF
- LTL Freight
- LTLR
- LTL Room of Choice Service
- LTLS
- LTL Vendor Specialty
- LTLT
- LTL Threshold Service
- LTLW
- LTL White Glove Service
- MXDC
- MXD Group Curbside Service
- MXDR
- MXD Group Room of Choice Service
- MXDT
- MXD Group Threshold Service
- MXDW
- MXD Group White Glove Service
- PIL1
- Pilot Threshold 1 Man
- PIL2
- Pilot Threshold 2 Man
- PILR
- Pilot Room of Choice
- PILW
- Pilot White Glove 1 Man
- PIW2
- Pilot White Glove 2 Man
- STIC
- STI Curbside Service
- STIR
- STI Room of Choice Service
- STIT
- STI Threshold Service
- STIW
- STI White Glove Service
- STND
- Star Track Next-Day
- STRE
- Star Track Regular
- STSD
- Star Track Same-Day Metro
- SUN2
- Sun Delivery Threshold 2 Man
- SUNW
- Sun Delivery White Glove 2 Man
- TEC2
- Tech Trans Threshold 2 Man
- TECT
- Tech Trans Threshold 1 Man
- TECW
- Tech Trans White Glove 1 Man
- TEW2
- Tech Trans White Glove 2 Man
- TNOE
- TNT Overnight Express
- TNRE
- TNT Road Express
- TOIP
- Toll IPEC
- TOPR
- Toll Priority
- U2AA
- UPS 2nd Day Air A.M.
- U2DA
- UPS 2nd Day Air
- U3DS
- UPS 3 Day Select
- UMID
- UPS Mail Innovations Domestic
- UNAE
- UPS Next Day Air Early
- UNAS
- UPS Next Day Air Saver
- UNDA
- UPS Next Day Air
- UPCG
- UPS Ground
- UPSF
- UPS Freight
- UPSP
- UPS Surepost
- UPSS
- UPS Standard
- USCG
- USPS Ground
- USFC
- USPS First-Class Mail
- USPE
- USPS Priority Mail Express
- USPL
- UPS Surepost Lightweight
- USPM
- USPS Priority Mail
Carrier's PRO/Reference or Bill of Lading
To specify identifying information
Code qualifying the Reference Identification
This value will be mapped to Package Reference Number Qualifier.
- BM
- Bill of Lading Number
- CN
- Carrier's Reference Number (PRO/Invoice)
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Package Tracking Number as provided by the Carrier.
Internal Vendor Number
To specify identifying information
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Mutually Defined
To specify identifying information
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
- line_item_package_span_flag
- Line Item Package Span Flag
Optional
Identify that multiple different trackingNumbers / shipments will contain this item by using the values of “1” or “true”
- package_carrier_manifest_id
- Package Carrier Manifest ID
Optional
Used with LTL shipments
- package_transportation_method_code
- Package Transportation Method Code
Optional
The transportation method code assigned by the carrier for the shipped package. Possible values include: 'A' for Air, 'J' for Motor, 'R' for Rail, 'S' for Ocean/Ship. Sometimes mapped as TD504.
- package_unit_of_measurement_code
- Package Unit Of Measurement Code
Optional
The unit of measurement code. Typically 'EA' for 'Each'. 'PR' for 'Pair' is also acceptable.
- package_warehouse_code
- Package Warehouse Code
Conditional
Ship Notice/Manifest Number
To specify identifying information
Code qualifying the Reference Identification
- MA
- Ship Notice/Manifest Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The Package Carrier Manifest ID - Used with LTL shipments.
Carrier-Assigned Package ID Number
To indicate identifying marks and numbers for shipping containers
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.
- CP
- Carrier-Assigned Package ID Number
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.
Carrier’s Package ID Number
If both REFCN and MANCP are given, REF*CN will post to the tracking number field on a shipment.
EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier
To indicate identifying marks and numbers for shipping containers
See trading partner specific guides
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- GM
- EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier
Code specifying type of date or time, or both date and time
- 011
- Shipped
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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)
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
See trading partner specific guides
Service, Promotion, Allowance, or Charge Information
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
Code which indicates an allowance or charge for the service specified
- If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
- C
- Charge
Code identifying the service, promotion, allowance, or charge
- G821
- Shipping
See trading partner specific guides
Service, Promotion, Allowance, or Charge Information
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
Code which indicates an allowance or charge for the service specified
- If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
- C
- Charge
Code identifying the service, promotion, allowance, or charge
- I132
- Total Invoice Amount
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- O
- Order
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
Customer Order Number
To specify identifying information
Code qualifying the Reference Identification
- CO
- Customer Order Number
Seller's Invoice Number
To specify identifying information
See trading partner specific guides
Code qualifying the Reference Identification
- IV
- Seller's Invoice Number
Vendor Order Number
To specify identifying information
Code qualifying the Reference Identification
- VN
- Vendor Order Number
Suppliers should include if you will be spending ship_from_location_code.
Party Identification
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Free-form name
Supplier name that is displayed on the package address label and packing slip.
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.
The warehouse code the package was shipped from. This should match the available warehouse codes the supplier has set up within their DSCO account. Ref: 'ship_from_location_code'.
Additional Name Information
To specify additional names
Party Location
To specify the location of the named party
Address information
First address line of Ship-From that is displayed on the package address label and packing slip.
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Ship-From City that should be displayed on the package address label and packing slip.
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.
Ship-From State that is displayed on the package address label and packing slip.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Ship-From Zip code excluding punctuation (hyphens) and blanks. As displayed on the package address label and packing slip.
Suppliers should include if you will be spending ship_from_location_code.
Party Identification
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Free-form name
Supplier name that is displayed on the package address label and packing slip.
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.
The warehouse code the package was shipped from. This should match the available warehouse codes the supplier has set up within their DSCO account. Ref: 'ship_from_location_code'.
Additional Name Information
To specify additional names
Party Location
To specify the location of the named party
Address information
First address line of Ship-From that is displayed on the package address label and packing slip.
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Ship-From City that should be displayed on the package address label and packing slip.
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.
Ship-From State that is displayed on the package address label and packing slip.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Ship-From Zip code excluding punctuation (hyphens) and blanks. As displayed on the package address label and packing slip.
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
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
Line item number on the PO. Required when two or more line items on the order have the same-SKU.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
The SKU of the item. A limit of 70 characters is enforced. A SKU is required. If a SKU is not available you may duplicate the UPC or EAN to this field.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- CB
- Buyer's Catalog Number
- EM
- Equipment Identification Number
- EN
- EAN/UCC - 13
- IB
- International Standard Book Number (ISBN)
- MG
- Manufacturer's Part Number
- SN
- Serial Number
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
Identifying number for a product or service
When the Qualifier is 'UP': Universal Product Code (UPC)
When the Qualifier is 'EN': European Article Number (EAN)
When the Qualifier is 'IB': International Standard Book Number (ISBN)
When the Qualifier is 'UK': Global Trade Number (GTIN)
When the Qualifier is 'BP': Partner SKU
When the Qualifier is 'CB': Retailer Item Identifier
When the Qualifier is 'EM': Dsco Item ID
When the Qualifier is 'SN': Serial Numbers are '^^' separated,
meaning that if there is '^^' in this field there are multiple serial
numbers
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- CB
- Buyer's Catalog Number
- EM
- Equipment Identification Number
- EN
- EAN/UCC - 13
- IB
- International Standard Book Number (ISBN)
- MG
- Manufacturer's Part Number
- SN
- Serial Number
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
Identifying number for a product or service
When the Qualifier is 'UP': Universal Product Code (UPC)
When the Qualifier is 'EN': European Article Number (EAN)
When the Qualifier is 'IB': International Standard Book Number (ISBN)
When the Qualifier is 'UK': Global Trade Number (GTIN)
When the Qualifier is 'BP': Partner SKU
When the Qualifier is 'CB': Retailer Item Identifier
When the Qualifier is 'EM': Dsco Item ID
When the Qualifier is 'SN': Serial Numbers are '^^' separated,
meaning that if there is '^^' in this field there are multiple serial
numbers
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- CB
- Buyer's Catalog Number
- EM
- Equipment Identification Number
- EN
- EAN/UCC - 13
- IB
- International Standard Book Number (ISBN)
- MG
- Manufacturer's Part Number
- SN
- Serial Number
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
Identifying number for a product or service
When the Qualifier is 'UP': Universal Product Code (UPC)
When the Qualifier is 'EN': European Article Number (EAN)
When the Qualifier is 'IB': International Standard Book Number (ISBN)
When the Qualifier is 'UK': Global Trade Number (GTIN)
When the Qualifier is 'BP': Partner SKU
When the Qualifier is 'CB': Retailer Item Identifier
When the Qualifier is 'EM': Dsco Item ID
When the Qualifier is 'SN': Serial Numbers are '^^' separated,
meaning that if there is '^^' in this field there are multiple serial
numbers
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- CB
- Buyer's Catalog Number
- EM
- Equipment Identification Number
- EN
- EAN/UCC - 13
- IB
- International Standard Book Number (ISBN)
- MG
- Manufacturer's Part Number
- SN
- Serial Number
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
Identifying number for a product or service
When the Qualifier is 'UP': Universal Product Code (UPC)
When the Qualifier is 'EN': European Article Number (EAN)
When the Qualifier is 'IB': International Standard Book Number (ISBN)
When the Qualifier is 'UK': Global Trade Number (GTIN)
When the Qualifier is 'BP': Partner SKU
When the Qualifier is 'CB': Retailer Item Identifier
When the Qualifier is 'EM': Dsco Item ID
When the Qualifier is 'SN': Serial Numbers are '^^' separated,
meaning that if there is '^^' in this field there are multiple serial
numbers
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- CB
- Buyer's Catalog Number
- EM
- Equipment Identification Number
- EN
- EAN/UCC - 13
- IB
- International Standard Book Number (ISBN)
- MG
- Manufacturer's Part Number
- SN
- Serial Number
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
Identifying number for a product or service
When the Qualifier is 'UP': Universal Product Code (UPC)
When the Qualifier is 'EN': European Article Number (EAN)
When the Qualifier is 'IB': International Standard Book Number (ISBN)
When the Qualifier is 'UK': Global Trade Number (GTIN)
When the Qualifier is 'BP': Partner SKU
When the Qualifier is 'CB': Retailer Item Identifier
When the Qualifier is 'EM': Dsco Item ID
When the Qualifier is 'SN': Serial Numbers are '^^' separated,
meaning that if there is '^^' in this field there are multiple serial
numbers
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- CB
- Buyer's Catalog Number
- EM
- Equipment Identification Number
- EN
- EAN/UCC - 13
- IB
- International Standard Book Number (ISBN)
- MG
- Manufacturer's Part Number
- SN
- Serial Number
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
Identifying number for a product or service
When the Qualifier is 'UP': Universal Product Code (UPC)
When the Qualifier is 'EN': European Article Number (EAN)
When the Qualifier is 'IB': International Standard Book Number (ISBN)
When the Qualifier is 'UK': Global Trade Number (GTIN)
When the Qualifier is 'BP': Partner SKU
When the Qualifier is 'CB': Retailer Item Identifier
When the Qualifier is 'EM': Dsco Item ID
When the Qualifier is 'SN': Serial Numbers are '^^' separated,
meaning that if there is '^^' in this field there are multiple serial
numbers
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- CB
- Buyer's Catalog Number
- EM
- Equipment Identification Number
- EN
- EAN/UCC - 13
- IB
- International Standard Book Number (ISBN)
- MG
- Manufacturer's Part Number
- SN
- Serial Number
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
Identifying number for a product or service
When the Qualifier is 'UP': Universal Product Code (UPC)
When the Qualifier is 'EN': European Article Number (EAN)
When the Qualifier is 'IB': International Standard Book Number (ISBN)
When the Qualifier is 'UK': Global Trade Number (GTIN)
When the Qualifier is 'BP': Partner SKU
When the Qualifier is 'CB': Retailer Item Identifier
When the Qualifier is 'EM': Dsco Item ID
When the Qualifier is 'SN': Serial Numbers are '^^' separated,
meaning that if there is '^^' in this field there are multiple serial
numbers
Item Detail (Shipment)
To specify line-item detail relative to shipment
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
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.
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
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
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Basic Sample
BSN*00*000000002*20200313*173020*0004~
HL*1**S~
TD1******G*5.1*LB~
TD5*Z*ZZ*UPS*ZZ*Ground**ZZ*UPCG~
REF*IA*3286495~
REF*CN*1Z12345F67890~
REF*ZZ*123456789*package_warehouse_code~
REF*ZZ*EA*package_unit_of_measurement_code~
REF*MA*456789*package_carrier_manifest_id~
DTM*011*20200313~
CUR*BY*USD~
SAC*C*G821***789~
HL*2*1*O~
PRF*11150439~
REF*VN*ST01173~
N1*SF**92*WH01~
HL*3*2*I~
LIN*0001*SK*999999~
SN1**2*EA~
HL*4*2*I~
LIN*0002*SK*98989898~
SN1**3*EA~
CTT*4~
SE*25*000020001~
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.