A four-page category listing arrived on 15 September 2026 as page one of four printed with page three of four. Pages two and four were not in the packet [TARGET]. The category is a refrigerant heat-exchanger category under another national scheme, and the appendix lists a product series. The review that received it states both halves of the result. Series-level material was received. The attachment cannot confirm the item identifier, the manufacturing location, or the conditions of use for the liquid-to-liquid duty this project needs, still less listing of the assembled unit. The missing pages equally fail to support the opposite inference, that the manufacturer holds no such listing. The project's own register of statements that may not return had already written the rule the attachment tests: using UL components does not make the cabinet UL Listed [FACT].
The Attachment Is Incomplete Even as a Component Listing
Certification on this project is written as three states that may not be blurred together [TARGET]. Components inside an enclosure may hold their own listings, and those listings do not transfer to the assembly; recognised components additionally carry conditions of use. The assembly itself may be type-listed at the factory under an applicable standard family with follow-up inspection and a mark applied before shipment. Or the assembly may arrive unmarked and be evaluated in the field by the testing laboratory, which is conditional because the authority has to accept that report and the code adoption question behind it is unanswered.
The attachment sits in the first state and is incomplete even there. A series-level category page is not an assembly mark. The exposure ends where a complete assembly listing names the item identifier, the manufacturing location and the conditions of use for this duty; that equipment then sits on the factory route.
The same review records the electrical half. Component manufacturers holding listings does not mean the specific model is covered. The listing subject and date for the assembled unit are undetermined. The single-line diagram, dual-supply transfer arrangement, reverse-power prevention, protective device schedule and short-circuit current rating table were not submitted. Schedule promises about future listing are recorded as promises.
Field Evaluation Is Not a Substitute for Factory Listing
The procurement package refuses to treat field evaluation as an equivalent route, and gives three differences [TARGET]. Timing: factory listing fails before shipment, field evaluation fails with the equipment already on site, and return under delivered-duty-paid terms means unwinding a completed customs entry. Predictability: factory listing is visible during production, while a field result rests on an assessor's judgement on site and then on a second variable, whether the authority accepts the report. Quantity: factory listing amortises across a batch, field evaluation is normally charged per unit with attendance, and its cost and duration grow with the count.
The clause that carries this is written as an information duty. Each supplier declares its route per enclosure and per unit, with blanket statements refused, and a factory route must name the standard family, the listing-scope description and the follow-up inspection arrangement without substituting component certificates. A field route must state five things [TARGET]:
- who commissions the evaluation;
- who pays for it;
- the expected schedule structure;
- who carries remedy and return responsibility if it fails;
- who holds storage while remedy runs.
Omitting one of the five leaves that difference with the buyer, which is why the clause counts them rather than describing them.
The Package Requires a Declaration, Not a Listing Promise
The package also converted its compliance clause from a promise into a declaration. It requires the standard family and version year the product was built to, a description of existing evidence with its conclusions removed, and the supplier's own list of known differences against the destination code system. It declines to accept a supplier undertaking that the equipment meets the code the authority will adopt, on the ground that such an undertaking cannot be performed and carries no evidentiary weight. A promise clause buys a free sentence. A declaration clause is the only pre-order window on an uncrossable listing gap.
The package forbids itself from writing a listing conclusion at every enquiry level, including the level at which an order would be placed. Drafting the ten listing clauses is not sending them. The send-out column on every package remains forbidden.
Limits and open items
Confirmed: using UL components does not make the cabinet UL Listed. [FACT]
Register figures, not obtained evidence: the three states; the three differences between factory listing and field evaluation; the five field-route declaration items; the six-link evidence chain; the two of four printed pages; and the ten clauses that can be written while both dates stay empty. [TARGET]
Open: a supplier declaration of route for any enclosure; the listing subject and date for the assembled cooling unit; the two missing pages; laboratory scheduling; and the authority's position on field evaluation. Neither of the two nodes the project cannot accelerate has a document behind it. The enquiry file has not been issued. Nothing here is a listing conclusion. [HOLD]
Two nodes on the evidence chain answer to nobody on the project: the testing laboratory's scheduling and the authority's acceptance. The chain runs from the enquiry clause through the supplier declaration, the record engineer's applicability check, the laboratory report and the authority's acceptance to energisation, and only the last link releases anything [TARGET]. All ten listing clauses can be written into the template while both dates stay empty, because none of them depends on an unclosed technical input [TARGET].
Ask for the Listing-Route Date and the Authority Date
The critical path for this equipment is therefore neither enquiry nor price comparison but two dates: the date the listing route is fixed, and the date the authority's position is known. Until those two exist, a component mark in the packet is still a component mark.
© 2026 K&K Data Service Inc. All rights reserved. Reproduction or republication is permitted only with clear attribution to K&K Data Service Inc. and a working hyperlink to the canonical URL of this article. Excerpts must preserve the technical context, maturity labels, assumptions, and limitations. No excerpt may imply project approval, field validation, certification, or endorsement that the original article does not state.
Source: K&K Data Service Inc., “UL Components Do Not Make a Listed Assembly,” https://www.kkdatasvc.com/lab/fire-structure-site-and-compliance/ul-components-do-not-make-a-listed-assembly/.
Discuss This Constraint. If your project record shows a different result, or the same failure domain under another name, we want to see it. Email inquiry@kkdatasvc.com or use the contact page.