Why does average ticket come out different in every report?
Because both halves of the fraction are ambiguous. The numerator can be invoice total, subtotal before tax, or revenue excluding memberships and financing fees. The denominator can be jobs, completed jobs, invoices, or opportunity jobs only. Every combination is defensible and they produce very different numbers. Write your definition down once, apply it everywhere, and expect it to disagree with someone else's.
Two ambiguous halves
Average ticket looks like the simplest metric in the business and is one of the most argued about. The disagreement is almost never about the data. It is about which invoices count and which jobs count.
Tax is the easiest example. Including sales tax makes technicians in high-tax jurisdictions look better than identical technicians elsewhere. Excluding it is more comparable and lower. Neither is wrong; only one can be in the report.
The decisions you have to make explicitly
- Tax in or out. Out is more comparable across markets and across time when rates change.
- Membership sales in or out. Including them rewards attach behavior and distorts comparison to periods before the program existed.
- Zero-revenue jobs in or out. Warranty visits, callbacks and estimates-only visits drag the average down. Excluding them is common; excluding them silently is not honest.
- Multi-invoice jobs. Average per invoice and average per job differ sharply once deposits and change orders are involved. Per job is usually what people mean.
- Which jobs qualify. Opportunity jobs only, or every job. Restricting to opportunity jobs is the most useful version and requires a clear definition of what counts as an opportunity.
The version most operators actually want
In practice the most useful definition is invoice subtotal excluding tax, summed per job, over completed opportunity jobs, with warranty and callback jobs excluded and membership revenue reported separately alongside. It is comparable across markets, it is not inflated by paperwork mechanics, and it isolates the behavior you are trying to influence.
Whatever you choose, publish the definition next to the number. Reports that carry their own definition survive scrutiny; reports that do not get relitigated every quarter.
Watch the mix before you praise or blame anyone
Average ticket moves with job mix far more than with technician behavior. A month heavy on maintenance visits lowers it. A month with two large replacements raises it. Comparing a technician who runs mostly diagnostics to one who runs mostly installs tells you about dispatch, not about selling.
The correction is to compare within job type, or to weight by mix, before drawing conclusions. That normalization is a standard part of building defensible views in revenue intelligence, and it matters even more when the same metric is used across locations. See custom dashboards for how definitions get pinned into the reporting layer itself.
Topics: average ticket · metric definitions · revenue · reporting
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.