Guides · Warranty work

Warranty vs callback: the difference that protects margins

Warranty work is $0 with a manufacturer claim behind it. A callback is your redo work. Confusing them costs you twice — here's the rule and the records.

Last updated Fri Oct 30 2026 00:00:00 GMT+0000 (Coordinated Universal Time) · 5 min read

What's the difference between a warranty job and a callback?

Short answer: A warranty job is covered by the manufacturer (or a service agreement) — the customer owes nothing and the manufacturer may owe you. A callback is your shop redoing its own work — nobody owes you anything, and the customer owes nothing again. Both invoice at $0. They are never the same thing, and mixing them up costs money in both directions.

The decision rule

Ask one question: did the failure belong to someone else's promise or ours?

| | Warranty | Callback | |---|---|---| | Who's responsible | Manufacturer / distributor / service agreement | Your shop | | Invoice | $0, warranty reference recorded | $0, linked to the original job | | Parts | Claimed from the manufacturer where the program pays | Your cost, absorbed — but tracked | | Labor | Claimed under the labor program if one exists | Your cost, tracked | | The real question | Did we file the claim? | Why did the first visit fail? |

Where shops lose money

Warranty jobs handled as callbacks. The part failed within the manufacturer's window, but the office recorded it as a callback redo — so no claim was filed, and the replacement part sat in inventory unbilled to anyone. You paid for the part twice: once to buy it, once in margin never recovered from the manufacturer. On a $780 compressor with a $150 labor claim, that's real money — repeated across a fleet of installs.

Callbacks billed as new work. The inverse: the customer calls back three days after the repair; the tech returns; the office generates a fresh invoice. The customer pays twice for one fix. This one costs more than dollars — it costs the customer, and in a 3–15 tech shop, every customer knows five others.

The quiet third case: callbacks with billed parts. A callback where the new part (different failure) is billed at full margin — legitimate — but the visit fee from the original repair isn't honored. Contract terms you set yourself are terms worth keeping.

A worked example

Same truck, two jobs, one week:

  • Job A — warranty. 2019-installed condenser, compressor failed at year 7, inside the 10-year parts warranty. Correct record: $0 invoice, "WARRANTY — Lennox, claim #LN-90412" in the memo, replacement compressor listed at $0. Outcome: customer pays nothing, shop recovers the $150 labor claim and the part cost from the manufacturer's program.
  • Job B — callback. The same shop's own install from August; the new blower motor's harness connector wasn't seated. Correct record: $0 invoice, "CALLBACK — original job #2087" in the memo. Outcome: customer pays nothing again, and the callback counter ticks — which is how the shop learns the harness step was being skipped.

Now the wrong version of Job B: office generates a fresh $189 invoice because "customer called, tech went, work happened." Customer pays twice for one fix. In a 3–15 tech shop, that customer tells five others. The dollar cost of the mistake is smaller than the trust cost — and both came from one unlabeled job.

Common mistakes

  • Recording callbacks as warranty because both are $0 — and losing track of which failures are yours to fix.
  • Recording warranty as callbacks and never filing the claims.
  • Letting callbacks generate new invoices. The return visit is covered by the original work.
  • Never computing the callback rate. It's the cheapest quality metric you own.

Record-keeping that prevents both

  1. Every $0 invoice says which it is. Description contains "WARRANTY — [manufacturer]" or "CALLBACK — original job #[number]". One glance, no ambiguity, forever.
  2. Warranty claims tracked to the invoice. Claim number in the invoice notes. Unclaimed warranty labor is invisible in every report except one that looks for $0 warranty invoices with no claim reference.
  3. Callback rate is a number you know. Callbacks ÷ completed jobs, monthly. Rising callback rate is the earliest warning of install-quality or tech-training problems — and it's free to compute from your own exports.

Author: Unbilled. Our reconciliation treats both as legitimate $0 work — and distinguishes them, so warranty claims you forgot to file surface as operations findings, not billing noise. Or let us run it: send three files, get a one-page report.

Or let us run it: send three files, get a one-page report.

Related