X12 856 Ship Notice/Manifest
This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.
The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.
- ~ Segment
- * Element
- > Component
- ^ 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
- 00403
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
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
- 004030
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Ship Notice
To transmit identifying numbers, dates, and other basic data relating to the transaction set
Code identifying purpose of transaction set
- 00
- Original
Used for shipments to DC, Store or International Orders
- 05
- Replace
- 06
- Confirmation
Used for Direct to Consumer orders
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.
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
- 0001
- Shipment, Order, Packaging, Item
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
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
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
- BAG
- Bag
- CTN
- Carton
- MIX
- Mixed Container Types
- PLT
- Pallet
- 25
- Corrugated or Solid
- 79
- Plastic
- 80
- Polyethylene Lined
- 94
- Wood
Number of units (pieces) of the lading commodity
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- 2
- Standard Carrier Alpha Code (SCAC)
Code identifying a party or other code
SCAC
Code specifying the method or type of transportation for the shipment
- A
- Air
- AE
- Air Express
- BU
- Bus
- C
- Consolidation
- CE
- Customer Pickup / Customer's Expense
- D
- Parcel Post
- E
- Expedited Truck
- H
- Customer Pickup
- L
- Contract Carrier
- M
- Motor (Common Carrier)
- R
- Rail
- S
- Ocean
- T
- Best Way (Shippers Option)
- U
- Private Parcel Service
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Ship Via/Routing Information.
Code indicating the level of transportation service or the billing service offered by the transportation carrier
- ND
- Next Day Air
- NS
- Not Served
- PB
- Priority Mail
- PI
- Priority Mail Insured
- SC
- Second Day Air
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
Code identifying type of equipment used for shipment
- 2B
- 20 ft. IL Container (Closed Top)
- 4B
- 40 ft. IL Container (Closed Top)
- AT
- Closed Container (Controlled Temperature)
- CI
- Container, Insulated
- CK
- Container, Heated/Insulated/Ventilated
- CN
- Container
- CV
- Closed Van
- CZ
- Refrigerated Container
- FT
- Flat Bed Trailer
- RC
- Refrigerated (Reefer) Car
- RT
- Controlled Temperature Trailer (Reefer)
- TA
- Trailer, Heated/Insulated/Ventilated
- TL
- Trailer (not otherwise specified)
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
Direct to Consumer Orders (BSN01 = 06):
- At least one occurrence of the REF segment with REF01 = CN or P8 is required.
DC, Store or International Orders (BSN01 = 00): - At least one occurrence of the REF segment with REF01 = CN, P8, BM or MB is required.
DC, Store or Intertationl Orders (BSN01 = 00) shipped Collect (FOB01 = CC)
If a Request for Routing (753) was sent and a corresponding Routing Instruction (754) was received, then an REF iteration with REF01 = S5 is required.
If FOB01=CC and BSN01=00 and TD503 (TD502=2) does not begin with UPS, FED, or FDE:
then Load ID (AppointmentNumber / REF02 (REF01=S5)) is Mandatory
Prepaid Shipments: If the FOB01 qualifier is PP (Prepaid), REF01 = S5 is not required as no 753 should have been sent.
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
- CN
- Carrier's Reference Number (PRO/Invoice)
- IK
- Invoice Number
Used to transmit the Commercial Invoice number
- MB
- Master Bill of Lading
- P8
- Pickup Reference Number
- S5
- Routing Instruction Number
This is the Load Number (BGN02) from the 754 (Routing Instructions) transaction
- ZM
- Manufacturer Number
Manufacturers ID (MID) Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time Reference
To specify pertinent dates and times
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
- CF
- Collect, Freight Credited Back to Customer
- FO
- FOB Port of Call
- PB
- Customer Pick-up/Backhaul
- PP
- Prepaid (by Seller)
- TP
- Third Party Pay
Code identifying type of location
- FOB02 is the code specifying transportation responsibility location.
- AC
- City and State
- DE
- Destination (Shipping)
- OR
- Origin (Shipping Point)
- PE
- Port of Entry
A free-form description to clarify the related data elements and their content
Code identifying type of location
- FOB06 is the code specifying the title passage location.
- AC
- City and State
- DE
- Destination (Shipping)
- OR
- Origin (Shipping Point)
- PE
- Port of Entry
A free-form description to clarify the related data elements and their content
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
Vendor
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
Not used when N101=SF
- 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.
Not used when N101=SF.
Additional Name Information
To specify additional names
Address Information
To specify the location of the named party
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.
City
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.
State
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Zip Code
Code identifying the country
Country Code
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- IC
- Information Contact
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- FX
- Facsimile
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
Vendor
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
Not used when N101=SF
- 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.
Not used when N101=SF.
Additional Name Information
To specify additional names
Address Information
To specify the location of the named party
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.
City
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.
State
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Zip Code
Code identifying the country
Country Code
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- IC
- Information Contact
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- FX
- Facsimile
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
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
Purchase Order Reference
To provide reference to a specific purchase order
Identifying number for Purchase Order assigned by the orderer/purchaser
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- PRF04 is the date assigned by the purchaser to purchase order.
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- 19
- Division Identifier
Mandatory
- CO
- Customer Order Number
Required if present on the Purchase Order
- IA
- Internal Vendor Number
Cabelas assigned Vendor Number - Mandatory
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Only used for shipments to the DC or Store, not Direct to Consumer orders
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
- CT
- Country of Origin
- Z7
- Mark-for Party
Code designating the system/method of code structure used for Identification Code (67)
Required when N101 = BY or Z7
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.
Required when N101 = BY or Z7
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
Marking, Packaging, Loading
To describe marking, packaging, loading, and unloading requirements
Code identifying loading or unloading a shipment
- 03
- Mixed
Reference Identification
To specify identifying information
REF01 of LT isrequired for products that have Batch or Lot numbers associated to them.
Use this segment if the single SKU carton (all quantities) have the same Lot number, else use line level REF segment.
When REF01 = CR, REF02 must equal 'True' or 'False' and REF03 must equal 'oversizeCartonFlag' or 'palletizationFlag'
This is used to communicate if a carton/pallet is oversized (REF02 = True and REF03 = oversizeCartonFlag ) or overweight (REF02 = True and REF03 = palletizationFlag ) per the agreed upon standards.
Code qualifying the Reference Identification
- CR
- Customer Reference Number
- LT
- Lot Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
Shipments to the Cabela DC or Store require MAN01 of GM. If a shipment is made to the DC or store and is being shipped via Parcel Carrier both qualifies GM and CP are required. GM should be sent in MAN01 and CP in MAN04.
Direct to Consumer shipments require qualifier CP in MAN01.
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
- 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.
SSCC18 (UCC128) Carton Number
Max Length = 20
Code specifying the application or source of Marks and Numbers (87)
- CP
- Carrier-Assigned Package ID Number
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN05 and MAN06 are used, MAN05 is the starting number of a sequential range, and MAN06 is the ending number of that range.
Date/Time Reference
To specify pertinent dates and times
This segment is required for products that have an expiration date associated to them.
Use this segment if a single SKU carton (all quantities) have the same expiration date, else use the line level DTM 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.
- I
- Item
Item Identification
To specify basic item identification data
One of UP,IN,SK must be returned
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.
- IN
- Buyer's Item Number
- 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)
- VA
- Vendor's Style Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- EAN/UCC - 13
- 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)
- UK
- EAN/UCC - 14
Identifying number for a product or service
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
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- SN103 defines the unit of measurement for both SN102 and SN104.
- AS
- Assortment
- BG
- Bag
- BK
- Book
- BN
- Bulk
- BO
- Bottle
- CA
- Case
- CQ
- Cartridge
- CT
- Carton
- DR
- Drum
- DZ
- Dozen
- EA
- Each
- FT
- Foot
- GS
- Gross
- HU
- Hundred
- IN
- Inch
- LB
- Pound
- OZ
- Ounce - Av
- PH
- Pack (PAK)
- PK
- Package
- PL
- Pallet/Unit Load
- PR
- Pair
- Q4
- Fifty
- RL
- Roll
- SO
- Spool
- TB
- Tube
- TH
- Thousand
- UN
- Unit
- VC
- Five Hundred
- YD
- Yard
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
Code identifying the general class of a product or process characteristic
- 08
- Product
- 73
- Vendor color description
- 74
- Vendor size description
A free-form description to clarify the related data elements and their content
Product Description
Carrier Details (Special Handling, or Hazardous Materials, or Both)
To specify transportation special handling requirements, or hazardous materials information, or both
Reference Identification
To specify identifying information
REF01 of LT is required for products that have Batch, Lot or serial numbers associated to them.
Use this segment if the pack contains multiple SKUs.
REF01 of SE is required for any products that have a serial number associated with them. There should be a unique REF iteration for each unique serial number in this carton.
Code qualifying the Reference Identification
- LT
- Lot Number
- SE
- Serial Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time Reference
To specify pertinent dates and times
This segment is required for products that have Expiration Dates associated to them.
Use this segment if the pack contains multiple SKUs.
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- Number of line items (CTT01) is the accumulation of the number of HL segments.
If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
Total number of line items in the transaction set
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
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.