“Tekmetric already shows average repair order.”
Shop-wide. It is several numbers, one per channel, and the differences are large.
For Tekmetric
Export repair orders from Tekmetric, upload the leads behind them, and rank channels on approved work rather than on cars through the door.
CloseRev reads a Tekmetric export of closed repair orders — the customer's phone or email, the total and the date — and matches it against the calls, ads and listings that produced the first visit. Tekmetric reports average repair order and approval rates unusually clearly; what it cannot say is which marketing produced the customers whose numbers are good. Orders with no traceable lead are reported as Direct / Unknown.
Page updated September 24, 2026.
The gap
Your average repair order is a shop-wide number. It is really several numbers, one per channel, and you cannot see them.
What was sold, to whom, and for how much.
The click, the keyword, the call, and what each one cost.
The file
Three things carry the match: who, how much, and when. Anything else is optional and only changes how the report can be sliced.
On the customer record. The phone number is the reliable key in this trade.
Parts and labor on closed orders, which is approved work rather than recommended work.
When the order was closed. Applied consistently to every row.
Mapped as Product / service — maintenance, major repair, tires. Declined work is not read; approval stays in Tekmetric's own reports.
Step by step
Written for somebody with Tekmetric open in the next tab. Report names vary by edition, so each step says what to look for.
One row per order with a customer contact detail, the total and the date.
Declined work is not read, but approval rate set beside each channel's revenue — the matched-records export names each customer's channel — is the most useful comparison here.
A repair customer is worth several visits, and the first one is often the smallest.
Call tracking, map listings, search ads, coupon offers and any fleet or warranty program.
The join runs on the phone and the email, normalized, with every return visit credited to the channel that produced the first.
What comes back
Revenue by channel, the count of sales behind each figure, and an honest bucket for the ones nobody could trace. Sample figures, from the worked example on the Auto Repair Shops page — not from a Tekmetric account.
| Channel | Share | Sales | Revenue |
|---|---|---|---|
| Google Ads | 203 | $101,500 | |
| Local service ads | 142 | $77,000 | |
| Meta Ads | 61 | $24,500 | |
| Direct / Unknown | 289 | $147,000 |
Unmatched sales stay in Direct / Unknown. They are never spread across the paid channels to make the total look better.
The argument
A digital inspection produces the same recommendations regardless of how the customer found the shop; what varies is whether they say yes.
That variation tracks with why the customer came: somebody drawn by a discounted oil change is making a price decision, and somebody whose car broke down is not.
Declined work is not read, but the report gives approved value per channel, and set beside Tekmetric's approval figures through the matched-records export, that explains a shop-wide average repair order that never made sense.
It is also the most actionable output here, because it points at the offer and the service advisor conversation rather than at the channel itself.
A channel with good traffic and poor approval can be fixable without changing the spend at all.
Oil change and brake specials fill bays quickly and produce a first transaction that is nearly identical across every channel that runs one.
The information appears later, in whether the customer returned for work that was not discounted.
A year of repair orders, every visit credited to the channel that produced the customer, separates the channels that bought a transaction from the ones that produced a relationship.
Discount channels can lose that comparison by a wide margin, which is not an argument against offers but against judging them on the day they run.
Mapping a first/return column as Product / service keeps first visits and later ones apart, so the two effects are never averaged into one misleading figure.
A small fleet is won once, serviced regularly and lost in a single bad experience, and its annual value dwarfs a retail customer's.
Averaged in, one fleet win makes whichever channel produced it look extraordinary on a result that will not repeat.
Mapped as Product / service, a customer-type column gives honest retail and commercial revenue lines, and the matched-records export shows whether the sources feeding each differ.
Where the export flags a customer type, map it; where it does not, mark fleet accounts before uploading, because the report will not infer them.
For a shop trying to build commercial work, that second ranking is the whole reason to run the report.
Drivers with a warning light or a noise call, and so do the ones who saw the sign, the map listing or the coupon.
Without tracked numbers those all arrive identically, and the lead file covers only the customers who used a web form.
Distinct numbers on the website, the map listing, any print and the sign itself produce a lead file with a source on every row.
Until that exists the report states the size of the untracked bucket rather than distributing it across whatever else was running.
It is worth doing before anything else on this page. A shop that tracks its calls can rank every channel it buys; a shop that does not is reading a report about the fraction of customers who happened to use a form, and that fraction is not representative of anything.
Fair questions
Shop-wide. It is several numbers, one per channel, and the differences are large.
They do. Whether they produce customers who approve real work is a different question the file answers.
Then most of this trade's inquiries have no source, and tracked numbers are the first fix rather than a different report.
No. It reads an exported file, so your orders, inspections and customer records stay where they are.
Closed repair orders with a customer contact detail, the total and the date.
It is not read. Set Tekmetric's approval rate beside each channel's revenue and it explains a shop-wide average repair order that never made sense.
A year, because a repair customer is worth several visits and the first is often the smallest. There is no window to set.
Yes, on a year of revenue per channel, which is where discount channels can lose their advantage.
Mark them with a customer-type column mapped as Product / service; otherwise one fleet win makes a channel look extraordinary on a result that will not repeat.
Yes. They carry the same contact detail, so they credit the channel that produced the first; a first/return column mapped as Product / service shows them apart.
Every order joins on the customer's phone or email, so all their vehicles credit the channel that produced the customer — the relationship rather than the vehicle is the unit.
Yes, mapped as Product / service where the export carries one, and maintenance and major repair behave differently.
Anything with no traceable lead, such as untracked calls and passing trade.
A contact detail, an amount and a date, plus a service type if you include one. No VINs required, no inspection photographs, no card data. Encrypted in transit and at rest and deleted with the import.
A year of revenue by source, every visit credited to the channel that produced the customer, fleet and retail apart where you mark them, and everything unmatched kept visible.
By trade
What the report looks like once the export is in, written for each one.
Other systems
Running more than one system, or comparing? The method is the same and the columns are not.
Tekmetric and the other product names and logos on this page belong to their owners and are shown to identify the software a file comes from. CloseRev is not affiliated with or endorsed by them, and connects to none of them: it reads a file you export.
From the blog
Multi-crew home and field services businesses run on phone calls and job management software, not on web forms. Which means the standard marketing dashboard is measuring the smallest part of the business and missing where the money actually is.
Read the articleCall tracking answers one question well: which campaign produced the ring. It has no view of what happened after the call ended, which is where the money is decided. This is what the gap costs, and how to close it without replacing the call tracker you already have.
Read the articleZillow Premier Agent sells connections by share of voice in a zip code, or through Zillow Preferred for a fee when a lead closes, generally within two years. A monthly bill set against this month's closings will mislead you either way. Here is how to measure Zillow ROI by connection cohort, where the break-even between the two pricing models sits, and what to do about leads who were already your clients.
Read the articleStart today
Nothing to install in Tekmetric, no API key, and no need to have been tracking anything until now. Last year works as well as this month.