How to Read a Used iPhone QC Report: A Guide for Bulk Buyers

A QC report is the only document that travels with your money. This guide shows what a usable report contains, which fields decide your margin, and how to verify the claims instead of trusting them.

What a QC report is — and what it is not

A QC report records the tests a supplier ran on your units, at a point in time, before shipping. It is not a warranty, and it is not proof of origin. Its real value is traceability: it lets you tie a specific unit to a specific test result, a technician and a date.

If a document cannot do that, it is marketing material rather than quality control. That distinction should drive what you accept before funds move.

Lot-level versus per-IMEI reporting

Two formats dominate wholesale. Lot-level reports summarise a batch with pass rates; per-IMEI reports list every unit with its own results. Lot-level reporting is acceptable for low-value consumables. For iPhones, per-IMEI is what protects you.

The fields that actually decide your margin

Reports vary in layout but not in what matters. These are the entries to check line by line, in the order a dispute would be argued.

Red flags in the document itself

Weak reporting is usually visible before you test anything. If you see several of these, the process behind the report is not dependable:

• A blanket "100% inspected" line with no unit list attached.
• Grade letters with no written definitions supplied to you.
• No technician, facility or date reference anywhere on the file.
• A scanned image where the identifier list cannot be searched or cross-checked.
• One battery health range quoted for an entire batch, such as "85–95%".
• Photos that cannot be matched back to specific units.
• Reports issued after invoicing instead of before payment.

How to verify a report before you rely on it

Verification is cheap compared with a bad lot. A short routine covers most of the exposure:

• Re-measure battery health and cycle count on 5–10% of the lot and compare with the file.
• Run the identifier list against blacklist and activation-lock checks.
• Pick three units, find their photos, and compare them with the stated grade.
• Confirm the identifiers match the devices, not just the cartons they shipped in.
• Keep the exact version you approved; request a revised report if anything changes afterwards.

This mirrors the discipline we describe in the documented inspection process and the arrival verification checklist: a report is a claim, and claims get sampled.

When the report and the arrival do not match

Mismatches are normal in mixed-grade trade; how they are handled is what separates suppliers. Keep the mechanics written down before you order:

• Raise discrepancies against the batch identifier inside the agreed window.
• Document per unit: photos, the reading you took, and the report line it contradicts.
• Separate functional failures from cosmetic disagreement — they resolve differently.
• Expect unit-level credit where the report was wrong, not a general apology.
• Track patterns: repeated cosmetic drift is a grading-culture problem, not bad luck.

The same evidence discipline applies to returns; see DOA and returns handling. If a report describes a unit as fully tested while a key subsystem was never listed, that gap is the argument.

Using reports to compare suppliers

Two suppliers can quote the same unit price and be thousands of dollars apart in true cost. The one that supplies per-IMEI data, published grade definitions and a fixed dispute window is cheaper in practice, because its failures are visible before you pay.

Ask the same three questions of every new source: show me one complete report, show me your written grade definitions, and tell me what happens when a unit fails my own check. Compare the answers, not the adjectives. The difference between inspected stock and stock sold as seen is documented in inspected versus used iPhones.

Frequently asked questions