Documentation

Why B2B Buyers Need Per-IMEI Reports, Not Batch Summaries

A batch summary tells you what a shipment looked like on average. A per-IMEI report tells you what you actually own. In used iPhone wholesale that difference decides who absorbs the loss when a lot arrives short.

Batch summary vs per-IMEI reporting

A batch summary is one row of numbers describing a shipment: average battery health, pass rate, grade mix, defect count. A per-IMEI report attaches those same inspection results to each individual device identifier, so every unit carries its own record.

The distinction sounds administrative until a dispute begins. An average can only be argued with; a unit-level record can be audited, matched to a physical phone and priced. Buyers who work on averages are effectively self-insuring against their supplier's sorting.

What an average hides

What a per-IMEI report must contain

You do not need every measurement; you need the fields that decide money and traceability.

FieldWhy it decides moneyBatch summary gives you
Serial + IMEILinks the record to a physical unit and to a claimNothing
Model, capacity, colour, market variantDetermines resale channel and price tierA mix percentage
Carrier lock statusLocked stock is unsellable in many marketsAn estimate
Activation lock / iCloud stateNon-negotiable precondition for tradeable stockA claim, not a record
Battery health + cycle countDrives grading and customer return rateAn average
Cosmetic grade on a defined scaleSets the price band per unitA grade mix
Per-subsystem functional resultSeparates DOA from slow failureA pass rate
Parts replacement disclosureChanges what you must tell your own buyerUsually absent
Technician and test dateProves when the condition was recordedOften missing

If a supplier already scans and grades units, this data exists. The request is a file format, not new labour.

Where unit-level data pays for itself

None of these benefits require perfect data. They require data attached to a specific device.

How a per-IMEI file turns a dispute into a claim

The first question in any quality dispute is "which units". If answering that requires re-testing the lot, the claim window is usually already gone.

  1. Inspect on arrival inside the agreed window and log results against the supplier's IMEI list, not against carton order. See our bulk IMEI verification workflow.
  2. Record the failing result with the identifier, a photo of the device and the test screen in one frame.
  3. Isolate faulty units immediately so they cannot be re-sold or mixed back into stock.
  4. Submit the IMEI list, evidence and a claimed remedy inside the notification deadline in the contract.
  5. Reconcile the credit line by line when it is issued; partial credits are common and rarely accidental.

Suppliers respond to specific, evidenced lists because they can be verified internally. They respond slowly to general dissatisfaction.

Why some suppliers resist, and what to ask for

Per-unit reporting costs labour: scanning, photographing and transcribing hundreds of records. Suppliers optimise for throughput, and reporting is the first thing dropped when a container must ship.

Batch summaries are still useful for forecasting. They are simply the wrong instrument for ownership and claims.

A rollout that does not slow intake

Adopt the minimum viable version first. Agree five mandatory fields with your main suppliers, require the file with every shipment, and spot-check roughly one unit in ten against the physical device. Store records in a searchable index keyed by IMEI, and keep claim history per supplier in the same system. Within two or three shipments you will have a supplier scorecard built on evidence, which is a far better negotiating position than a memory of how the last lot felt.

Frequently asked questions

Is a per-IMEI report the same as a warranty?
No. It is a dated record of condition, not a promise about the future. Read how the two documents interact in our guide to warranty and after-sales practice.
What if the supplier refuses to provide unit-level data?
Start with a subset: request it for the highest-value models in the lot. If they still refuse, treat it as information about how claims will be handled.
Can I create the report myself on arrival?
Yes, and you should for your own records. The value is highest at origin, where it fixes condition before transit and before payment is settled.
How does this relate to a QC report?
A per-IMEI file is the structure; the QC report is the content. See how to read a used iPhone QC report for the fields worth checking.

Need documentation you can audit?

AppleUsed supplies inspected, graded pre-owned iPhones to wholesale partners in 40+ countries, with serialised QC data available per unit and a defined claims process.

Request Our Price List

AppleUsed · Pre-owned iPhone wholesale supplier · All guides · Contact