AUTO REPAIRBUSINESS BROKERBook a call
Menu

What is average repair order (ARO)?

Average repair order is net sales on a defined set of completed repair orders divided by the number of orders in that same set. Define tax, discounts, refunds, and internal work before comparing shops. Read the average alongside visit count, direct cost, and gross profit to see what changed in the business.

Key takeaways

  • Match the revenue period and the closed-ticket population.
  • Weight group averages by ticket count when combining locations.
  • Test parts cost and labor margin before assigning value to an increase in ARO.

Average repair order (ARO) is qualifying repair sales divided by the number of qualifying completed repair orders over the same period. Your calculation needs a dollar definition, a ticket definition, and a date rule. Without those three items, comparing your average with another shop’s can create an apparent difference that comes entirely from reporting.

Which dollars belong in the numerator?

Use the sales earned on the set of orders you are counting. For a shop operating review, start with parts, labor, and other included repair charges after discounts and returns. Identify how the report treats sublet work, environmental fees, shop supplies, and sales tax. Save a bridge when its displayed total differs from the amount you use.

At the counter, a customer sees an amount due. In the books, that amount can contain money collected for a taxing authority or a prior deposit that reduces the current payment. If you use the card receipt as the sale, a deposit paid last month can make today’s invoice look too small. If you add tax to revenue, a change in the taxable mix can make average job size appear to grow.

Ask for a closed invoice that includes parts, labor, a discount, tax, and a payment. Write each element on its own line and mark its treatment. Then run the same convention across the whole period. A clear rule you apply consistently makes it possible for a buyer to check the figure and for a seller to explain why it differs from a dashboard.

Which repair orders belong in the denominator?

Count the orders that produced the sales you retained. A quote the customer declined belongs in a conversion analysis. Mixing it into an average of completed sales changes the question. Keep separate counts for written estimates, approved work, completed orders, and paid transactions if your software supports them.

Watch for jobs split into multiple invoices. A fleet statement may combine many repair orders into one bill. Conversely, a business may issue an invoice for diagnosis and a separate one for the repair during the same visit. Identify the convention before using ARO to estimate customer spending per visit. Your car count definition determines whether those two metrics mean the same thing.

A service writer report may use a different date or credit rule from an accounting report. Ask the writer to demonstrate one invoice that moved between employees or was reopened. Check how each report classifies it. Use the same exported population when validating the numerator and denominator, even if you also retain the software’s native KPI for day-to-day management.

How can two locations change the group average?

Combine sales and tickets before doing the division. The location with more orders should contribute more weight. A simple average of location AROs only gives the right group result when the relevant order counts are equal or the separate averages happen to coincide.

Illustrative composite — not a real client. A general repair location closes 300 tickets and sells $135,000 of work. Its ARO is $450. A specialty location closes 60 tickets on $54,000 of sales, for an ARO of $900. An unweighted average gives $675. The actual group figure is $189,000 divided by 360 tickets, or $525.

Illustrative two-location average repair order
LocationNet salesOrdersARO
General repair$135,000300$450
Specialty repair$54,00060$900
Both locations$189,000360$525

If the specialty location grows faster, the group average can rise even when neither location changes its own pricing. Make a location-by-location comparison before treating the increase as proof that your service writers improved. The same principle applies to fleet and retail work, diagnostic jobs and routine maintenance, and newly acquired locations.

Does a higher ARO increase what a buyer can pay?

Only the part that becomes sustainable earnings helps fund a purchase. A larger ticket can come from stronger diagnostic billing, a change in vehicle mix, a supplier price increase, or a single expensive replacement. Each has a different effect on gross profit and cash requirements.

Take a month with several high-cost transmission replacements. The purchased assemblies can make the average invoice look much larger while tying up cash until the vehicles leave. Look at technician hours, the parts cost, core credits, warranty terms, and payment dates. Check whether those jobs displaced other profitable work. The dealer invoice or parts statement can reveal a margin different from the one still recorded in the shop system.

Use the shop earnings builder with your original volume first. Then change only the average order and the margin associated with the work that caused it. If your model assumes higher ARO, higher volume, and unchanged margin all at once, name the evidence for each change. The buyer can then decide which assumptions to carry into the offer.

Did customers approve larger jobs, or did the job mix move?

Break the tickets into two or three service groups that your shop records consistently. A useful first pass might separate maintenance visits from major repairs. Compare the average within each group, then hold the averages still and change the mix. This lets you explain an increase in the combined figure without assuming that the service writer raised prices or persuaded anyone to buy more work.

