“Class A solar panel” is often used as if it were a complete rooftop fire specification. It is not. A module can have an identified fire type or module-level classification, while the installed rooftop system classification depends on the tested or certified combination of module, mounting system, roof covering and installation conditions. Standoff, slope, array geometry and required accessories can be part of that boundary.
For procurement, the decisive question is not whether a brochure contains the word fire. It is whether the exact quoted module and rack can be installed over the actual roof covering in the proposed geometry while preserving the fire classification required by the project’s adopted code and authority having jurisdiction.
This guide addresses that evidence chain. It is separate from the solar mounting corrosion and structural-load guide, which deals with materials and mechanical load paths, and from the roof flashing and water-shedding guide, which treats roof penetrations and drainage. A fire-classified combination can still have an inadequate structure or leak; structurally adequate and watertight hardware can still fall outside the tested fire configuration.
This article does not claim a fire classification for any SINAWATTS product, module, rack, roof assembly, factory or project. It does not establish certification, testing capability, installation capability, price, stock, MOQ or lead time. Obtain current product records and written project approval from the module manufacturer, mounting manufacturer, roof manufacturer, qualified design team, certification body and authority having jurisdiction.
Direct answer: what should a rooftop fire RFQ require?
Ask each bidder to return a configuration schedule containing:
- exact module manufacturer, model, construction suffix, fire type/class marking, certification category, file or certificate number and current datasheet/nameplate evidence;
- exact mounting-system manufacturer, system name, rail or rail-less model, clamp/retention parts and UL 2703 or other applicable system record;
- the resulting system fire classification for that module/rack combination, not only a module statement;
- roof-covering manufacturer, product, listing/classification, substrate/deck and assembly where the evaluation requires them;
- roof slope, module orientation and array layout limits;
- minimum and maximum module-to-roof standoff or other defined separation datum;
- required perimeter treatment, skirts, deflectors, flashings, setbacks or accessories;
- mounting orientation, attachment method and any limitations on rails, clamps or exposed gaps;
- installation manual and certification-record revisions that contain those conditions;
- written mapping from tested models to the exact offered SKU and declaration of differences; and
- project code edition, required roof/system classification and authority acceptance path.
Require the bidder to highlight the applicable pages and table rows. A stack of certificates without a marked configuration transfers the interpretation risk to the buyer.
Separate four labels that are often confused
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Evidence item | What it can establish | What it does not establish by itself |
|---|---|---|
| Module fire type or module-level class | Construction identity used in a module safety/fire evaluation | System class on every roof or rack |
| Mounting-system certification | Covered rack components and evaluated functions/conditions | Compatibility with every module and roof |
| Roof-covering classification | External fire performance of the identified roof covering/assembly | Performance after any PV array is added |
| Rooftop PV system fire classification | Result for an identified module/rack/roof configuration under stated conditions | Structural, waterproofing or electrical adequacy outside that scope |
UL Solutions’ official PV mounting certification overview, checked on 2026-09-28, says UL 2703 covers mounting systems, mounting devices, clamping devices and ground lugs used with flat-plate modules. It also explains that rooftop fire classification concerns a specific PV module and racking system and evaluates the installation’s resistance to external fire exposure so the roof’s fire performance integrity can be maintained. UL Solutions PV mounting systems certification.
The phrase specific module and racking system is the key procurement boundary. A rack listing cannot be combined casually with a module carrying a familiar fire label. The certification record and installation documentation must show that the offered combination is covered.
Do not confuse module fire type with system fire class
In North American documentation, module manuals and datasheets may state a module fire type, while mounting-system documentation provides the resulting system fire class for named module types and conditions. The type is an input to the combination; it is not automatically the roof system’s final class.
Canadian Solar’s general installation manual EN-Rev IM/GN-EN/3.1, dated November 2025 and checked on 2026-09-28, illustrates this distinction. It identifies fire types/classes for covered module constructions and says detailed types should be checked on the datasheet or product nameplate. Under its UL 61730 system fire provisions, it states that the module fire rating is valid only when installed as specified, calls for installation over a fire-resistant roof covering rated for the application, and describes evaluation of UL 61730-certified modules with a UL 2703-certified mounting system and roof covering. It also tells installers to observe mounting-system limits such as inclination and accessories needed to maintain a system fire class. Canadian Solar installation manual.
Those statements apply only within that manual’s product scope. They should not be copied as generic permission for another module or rack. They demonstrate the evidence logic: module identity, mounting configuration, roof covering and installation conditions must travel together.
Avoid mixing terminology from different schemes. “Type 1,” “Class A,” “Class C,” “reaction to fire,” “fire resistance” and “external fire exposure” are not interchangeable marketing synonyms. Record the exact standard, edition, jurisdiction and scope associated with each term.
Read IEC module safety evidence within its scope
IEC 61730-1:2023 defines construction requirements intended to support safe electrical and mechanical operation of PV modules and addresses prevention of electric shock, fire hazards and personal injury arising from mechanical and environmental stresses. IEC 61730-2:2023 lists safety-qualification test sequences and pass criteria intended to reveal breakdowns of internal or external components that could cause fire, electric shock or personal injury. The IEC pages also make clear that national or regional codes can add requirements. IEC 61730-1:2023 official scope and IEC 61730-2:2023 official scope.
An IEC 61730 certificate is therefore valuable module safety evidence, but it is not an automatic rooftop system classification for every jurisdiction. The RFQ must state whether the project requires IEC module safety qualification, a North American module fire type, an external-fire roof/system class, or another national scheme. Ask the qualified code professional to identify the exact approval route.
Do not convert one scheme’s label into another without a recognized basis. A module may be offered globally under related model names but have different certificates, labels or manuals for different markets. Request the certificate applicable to the destination and delivered model.
Define the actual roof covering and assembly
“Class A roof” is incomplete. Record roof-covering manufacturer and product, listing/designation, deck, insulation/cover board where relevant, underlayment, slope, age, repair layers and any existing overlay. Confirm the roof’s classification and warranty from current project records.
The PV system evaluation may assume a particular roof classification rather than one exact brand. Even then, the project must show the installed roof belongs to that permitted class and meets any substrate or slope limitations. A field description such as “asphalt shingles” or “metal roof” cannot establish that mapping.
Distinguish roof covering from roof structure. External-fire classification does not prove that rafters, deck or attachments can carry the array. The roof structural screw embedment guide covers that separate load path. Likewise, a roof-covering fire class does not approve penetrations or sealants; review waterproofing documentation independently.
If the roof will be replaced before PV installation, freeze the replacement covering and assembly early enough to verify the PV combination. A “like-for-like” roofing substitution can affect classification, warranty, flashing compatibility or standoff geometry.
Treat standoff as a controlled dimension
The air space between module and roof can influence flame spread and heat transfer. Certification or mounting-system instructions may define a minimum or range using a particular datum: roof surface to module frame, roof surface to module backsheet/glass, or another point. Copy the datum and tolerance into the drawing.
Standoff can vary with roof profile, rail height, attachment, flashing, clamp, frame thickness and local deck variation. A nominal rail height alone does not prove the installed separation. Prepare a section through every roof/mounting condition and calculate minimum and maximum credible standoff after tolerances.
Do not lower rails, change attachments or add spacers solely to meet a presumed fire dimension. Such changes can affect structural load, water shedding, bonding, cable clearance and manufacturer warranty. The exact mounting manufacturer should confirm the covered configuration, and the design team should approve all interfaces.
Where fire-class evidence specifies skirts, deflectors or perimeter accessories, include their exact part numbers, locations, gaps and fasteners. Treat missing accessories as a nonconformance, not a cosmetic omission.
Control slope, orientation and array geometry
Roof slope can be a certification condition. So can module portrait/landscape orientation, rail direction, array edge treatment and distance from roof boundaries. Ask the mounting supplier to return a marked plan and section showing compliance.
Do not assume a steeper slope is always more conservative. Fire behavior depends on the test method and airflow/flame path. Follow the documented range. If the roof contains multiple slopes, schedule each separately.
Array gaps and pathways can create discontinuities in the fire configuration. The certification may rely on module dimensions, row spacing or specific treatment at edges. A layout optimized after procurement can leave the documented configuration. Require a fire-class review when module size, orientation, row count, gap, skirt or setback changes.
For carports, canopies, façades or building-integrated PV, a conventional rooftop-rack classification may not apply. UL Solutions’ official BIPV overview explains that BIPV functions both as PV equipment and as building-envelope material and may be evaluated to standards such as UL 7103, UL 61730 and UL 790 depending on design/application. UL Solutions BIPV testing and certification. Identify the correct product category before using a rooftop-rack result.
Verify the certification record rather than the logo
Request the current certification database record or certificate, not only a logo on a brochure. The file should identify applicant/manufacturer, product category, models, evaluated functions and conditions. Obtain the installation manual revision referenced by the record.
Search by exact model and file where the certification body provides a directory. A certificate can be genuine but irrelevant because the offered model suffix, module type, rack generation or accessory set is outside its scope. Record the verification date and save the applicable pages under the project document-control policy.
Create a configuration cross-reference:
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Project field | Certification/manual field | Offered condition | Disposition |
|---|---|---|---|
| Module model/fire type | Covered module table | Exact SKU/nameplate | Match/hold |
| Rack system | Certified system/model | Quoted BOM | Match/hold |
| Roof covering | Required class/type | Existing/new assembly | Match/hold |
| Slope | Permitted range | Surveyed design | Match/hold |
| Standoff | Defined range and datum | Tolerance section | Match/hold |
| Orientation | Portrait/landscape limits | Array layout | Match/hold |
| Accessories | Skirt/deflector/edge parts | BOM and plan | Match/hold |
| Manual revision | Certification reference | Submitted instruction | Match/hold |
Any blank field is a technical hold point. Do not fill it with a statement that the products are “industry standard.”
Map tested construction to the offered module
Module fire behavior can depend on front/rear glass, backsheet, encapsulant, frame, junction box, cables and other construction details. Require the manufacturer to map the exact sales model and controlled BOM to the certified construction. A change from glass-backsheet to glass-glass, a different backsheet chemistry or a thinner front glass is not merely a wattage change.
IEC TS 62915:2023 sets out a uniform approach for maintaining module design and safety qualification after material or design modification. Its official scope says it contains a comprehensive retest matrix and separates IEC 61215 and IEC 61730 requirements. IEC TS 62915:2023 official scope. The manufacturer or certification body must apply the full technical specification; the buyer should ask for the resulting written disposition rather than attempt to decide from the public summary.
Require advance notification of changes to glass, encapsulant, rear layer, frame, junction box, cable, connector, adhesive, production site and certified mounting combination. The supplier should state whether the change affects only electrical output, also changes fire type, or requires a new system compatibility review.
Do not accept “same certificate family” without the annex or model list. Preserve the certificate revision used for approval and compare it with the delivered nameplate.
Resolve conflicts between module, rack and roof instructions
The module manual may require one clamp zone or standoff while the rack fire record assumes another. The roof manufacturer may restrict penetrations, adhesives or contact materials. Prepare a three-column requirements table and identify conflicts before ordering.
Examples include:
- the rack’s fire-class standoff conflicts with the module’s maximum unsupported geometry;
- a skirt required by the fire configuration obstructs roof drainage or module leads;
- the permitted roof slope differs from the project slope;
- a roof warranty requires an attachment not included in the rack configuration;
- module orientation allowed structurally is absent from the system fire record; or
- an accessory part changes bonding or cable-management details.
Do not let an installer select whichever manual appears less restrictive. Obtain written resolution from the responsible manufacturers and design authority. If no covered combination exists, choose a documented alternative or pursue the jurisdiction’s approved engineering/evaluation path; do not describe the unresolved assembly as certified.
Keep electrical and fire pathways coordinated
Cables and connectors must be routed so they do not rest on the roof or create an unapproved obstruction. Cable clips, conduit, junctions and rapid-shutdown equipment may occupy the air space included in the fire configuration. Confirm permitted positions with the rack and module documentation.
Bonding devices and ground lugs can also be model-specific. The mounting bonding and grounding clip guide explains how an evaluated electrical path depends on the exact module frame, rail, clip, fastener and installation. A fire-class record does not replace that verification.
Keep rooftop conductor and equipment requirements from the adopted electrical code in the project specification. Fire classification of the PV/roof combination does not establish conductor ampacity, overcurrent protection, rapid shutdown, arc-fault protection or workmanship. The project’s qualified electrical design remains separate.
Inspect the first installed array section
Approve a first article for every roof/rack/module configuration before full release. Verify:
- roof-covering identity and condition against the approved assembly;
- module model, nameplate and fire type/class field;
- rack, clamps, attachments and required fire accessories;
- slope, orientation, row edge and pathway arrangement;
- standoff at defined measurement points, including tolerance extremes;
- skirt/deflector continuity, gaps, fasteners and terminations where required;
- cable routing and clearance;
- bonding parts and hardware identity;
- flashing, drainage and roof-warranty details; and
- photographs tied to plan coordinates and inspector acceptance.
The first article does not reproduce a fire test. Its purpose is to show that the field configuration matches the accepted documents. Use calibrated or suitable measuring tools for controlled dimensions and preserve the datum in the inspection instruction.
Production inspection should sample every configuration and focus on transitions, array edges, penetrations, roof elevation changes and accessory terminations. A wide photograph of completed modules cannot verify hidden standoff or missing edge parts; collect evidence before access is lost.
Control substitutions and value engineering
Treat changes to any of these as fire-class review triggers:
- module manufacturer, model, fire type or construction;
- mounting-system generation, rail/rail-less component, clamp or attachment;
- roof covering, underlayment or deck assembly where relevant;
- roof slope, module orientation, standoff or array layout;
- skirt, deflector, flashing or perimeter accessory;
- module dimensions or frame profile;
- cable-management equipment occupying the tested cavity; and
- certification record or installation-manual revision.
A substitute can be physically compatible and still lack the accepted fire combination. A supplier letter saying “similar” is not enough unless the certification/approval pathway recognizes that mapping and the authority accepts it.
Value engineering should compare complete compliant systems. A cheaper rack that requires additional fire accessories, a different standoff or a module change may alter labor, roof detailing and structural design. Capture those effects in the commercial comparison rather than evaluating rail unit price alone.
Build a comparable fire-evidence matrix
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| RFQ field | Acceptable return | Hold point |
|---|---|---|
| Required classification | Project code/authority basis and exact target | “Class A preferred” without jurisdiction basis |
| Module identity | Exact model, fire type/class, current record and label | Brochure family or generic IEC/UL claim |
| Rack identity | Certified system and exact BOM | UL 2703 logo without system/model scope |
| Combination | Record/manual row linking module type and rack to system class | Separate module and rack certificates only |
| Roof | Identified covering/assembly and classification | “Metal” or “shingle” |
| Geometry | Slope, orientation, standoff datum/range and layout | Nominal rail height only |
| Accessories | Required parts, locations and installation details | Fire skirt shown only in a sales rendering |
| Change control | Tested-to-offered mapping and notification triggers | Uncontrolled equivalent materials |
| Field QA | First article and measurable inspection criteria | General completion photograph |
Rate applicability before price. An apparently higher class with an unidentified roof or missing standoff evidence is not a stronger bid.
Send a complete rooftop PV fire RFQ
Issue the roof survey, roof-covering record, required code classification, module layout, slope, structural mounting concept and authority requirements. Ask bidders to return the exact module/rack combination, marked certification record, section dimensions, accessories and deviation register.
Request commercial terms for the accepted BOM as written supplier returns: unit price, MOQ, availability, sample timing, lead time, packaging, document language, change-notification period and support responsibility. This guide does not supply or imply those terms.
When the module type, rack system, roof covering and geometry are aligned, send the project-specific rooftop fire RFQ. Include the configuration matrix so every bidder prices the same certified scope.
Buyer FAQ
Is a “Class A module” automatically a Class A rooftop PV system?
No. The installed result can depend on the specific module fire type, certified mounting system, roof covering, slope, standoff and accessories. Verify the combination in current system records and manuals for the destination jurisdiction.
What is the difference between a module fire type and a system fire class?
The module fire type identifies a module construction used in an evaluation. The system fire class describes performance of an identified rooftop combination under stated installation conditions. The type is an input; it is not the complete system result.
Does UL 2703 certification cover structural roof capacity?
No. UL describes the covered mounting equipment as part of a nonstructural building component and discusses system fire classification for module/rack combinations. Project structural loads, roof capacity and attachments require separate design and evidence.
Is an IEC 61730 certificate enough for a U.S. roof permit?
Do not assume so. IEC 61730 is module safety qualification, while national and local codes can require additional module, rack and roof-system classifications. The authority having jurisdiction and qualified design team should define the approval evidence.
Why does module-to-roof standoff matter?
The air space can influence flame and heat behavior, and certification documentation may define a range using a specific datum. Show minimum and maximum installed standoff after tolerances; nominal rail height is not sufficient.
Can we change from portrait to landscape without another fire review?
Only if the current system evidence and manuals cover the revised orientation and all other conditions remain satisfied. Orientation can affect support, gaps, edge treatment, cable routing and configuration scope.
Does a metal roof automatically meet the roof-covering condition?
No. Identify the actual roof-covering product and assembly, its classification, slope and any conditions in the PV system record. “Metal roof” is too broad for a traceable approval.
Are skirts or deflectors optional cosmetic parts?
Not when they are required to achieve the documented system fire class. Include exact parts, locations and fasteners in the BOM and field inspection. Their omission changes the accepted configuration.
Can an equivalent module with the same fire type be substituted?
Only through the documented certification and project change process. Confirm exact model/type mapping, dimensions, construction, rack compatibility and authority acceptance. A shared label alone does not establish equivalence.
What should the first-article inspection measure?
Verify roof covering, module/type, rack parts, slope, orientation, defined standoff, required accessories, cable routing, bonding and roof details. Tie photographs and measurements to the approved configuration row and plan location.
Does this article verify SINAWATTS fire certification or testing?
No. It is an evidence-based procurement method. Require current written certification, model scope, laboratory or certification-body records and project approval for every offered product and combination.