CDTech LCD touch screen

display / touch / bonding solutions

Warranty Terms for LCD Modules: What a Twelve-Month and a Twenty-Four-Month Clause Really Cover

Author: CDTech Publish Time:  Origin:

Warranty terms for LCD modules are usually settled in the last hour of a commercial discussion, once price and schedule are agreed. What gets signed is often a single line offering twelve months against defects in materials and workmanship. Two suppliers can offer an identical twenty-four-month term while carrying very different amounts of the buyer's risk, because the duration sets the window and the surrounding paragraphs decide what is allowed into it.

This guide compares the wording on the four points that decide most claims: cosmetic against functional, the dead-on-arrival window, return freight and labour. It then covers the reserve a buyer should hold per hundred units, coverage after integration, bright dot and mura limits, and the RMA mechanics that decide whether a clause is usable at all.

Twelve months and twenty-four months cover different failures

Duration is the least informative part of a warranty: the same twelve months can cover a failed backlight and exclude a discoloured polariser. The term is a window, and the failure mechanisms the supplier expects inside it decide what the window is worth. A twelve-month clause is written around early-life failures that trace back to the supplier's process, from assembly defects to a driver IC that fails early.

A twenty-four-month clause reaches past that phase into wear. Backlight output declines, polariser and adhesive layers yellow, elastomer connectors lose contact pressure. A supplier offering twenty-four months while excluding wear has extended the label, not the cover.

Failure mechanismTwelve-month clauseTwenty-four-month clause
Early-life assembly and component defectsCoveredCovered
Latent connector and solder joint failuresCoveredCovered, sometimes prorated
Backlight LED output declineRarely coveredOften excluded as wear
Polariser discolouration or delaminationDisputed case by caseUsually excluded as wear
Handling damage after deliveryExcludedExcluded

Ask which mechanisms the supplier expects in months thirteen to twenty-four.

Cosmetic or functional: the line that decides claims

Most disputes are not about whether a unit failed but about which category it failed in. A functional failure is judged against the datasheet: no display, a missed timing specification, current outside range. A cosmetic failure is judged against an acceptance standard that may not be attached to the warranty, so the claim often fails on paperwork rather than evidence.

  • Definition of defect. Does the clause name cosmetic criteria, or only electrical function?
  • Acceptance standard. Attached as an annex, revision identified, and referenced by the warranty?
  • Deciding party. Supplier failure analysis, third-party laboratory, or joint inspection at your dock.
  • Claim basis. Per unit, per lot or per shipment, since a per-lot limit swallows isolated failures.
  • Exclusions. Scratches, pressure marks and fingerprints, which are the defects that actually arrive.

Cosmetic coverage is therefore agreed before the order, inside the acceptance standard.

2.1 inch 480x480 round LCD display with RGB interface
A 2.1 inch 480x480 round LCD display with RGB interface. On a small round module the visible area is limited enough that a zone map decides bright dot claims more often than a percentage limit does.

A DOA window is a clock, not a warranty

The dead-on-arrival window is a separate mechanism, and the one buyers most often lose by default. A unit that fails at first power-up is a different commercial event from one that fails in month nine: the cause is almost certainly handling, transit or a build defect, and nobody has to argue about wear.

The clock starts at delivery, not at integration. Notification must arrive inside the window, in writing, with serial numbers, and with the original packaging retained. Modules that have been reworked, coated, glued in or powered outside the datasheet may fall out of the path. Missing the window does not remove coverage, but it moves the claim into the warranty process, where freight and causation become arguable.

The operational answer is procedural: log the delivery date per shipment, power-test a defined sample inside the window, and record the result against serials, which is the record-keeping the CDTech reliability and inspection guide sets out.

Who pays return freight and above what value

Freight usually follows the value of the claim.

Below a threshold written into the clause, the supplier credits the part and leaves the unit with you, because return freight costs more than the hardware.

Above that threshold the question splits into four: who pays freight on the failed unit, who pays freight on the replacement, who carries duty, and what happens if the failure is later attributed to handling. Most templates answer only the second. A return is a new export and import rather than a continuation of the original shipment, so the Incoterms 2020 rules that governed delivery do not automatically govern the return leg. The module also re-enters under its own HS heading, so duty can be charged twice unless the paperwork identifies returned goods; the EU Access2Markets service shows what a returning consignment faces.

Labour and rework, the cost most warranty clauses omit

The replacement module is usually the cheapest element of a field failure. The expensive elements are technician time, the re-test after the swap, the adhesive and gasket that cannot be reused, and the labour already spent diagnosing a unit that turned out to be a display.

Common arrangements are a labour allowance per accepted claim, a fixed credit per failure that folds labour into one number, and a no-labour clause that leaves the exposure with the buyer. Only the third requires the reserve to price labour in.

Cost elementCommonly coveredFrequent gap
Replacement moduleYes, within the termProrated or capped after year one
Freight on the replacementOftenExpress uplift not covered
Freight on the failed unitRarelyNo return accepted below a threshold
Technician labour and re-testSometimes, as an allowanceField service and travel excluded
Line downtime and scrapped partsAlmost neverNot priced in the contract

Sizing a warranty reserve per hundred units

A reserve is not a prediction of supplier behaviour; it is the amount your accounts hold so that a bad quarter does not become a programme problem. Build it from four inputs: claims per hundred units, module cost, labour per swap, and freight per return, plus a severity factor for escalated claims.

