How to Keep IMEI and Inventory Records for a Phone Wholesale Business

A phone wholesale business is judged on its books as much as its buying. This guide sets out a record structure that holds up in a supplier dispute, a tax review and a fast-moving stock list — from purchase order down to a single unit's cost basis.

The record stack: three levels that must reconcile

Every purchase should exist at three levels at the same time: the purchase order, the lot, and the individual unit. Most disputes and most accounting errors come from keeping only two of the three, or from keeping them in three unrelated files.

Link the three with one identifier so a unit can always be traced back to the shipment and the invoice. The supplier-side document that feeds this structure — the per-IMEI file — is covered in our guide to per-IMEI reports rather than batch summaries, and the checks that happen at receiving are in the bulk IMEI verification guide. This page is about what your own books must contain afterwards.

Capture at intake: one pass, no re-typing

Every manual re-entry step is a place where an IMEI silently loses a digit. Design receiving so each identifier is read once and validated at the moment it is scanned.

• Read the IMEI from the device or its box; do not transcribe digits from a packing list.
• Validate length and check digit structure before the unit is accepted into sellable stock.
• Match the scanned value against the supplier's file for that same lot.
• Quarantine mismatches immediately — do not "fix" your file to match the phone.
• Stamp each record with the receiving date and operator.

A lot with unverifiable identifiers is a lot whose records no longer prove anything — in front of a buyer or a tax inspector.

Turn one invoice into a per-unit cost basis

The invoice price is not a cost basis. Landed cost per unit is the purchase price plus freight, insurance, duty, clearing and local handling, spread across the units that arrived in working order. Our guide to calculating the landed cost of a shipment covers the mechanics.

• Allocate freight and duty by unit, with a separate rate for model tiers when the mix is uneven.
• Charge dead units against the lot, not against the whole company's overhead.
• Store cost at lot level and keep the FIFO order visible, so aged stock cannot hide.
• Recalculate the basis whenever a credit note, rebate or replacement shipment lands.

A system that stores only the purchase price overstates margin on every imported lot, quietly, until a tight cash-flow month exposes it.

The four reports that should drive your buying

Inventory records earn their keep when they change a decision. Four reports cover most of the value:

• Ageing — units and value by weeks held, split by model and grade.
• Sell-through — units sold per week per model, storage and grade.
• Realised margin per unit — sale price minus the allocated lot cost, not an estimate.
• DOA and return rate — by supplier and by lot, which is the number that should change who you buy from.

A supplier at a slightly higher unit price with a materially lower return rate is usually the cheaper supplier. Unit-level records are what make that visible.

Reconcile on a schedule, and write down the variance rule

Run a full count monthly on high-value stock and spot counts weekly by location. Count blind — hide the expected quantity — or the count will confirm your file instead of testing it. Before any unit is written off, work the variance rule in order.

• Check the obvious first: sold but not invoiced, returned but not booked in, moved to repair or to a demo shelf.
• Re-check device status against blacklist, lost-or-stolen and activation-lock checks before disposal.
• Allow write-offs only with a named approver and a reason code attached to the entry.
• Log every adjustment, including corrections; unexplained shrinkage is a process failure, not a paperwork one.

Tie the variance loop to your supplier remedy process so claims are raised inside the dispute window — see our DOA and returns guide.

Record hygiene: access, backup and retention

An IMEI file is both an asset and a liability. It proves provenance to a buyer, and it becomes a privacy problem the moment it is combined carelessly with customer data.

• Keep one authoritative system. Parallel spreadsheets become warehouses of stale copies.
• Back up daily and test a restore, not just the backup job.
• Restrict cost, margin and supplier fields to staff who need them for their role.
• Share only the fields a partner needs — a registration agent wants IMEIs, not your cost sheet.
• Set a retention period, store exported files encrypted, and check local data-protection rules before holding customer details next to device records.

A rollout you can run this week

• Freeze one naming rule for lots and units, and apply it to new receipts only.
• Make IMEI a required field with validation — no unvalidated unit reaches sellable stock.
• Add a cost-basis field populated at intake and updated at each adjustment.
• Publish the ageing and DOA reports on a fixed weekly review slot.
• Run one blind count and log every variance with a reason code.
• Review one supplier's lot history and change one line of the next purchase order as a result.

Frequently asked questions