Every display program eventually meets a returned unit. How the warranty is defined, how failures are diagnosed and who pays are far easier to agree before the first order than after the first complaint. This guide covers what a sensible display warranty and RMA process looks like, and what to put in writing.
What a display warranty normally covers
Most suppliers offer 12 months from shipment or delivery against manufacturing defects — dead pixels beyond the agreed criteria, lines, uneven backlight, touch failures, connector or FPC faults that were present at shipment. Typical exclusions are physical damage, ESD or electrical overstress, liquid ingress, misuse and modification. Agree on three things in writing: the warranty start date, whether it covers modules only or also cost of assembly rework, and the cut-off for "dead on arrival" (DOA) claims, commonly 7–30 days.
Agree acceptance criteria before production
Most disputes are really disagreements about what counts as a defect. Put the cosmetic and pixel criteria in the purchase specification — dead-pixel count by zone, mura, scratch and particle limits, and the viewing conditions used to judge them. Our QC checklist shows how to tie this to AQL sampling and a golden sample, and our datasheet reading guide helps you spot which specs are guaranteed.
A practical RMA process
- Report quickly with evidence — photos or video of the symptom, the module's label or serial number, batch/date code and quantity affected
- Rule out your own side first — power supply, interface timing, firmware initialization (see our bring-up checklist) and connector seating cause many "failures"
- Return the unit properly packed — ESD-safe, protected glass, original or equivalent packaging; transit damage is the most common reason a claim is disputed
- Failure analysis at the supplier — the supplier tests, reproduces and, where needed, opens the module; ask for a written report
- Resolution — replacement, credit or repair, as agreed; a systematic issue should trigger a corrective action report
Reading a failure analysis report
A useful report names the failure mode, the root cause and the corrective action. Typical root causes fall into a few groups: bonding or FPC cracks (see our FPC routing guide), ESD damage (our ESD/EMI guide), moisture or storage damage (our storage guide), backlight LED failure, or assembly stress. If the report says only "customer misuse", ask for evidence — photos of the damage mechanism, test data.
Field failure rates: what to expect and track
Early-life failures show up in the first weeks, random failures through the life of the product and wear-out near the end. Track returns per batch and per assembly lot, not just totals; a rise in one batch points to a process or material change, which links to our obsolescence guide on silent changes. Agree a threshold, for example a return rate above an agreed percentage in one batch, that triggers a joint investigation and sorting at the supplier's cost.
Contract points worth writing down
- Warranty period and start date; DOA window
- Defect definitions and inspection standard (AQL, golden sample)
- Return shipping cost responsibility for confirmed defects
- Response time for failure analysis (for example 5–10 working days)
- Handling of batch-wide defects: stop-ship, sorting and rework costs
- Spare stock (a small percentage of the order) to avoid line stoppages while a claim is processed
Reducing the odds of claims in the first place
Sample approval, in-line inspection, careful handling and sensible storage prevent most returns. See our sample-to-production sourcing timeline and the China factory guide for how this fits into the overall process.
Planning a display order and want warranty and RMA terms defined up front? Request a quote and tell us your volumes and quality expectations — we'll outline the terms we can support.