IMEI Checker: Stop Buying Stolen Devices

Using an imei checker before accepting or purchasing any device is one of the most important habits a repair shop can build — and one of the most overlooked. Whether you run a solo phone repair bench or a multi-technician shop, the moment you accept a stolen handset you become part of the problem in the eyes of the law. This guide walks you through what an IMEI checker is, how to use one correctly, the mistakes shops commonly make, and how the right software makes the whole process effortless.

What Is an IMEI Checker and Why Does It Matter?

Every mobile phone, tablet, and many laptops carry a unique 15-digit IMEI (International Mobile Equipment Identity) number. When a device is reported lost or stolen, networks and police databases can flag that IMEI as blacklisted.

An IMEI checker queries one or more of these databases and returns a status report — clean, blacklisted, or blocked. For your shop, that report is the difference between a legitimate repair job and unknowingly receiving stolen goods, which in the UK can result in prosecution under the Proceeds of Crime Act 2002.

Beyond the legal risk, there is a commercial one: if you buy secondhand devices for resale and one turns out to be stolen, you lose both the device and the money you paid for it.

Step-by-Step: How to Run an IMEI Check in Your Shop

Follow this process every single time — not just when something feels suspicious.

1. Locate the IMEI. Ask the customer to dial *#06# on the device. The number appears on screen instantly. Alternatively, check under the battery, on the SIM tray, or in the device settings under About Phone.
2. Choose a reputable checker. Free checkers exist but often query limited databases. Paid services such as Checkmend (UK) or GSMA Device Check pull from broader blacklists including police records. Budget around £0.25–£1 per check — cheap insurance.
3. Run the check before touching the device. Do not begin a repair or hand over cash until you have a result in hand.
4. Record the result immediately. Log the IMEI number, the check service used, the result, the date, and the staff member who ran it. This timestamped record is your evidence that you performed due diligence.
5. Act on the result clearly. If the device comes back clean, proceed. If it is blacklisted, decline the job politely and, depending on your local obligations, consider reporting it. Do not let social pressure from the customer change your decision.
6. Give the customer a receipt that includes the IMEI. This creates accountability on both sides.

Using repair ticketing software that captures the IMEI at intake means steps 4 and 6 happen automatically — no separate spreadsheet required.

Common Mistakes Repair Shops Make with IMEI Checks

Even shops that know they should be checking devices often undermine their own process with these errors.

• Only checking devices that look suspicious. Stolen devices are frequently in pristine condition. Inconsistency also undermines your legal defence — “we check when we feel like it” is not due diligence.
• Using a single free checker. Free tools often rely on a single database with poor coverage. A device can be flagged on the GSMA registry but return clean on a minimal free tool.
• Not logging the result. A verbal check with no record is worthless if you are ever questioned by police. You need a paper trail with a timestamp.
• Checking too late. Some shops run the check after the repair is complete. By then you have already provided a service on what may be a stolen device.
• Not training all staff. If the process lives in one person’s head, it disappears on their day off. Write a one-page SOP and keep it visible at the counter.
• Forgetting trade-ins and buybacks. Shops that buy secondhand devices sometimes only check customer repairs, not purchases. Trade-ins carry the same or higher risk.

How Admin Repairs Helps You Build a Foolproof IMEI Process

Manual IMEI logging in a notebook or a separate spreadsheet creates gaps. Admin Repairs solves this by embedding IMEI and device tracking directly into the repair workflow.

Here is what that looks like in practice:

• IMEI captured at ticket creation. When your technician opens a new repair job, the IMEI field is required before the ticket can be saved. No device enters your system without a logged IMEI.
• Searchable history. If a device comes back six months later, you can search by IMEI and pull up the full repair and check history instantly. That is useful for warranty disputes and invaluable during a police inquiry.
• Linked customer profiles. Every device is tied to a customer record, so you know exactly who brought in which handset and when.
• Audit-ready records. Admin Repairs timestamps every action, giving you the kind of documented trail that demonstrates professional due diligence.

Pair the software with your chosen external IMEI checker service. Run the check, paste the result into the ticket notes, and you have a complete, searchable, timestamped record — all in one place rather than scattered across tools.

Building a Culture of Compliance in Your Shop

Process only works when people follow it every day. Here are a few practical steps to embed IMEI checking into your shop culture:

• Post a laminated checklist at every intake point.
• Include IMEI checking in onboarding for any new staff member.
• Review your repair reports monthly to confirm that every ticket has an IMEI logged — gaps are a warning sign.
• Talk openly with customers: “We check every device we take in — it protects you as much as us.” Most legitimate customers appreciate the transparency.

The shops that handle stolen devices are rarely the ones that set out to do so. They are the ones that skipped a step once and then kept skipping it. A consistent process, backed by software that enforces it, removes that risk almost entirely.

Ready to make IMEI checking a built-in part of every repair job rather than an afterthought? Start your free trial of Admin Repairs and see how device tracking, repair ticketing, and customer records work together in one straightforward platform.