Warranty and field service

1.Warranty policy design

The warranty is a contractual commitment plus a marketing message. Both sides need clear specification.

1.1Standard warranty terms (consumer hardware)

1.2EU Consumer Sales Directive 2019/771 (effective 2022)

• Minimum 2-year warranty mandatory for B2C sales.
• Reversed burden of proof for first yearDefects in first year are assumed to be present at delivery.
• Updates obligation for products with "digital element" (apps, firmware)Provide updates for "reasonable time".
• Right to remedyRepair, replacement, price reduction, or contract termination.
• Cannot waive in contractsConsumer cannot be made to accept less.

1.3US warranty considerations

• Magnuson-Moss ActFederal law requires warranty terms be available pre-purchase.
• Express vs. implied warrantyExpress is what you say; implied is what's reasonable. Limit both in writing.
• State-by-state limitationsSome states (CA, NY, MA) override certain warranty limitations.

1.4Warranty scope decisions

• What's coveredManufacturing defects, component failure, software bugs (sometimes).
• What's excludedUser damage (drop, water), unauthorised modifications, normal wear, cosmetic-only issues.
• Coverage tierMandatory (per law) vs. optional extended.
• Replacement vs. repairMost consumer products go straight to replacement; industrial repair.

1.5Exclusion language (typical)

``` This warranty does not cover:

• Physical damage from accidents, drops, or impacts
• Water damage beyond the IP rating
• Damage from unauthorised modifications
• Cosmetic wear from normal use
• Damage from incompatible accessories
• Issues caused by user error not addressed by clear documentation
• Loss of data or business interruption
• Consumable components (batteries beyond cycle warranty)

```

1.6Battery warranty

Lithium batteries have a cycle-life warranty separate from the product warranty:

• First year + ~80 % capacityIndustry standard; replace if below 80 %.
• Apple iPhone1 year, 80 % retained capacity for 1 year of use.
• EV batteries8 years / 70-80 % retained capacity.
• Consumer electronicsOften 1 year + ~70-80 % capacity warranty.

2.RMA process

The RMA (Return Merchandise Authorisation) is the customer-facing process for warranty returns. Designed well, it filters legitimate returns from misuse claims.

2.1RMA workflow

`` Customer reports issue ──→ Service triage (online or phone) │ ├──→ Software / setup issue → Self-help ├──→ User error / abuse → Not covered └──→ Hardware defect → RMA approved │ ├──→ Return label issued ├──→ Replacement shipped (sometimes) ├──→ Failed unit received ├──→ Defect analysis ├──→ Refurb or scrap └──→ Trend logged ``

2.2RMA triage gates (catches 60-80 % of "defective" claims that are actually user error)

• Symptom descriptionSpecific failure mode (not "doesn't work").
• Setup verificationHas user followed correct setup? (App connected, paired, charged, etc.)
• Software/firmware versionIs unit on latest version? Force update if not.
• Self-test resultsRun remote diagnostic if available; capture sensor readings.
• Pre-shipment photosCustomer photo of issue; reveals impact damage, missing parts.
• IdentificationSerial number, purchase date, channel.

2.3Replacement decisions

• Cross-ship (replacement before return)Higher customer satisfaction; risk of receiving non-defective return.
• Repair-only (no replacement)Lower cost; longer customer wait time.
• Refurbished replacementStandard for many brands; ~60-80 % of original product cost.
• New replacementPremium customer experience; full BoM cost.

2.4Returns processing

• Diagnostic at receivingStandard tests verify the reported failure.
• No-fault-found (NFF) rateTypically 20-40 % of returns. Document; refurb and resell.
• True failuresRefurb (if economical) or scrap.
• Repair cost vs. replacement costIf refurb cost > 60 % of new, scrap.

3.Field-failure analysis

Returns are data. Trends in returns reveal product issues earlier than aggregate yield numbers.

3.1Failure mode analysis

3.2Root-cause analysis (5 Whys)

For each failed unit: 1. Why did the device fail? (Symptom) 2. Why did that happen? (Mechanism) 3. Why did the mechanism occur? (Process or design issue) 4. Why did the process or design have that issue? (Process control gap) 5. Why was the control gap not caught? (System improvement opportunity)