Reserve per 100 units = (claims per 100 units x (module cost + labour per swap + freight per return)) + (escalated claims per 100 units x severity cost)

Work it with your own figures. If a programme sees two claims per hundred units, and the module, technician time and freight each carry a known number, the first bracket is two multiplied by their sum. If one claim in ten escalates to a field visit or a customer credit, the second bracket captures it. Run the first year and the second year separately, because the later claim rate is driven by wear.

4.3 inch RGB TFT LCD module with 800x480 resolution
A 4.3 inch 800x480 RGB TFT module. Where a module is bonded into a bezel, the labour and re-test in a claim usually exceed the part value.

Does the warranty survive integration into your product

Usually not automatically, but cause decides the claim.

A blanket clause voids cover once the module is built in; a well-drafted one keeps latent defects in scope and uses failure analysis to separate them from process damage.

The module warranty is written for the module as delivered. Integration adds handling, electrostatic discharge, thermal cycling from your enclosure, mechanical stress from a bezel or adhesive, and cleaning chemistry the supplier never approved. A supplier cannot see any of that, so templates respond by voiding cover on integration, which turns every field failure into an argument about causation.

A workable version keeps coverage for defects present at delivery and latent at the time, requires failure analysis rather than refusal, and sets the evidence you must preserve: serials, build records, failure conditions. Where the module goes into a regulated market, the after-sales expectations for the finished product do not shrink to match the module term; the EU General Product Safety Regulation (EU) 2023/988 keeps duties on the operator, and twelve months does not shorten them.

Bright dot and mura limits written as acceptance criteria

Bright dot defects and mura generate argument because both are continuous rather than binary. A bright dot is a sub-pixel stuck on; a mura is low-contrast cloudiness that shows on a grey field and disappears on black. Neither is a functional failure; both are decided by a written limit, so the acceptance criteria decides these claims.

Write the limit so incoming inspection and warranty share one boundary: a zone map, because a dot near the centre matters more than one at the edge; a counting rule for adjacent dots and minimum separation; measurement conditions, including viewing distance, luminance and the grey level at which mura is judged; and who inspects, with what instrument. Pixel defect classification schemes are published through standards bodies such as ISO, and your customer's specification will usually cite one.

Check the direction of the gap. If your incoming standard is looser than the limit your customer applies, every unit that passes your dock and fails theirs is a cost you carry. CDTech publishes its own quality and certification documentation in that form.

RMA mechanics: response time, replacement or credit, cycle count

A warranty is only as good as the process behind it, and the process lives in paragraphs that rarely get negotiated. How long the supplier takes to acknowledge a claim, whether a return authorisation number is needed before anything ships, who performs failure analysis, and whether the remedy is replacement or credit: each decides whether the clause is usable.

The most useful single number is the cycle count: how many failed units of one part number are accepted before the remedy changes from unit-by-unit replacement to a lot-level corrective action. Without it, a systematic defect is processed as individual claims, each with its own freight and paperwork, and the pattern is never acknowledged. Ask for a written escalation: a defined count within a defined period triggers analysis on the lot and a corrective action report, in the form automotive programmes expect under AIAG.

No-fault-found outcomes also need a rule, because a supplier that finds nothing wrong will return the unit and close the claim. The acknowledgement clock should then run from a complete claim, with completeness defined in writing.

Next step. If your team is comparing warranty wording across display suppliers, CDTech can share how its terms treat cosmetic limits, DOA notification, return freight and failure analysis, with the documentation behind them. No obligation to shortlist on the strength of it.

Ask about warranty and RMA terms · [email protected]

FAQ

Is a DOA window separate from warranty?

Yes, and it runs on a different clock. The DOA window is a short notification period counted from delivery that gives you a no-argument replacement path for units failing at first power-up, while the warranty is the longer term for failures appearing later. Missing the window does not normally end coverage, but it moves the claim into the warranty process, where the supplier can ask about handling, storage and integration before accepting it. Treat the two as separate procedures with separate deadlines and separate evidence.

Are cosmetic defects warrantable?

Only to the extent the acceptance standard defines them as defects. Most warranty text covers defects in materials and workmanship, then excludes cosmetic conditions inside the agreed limits, so a scratch within the standard is not a claim and a scratch outside it is. That makes the acceptance standard the operative document for cosmetic claims, including bright dot and mura limits. Confirm the standard and its revision are attached to the contract, and that incoming inspection uses the same revision the warranty references.

Who pays return freight on a claim?

It depends on the clause and on the value of the claim. Many suppliers accept the return leg on accepted claims above a written threshold, and credit the part without a return below it, because processing a low-value return costs more than the hardware. Ask separately about freight on the failed unit, freight on the replacement, express uplift, and duty on a re-imported module. Duty is the item most often missed, since a returned module is a fresh import under its own HS heading.

Does the warranty survive integration into a product?

Not automatically, and the clause wording decides it. A blanket exclusion for integrated modules shifts the entire risk to the buyer, while a clause that keeps latent defects in scope and requires failure analysis to attribute cause leaves a usable claim path. Check what evidence the supplier expects you to preserve, and whether it will analyse a returned unit rather than sending it back unrepaired. Where the finished product carries a longer remedy for end users, the difference is yours to fund.

×

Contact Us

(Accept word, pdf, dxf, dwg, jpg, ai, psd file, Max 10M)
captcha

By continuing to use the site you agree to our privacy policy Terms and Conditions.

I agree