Car count vs tickets is the gap between the cars that came through a store and the tickets the POS closed for them. Count cars with your bay or tunnel cameras, count every closed ticket including $0 ones, and subtract. Do it daily, by store. A small, steady gap is normal. A gap that grows, or sits at one store, tells you where to look.
Quick answer
- Two counts: cars seen (cameras or tunnel controller) and tickets rung up (POS, including $0 tickets and member washes).
- One number per store: gap = cars seen minus tickets. Ticket rate = tickets ÷ cars seen.
- Sort before you judge: top-offs, comebacks, employee cars, rewashes and camera double counts explain most of a gap.
- Read it by store and shift: the same gap everywhere points to a process. A gap at one store points to that store. (Where this sits among the other KPIs by store.)
What the top results leave out
Search "car count vs tickets" today and the top result is a 2010 shop owner forum thread, mostly members-only, about whether chasing car count hurts average repair order (AutoShopOwner). The rest of page one is off-topic. For "car count doesn't match POS", the top results are car wash forum threads where operators list causes like reprinted receipts, transactions voided before the car enters the tunnel, and a tunnel controller that isn't linked to the POS (Car Wash Forum). Trade press covers how many cars shops do: in NOLN's 2025 operator survey, 40.6% of quick lube respondents said they average 20 to 39 cars a day (NOLN).
None of them gives you:
- A definition. What counts as a car seen and what counts as a ticket.
- A daily method by store, so the number shows up while it still matters.
- The honest reasons for a gap, sorted, so a good crew doesn't get blamed for a warranty re-check.
- A worked example of reading the gap across several stores.
Why this number matters when you can't be at every store
With one store, you see the cars. With three or more, the POS is often your only record, and it only knows about cars someone rang up. A car worked and never ticketed doesn't appear in any sales report, and neither does a free wash or a favour for a friend.
Owners put it plainly: they can't see what's happening at each store, and every store does it a little differently. Car count vs tickets checks the POS against something outside it. It won't tell you why a gap exists, but it tells you which store, day and shift to ask about.
The two counts, defined
Cars seen. Every vehicle that entered a bay or the tunnel, from a source that doesn't depend on anyone pressing a button:
- Quick lube and tire: bay cameras logging car in, hood up and car out per bay.
- Car wash: the tunnel controller count, or cameras at the entrance or conveyor.
- Auto repair: cars on lifts by day. Multi-day jobs need care here (see below).
Tickets rung up. Every closed ticket for the same store and day, including:
- $0 tickets for top-offs, comebacks and courtesy checks
- Member washes redeemed by plate reader or tag
- Fleet and account tickets billed later
Leave voided tickets out of the count, but keep the void list. A ticket rung up and voided while the car was still worked on is one of the things you're looking for.
The math:
- Gap = cars seen − tickets rung up
- Gap % = gap ÷ cars seen
- Ticket rate = tickets rung up ÷ cars seen
Use the percentage when you compare stores, so a busy store and a quiet one sit on the same scale.
Honest reasons for a gap, by business
Most of a gap is ordinary. Rule these out first, and the list gets short.
| Business | Usual honest reasons | How to clear it |
|---|---|---|
| Quick lube | Free top-offs, comebacks, courtesy checks, employee cars, a car repositioned between bays | Every no-charge visit gets a $0 ticket with a reason code; keep a staff plate list |
| Car wash | Rewashes, member washes counted somewhere else, equipment test runs, employee cars, a car that backed out of the line | Include member redemptions in the ticket count; log rewashes and tests at the pay station |
| Tire and auto repair | Cars waiting on parts, multi-day jobs, one repair order covering two visits, a quick look with no work | Count cars by repair order, not by day, for jobs that span days; write $0 tickets for quick looks |
| Any | Camera double counts, a bumped camera, a ticket dated the next morning, a ticket rung up at the wrong store | Check the bay or lane with the gap, and match tickets by time window as well as date |
The $0 ticket rule shrinks the gap fastest. Once every car that enters a bay gets a ticket, even a free one, what's left is small enough to check one car at a time.
How to run it daily, by store
- Pull both counts every morning for yesterday, by store and by bay or lane.
- Show the gap and gap % next to car count and average ticket on each store's daily scorecard, and let managers see the same numbers you see. Our guide to holding managers accountable across multiple stores has a scorecard layout, and quick lube KPIs has the other formulas.
- Set a normal range after two weeks. Every store has a few honest gaps. You're looking for days and stores outside that range.
- Sort the gap at any store outside its range, using the table above. Match visits to tickets by time window, and by plate or VIN where you have it.
- Look at what's left with a snapshot or short clip for each car, and give the store a chance to explain before anyone draws a conclusion.
Read the pattern as well as the total:
- Same gap at every store: a process problem. The $0 ticket rule isn't written down, or the POS lets tickets close after the car leaves.
- One store: a manager conversation. Start with the process, then the people.
- One shift or day: look at who was on and what was different.
- After posted hours: cars in the bay before open or after close need a reason every time.
Worked example: one week, four stores (made-up numbers, not real store data)
Every number here is an example to show the math.
| Store | Cars seen | Tickets rung up (incl. $0) | Gap | Gap % |
|---|---|---|---|---|
| Store A | 412 | 405 | 7 | 1.7% |
| Store B | 368 | 363 | 5 | 1.4% |
| Store C | 455 | 421 | 34 | 7.5% |
| Store D | 290 | 284 | 6 | 2.1% |
Stores A, B and D sit in a normal range for this example. Store C stands out, so the owner sorts its 34:
| Reason | Cars |
|---|---|
| Top-offs and comebacks with no $0 ticket | 11 |
| Camera counted the same car twice at bay 2 (car backed out and pulled in again) | 9 |
| Employee cars | 6 |
| Left to look at | 8 |
Of the 8 left, 5 were in a bay after posted close on two evenings, and 3 were during the day with no ticket at all. Those 8 go to someone outside the store with a snapshot of each, the bay, the times and the plate where the camera read it.
What the owner does with it:
- The 11 top-offs become a coaching note for the whole store: write the $0 ticket.
- The 9 double counts need a camera fix at bay 2.
- The 6 employee cars go on the staff plate list, so they clear on their own next week.
- The 8 get a quiet look. Some may still have a plain answer. If they don't, the conversation is about how work gets rung up after close.
If Store C's gap doesn't drop into range next week, that's the next one-on-one.
What not to do with the number
- Don't walk in and ask about it. You'll get a cleaner-looking gap from then on and learn nothing.
- Don't send every gap to the store manager as a problem. Most are top-offs and camera hiccups.
- Don't skip the notice. If cameras are part of how you measure work, tell staff what's measured and why. In Ontario, employers with 25 or more employees need a written electronic monitoring policy (Ontario ESA guide); other provinces and states have their own rules, so check with your HR advisor or employment lawyer.
For the quick lube version of the car-by-car match, with the full decision table and false-positive sort, see employees not ringing up oil changes. For car wash member plates that don't match the person paying, see the membership sharing audit.
Where Trilix fits
We build camera analytics on the cameras most stores already have. They count cars by bay or lane and match each visit to your POS tickets, with a snapshot for every car that has no ticket. The gap by store lands on an executive dashboard each morning, next to car count, ticket average and calls, so you know what's happening at every store without driving the route. Running several washes? See car wash analytics. To put a dollar figure on your own gap, try the bay camera payback calculator, or get in touch.
Want to see this on your stores?
We’ll look at your calls, bays and tickets with you and show what we’d build first.