Suppose a shop closes 150 maintenance visits averaging $180 and 50 major repairs averaging $900 in April. The two groups produce $27,000 and $45,000 respectively. Across 200 orders, April ARO is $360. In May it closes 100 maintenance tickets at $180 and 100 major repairs at $900. Sales are $108,000 and the average is $540. The average ticket increased by half even though neither group charged more per visit. This is an illustrative mix calculation. It says little about the next month until you know why the mix changed.

Ask the scheduler what happened to those fifty maintenance visits. Perhaps the team moved routine work to a sister location while one advisor was out. Perhaps the fleet customer brought a batch of major jobs forward before summer. Either explanation matters when you project what an independent buyer could repeat. Check parts dollars and technician hours as well. A few expensive assemblies can lift the ticket average while tying up scarce bay time and cash. If a buyer would need to hire an additional technician to sustain the new mix, include that hire in the proposed operating plan.

How much influence did the five largest invoices have?

Rank the paid repair orders by net amount. Put the largest five beside the median ticket and the shopwide average. You can show a buyer the original result and a sensitivity excluding those five while keeping the same filters. The exercise measures concentration. It does not give you permission to remove genuine recurring work from the reported period simply because the invoice amounts are high.

Imagine 100 paid tickets with $70,000 in total sales. Five transmission replacements contribute $25,000. The other 95 tickets produce $45,000, so their average is about $474. The reported $700 average is correct for the full month. The gap of approximately $226 per order shows how heavily those five replacements influenced the headline. Ask how those jobs arrived, whether the referring business still sends them and whether your proposed staff could complete them. A history of similar orders throughout the year supports a different forecast from a single batch sent by a neighboring shop during a temporary closure.

A median can help explain what your usual customer experiences, but it cannot replace the arithmetic average in a revenue bridge. Multiplying the median by ticket count will generally give you the wrong sales total. For a business plan, project the count and realizable average separately for the groups you expect to serve. Grouping by repair family can be more informative than grouping by dollar size when each family consumes a different kind of labor.

At the front counter, the same analysis can prompt a better conversation. If the routine-service average held steady while the overall average rose, avoid telling the team its inspection process improved until you have checked estimates written, jobs authorized and work completed. Look at actual customer authorizations before crediting a training program. The monthly arithmetic can establish where to look. The ticket history provides the evidence you need to attribute a change to a particular action.

What should you take from the report to a diligence meeting?

Take the underlying ticket file, the settings used to produce it, and a short reconciliation. Include the counts and dollars for jobs you excluded. The SMS report request checklist helps you ask for enough detail without circulating customer names or vehicle identifiers unnecessarily.

  1. Rebuild the ARO for one complete month and one location. Check your result against both the software display and the general ledger.
  2. Split the population into service categories that explain the business. Compare counts, net sales, and gross profit in each category.
  3. Pull unusual tickets and explain the business event behind them. Flag an engine replacement for a family vehicle differently from a repeatable fleet maintenance program.
  4. Compare the distribution across months. Include a middle-sized ticket and a range of typical visits so the average cannot hide a handful of unusually large jobs.

If you are selling, put that explanation in your data room before buyers ask why the number jumped. If you are buying, use it to decide what portion of the historical mix you can maintain with the technicians, suppliers, and customer relationships that will remain. Revisit the operations hub when the real constraint turns out to be bay space or technical coverage.

What else should you know?

Should I include sales tax when calculating ARO?

For an operating comparison, use net shop sales and state how you treated tax, discounts, credits, and fees. Tax collected for a government generally does not measure shop earnings. If software displays a tax-inclusive average, retain the original number and show the adjustment to the comparison basis.

Can I average the ARO figures for my three locations?

Add net sales across the locations and divide by their combined qualifying repair orders. An unweighted average gives a small specialty location the same influence as your busiest general repair shop. Show location-level figures underneath the combined result so a reader can see how the mix changed.

Why did my ARO rise while my gross profit fell?

Check the underlying jobs. Higher parts costs, a few expensive low-margin components, discounted labor, or a drop in smaller profitable visits can raise the average invoice while reducing total profit. Compare gross profit per visit and gross profit dollars for the whole period before drawing a conclusion.

How do I verify a seller’s claim about ARO growth?

Ask for ticket-level data for both periods and the report settings used. Recompute net sales and order count on the same basis, then split the change by service category and location. Trace a few unusually large jobs to authorizations, invoices, and settlement records before projecting their recurrence.

Which sources can you check?

Explore the operations hub

Where is this term used?

Recommended for you

Talk through your next move.

Bring your shop, your offer, or the question holding up your decision.

Book an intro call