Compare the applicable documents before comparing the headline warranty period. A useful PV module warranty file connects the exact model, destination, contracting parties, applicable revision, start-date evidence and claim procedure. Separate product-defect coverage from power-performance coverage, then identify the records and responsibilities needed to use each route. A quotation that states only a number of years leaves those purchasing questions unanswered.
This guide provides an RFQ and document-control method for module buyers, distributors and project procurement teams. It does not decide whether a particular loss is legally covered. Have the responsible commercial or legal reviewer resolve conflicts between the purchase agreement, warranty statement and applicable local requirements before order release. No manufacturer example below establishes terms for a SINAWATTS quotation or an unspecified module purchase.
The objective is a package another person can understand after delivery: what was bought, which statement was confirmed, where each module went, and how an observed problem would be documented. That package supports supplier comparison even when no claim occurs. For technical shipment records, use the separate flash-test and EL report traceability guide; those reports and the warranty file answer different questions.
Start with document identity, not a marketing badge
Create one applicability record for each offered module configuration. Copy the complete model designation, including suffixes, rather than shortening it to a product family. Record the installation country and proposed use, the quotation number and the purchasing entity. Ask the supplier to identify the warranty issuer separately from the seller. A familiar brand name is not a complete record of those relationships.
Manufacturer publications show why this matters. Canadian Solar's January 2026 TOPBiHiKu revision 1.6 identifies specified models and an order-date applicability condition, excludes Australia, New Zealand and China, and distinguishes product defects from performance coverage. The document must be matched to the actual transaction. Canadian Solar TOPBiHiKu limited warranty, revision 1.6.
Its separate US revision 1.5 names CS Power Systems Inc., identifies a different applicable model list and contract-date condition, and limits its stated scope to products sold and installed in the United States. A higher revision number on another regional file is not enough to choose between them. Canadian Solar US TOPBiHiKu limited warranty, revision 1.5.
Save the confirmed PDF with its original title and revision, its source address and the retrieval date. Keep the supplier's applicability confirmation beside it. A download date records when someone obtained a file; it does not, by itself, establish which version governs the purchase. If the supplier sends a later file during negotiation, request an explanation and preserve both versions with their decision history.
Build a warranty comparison sheet with explicit unknowns
Use a comparison sheet that distinguishes an unanswered question from a confirmed exclusion. Blank cells are easy to interpret optimistically. Write “not supplied,” “supplier clarification pending” or “confirmed by document reference,” and name the person responsible for closing the item. The following is a proposed purchasing worksheet, not a reproduction of any manufacturer's warranty.
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Comparison field | Evidence to place in the file | Action if incomplete |
|---|---|---|
| Offered product | Full model, suffix and quotation line | Ask for an exact cross-reference |
| Geographic scope | Destination and applicable regional statement | Hold the applicability conclusion |
| Issuer and seller | Named entities and stated service route | Clarify who receives the inquiry |
| Governing document | Revision, effective conditions and written confirmation | Preserve competing files for review |
| Product coverage | Relevant clause and defined covered condition | Avoid substituting a brochure summary |
| Performance coverage | Defined output basis and verification procedure | Request the missing technical reference |
| Start event | Applicable clause plus supporting delivery records | Flag the date as unconfirmed |
| Notice and authorization | Trigger, applicable deadline, responsible person and return permission | Resolve the required action before shipment or work |
| Claim and remedy process | Required evidence, authorization and cost allocation | Assign commercial follow-up |
Attach a short decision note, rather than filling the sheet with pasted legal paragraphs. For example: “The offered suffix is absent from the supplied model list; supplier confirmation requested.” This is an observable discrepancy. “Warranty is invalid” would be a legal conclusion the worksheet cannot establish. Keep the decision proportionate to the evidence available.
Keep product, performance and site output questions separate
Use three separate headings in the RFQ response. Under product, ask which documented conditions are covered and what evidence establishes the relevant defect. Under performance, ask how the warranted output is defined and how a reported shortfall is evaluated. Under site output, record the project's operational observations and who will investigate them. Do not compress all three into “panel not performing.”
An operating report may be useful evidence of an observed change, but the purchasing team still needs a bridge between that observation and the stated verification method. Record the affected assets, observation interval, system configuration and available measurements without declaring the cause. Request the agreed next diagnostic step from the appropriate technical party. A clear problem statement is more useful than an unsupported attribution to module degradation.
The RFQ should ask for the performance statement's measurement reference, treatment of measurement uncertainty, applicable module face or configuration, and the route for resolving conflicting results. Record the answer as a document reference and an assigned reviewer. Do not invent a universal field-test pass limit. The STC and NMOT datasheet guide helps organize the different measurement descriptions; it does not replace the applicable warranty procedure.
Keep qualification evidence in its own folder. A PID, LID or LeTID test report concerns a defined test and sample. The commercial question here is which document governs the delivered model and how an actual concern is handled. Link the folders through product identity, while retaining their different purposes.
Record the event that starts the warranty clock
Do not automatically populate the start-date field with the invoice date, commissioning date or today's date. First identify the event defined by the applicable statement, then collect the records needed to establish it. Preserve the raw dates as separate fields so a later reviewer can see how the selected date was obtained.
Trina Solar's June 2026 global warranty, revision AC, covers listed products; Germany and Turkey use country-specific statements. Its start date is the earlier of initial delivery to the customer by Trina Solar or its authorized manufacturer under Incoterms 2020, and six natural months after the module's factory-out date identified through its serial number. This is a document-specific example, not a date inferred from a downstream receipt. Trina Solar global limited warranty, sections 1, 4 and 12.
For a project buying stored inventory, ask who can provide the relevant upstream records before accepting a date supplied in a sales email. If the evidence is missing, mark the date unresolved and request clarification. The useful purchasing result is a traceable calculation approved by the responsible reviewer, not a convenient date that makes two bids appear comparable.
Design serial-number records before modules arrive
Build an asset register that can join commercial documents to physical modules. Use one row per module where practical, with the full serial number treated as text. This preserves leading zeros and avoids spreadsheet conversion of long identifiers. Keep pallet references as separate fields, since a pallet identifier and a module serial are different records.
The proposed register should include model, serial, purchase line, invoice reference, shipment or pallet reference, receiving record, installation location and the applicable document-set identifier. Add a status field for delivered, installed, held for investigation, replaced or transferred. Record who changed the status and why. Avoid embedding the only copy of a serial number inside a photograph filename.
Test the register with a small sample before accepting the entire handover. Select a row, locate the corresponding label image and receiving record, then follow it back to the purchase line. Try the reverse route from a physical label to the register. This is a practical document check, not evidence that the module passed an electrical test or that coverage has been accepted.
When modules move between storage locations or project areas, update the location reference without overwriting the earlier entry. Keep replacement serials linked to the units they replaced. Agree who maintains the register after handover; an installer, distributor and owner may otherwise each assume another party has retained the source files. Request a usable export instead of access that depends indefinitely on one person's account.
Prepare claim evidence without inventing a diagnosis
A useful initial incident record describes what was observed, when, where and on which identified units. Separate photographs, measurements, maintenance events and technical opinions. Label unconfirmed explanations as hypotheses. Do not rewrite an uncertain observation as a manufacturing defect merely to fit a claim category.
Canadian Solar's cited revision 1.6 requests supporting claim information including quantities, serial numbers and purchasing proofs; it also requires authorization before product returns. Use the applicable instructions to plan the evidence route before arranging a return. Canadian Solar claim process and remedies.
Trina Solar revision AC describes a customer-service portal route and asks for purchasing evidence, product and claim details, editable serial numbers, and supporting photographs or data. Its applicant requirements also address the warranty-right holder or an authorized representative. These are specific documentary requirements, not a promise that a complete upload will be accepted as a valid claim. Trina Solar claim procedure, section 8.
Make an incident index with separate links to original files and later interpretations. Preserve file dates, the person making the observation and the equipment or method used for measurements. Let qualified personnel decide any physical examination or testing. The procurement role is to maintain an understandable evidence chain and obtain written instructions, not to improvise a destructive investigation.
Add an action log for any notice or authorization requirement: the applicable clause, triggering event, evidenced event date, required action, due date and assigned owner. Ask the responsible reviewer to resolve ambiguous timing promptly. Do not substitute an internal RFQ response date for a contractual notice requirement or invent a standard deadline for every manufacturer.
Send the offered module identity, destination and document list with your RFQ inquiry. State which records are available and which supplier confirmations remain open so the requested response has a defined scope.
Separate remedy scope from project recovery costs
Ask the commercial reviewer to distinguish the available remedy from the work required to restore a project. The comparison should identify the relevant clause for each cost category, any separate written agreement and unanswered questions. Do not assume that a replacement-module reference also answers every logistics, access or installation question.
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Project activity | Question for the commercial review | Record to retain |
|---|---|---|
| Investigation | Who authorizes the method and any external work? | Written scope and authorization |
| Handling and movement | Which party arranges and pays each movement? | Agreed responsibility record |
| Removal and installation | What work is included or separately quoted? | Scope with explicit exclusions |
| Replacement selection | Who checks the proposed substitute against the system? | Engineering acceptance record |
| Service coordination | Who communicates decisions to the asset owner? | Named contact and escalation route |
These are proposed questions, not assertions that a particular manufacturer covers or excludes those activities. Keep commercial allocation separate from technical acceptance. A proposed replacement still needs a check against the actual installation, even when its paperwork has been processed. For associated hardware, the solar accessories range is a starting point for a separate inquiry; no module warranty compatibility is implied by a category listing.
Worked example: compare two hypothetical document packages
Consider a fictional buyer comparing two offers for the same project destination. These are invented document scenarios, not supplier performance data, customer cases or legal conclusions. Neither offer is approved merely because it looks more complete.
Offer A includes a brochure with a long warranty headline and a PDF for a broad product family. The quotation uses a model suffix not shown in that file. The seller says registration can happen after delivery but has supplied no procedure. Its planned serial handover is a photograph of each pallet label. The purchasing record should identify three open issues: exact applicability, registration instructions and module-level identity.
Offer B identifies the offered suffix, a regional statement and the supplier's written applicability confirmation. It proposes an editable module register and names the person providing delivery evidence. However, the quote does not explain who will assemble an incident file after installation, and the project team has not reviewed replacement acceptance or associated costs. Those remain open items rather than automatic advantages hidden inside a headline duration.
The buyer sends each bidder the same clarification sheet. A receives a request for the model-document cross-reference and a sample serial handover. B receives a request for service responsibilities and the outstanding cost references. The buyer sets an internal response date for comparison; this is an RFQ deadline, not a manufacturer claim deadline.
After replies arrive, update each cell with the new evidence and retain the earlier status. If A resolves its gaps, compare the completed packages. If B leaves a material question open, do not mark it accepted simply because it replied first. This method produces a reviewable procurement decision without predicting future claim success or assigning a monetary value to an unverified promise.
Allocate records across the purchasing handover
Assign the evidence while the relevant people can still supply it. The buyer can own the purchase-document index; logistics can provide receiving references; the installer can provide the as-installed asset map; and the operating team can maintain observation records. Adapt those proposed roles to the actual contract instead of assuming the organizations have already accepted them.
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Stage | Proposed handover output | Check before closing the stage |
|---|---|---|
| RFQ comparison | Applicability sheet and unresolved items | Every conclusion has a reference |
| Order confirmation | Agreed document set and named owners | Changes from the quotation are resolved |
| Delivery | Serial register and receiving evidence | Sample records reconcile both ways |
| Installation | Asset-location map and handover index | Ownership of future updates is assigned |
| Operation | Incident and maintenance records | Original observations remain retrievable |
Use the module packaging and storage guide to define receiving evidence and the cleaning and maintenance record guide for that separate operational handover. This article coordinates document ownership; it does not prescribe cleaning methods or replace the installation manual.
Reopen the review when the offer changes
Treat a model substitution as a document change requiring review, even if the quoted power class is unchanged. Request a revised applicability sheet and identify which existing records remain valid. The same approach applies when the destination, intended installation, contracting entity or supplied document revision changes. Do not quietly replace a file and leave the old approval note attached to it.
For staged deliveries, retain a shipment-to-document map. Ask the supplier to explain whether each delivery uses the same confirmed configuration and document set. A later shipment should not inherit an earlier conclusion solely because both appear under one project name. Record any approved deviation explicitly, including the affected purchase lines and the person authorized to accept it.
When transferring an asset or changing service providers, include a document inventory in the handover. Ask the responsible reviewer whether any assignment, notice or authorization requirements apply. An organized folder cannot establish transfer rights by itself. The practical objective is to preserve the evidence needed for that review and prevent the next operator from starting with an unexplained brochure.
Use separate comparison and release decisions
Give the package a status that reflects the decision actually made. Ready for comparison means the offers contain enough identified information to evaluate against each other. Ready for order review means material questions have written responses and named reviewers have addressed them. Handover accepted means the agreed delivery records have arrived and passed the document checks. None of these internal statuses means that a future warranty claim has been approved.
For each status change, retain a short evidence note and a reviewer. If the sample serial file contains a transcription error, return that record for correction and check the corrected mapping. Do not silently fix it in the buyer's copy while the supplier continues using a different identifier. If a document refers to an obsolete quotation line, correct the cross-reference before recording the package as complete.
Keep outstanding items ranked by their effect on the decision. An unresolved offered-model match prevents an applicability conclusion. A missing administrative contact may require an assigned follow-up, depending on the agreed release rules. Let the responsible team define which gaps block its purchase; do not give every missing field the same automatic outcome. This makes the review useful without turning document collection into a substitute for commercial judgment.
Buyer FAQ
Is the longest advertised warranty automatically the best offer?
No comparison is complete from the duration alone. First establish that the supplied statement matches the offered product and transaction. Then compare its defined scope, evidence route and commercial responsibilities with the project's needs. Record unknowns explicitly. A longer headline does not close a missing model reference or identify who will maintain the asset records.
Can we use the newest warranty PDF for modules already purchased?
Do not make that assumption. Retain the document confirmed for the purchase and request written clarification if a newer file appears. Record the applicable conditions and any agreed change. A website publication date or a download timestamp is useful for document control but does not by itself settle the terms of an earlier transaction.
Does a low site-energy reading prove a performance-warranty claim?
It documents an observation to investigate. Preserve the interval, affected assets and available operating information, then follow the applicable technical verification route. The procurement team should avoid declaring a cause from a single summary value. Ask who evaluates the concern and which additional evidence is required before commissioning work or accepting a final diagnosis.
What if the supplier cannot provide an editable serial list?
Ask for an alternative that can be reconciled to the delivered modules and retained by the future record owner. Trial the proposed format before handover and document any manual transcription checks. If identification remains incomplete, leave that issue open in the release decision. A collection of pallet photographs should not be silently treated as a verified module register.
Does completing a claim form mean coverage has been accepted?
Treat submission, acknowledgment, technical review and resolution as separate statuses. Keep correspondence and assigned actions linked to the incident record. A submitted file proves that information was sent through a route; it does not establish a coverage decision. Obtain the relevant written response before recording a claim as accepted or a proposed remedy as agreed.
Should the RFQ ask for a specific warranty duration, MOQ or delivery promise?
State the project's requirements and ask the supplier to confirm its actual offer, supporting documents and exceptions. Request quantity and delivery terms separately from warranty applicability so neither is inferred from the other. This guide supplies no standard MOQ, guaranteed dispatch date or universal warranty duration. Compare only the terms actually returned for the defined purchase.
Prepare a warranty-document RFQ that can be answered
Send the full model or proposed specification, destination, intended installation, purchasing parties, quantity schedule and current quotation references. Attach the warranty files already received and a short list of unresolved questions. Request an applicability confirmation, serial-register sample, start-date evidence plan, incident-contact route and the commercial references needed for your comparison.
Name the person who will accept the document package and the records required at delivery. Keep technical module evaluation, commercial terms and future evidence ownership connected without treating them as interchangeable approvals. The result should be a traceable purchasing file, with clear open questions wherever evidence is still missing.
Request an RFQ review with your module document list and purchasing requirements.