| Sector | Phone, tablet and electronics shops doing retail, repair or both |
|---|---|
| Common problems | Repair jobs on paper dockets, no parts visibility, constant "is it ready?" calls, stock unknown across branches |
| Typical fix | Repair jobs tracked against device and IMEI, parts linked to jobs, automatic customer notification, one stock view across branches |
| Also relevant | Daily till close across branches, which is what Reckon was built for, and network commission reconciliation |
| Starts with | A free operational audit |
| Area served | Ireland |
Two businesses behind one counter
A phone shop is a retail business and a workshop at the same time, sharing one set of staff and one counter. Retail wants stock, pricing and a fast till. Repair wants job tracking, parts and a way to tell a customer their phone is ready. Most shops run the first on a POS and the second on a paper docket book.
That gap is where the day disappears.
Where the time goes
- Repair jobs on paper dockets. A handwritten note with a name, a phone number and a description of the fault. Legible on Monday, ambiguous by Thursday.
- "Is my phone ready yet?" Every enquiry interrupts a sale and requires somebody to walk out the back and look.
- Parts with no link to jobs. A screen is ordered for a customer, arrives, gets used on a different repair, and the first customer waits another week.
- Stock invisible across branches. One shop orders what another already has.
- Trade-ins valued from memory. With no record of what was offered, why, or what the device was later worth.
- Commission taken on trust. Network and supplier statements arrive as totals that cannot practically be checked, so they are accepted.
- Each branch closing differently. Making any comparison across shops an exercise in reconciliation rather than reading.
What automating it looks like
Every repair a tracked job
Device, IMEI, reported fault, diagnosis, parts used, technician, status and price, recorded against one job from intake to collection. The docket book stops being the system of record.
The customer is told, not asked
Status changes notify the customer automatically. The phone stops ringing, the counter stops being interrupted, and collections happen sooner because people know.
Parts tied to the job that needs them
An ordered part belongs to a specific repair, so it cannot be quietly consumed by another one, and a job waiting on a part is visible as exactly that.
One stock view across branches
What is where, so a part is moved rather than ordered again.
A daily close that compares
Multi-branch shops have the same close problem as any retail group: every site recording things its own way. See multi-shop back office and Reckon.
Commission reconciled line by line
Statements checked against your own records rather than accepted as a total. Oxus does this at consignment level for parcel operators in DepotIQ, and the underlying problem is the same one.
Where to start
Start with a free operational audit. The quickest test of whether this is worth doing: count how many times in one day somebody has to walk to the workshop to answer a question a customer asked at the counter.
Frequently asked questions
What is the biggest time drain in a phone shop?
Customers ringing or calling in to ask whether a repair is ready. Every one of those interrupts whoever is serving, takes a trip to the workshop to check, and produces no revenue. Automatic notification when a job changes status removes almost all of them, because the customer already knows.
Why track repairs against the IMEI?
Because it is the only identifier that unambiguously identifies the device. Names get misspelled, phone numbers change, and two customers bring in the same model in the same week. The IMEI ties the job, the parts used, the warranty position and the history to one specific handset, which matters most when something comes back.
We have more than one branch. What changes?
Two things get worse. Stock becomes invisible, so one branch orders a part another branch already has sitting in a drawer. And the daily close diverges, because each shop develops its own way of recording it. That second problem is exactly what Reckon was built to solve for multi-shop groups.
Can you reconcile network and supplier commission?
Yes. Where a shop sells contracts or connections, commission statements arrive with totals that rarely match what the shop believes it is owed. Reconciling line by line against your own records is how a discrepancy becomes traceable instead of arguable. Oxus does this at consignment level in DepotIQ for parcel operators, and the problem is structurally identical.
What about warranties and returns?
Warranty position is a property of the device and the job that repaired it, so once repairs are tracked against the IMEI, a return is a lookup rather than an argument. It also makes recurring failures visible, such as a particular part or supplier producing more repeat repairs than it should.