Solar Street Light Warranty Terms — Scope, SLA & Evidence (Tender-Ready)

In real projects, “5-year warranty” is meaningless unless the scope, claim workflow, SLA, and evidence requirements are written clearly. This page gives an evidence-based warranty framework you can copy into RFQs/BOQs so bids become comparable and warranty claims stay enforceable.

Where This Guide Fits

TL;DR (What makes a warranty enforceable)

  • Component-level scope: battery, controller, LED/driver, PV module, housing — each must have defined terms.
  • Clear SLA: response time, diagnosis time, replacement/dispatch time, and who pays shipping.
  • Evidence chain: serial-to-location mapping + commissioning record + installation photos + maintenance logs.
  • Defined exclusions: misuse, improper installation, vandal/theft, extreme events — written clearly.

Use these operational pages as the “evidence backbone”:

1) Define warranty scope by component (do not accept one-line promises)

Require the supplier to list warranty terms by component, not only a single headline number.

Minimum component list

  • Battery pack (and BMS): coverage scope + replacement method + evidence required
  • Controller: charging/lighting logic failures, configuration support policy
  • LED module & driver: functional failure coverage; define if lumen maintenance is included (if promised)
  • PV module: functional failure vs performance degradation (define what is actually covered)
  • Housing / lens / seals: manufacturing defect vs installation/ingress mistakes
  • Mounting hardware (brackets/fasteners): corrosion policy (especially coastal/humid)

Related engineering references (to prevent disputes):

2) Specify the warranty SLA (response, diagnosis, and replacement)

Without an SLA, warranty is often “best effort”. Require these minimum SLA items:

  • Response time: supplier replies within X business hours
  • Diagnosis time: supplier provides a diagnosis plan within X business days after receiving evidence
  • Replacement/dispatch time: parts shipped within X business days after approval
  • Logistics rule: who pays shipping, customs, and whether advance replacement is available
  • DOA policy: how dead-on-arrival is handled and within what window

Procurement tip: request “parts-only vs full-unit replacement” policy. For remote projects, parts-only serviceability is often faster and cheaper.

3) Define claim evidence requirements (this is the real warranty)

A warranty claim is an evidence workflow. Require the evidence list upfront so installers and owners can comply.

Mandatory evidence pack (minimum)

  • Serial number (photo of label) + pole ID/location
  • Commissioning record (dimming mode + settings used)
  • Installation photo set (PV bracket/fasteners, cable routing, cable glands/sealing points, luminaire mount)
  • Maintenance log excerpts (last cleaning/inspection date and actions)
  • Failure description: pattern and conditions (after rain vs after cloudy weeks)
  • Photos/video of the symptom and any visible damage/corrosion/condensation

Use these pages to standardize evidence collection:

4) Define exclusions clearly (to avoid “gotcha” disputes)

Exclusions should be written plainly so everyone understands what is not covered. Typical exclusions include:

  • Improper installation or missing commissioning records
  • Unauthorized modifications or non-approved spare parts
  • Physical damage, vandalism, theft, or accidents
  • Extreme events beyond design assumptions (flooding/immersion, storms) unless explicitly covered
  • Normal wear items where applicable (define what “wear” means)

Engineering reality: many “ingress failures” are installation-driven (glands, gaskets, orientation). That’s why evidence photos are not optional.

Related references:

5) Warranty claim workflow (simple and auditable)

Require the supplier to publish a workflow like this:

  1. Submission: customer submits evidence pack (serial + photos + records)
  2. Triage: supplier confirms whether evidence is sufficient
  3. Diagnosis: supplier proposes tests/actions (remote first where possible)
  4. Decision: approve replacement (parts or full unit) or reject with a written reason
  5. Dispatch: ship replacements under SLA
  6. Closure: update serial-to-location mapping and maintenance records

Procurement tip: make sure the workflow specifies who does on-site labor (installer vs owner) and whether labor is covered or excluded.

6) PASS/FAIL procurement rules (make quotes comparable)

Mark a bid FAIL (Not Comparable) if it lacks:

  • Component-level warranty scope (battery/BMS, controller, PV, LED/driver, housing/seals)
  • SLA (response/diagnosis/replacement timeline + logistics responsibility)
  • Claim evidence list (serial mapping + commissioning record + photo checklist + logs)
  • Exclusions written clearly
  • Spare parts policy and replacement method

Use these procurement hubs as “source of truth”:

Copy/Paste RFQ Clauses (Warranty Terms)

Clause 1 — Component-level warranty scope (mandatory)

Supplier shall provide warranty terms by component at minimum for: battery/BMS, controller, LED module/driver, PV module, housing/lens/seals, and mounting hardware. A single headline warranty statement is not acceptable.

Clause 2 — Warranty SLA (mandatory)

Supplier shall define SLA including response time, diagnosis time after evidence receipt, and replacement/dispatch time. Logistics responsibilities (shipping/customs) and DOA policy shall be disclosed.

Clause 3 — Claim evidence package (mandatory)

Warranty claims require an evidence package including: serial-to-location mapping, commissioning record (mode + settings), standardized installation photos, maintenance log excerpts, and symptom photos/videos. Supplier shall provide templates for these records.

Clause 4 — Exclusions and responsibilities

Supplier shall list exclusions in plain language and define responsibilities for on-site labor, installation quality, and authorized maintenance access procedure.

Clause 5 — Bid comparability rule

Bids missing component-level scope, SLA, and claim evidence requirements shall be labeled “Not Comparable / High Risk” before price comparison.

Request Warranty Terms & Claim Templates

Get the editable pack used to standardize warranty terms and speed up resolution:

  • Component-level warranty scope template
  • SLA clause template (response/diagnosis/dispatch)
  • Claim evidence checklist (serial + photos + records)
  • Commissioning record template (mode + settings)
  • Maintenance log template (for warranty protection)

Want a quick engineering sanity check?

Share your road class, pole height, target lux/uniformity, and worst-month PSH assumptions.

Contact Inlux Solar →

Next Steps (Keep Your Project Tender-Ready)

Ensure your solar street light project meets all procurement and engineering standards.

Templates & Evidence

Shortlist a System Type

Back to All Guides Hub →

FAQ

What’s the difference between “warranty years” and “warranty coverage”?

Years alone mean nothing unless coverage scope is defined by component (battery/controller/PV/LED/housing), with clear exclusions, SLA, and a claim workflow.

What evidence is required for a strong warranty claim?

Serial number + location mapping, commissioning record (settings), standardized installation photos (including sealing points), maintenance logs, and clear symptom photos/videos.

What should a warranty SLA include?

Response time, diagnosis timeline after evidence is received, replacement/dispatch time, and logistics responsibilities (shipping/customs) plus a DOA policy.