Car wash car count vs POS sales: a daily reconciliation worksheet

To match car count to sales at a car wash, take the day's count from the tunnel controller or an entrance camera, subtract every car that shouldn't carry a retail sale (member scans, re-washes, comps, test and employee cars), and compare what's left with the retail washes rung up in the POS. Do it by hour and by lane, because a gap that disappears in a daily total often shows up clearly at 2pm on lane 2. Every car you still can't explain goes on a short list to check against video.

This worksheet is for express tunnel, flex and in-bay automatic operators, and for the managers who close out each site. It works with any POS and any controller. Print it, or copy the tables into a spreadsheet and use the same version at every site.

Updated November 22, 2026.

Quick answer

Take the day's car count from your tunnel controller or entrance camera, subtract every car that shouldn't have a retail sale (member scans, re-washes, comps, test and employee cars), and compare what's left with retail washes rung up in the POS. Do it by hour and by lane, not just for the day. Any car you can't explain goes on a short list to check against video.

Before you sign anything, you’ll speak with businesses we already work with. No pitch deck, no pressure. If it’s not a fit, we’ll tell you.

Why doesn't my car count match my POS sales?

Because the two systems count different things. The controller (or a camera at the entrance) counts cars that went through. The POS counts sales. A car can go through without a retail sale for honest reasons, and a sale can exist without a car going through. The common causes:

CauseCar counted?Retail sale in POS?Where to check
Member scan (RFID, plate or barcode)YesNo (shows as a member wash)Membership or plate recognition report
Re-wash for an unhappy customerYesNoRe-wash log or manager code
Comp, coupon or free wash codeYesSometimes $0Discount and comp report
Gate opened by hand or wash fired from the controllerYesNoController event log, gate override report
Test car, employee car, equipment checkYesNoManager log
Sale rung up but car never washed (refund, drove off)NoYesVoids, refunds, incomplete sales
Car counted twice (backed up, sensor glitch)Yes, twiceOnceController log, video
Clock differences between systemsShifts between hoursYesCompare both clocks at opening

Some POS systems already put the two counts side by side. FlexWash's Wash Analytics report, for example, shows a POS car count, a controller car count and the difference, and its documentation says that view can show washes "potentially being fired on the controller directly without being charged" (FlexWash docs). DRB's own guide to POS reports notes that sales "marked paid but never marked as serviced" can point to a communication problem between the POS and the tunnel controller, and that shortages can mean theft or simply a setup issue (DRB). If your system has a report like this, start there. The worksheet below is for when it doesn't, or when you want to know why the difference is what it is.

Before you start: set the rules once

Fill these in for each site and keep them the same every day. Changing the rules is the easiest way to make a gap disappear on paper.

RuleYour answer
Count source (controller, entrance camera, both)
Business day cut-off time (same at every site)
Which POS reports you pull (retail washes, member washes, comps, voids, refunds)
Who can approve a re-wash or comp, and how it's recorded
Who can open the gate or fire a wash from the controller, and how it's recorded
How test and employee cars are logged
Gap that triggers a video check (cars per hour or per day)
Who reviews the worksheet, and by what time

The daily worksheet

One row per hour per lane. For a single-lane tunnel, one row per hour.

HourLaneCar countMember scansRe-washesComps / freeTest / employeeGate overridesExpected retail washesRetail washes in POSUnexplained gap
Day total

The formula:

  • Expected retail washes = car count − member scans − re-washes − comps − test / employee cars − logged gate overrides
  • Unexplained gap = expected retail washes − retail washes in POS

A positive gap means more cars went through than you can account for. A negative gap means the POS shows more retail sales than cars, which usually points to refunds, drive-offs after paying, or a counting problem.

Note that a logged gate override is subtracted because someone recorded why it happened. An override with no reason recorded stays in the gap.

Worked example

Made-up numbers, not real store data. One express tunnel, one Saturday afternoon, two pay lanes.

HourLaneCar countMember scansRe-washesComps / freeTest / employeeGate overrides (logged)Expected retailRetail in POSGap
12–1pm14830110016160
12–1pm24427020015150
1–2pm15233011017161
1–2pm25029110019136
2–3pm14629000116160
2–3pm24125010015141
Total281173261198908