Each "why" deepens understanding; root cause is usually 3-5 levels down.

3.3Pareto analysis

80 % of failures come from 20 % of failure modes. Identify the top 5 failure modes; fix those first.

``` Example field-return distribution (year 1, 5 000 units returned):

Battery degradation 1 800 (36%) Charging connector wear 850 (17%) Display defect 600 (12%) App connectivity 400 (8%) Mechanical (button) 350 (7%) Cosmetic (scratch) 280 (6%) Other 720 (14%) ───── Total 5 000 ```

Top 3 (battery, charging, display) = 65 % of returns. Investigate root causes; prioritise these for ECN.

3.4Trend tracking

Monitor monthly:

• Total returns vs. shipped (return rate %)
• Returns by failure mode
• Returns by manufacturing batch (date code, lot)
• Returns by region (climate, usage patterns)
• Returns vs. age of product

4.MTBF + reliability

MTBF (Mean Time Between Failures) is the expected operating hours between failures.

4.1MTBF estimation

``` MTBF (hours) = Total operating hours / Number of failures

Example: 1 000 units, average usage 8 hours/day, 12 months in field, 50 failures: Operating hours = 1 000 × 8 × 30 × 12 = 2 880 000 hours MTBF = 2 880 000 / 50 = 57 600 hours (~6.6 years operating, ~22 years calendar) ```

4.2MTBF interpretation

• Calendar time vs. operating timeA product used 1 hour per day has 24× higher MTBF (calendar) than one used 24 hours per day.
• Field data trumps predictionMIL-HDBK-217F and similar predictions are increasingly inaccurate; rely on field data.
• Warranty period sets expectationsMTBF should comfortably exceed warranty period × usage rate.
• MTBF varies by failure modeBattery has its own MTBF (lifetime cycles); electronics have another.

4.3Reliability metrics

4.4Target AFR by product class

5.Support tiers

Customer support is the operational interface for warranty + general help.

5.1Support tier structure

5.2Self-service infrastructure

• Knowledge basePer-product FAQs, troubleshooting guides, video tutorials.
• Diagnostic toolsIn-app diagnostics that capture device state for support.
• Forum / communityPeer-to-peer support reduces L1 ticket volume.
• Status pageService health for connected products.

5.3L1 cost economics

• Cost per ticket$10-30 for in-house, $5-15 for offshore.
• Tickets per customer per yearTypically 0.05-0.15 for consumer products.
• Self-service deflectionGood knowledge base deflects 40-70 % of L1 tickets.

5.4Response time targets

6.Cost reserves + accounting

Warranty cost is real. Account for it; reserve for it.

6.1Warranty cost components

• RMA processing labor$15-30 per RMA
• Return shipping$5-25 per parcel
• Diagnostic time$10-30 per unit
• Refurbishment material + labor$5-30 per unit
• Replacement unit cost (if applicable)Unit cost × replacement rate
• Outbound shipping$5-25 per parcel
• Customer service support$5-50 per case

Total per RMA: typically $40-150 per case for consumer hardware.

6.2Warranty reserve formula

``` Reserve per unit = (Expected return rate) × (Avg cost per RMA)

Example: 5 % return rate × $100/RMA = $5/unit reserve For a $50 COGS product, that's 10 % of COGS reserved against warranty. ```

6.3Setting the reserve

• Pre-launch estimate3-8 % return rate for consumer hardware (varies by category).
• Year 1 actualTrack and adjust.
• Year 2+ refinedUse field data + Pareto analysis to predict.
• Reserve as accounting lineRecognised as expense at sale, drawn down as RMAs occur.

6.4Per-channel warranty terms

6.5Extended warranty (revenue opportunity)

• Pricing5-15 % of product price for 1-year extension.
• Margin50-70 % on extended warranty (industry-typical).
• ChannelDirect customer offer; partner with third-party (SquareTrade, Asurion) for retail.
• Disclosure requiredMust clearly describe coverage; differentiate from manufacturer warranty.