X12 856 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
- None included
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
- 00404
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2000
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
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
- 004040
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2000
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
ASN number must be associated to the entire shipment and must unique for at least 180 days after 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.
Code specifying the type of transaction
- BSN06 is limited to shipment related codes.
- BSN06 and BSN07 differentiate the functionality of use for the transaction set.
If PO BEG02 Order Type = DR, BSN06 must contain ZZ.
If PO BEG02 Order Type is not DR or the PO is manual, BSN06 must be blank.
- ZZ
- Mutually Defined
Date/Time Reference Estimated Delivery
To specify pertinent dates and times
Date/Time Reference Shipped
To specify pertinent dates and times
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.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 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
For Store shipments, the TD1 segment is not required.
Only one TD1 segment is allowed per ASN.
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
- CTN
- Carton
- MXD
- Mixed
- PLT
- Pallet
- UNT
- Unit
Number of units (pieces) of the lading commodity
This value represents the number of handling units included in the shipment. A handling unit is the largest container that will be moved as a unit - pallet, carton, or loose line item.
For example: if a shipment has all line items containerized on pallets only the pallets would be counted as handling units. Please see the CARQUEST Supplier Product Labeling Requirements document for further clarification.
Each pallet must contain two copies of the same License Plate (LP) with a scannable barcode. For small parcels, each handling unit must contain one License Plate (LP) with a scannable barcode.
CARQUEST will accept the Lading Quantity as an integer value up to 5 digits.
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
At least one iteration where the TD502="2" is required.
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 specifying the method or type of transportation for the shipment
- A
- Air
- J
- Motor
- M
- Motor (Common Carrier)
- O
- Containerized Ocean
- R
- Rail
Carrier Details (Special Handling, or Hazardous Materials, or Both)
To specify transportation special handling requirements, or hazardous materials information, or both
For a DC Shipment, utilize this segment w hen a HAZMAT sticker will be placed on a handling unit on the shipment.
Reference Identification Bill of Lading Number
To specify identifying information
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
BOL should be a different value than the Pack Slip number.
CARQUEST will accept a Bill of Lading or Tracking Number up to 30 characters.
Reference Identification Carrier's Reference Number (PRO/Invoice)
To specify identifying information
Code qualifying the Reference Identification
- CN
- Carrier's Reference Number (PRO/Invoice)
Name
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
- ST
- Ship To
Required
- VN
- Vendor
- Z7
- Mark-for Party
Code designating the system/method of code structure used for Identification Code (67)
While any valid X12 code may be sent, the following is recommended:
91 Assigned by Seller (Used w hen N101 = ST, VN & Z7)
92 Assigned by Buyer (Used w hen N101 = SF)
- 91
- Assigned by Seller or Seller's Agent
For ST, VN, and Z7
- 92
- Assigned by Buyer or Buyer's Agent
For SF
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.
For a DC shipment, the Ship To N104 DC code must be 3 characters in length. Please see the Distribution Center Listing file for valid codes.
For a Store shipment, the Ship To N104 Store number must be 5 digits in length. Please see the Store Listing file for valid store codes.
The Ship From N104 is recommended and must be a unique, vendor-assigned ship from location code. It is used to identify the vendor shipping facility from which the goods are departing (not the trade partner ID).
If an HLE is present, the HLO must be nested within the HLE.
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
Identifying number for Purchase Order assigned by the orderer/purchaser
This field should contain the Buyer’s PO number, which can be found in the BEG03 element of the EDI 850 PO.
For manual order ASNs, use the PO communicated in a phone, fax, or email.
Please include the numeric portion of the printed PO only (not the leading DC code).
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- PK
- Packing List Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
CARQUEST will accept a Packing List Number up to 30 characters.
The Pack Slip number should be different from the BOL.
The HLT (Tare) loop is used to indicate a Pallet.
For Pick and Pack, the HLT loop is nested under the HLO loop. It may contain nested HLP or HLI loops.
The HLT loop is optional in the Pick and Pack structure.
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.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
When the highest handling unit is a pallet, the HLT MAN segment is required to convey the License Plate number.
Example:
HL83T
MANAI*00106862260024599671
For DC shipments a License Plate with a scannable barcode number on the physical pallet is required.
For store shipments the License Plate on the physical pallet is optional.
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.
- AI
- UCC/EAN-128 Application Identifier (AI) and Data
- 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.
This number should be a unique identifier for the handling unit, in human-readable text, with a field length up to 18 characters plus 2 leading 0's indicating the Serial Shipping Container Code.
The scannable barcode number on the Pallet w ill be used.
This LP number must be unique for at least 180 days after shipment.
Pallet Information
To identify the type and physical attributes of the pallet, and, gross weight, gross volume, and height of the load and the pallet
For DC shipments, this information provided in this segment is for the pallet.
The dimensions will be external measurements, if available.
The weight will be of the handling unit, if available.
Numeric value of weight per unit
- PAL05 (Unit Weight) is the weight of the pallet alone, before loading.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- GR
- Gram
- KG
- Kilogram
- LB
- Pound
Largest horizontal dimension of an object measured when the object is in the upright position
- PAL07 and PAL08 (Length and Width) are the dimensions of the pallet before loading.
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Vertical dimension of an object measured when the object is in the upright position
- PAL09 (Height) is the height of the pallet and load.
The HLI (Item) loop is used to indicate item information. For Pick and Pack, the HLI loop is nested in the below hierarchical structures. If the optional HLT and optional HLP loops are absent the HLI is nested directly under the HLO and becomes the largest handling unit. This would indicate the item not containerized which would be rare.
The HLI loop is required in the Pick and Pack structure.
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
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.
- BP
- Buyer's Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PL
- Purchaser's Order Line Number
Identifying number for a product or service
Line number in which the item was ordered on the 850.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MF
- Manufacturer
Identifying number for a product or service
Can be found in the PO109 of the EDI 850 PO or as a value in the Vision, Faxed or emailed order.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- UCC - 12
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LT
- Lot Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SN
- Serial Number
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
Any item with a quantity of zero must not be included in the ASN transaction.
The SN102 must contain a number greater than zero or the transaction will fail.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
When the highest handling unit is a loose line item (not containerized), the HLI MAN is required to convey the License Plate number.
Example:
HL83I
LIN1BPG20170-1616PL22MFJ56
SN1*1EA
MANAI00106862260024599671
For DC shipments a License Plate with a scannable barcode number on the physical loose line item is required.
For store shipments the physical pallet License Plate on the physical loose line item is optional.
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.
- AI
- UCC/EAN-128 Application Identifier (AI) and Data
- 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.
This number should be a unique identifier for the handling unit, in human readable text, with a field length up to 18 characters plus 2 leading 0's indicating the Serial Shipping Container Code.
The LP number must be unique for at least 180 days after shipment.
If there is a loose Item on the Shipment, the scannable barcode number will be used.
Date/Time Reference Expiration
To specify pertinent dates and times
Date/Time Reference Production
To specify pertinent dates and times
The HLP (Pack) loop is used to indicate pack information. For Pick and Pack, the HLP loop is nested under the HLT (Tare) loop nested under the HLO (Order) loop. If the optional HLT is absent the HLP is nested directly under the HLO and becomes the largest handling unit.
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.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
When the highest handling unit is a carton, the HLP MAN segment is required to convey the License Plate number.
Example:
HL83P
MANAI*00106862260024599671
For DC shipments a License Plate with a scannable barcode number on the physical carton is required.
For store shipments the physical pallet License Plate on the physical carton is optional.
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.
- AI
- UCC/EAN-128 Application Identifier (AI) and Data
- 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.
This number should be a unique identifier for the handling unit, in human-readable text, with a field length up to 18 characters plus 2 leading 0's indicating the Serial Shipping Container Code.
The scannable barcode number on the carton will be used.
The LP must be unique for at least 180 days after shipment.
Pallet Information
To identify the type and physical attributes of the pallet, and, gross weight, gross volume, and height of the load and the pallet
For DC shipments, this information provided in this segment is for the pack.
The dimensions will be external measurements, if available.
The weight will be of the handling unit, if available.
Numeric value of weight per unit
- PAL05 (Unit Weight) is the weight of the pallet alone, before loading.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- GR
- Gram
- KG
- Kilogram
- LB
- Pound
Largest horizontal dimension of an object measured when the object is in the upright position
- PAL07 and PAL08 (Length and Width) are the dimensions of the pallet before loading.
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Vertical dimension of an object measured when the object is in the upright position
- PAL09 (Height) is the height of the pallet and load.
The HLI (Item) loop is used to indicate item information. For Pick and Pack, the HLI loop is nested in the below hierarchical structures. If the optional HLT and optional HLP loops are absent the HLI is nested directly under the HLO and becomes the largest handling unit. This would indicate the item not containerized which would be rare.
The HLI loop is required in the Pick and Pack structure.
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
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.
- BP
- Buyer's Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PL
- Purchaser's Order Line Number
Identifying number for a product or service
Line number in which the item was ordered on the 850.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MF
- Manufacturer
Identifying number for a product or service
Can be found in the PO109 of the EDI 850 PO or as a value in the Vision, Faxed or emailed order.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- UCC - 12
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LT
- Lot Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SN
- Serial Number
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
Any item with a quantity of zero must not be included in the ASN transaction.
The SN102 must contain a number greater than zero or the transaction will fail.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
When the highest handling unit is a loose line item (not containerized), the HLI MAN is required to convey the License Plate number.
Example:
HL83I
LIN1BPG20170-1616PL22MFJ56
SN1*1EA
MANAI00106862260024599671
For DC shipments a License Plate with a scannable barcode number on the physical loose line item is required.
For store shipments the physical pallet License Plate on the physical loose line item is optional.
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.
- AI
- UCC/EAN-128 Application Identifier (AI) and Data
- 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.
This number should be a unique identifier for the handling unit, in human readable text, with a field length up to 18 characters plus 2 leading 0's indicating the Serial Shipping Container Code.
The LP number must be unique for at least 180 days after shipment.
If there is a loose Item on the Shipment, the scannable barcode number will be used.
Date/Time Reference Expiration
To specify pertinent dates and times
Date/Time Reference Production
To specify pertinent dates and times
CARQUEST is currently not utilizing information that may be provided in the HLE segment.
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.
- E
- Transportation Equipment
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 (Equipment)
To specify transportation details relating to the equipment used by the carrier
Prefix or alphabetic part of an equipment unit's identifying number
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- SN
- Seal Number
If an HLE is present, the HLO must be nested within the HLE.
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
Identifying number for Purchase Order assigned by the orderer/purchaser
This field should contain the Buyer’s PO number, which can be found in the BEG03 element of the EDI 850 PO.
For manual order ASNs, use the PO communicated in a phone, fax, or email.
Please include the numeric portion of the printed PO only (not the leading DC code).
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- PK
- Packing List Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
CARQUEST will accept a Packing List Number up to 30 characters.
The Pack Slip number should be different from the BOL.
The HLT (Tare) loop is used to indicate a Pallet.
For Pick and Pack, the HLT loop is nested under the HLO loop. It may contain nested HLP or HLI loops.
The HLT loop is optional in the Pick and Pack structure.
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.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
When the highest handling unit is a pallet, the HLT MAN segment is required to convey the License Plate number.
Example:
HL83T
MANAI*00106862260024599671
For DC shipments a License Plate with a scannable barcode number on the physical pallet is required.
For store shipments the License Plate on the physical pallet is optional.
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.
- AI
- UCC/EAN-128 Application Identifier (AI) and Data
- 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.
This number should be a unique identifier for the handling unit, in human-readable text, with a field length up to 18 characters plus 2 leading 0's indicating the Serial Shipping Container Code.
The scannable barcode number on the Pallet w ill be used.
This LP number must be unique for at least 180 days after shipment.
Pallet Information
To identify the type and physical attributes of the pallet, and, gross weight, gross volume, and height of the load and the pallet
For DC shipments, this information provided in this segment is for the pallet.
The dimensions will be external measurements, if available.
The weight will be of the handling unit, if available.
Numeric value of weight per unit
- PAL05 (Unit Weight) is the weight of the pallet alone, before loading.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- GR
- Gram
- KG
- Kilogram
- LB
- Pound
Largest horizontal dimension of an object measured when the object is in the upright position
- PAL07 and PAL08 (Length and Width) are the dimensions of the pallet before loading.
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Vertical dimension of an object measured when the object is in the upright position
- PAL09 (Height) is the height of the pallet and load.
The HLI (Item) loop is used to indicate item information. For Pick and Pack, the HLI loop is nested in the below hierarchical structures. If the optional HLT and optional HLP loops are absent the HLI is nested directly under the HLO and becomes the largest handling unit. This would indicate the item not containerized which would be rare.
The HLI loop is required in the Pick and Pack structure.
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
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.
- BP
- Buyer's Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PL
- Purchaser's Order Line Number
Identifying number for a product or service
Line number in which the item was ordered on the 850.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MF
- Manufacturer
Identifying number for a product or service
Can be found in the PO109 of the EDI 850 PO or as a value in the Vision, Faxed or emailed order.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- UCC - 12
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LT
- Lot Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SN
- Serial Number
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
Any item with a quantity of zero must not be included in the ASN transaction.
The SN102 must contain a number greater than zero or the transaction will fail.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
When the highest handling unit is a loose line item (not containerized), the HLI MAN is required to convey the License Plate number.
Example:
HL83I
LIN1BPG20170-1616PL22MFJ56
SN1*1EA
MANAI00106862260024599671
For DC shipments a License Plate with a scannable barcode number on the physical loose line item is required.
For store shipments the physical pallet License Plate on the physical loose line item is optional.
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.
- AI
- UCC/EAN-128 Application Identifier (AI) and Data
- 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.
This number should be a unique identifier for the handling unit, in human readable text, with a field length up to 18 characters plus 2 leading 0's indicating the Serial Shipping Container Code.
The LP number must be unique for at least 180 days after shipment.
If there is a loose Item on the Shipment, the scannable barcode number will be used.
Date/Time Reference Expiration
To specify pertinent dates and times
Date/Time Reference Production
To specify pertinent dates and times
The HLP (Pack) loop is used to indicate pack information. For Pick and Pack, the HLP loop is nested under the HLT (Tare) loop nested under the HLO (Order) loop. If the optional HLT is absent the HLP is nested directly under the HLO and becomes the largest handling unit.
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.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
When the highest handling unit is a carton, the HLP MAN segment is required to convey the License Plate number.
Example:
HL83P
MANAI*00106862260024599671
For DC shipments a License Plate with a scannable barcode number on the physical carton is required.
For store shipments the physical pallet License Plate on the physical carton is optional.
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.
- AI
- UCC/EAN-128 Application Identifier (AI) and Data
- 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.
This number should be a unique identifier for the handling unit, in human-readable text, with a field length up to 18 characters plus 2 leading 0's indicating the Serial Shipping Container Code.
The scannable barcode number on the carton will be used.
The LP must be unique for at least 180 days after shipment.
Pallet Information
To identify the type and physical attributes of the pallet, and, gross weight, gross volume, and height of the load and the pallet
For DC shipments, this information provided in this segment is for the pack.
The dimensions will be external measurements, if available.
The weight will be of the handling unit, if available.
Numeric value of weight per unit
- PAL05 (Unit Weight) is the weight of the pallet alone, before loading.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
While any valid X12 code may be sent, the following is preferred:
GR Gram
KG Kilogram
LB Pound
- GR
- Gram
- KG
- Kilogram
- LB
- Pound
Largest horizontal dimension of an object measured when the object is in the upright position
- PAL07 and PAL08 (Length and Width) are the dimensions of the pallet before loading.
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Vertical dimension of an object measured when the object is in the upright position
- PAL09 (Height) is the height of the pallet and load.
The HLI (Item) loop is used to indicate item information. For Pick and Pack, the HLI loop is nested in the below hierarchical structures. If the optional HLT and optional HLP loops are absent the HLI is nested directly under the HLO and becomes the largest handling unit. This would indicate the item not containerized which would be rare.
The HLI loop is required in the Pick and Pack structure.
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
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.
- BP
- Buyer's Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PL
- Purchaser's Order Line Number
Identifying number for a product or service
Line number in which the item was ordered on the 850.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MF
- Manufacturer
Identifying number for a product or service
Can be found in the PO109 of the EDI 850 PO or as a value in the Vision, Faxed or emailed order.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- UCC - 12
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LT
- Lot Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SN
- Serial Number
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
Any item with a quantity of zero must not be included in the ASN transaction.
The SN102 must contain a number greater than zero or the transaction will fail.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
When the highest handling unit is a loose line item (not containerized), the HLI MAN is required to convey the License Plate number.
Example:
HL83I
LIN1BPG20170-1616PL22MFJ56
SN1*1EA
MANAI00106862260024599671
For DC shipments a License Plate with a scannable barcode number on the physical loose line item is required.
For store shipments the physical pallet License Plate on the physical loose line item is optional.
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.
- AI
- UCC/EAN-128 Application Identifier (AI) and Data
- 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.
This number should be a unique identifier for the handling unit, in human readable text, with a field length up to 18 characters plus 2 leading 0's indicating the Serial Shipping Container Code.
The LP number must be unique for at least 180 days after shipment.
If there is a loose Item on the Shipment, the scannable barcode number will be used.
Date/Time Reference Expiration
To specify pertinent dates and times
Date/Time Reference Production
To specify pertinent dates and times
Summary
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
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.