Deciding Whether a Callback Is Warranty or Billable

Why this matters

Every callback is one of two things in your books: a warranty event you absorb, or a billable job you invoice. Which label it gets is not only what the customer pays. It is how the work is coded in your system, and that coding is what makes your true warranty cost visible and your reserve fundable. Get the label wrong in either direction and you pay twice: once on the job, and again in a warranty number you can no longer trust. This card is about classifying the callback correctly inside your own operation, which is a different job from deciding what to charge the customer.

The sort: warranty or new work

The line between warranty and billable is causation. Warranty covers what traces back to your prior visit. Billable covers what does not.

• Warranty (you absorb it): your repair did not hold, you misdiagnosed and replaced a good part, you damaged something on the visit, or a part you installed failed within its terms. All of it connects to work you already did and were already paid for.
• Billable (you invoice it): a genuinely separate fault on the same system, a pre-existing condition your repair merely revealed, new damage from the customer's use or an outside event, or a wear item that reached end of life on schedule.

The unifying test: no link to your prior visit, no obligation to absorb it. A link to your prior visit, no invoice.

The manufacturer part is a third payer, not a third label

A callback can be "warranty" to the customer while the money comes from a third place. When the failed item is a covered manufacturer part, the classification splits by payer:

• The part is the manufacturer's cost, recovered by filing their claim.
• The labor to swap it is yours to decide by policy: absorbed under your workmanship promise, or billed, depending on your stated labor coverage.

Coding this as a flat "warranty, no charge" hides the fact that the part cost belongs to the factory and should be recovered. Coding it as "billable" hides that the customer owes nothing for the part. Split the payer so both stay true.

The mixed visit: one trip, two labels

Real callbacks are often partly your miss and partly new work, and forcing the whole trip into one label overcharges or overgives. Split the invoice instead.

• Waive the trip charge and the diagnostic when your prior work is what brought you back, then bill the genuinely separate repair you also did while there.
• On a pre-existing fault your repair unmasked, a common and fair split is to bill the new parts and labor while waiving the trip, so the customer sees you sharing the connection without eating a whole new repair.
• Put the split on the invoice in plain terms. A customer who sees "warranty, no charge" on one line and a billed line for the separate fault trusts the bill more than a single opaque total.

A mixed visit coded as all-warranty or all-billable is the most common way the warranty number drifts.

Both misclassification directions cost you

This is why the label matters beyond the single invoice.

• Calling your miss "billable" overcharges a customer for your own error. It wins one invoice and loses the relationship and the review, and it hides a workmanship problem you needed to see.
• Calling new work "warranty" gives away revenue you earned, and worse, it inflates your apparent warranty cost with work that was never a defect. Now your callback rate looks like a quality problem when it is actually a classification problem, and you may shorten a term or chase a training issue that does not exist.

The first error is visible because the customer complains. The second is invisible, which is what makes it dangerous. It quietly corrupts the one number you use to size your warranty program.

Coding it so the number stays honest

Classification is a bookkeeping act with consequences. Make it deliberate.

• Give warranty callbacks their own work-order type, distinct from billable service, so absorbed cost is counted, not written off into general labor.
• Tag each warranty callback with a root cause: installer, product, application, or customer condition later reclassified. The mix tells you whether your warranty cost is training, materials, or the normal price of the work.
• Reconcile periodically. If the warranty bucket is filling with work that was really new billable service, your labels are drifting and your reserve is being sized off fiction.

The principle to keep

The customer pays for new problems and never for your misses, and your books record which was which, honestly, every time. The charge decision protects the relationship. The classification decision protects the warranty program. They travel together, but do not confuse them: a callback correctly waived to the customer must still be coded as the warranty cost it is, or you are flying blind on the very promise you are funding.

References

• U.S. Small Business Administration (SBA), job costing and service-warranty policy basics
• Trade-standard practice on callback classification and workmanship warranties
• See related: Deciding What a Callback Should and Shouldn't Cost the Customer; Setting Warranty Terms You Can Actually Afford to Honor