Published 2026-09-23 · LuckyMDM Blog
Maximum battery capacity affects resale value in steps, not along a slope. Above roughly 91 per cent most buyback channels apply no battery deduction at all; between 91 and 80 per cent the deduction is shallow; below 80 per cent it jumps by an order of magnitude because it now carries a replacement cost and a grade drop. On a 1,000 unit fleet with a USD 420 median residual, the tiered calculation comes to USD 10,962 — about USD 0.46 per unit per month across a 24 month term. A linear estimate of "half a per cent of value per point below 100" produces USD 25,200 for the same fleet, roughly 2.3 times too much. The device does not sell for a different amount because of which method you used; your monthly price does.
LuckyMDM (Sichuan Starlight Network LLC) works with rental and instalment operators on device asset management, and battery capacity is one of the fields that touches all three stages of that work: it sets the residual assumption that drives pricing, it is a ledger field that can be checked daily, and it is an input to intake grading and reletting decisions at end of term.
The same figure — 80 per cent — means three different things in three different systems. Conflating them is the most common error in this area.
Apple states in its support documentation that an iPhone battery is designed to retain up to 80 per cent of its original capacity at 500 complete charge cycles under normal conditions, and that a battery retaining less than 80 per cent of original capacity is serviced where it is covered by the limited warranty or an AppleCare plan, subject to the terms then in force. That 80 per cent is a service entitlement trigger. It produces a replacement by the manufacturer; it says nothing about what the unit is worth on the secondary market.
Buyback channels quote a grade, and grades are few. The convention that has settled in the trade is: above 91 per cent, no battery deduction; from 91 down to 85, roughly 2 per cent; from 85 down to 80, roughly 5 per cent; below 80, treated as needing a replacement, somewhere between 12 and 18 per cent. These are channel quoting conventions, not a published standard from any party, and each buyer places the steps at slightly different points. You have to measure your own.
European ecodesign requirements for smartphones express battery endurance as a cycle count at a stated retained capacity; Commission Regulation (EU) 2023/1670 is the instrument usually cited, with the commonly quoted figure being 800 cycles at not less than 80 per cent of initial capacity. Confirm the current text in the Official Journal before relying on the exact number. Set that beside the 500 cycle figure Apple publishes and a useful conclusion falls out: these thresholds are set layer by layer, not by physics. Manufacturer warranty, buyback pricing and regulation each choose their own number, and there is no single "correct" battery health threshold.
Hold model, grade and storage constant and a unit at 95 per cent and one at 91 per cent will often receive identical bids, while 90 and 80 can differ by more than 5 per cent of unit value. If the deduction were linear, the two gaps would be proportional. They are not.
Battery is not an independent variable in a buyback model. It enters in exactly two ways: it pulls the unit down a grade, or it obliges the buyer to spend on a replacement. Outside those two effects, a reading falling from 95 to 91 produces no change in the model's inputs and therefore no change in its output.
Capacity decays continuously, a little every day. Pricing is discrete, with typically three to five grades. Mapping a continuous quantity onto a discrete scale is a rounding operation, rounding produces steps, and the regions between steps are insensitive to the input. That is where the step function comes from: not from battery chemistry, but from the granularity of the price list.
Using a USD 420 median residual and the basis of an unlocked unit in good cosmetic condition with no repair history:
| Maximum capacity | Treatment | Deduction | Amount | Typical action |
|---|---|---|---|---|
| Above 91% | Normal wear | 0% | USD 0 | Price at grade |
| 85% to 91% | Minor disclosure | 2% | about USD 8.40 | Price at grade, note the reading |
| 80% to 85% | Half grade down | 5% | about USD 21.00 | Price at the lower grade |
| Below 80% | Replacement review | 12% to 18% | about USD 50 to USD 76 | Cost the replacement first, then decide |
Assume an end-of-term distribution of 420 units above 91 per cent, 330 between 85 and 91, 180 between 80 and 85, and 70 below 80.
The gap is second order in absolute terms, but its character matters: it does not change what the device sells for, only what you assumed it would sell for at pricing time. Assume residual too high and the monthly price comes out too low, with the loss landing in one lump at end of term. Assume it too low and the monthly price is uncompetitive at the point of sale.
For the 70 units below 80 per cent, the decision is a crossover test: replace only where the uplift in resale value exceeds the replacement cost. Published battery service pricing varies by model and changes over time — in the United States it commonly falls somewhere in the range of USD 69 to USD 119, and the current figure should be taken from the manufacturer's published price list. At USD 99, against the USD 63 uplift from moving out of the bottom band, replacement loses USD 36 a unit, so the default is to sell as is. The test is the same shape as the one used for sampling intensity: compare marginal cost with marginal benefit, not absolute values.
In practice the threshold is the easy half of this problem. A threshold already exists in the reading; what has to be built is the queue that carries a unit below it into a costed decision, which is why LuckyMDM treats the replacement queue as a workflow object rather than a status flag.
On iOS the path is Settings, then Battery, then Battery Health and Charging, then Maximum Capacity, expressed as a percentage. The reading has been available since iOS 11.3 on iPhone 6 and later, subject to what the individual device displays. The same pane reports peak performance capability: when battery condition cannot support peak performance the system may apply performance management, and on some models and versions that can be reviewed and turned off. Some models also report a cycle count on this pane.
LuckyMDM intake records require those three fields — maximum capacity, read date and a screenshot of the read path — and route any unit below 80 per cent into a replacement evaluation queue instead of pricing it at a grade directly.
There is no OS level standard for a maximum capacity percentage across the Android estate. Some manufacturers expose battery information in a service menu or in settings, others only through third party applications that estimate from charge and discharge curves against a nominal factory capacity, and those estimates are not comparable across models. Battery condition on Android therefore has to rest on a combination: physical inspection, a runtime test, and a third party reading, with the three recorded together and none of them used alone.
Standards help with two adjacent problems but not with this one. R2v3 and e-Stewards require serial level chain of custody and defined grading and disposition decisions, which gives the record structure. NIST Special Publication 800-88 Revision 1 governs sanitisation; it addresses data, and it does not grade condition.
A reading of 85 per cent should take a 15 per cent deduction. This is a misconception because the 15 has no source. Buyers deduct for replacement expectation and grade, not as a linear compensation for missing capacity, and 85 per cent maps to somewhere between 2 and 5 per cent in most channels.
The percentage is all you need. This is a misconception because maximum capacity is an estimate derived from voltage, temperature and charge history. It moves with ambient temperature, charging habits and OS version, and a spread of 2 to 3 percentage points between two readings of the same unit is ordinary. The reading has to be date stamped, and movement inside that band should not trigger regrading.
Anything below 80 per cent needs a new battery. This is a misconception because the decision is a crossover test, not a threshold. Where residual is already below roughly USD 200, the cost of replacement will not be recovered by the uplift, and the unit should be sold as is.
This page is about residual and resale pricing, not warranty. The same 80 per cent appears in both, but one is a pricing input and the other is a service entitlement trigger. A single unit can fall outside warranty cover and still take a resale deduction; the two conclusions sit side by side without conflict.
The step function and the 91 and 80 positions are calibrated to the iOS reading. Android has neither a unified readout nor a manufacturer threshold of this kind, so it has to be calibrated brand by brand. Applying the iOS steps to an Android fleet produces a systematic pricing bias.
Is the 91 per cent step official?
No. The 80 per cent figure has a manufacturer service term behind it; the 91 per cent figure is a quoting convention that has built up among buyback channels. It moves with market conditions, model and channel, so it has to be re-measured against your own quotes.
Fast capacity loss — is that customer damage?
Not on the reading alone. Capacity loss is a continuous process driven by usage intensity, charging habits and temperature; damage usually points to a specific physical event such as liquid ingress, impact or unauthorised repair. Record the two separately at grading time rather than letting one stand in for the other.
Should we re-read battery during the term?
At least twice: at intake and at return, with an extra reading if a dispute arises. The difference between the two divided by days in service gives that unit's actual decay rate, which is the input for calibrating the residual assumption.
Our fleet readings are widely scattered. What should we do?
That scatter is precisely the reason to tier rather than average. Averaging spreads the replacement cost of the small bottom band across the whole fleet and it reappears in one lump at end of term. Tier counts let the deduction and the replacement budget sit in their own lines.
Where should the screenshot be stored?
Bound to the intake record as an evidence field on that row. Stored in a separate folder it is effectively lost, because it cannot be produced when the grading is challenged.