Car wash equipment monitoring: how to know a bay or pay station is down before your customers do

Car wash equipment monitoring works best in three layers: the device tells you when it drops offline, your sales data tells you when a bay goes quiet during an hour it's normally busy, and your cameras tell you whether cars are pulling in and leaving without paying or washing. Most self-serve sites only have the first layer, and only for some devices.

The rest of this post is a worksheet for finding your blind spots and the math for setting a "this bay has gone quiet" alert that doesn't fire every slow afternoon.

Quick answer

• Layer 1, device alerts: the card reader, pay station or controller reports it's offline. Fast, but only covers what's connected.
• Layer 2, sales-gap alerts: a bay that normally takes several sales an hour shows none for a set window. Catches failures the devices don't report.
• Layer 3, cameras: cars pull in and leave without a sale, or nobody pulls in at all. Tells you whether it's the bay or just a slow day.
• Start with: the worksheet below, one row per thing that can stop a sale.

Why do operators find out last without car wash equipment monitoring?

In a sponsored Professional Carwashing & Detailing piece on remote monitoring, an operator put it plainly: "Typically, our stores don't know if their carwash is down until a customer says, 'Hey, I can't get a carwash.'" That's an in-bay automatic operator, but self-serve sites have the same problem with more pieces that can fail.

Stripe's guide to car wash payment terminals makes the same point from the payment side: many terminals can send alerts when a device goes offline, and small issues like a dim screen or slow reader "can lead to lost revenue, if ignored." It also notes that offline mode, where a reader keeps taking cards without a connection, is only offered on some models.

The catch is that a lot of what stops a sale isn't the payment device at all. A reader can be online and healthy while the wand behind it puts out nothing.

What can stop a sale at a self-serve bay?

Here's the worksheet. Fill in one row per failure for your own equipment. The first rows are common examples; add yours.

The column that matters most is the third one. Anything that says "customer complaint" or "next site visit" is a blind spot. If you visit each site once a week, a failure on Saturday morning can cost you the whole weekend.

How to set a sales-gap alert that doesn't cry wolf

A sales-gap alert fires when a bay has had no sales for longer than it normally would at that hour. The trick is that "normally" changes through the day. A gap of 30 minutes means nothing at 6 a.m. and a lot at 11 a.m. on a sunny Saturday.

Step by step

1. Pull 8 to 12 weeks of sales by bay and hour. Your pay station or POS export usually has a timestamp per sale.
2. Work out the average sales per hour for each bay, day of week and hour. Saturday 11 a.m. gets its own number.
3. Pick how often you're willing to get a false alarm. About 1 in 100 alerts is a reasonable start.
4. Set the gap window so a quiet bay that's working would hit it only that often. The example below shows the math.
5. Only run the alert in hours busy enough to support it. For slow hours, rely on device alerts and cameras.

Example calculation (made-up numbers)

Say a bay averages 6 sales an hour on Saturday late morning. If sales arrive roughly at random, the chance of a working bay going a whole window with zero sales is e^(−expected sales in the window), the standard Poisson estimate.

At 6 sales an hour, a 45-minute gap is a good alert: a working bay hits it about once in 90 tries. Now try a slow hour with 1 sale an hour on average. You'd need about 4.5 hours of silence for the same confidence. That's too late to be useful, which is why sales-gap alerts belong to your busy hours and cameras cover the rest.

What a missed weekend can cost (example)

Same example bay: 6 sales an hour at an $8 average sale, busy for 8 hours on Saturday and 8 on Sunday.

Swap in your own numbers. The point is that the cost of a failure is mostly the time until someone knows, not the repair.

What do cameras add?

Device alerts and sales gaps tell you something is wrong. Cameras tell you what kind of wrong, which decides whether you send a tech or ignore it.

• Cars pull in, then leave within a minute or two with no sale. The customer tried and gave up. Likely payment or startup.
• Cars pull in, a sale goes through, they leave early. Payment works, the wash doesn't. Likely pressure, chemical or the wand.
• Nobody pulls in at all during a busy hour. Bay looks closed: a light out, something blocking the bay, or a sign problem.
• Other bays are busy and this one is empty. Strong signal it's this bay, not the weather.

Most sites already have cameras covering the bays for security. The footage is there. Nobody is watching it until something goes wrong. Pointing an analytics layer at those same cameras turns them into a sensor that counts cars per bay and compares them to sales. We cover what that costs and what it can track in our car wash camera AI guide.

Who should get the alert?

An alert that goes to a shared inbox is the same as no alert. Decide three things per site:

1. Who gets it first. Usually the person closest to the site, by text.
2. What they do in the first 15 minutes. Check the camera, try a remote reset if your equipment supports it, or go look.
3. When it escalates. If the bay is still quiet after an hour, it goes to the owner or ops manager.

Then log each alert: what fired, what it was, how long until it was fixed. After a month you'll know which alerts are worth keeping and which equipment fails most.

How Trilix fits

We build bay camera analytics on the cameras most sites already have. For car washes, that means car counts per bay matched against sales, alerts when a bay goes quiet in a busy hour or cars leave without washing, and every site on one owner dashboard. It sits on top of your pay stations and POS rather than replacing them. More on the car wash side on our car wash analytics page.