Phone Repair Shop Warranty Tracking: What to Record and When

Phone repair shop warranty tracking comes down to one test: when a customer walks back in with the screen you replaced, can you answer three questions before they finish their sentence? Which job was it, is it still inside the warranty window, and is this the same fault or new damage? If you can answer all three from your records, you are tracking warranties. If you are digging through a drawer of paper tickets or scrolling your personal texts, you are not, and every comeback turns into a negotiation.

This post is about the record-keeping side. It is not about what your warranty should promise (that is a separate decision, and our repair shop warranty policy template covers the terms). It is about what to write down at the counter, when the clock starts, how to find the original job fast, and how to count comebacks so they tell you something about your parts.

The three questions every warranty return asks

A warranty return is a lookup problem before it is a repair problem. The customer says "the screen you put in stopped working," and you need three facts:

• Which job. The original repair, with the date, the device and the part you used.
• Which window. The warranty length you gave on that ticket, and the date it started counting.
• Which fault. What the phone looked like when it came in, so you can tell a failed part from a fresh drop.

Every field you record at intake exists to answer one of those. If a field does not help with any of them, you can probably skip it (your counter line is long enough already).

What to record at the counter, before you open the phone

Most of the useful warranty data is captured in the first few minutes of a job, not at pickup. Once the phone is open, you cannot go back and photograph the cracked corner that was already there.

• Customer phone number. This is the key you will search by later. Names get misspelled and receipts get thrown out, but people rarely forget their own number.
• Device and identifier. Model, colour and the IMEI or serial number. The identifier is what tells you the phone on the counter is the same phone you fixed, and not a second device in the family.
• Pre-existing condition, with photos. Frame dents, a bent corner, a lifted back glass, signs of liquid. Photos taken at drop-off settle most "new damage or old fault" arguments before they start.
• The part. The grade you installed (OEM, refurbished or aftermarket) and the supplier you bought it from. This matters more than it looks, and we come back to it below.
• The warranty on this ticket. If you offer different lengths by part grade, write the one that applies to this repair. Do not rely on remembering which grade went in.
• Who did the work. Only relevant once you have more than one tech, but cheap to record from day one.

A full repair shop intake form covers the rest of the counter conversation (passcode handling, the estimate, the signature). The list above is just the part that warranty tracking depends on.

When does the warranty clock actually start?

This sounds like a detail until a phone sits on your shelf for a week after the repair. Did the warranty start when you finished the work, or when the customer picked it up?

Big repairers pick a date and write it into the terms. Apple's repair terms, for example, warrant parts used in service "for ninety (90) days from the date of service." That wording ties the clock to the service date, not to the day the customer collects the device.

For a small shop, the pickup date is usually the fairer choice (and the easier one to defend), because the customer cannot use the phone while it is waiting on your shelf. Either choice works, technically, as long as three things are true: the policy names the date, the ticket records that date, and you apply the same rule to every job. The shop that argues about start dates is almost always the shop that never wrote one down.

Finding the original job when the customer walks back in

Search by phone number first, then by name. A customer who calls themselves "Mike" at drop-off and "Michael" at the return will not show up in a name search, but the number is the same both times.

The other trap is archiving. Most shops clear finished jobs out of the active list so the day's work stays readable, which is sensible. But warranty returns come from the archive by definition, so whatever you use has to search finished and archived jobs, not only the open ones. Test this before you need it: pick a job you closed a month ago and time how long it takes to pull it up.

If the answer is "I would have to ask the customer for the receipt," the tracking lives on paper in the customer's pocket, not in your shop.

Is it a warranty claim or new damage?

With the original job open, the call is usually quick. Compare the intake photos with the phone in front of you. A screen that went dark with no new marks on the frame points at the part. A fresh impact point on the glass, or liquid indicators that were clean at drop-off and are now tripped, points at new damage.

While photos settle most cases, they will not settle all of them, and a borderline case is a judgement call. Your written exclusions decide the outcome, and your tone decides whether the customer comes back. If a return turns heated, the advice on how to handle an angry customer at a repair shop applies here too.

Log the comeback on the original job, not as a new ticket

This is the habit that turns warranty tracking from a defensive chore into something useful. When a covered repair comes back, reopen the original job and record the return there: the date, what failed and what you did about it. Do not open a fresh ticket with a zero price.

Why does it matter where the note goes? Because a zero-dollar ticket looks like a new job in your numbers, and a note on the original job ties the failure to the part, the supplier and the tech that produced it. After a few months you can answer questions that actually change how you buy parts: which supplier's screens come back most, whether one part grade fails faster, and whether returns cluster on one tech.

You do not need a dashboard for this. A weekly look at the jobs that came back, grouped by supplier, is enough to spot a bad batch before it costs you a month of free rework. It also gives you an honest answer when a customer asks whether the cheaper screen is worth it.

What FixyFlow does here, and what it does not

FixyFlow is phone repair shop software for the customer side of a repair: status texts, a tracking link, and replies from the customer. It is not a warranty system, so here is the honest split.

What it does:

• The Customers view searches by name, phone number or last job, and archived jobs have their own search, so a job you closed months ago is still findable.
• Each job holds photos, which is where the drop-off condition shots go.
• You can pin an operator-only note to the top of a job (customers never see it on their tracking page). "OEM screen, supplier B, warranty from pickup" fits in one line.
• You can move a finished job back to an earlier stage for warranty work, and the customer gets no text for the backward move, so they are not confused by a "status changed" message.
• If the rework changes the price, "Revise estimate" has a reason field, and each revision is kept on record. A reduction applies without re-asking the customer for approval.

What it does not do: there is no warranty-expiry field, no countdown and no parts or supplier inventory. FixyFlow also does not replace your ticketing or POS. If you run RepairShopr or RepairDesk for tickets, the ticket there is your warranty record, and FixyFlow sits on top for customer updates. For a solo shop without a ticket system, the pinned note and photos cover the three questions above, which is most of what warranty tracking needs.

One more piece that helps: a short check-in text a week after pickup. It is part of a good customer follow-up after service, and it surfaces a failing part while the customer is still friendly about it, not after they have given up on you. If time at the counter is your real bottleneck, the post on phone repair shop efficiency covers the rest of the day.

A short version to put on the wall

1. Photograph the phone at drop-off, before it is opened.
2. Record the identifier, the part grade and the supplier on every ticket.
3. Write the start date your policy uses, and use the same rule every time.
4. Search by phone number, and make sure archived jobs are searchable.
5. Log every comeback on the original job, then look at them by supplier once a week.

If you want to try the customer-update side with your own jobs, FixyFlow has a free trial of the field service software (14 days, no credit card), and the field service software pricing page lists what each plan includes after that.

— Lasse
Built FixyFlow in Collingwood