The day total says 8 cars out of 281 don't match, which is easy to shrug off. The hourly view says 6 of those 8 came through lane 2 between 1 and 2pm. That's one hour on one lane to look at on video, not a whole day. It might be a member tag that didn't read and was waved through, a stuck pay station, or a gate opened without a reason logged. You find out by watching those cars, not by guessing.

What does a normal gap look like?

There's no published industry benchmark we'd trust for this, so don't borrow someone else's number. Use your own:

  1. Run the worksheet for two weeks without acting on it, to see each site's usual gap.
  2. Treat a small, steady gap spread across the day as noise to keep an eye on (clock drift, a sensor that double-counts now and then).
  3. Treat these as worth a video check: a gap concentrated in one hour, one lane or one shift; a gap that grows week over week; a site whose gap is clearly different from your other sites; gate overrides with no reason logged.
  4. Re-check the rules if every site shows a gap of the same size. That usually means a counting or cut-off problem, not people.

How to look into a gap without blaming staff

Most gaps turn out to be process, not theft: a member tag that stopped reading, a re-wash nobody logged, a manager code used for a comp. Start from that assumption.

  1. Pull the video for the cars in the gap, at the pay station and the tunnel entrance, for that hour and lane.
  2. Sort each car into a reason: unread member tag, unlogged re-wash or comp, gate opened by hand, double count, or no reason found.
  3. Fix the cause you find. Retrain on logging re-washes, replace a tag reader, change who can open the gate.
  4. Only then look at people, and only for cars with no reason after review. If one shift or one code keeps coming up, have a private conversation with the manager and show them the clips.
  5. Write down what you found in the worksheet's notes, so next week's review starts from what you already know.

How often should you reconcile car count and sales?

Daily, per site, before the morning report goes out. Weekly is too slow: by the time you look, the video for the hour that matters may already be overwritten. Monthly is only useful for trends. If you run several sites, put each site's daily gap side by side on one page so you can see which one is drifting.

How Trilix fits

We build this check so nobody fills it in by hand. Using the cameras you already have, we count every car at the entrance by lane, match each one to a POS sale, member scan, re-wash or comp, and list the cars with no match along with their clips. The result shows up every morning on one owner dashboard by site, lane and hour, next to car count, member mix and sales. More on the car wash side on our car wash analytics page, in car wash cameras with AI, and in our membership sharing audit. For claims, use the car wash damage claim checklist.

Frequently asked questions

Something else on your mind? Ask us directly or call 416-262-2723.

Does the tunnel controller count equal sales?

No. The controller counts cars that went through, including members, re-washes, comps, test cars and any wash fired directly from the controller. Subtract the cars that shouldn't have a retail sale before you compare it with POS sales.

How do members affect the car count reconciliation?

Members go through without a retail sale, so subtract member scans first. Watch for cars waved through when a tag or plate didn't read: they show up as a gap unless someone logs them as member washes.

What is a gate override at a car wash?

It's when the gate or the wash is triggered by hand, from the controller or a manager button, instead of by a paid sale or a member scan. Overrides have honest uses (a stuck pay station, a re-wash), which is why each one should have a reason recorded.

Should I count cars with a camera or the controller?

Either works if you use the same source every day. Using both is better: when the controller and an entrance camera disagree, you know the count itself needs checking before you look at sales.

How do I check free washes and comps?

Pull the comp, coupon and $0 sales report for the day, match it to the re-wash log and manager approvals, and look at who approved each one. A comp with no reason or no approver is worth a question.

Can I use this worksheet for an in-bay automatic?

Yes. Treat each bay as a lane and use the bay's cycle count as the car count. The same subtractions apply.

How long does the daily reconciliation take?

By hand, it depends on how many reports you have to pull and how many sites you run. Once the reports are exported in the same format every day, filling in the totals is quick. The video checks take longer, which is why you only do them for the hours and lanes with a gap.

Want this check done for you every morning?

Tell us your POS, controller and cameras, and we'll show you what a daily car count vs sales view would look like for each site and lane.

Before you sign anything, you’ll speak with businesses we already work with. No pitch deck, no pressure. If it’s not a fit, we’ll tell you.