Device unlocking workflows can add value, but only when teams treat unlocking as a controlled decision in the process. Many losses happen when staff unlock too early, unlock the wrong devices, or fail to separate network unlocking from other issues such as account locks or device risk flags.

This guide focuses on the operational side of unlocking for traders and refurb teams: when unlocking makes sense, when it should wait, and how to keep an audit trail that reduces delays and disputes.

Why unlocking needs a clear workflow decision

Unlocking is often profitable, but only when the device is suitable and the sequence is right. In practice, the most common mistakes are procedural:

  • Unlocking before checks and testing: money is spent on stock that later fails another stage
  • Confusing lock types: staff treat network unlocking as a fix for account lock issues
  • No written rule: teams make different decisions on similar devices
  • No audit trail: support disputes take longer to resolve later

Ofcom’s rules banning mobile companies from selling locked handsets changed part of the consumer market. However, unlocking still matters for legacy stock, certain trade channels and specific device histories. The safest approach is to treat it as a controlled step rather than a default action.

Unlocking rule: Every device should end up as unlock now, unlock later, or do not unlock, with the reason recorded against the device record.

The unlocking decision: when it adds value

Device unlocking can be commercially useful when:

  • the unlocked resale value uplift is real
  • the device has passed intake checks and core testing
  • the route to sale is clear and timely

By contrast, unlocking is usually a poor decision when:

  • device ownership or risk status is unclear
  • account lock status is unresolved
  • the device is borderline or likely to fail later stages
  • the cost or time outweighs the resale uplift

The practical unlocking workflow

Use this as your unlocking SOP. It is designed to stop money being spent on the wrong devices and reduce failed jobs.

Step 1: Capture identifiers and route status first

  • Record IMEI and serial at intake and tie them to one device record.
  • Run the due diligence and lock checks your process requires.
  • Do not let devices move into unlocking without a clear route status.

This prevents unlocking from becoming an expensive detour.

Step 2: Clear the non-unlocking blockers

Before you unlock anything, confirm that the device is otherwise suitable for processing. In practice, this usually means:

  • risk and status checks completed
  • account-lock issues resolved where relevant
  • basic functional testing completed

If a device still has an unresolved account lock or major functional failure, unlocking often adds cost without adding value.

Step 3: Apply a written unlock timing rule

  • Unlock now: checks and tests have passed, and the device is ready for a route where unlocking improves resale value
  • Unlock later: further inspection or repair is still pending, or sale timing is uncertain
  • Do not unlock: the stock is flagged, disputed, low-value or otherwise unsuitable
Simple policy example: Only unlock devices after due diligence and core functionality checks pass.

Step 4: Record the unlock process and result

A proper unlock record saves time later when a buyer or colleague asks what happened.

  • IMEI or serial
  • method or provider used, where relevant
  • date and time
  • result and any notes
  • operator or system reference

Step 5: Re-test key connectivity functions after unlocking

  • SIM and network detection
  • calls and data where relevant
  • basic signal and connectivity checks

This step catches simple issues before the device reaches a buyer.

How MobiCode keeps unlocking decisions tied to the right checks

MobiCode helps most when it stops teams from treating every locked device as the same problem. The real operational benefit comes from separating risk, account issues and genuine unlock opportunities.

  • Unlock services: support value recovery where unlocking is commercially worthwhile.
    See: MobiCode Unlock
  • Due diligence before unlocking: reduce wasted spend on risky stock.
    See: MobiCode CHECK
  • Connected processing flow: keep unlock decisions tied to check, test and wipe stages.
    See: MobiONE

The practical result is fewer failed unlock jobs, fewer delays and better use of bench time.

Current factual note

Ofcom’s rules banning mobile companies from selling locked handsets came into force in December 2021. That reduced some consumer-facing locking issues. Even so, trade and refurb teams still need unlocking workflows in cases where stock age, source and resale route vary.

Common mistakes that cost money

  • Unlocking before checks: teams waste spend on devices that later fail another stage
  • Confusing network unlock and account lock: the wrong fix is applied to the wrong problem
  • No timing rule: staff make inconsistent decisions
  • No records: disputes and support queries take longer
  • No re-test after unlock: teams find issues after sale
Android device unlock workflow on a technician bench
Unlocking delivers the best value when teams treat it as a controlled step rather than a reflex action.

Unlocking takeaway

Unlocking delivers the most value when you control it. Treat it as a workflow decision with clear prerequisites, timing rules and records. That is how traders reduce rework and avoid spending money on the wrong devices.

What a safe Android lock workflow looks like

On Android and legacy devices, the practical issue is often FRP, a Samsung account lock, or another account-based lock that survives a reset. The safest workflow is to verify account status before you promise a turnaround, then ask the original owner to remove the account through the legitimate vendor route. If they cannot, pause the job and price it accordingly rather than pushing it through on hope.

This matters because teams often use “unlocking” as a loose catch-all term in the trade. Legitimate account removal and proof-of-ownership checks are one thing. Promising a bypass when you do not have lawful access or the original credentials is something else entirely, and it usually ends in failed jobs, refunds and wasted bench time.

FAQ: device unlocking workflows for traders

Should we unlock before or after testing?
Usually after due diligence and core functional checks, so you do not spend money on devices that should be held or rejected.

Does network unlocking solve account lock problems?
No. Network unlocking and account locks, such as Activation Lock, are different issues and need different checks and workflows.

Why keep unlock records?
Because they reduce support time, help resolve buyer issues and make the process more consistent across the team.

Useful references