Car wash management software: the whole business on one screen

Written by Tanrikulu Apps — the team that builds WashPro. We describe our own product separately at the end; the criteria are written for evaluating any system. Last updated: October 16, 2026.

A day at a car wash is really seven or eight linked records: which car arrived, what is being done, who is doing it, when it will be finished, what it came to, who took the money, and what each person is owed at the end of the month. Every one of those records is already being kept today. The problem is not that they are missing — it is that they are kept in different places: partly in a notebook, partly in someone's head, partly in a phone call.

This page does not start as a product pitch. It starts with where a car wash actually loses time and money, and what a management system has to do about it. Our own app appears further down; but the questions come first, because software chosen against the wrong questions gets abandoned within six months.

Where the day leaks

Ask an operator what the hardest part of the job is and the answer is almost never “washing the car”. The hard part is holding four things in mind at once:

• The queue. Who arrived first, which car is being washed, which one is waiting to be dried. At peak hour that lives in someone's memory, and memory is wrong sometimes.
• The promise. A car promised in half an hour takes forty-five minutes, so the customer rings. The phone goes, and the person actually working takes their gloves off.
• The money. Cash or card; who left on credit; what should be in the till tonight. When the count does not reconcile, the mistake is not found — it is papered over.
• The payroll. The end-of-month “I washed this many cars” argument. Both sides believe they are right, because both numbers are estimates.

All four are record-keeping problems. They do not leak because nobody works hard enough; they leak because the record never accumulates in one place. That is precisely the job of car wash management software: never asking for the same fact twice.

What car wash software actually has to handle

What follows is not a feature list written to look long. These are the things that stop the day when they break, and they are worth asking about one by one when you evaluate any system.

1. Intake has to take seconds

Nobody fills in a form while the customer sits in the car. The right flow is: photograph the plate, let it be read, pick the vehicle class and the services, and the job is in the queue. Manual entry still has to exist — dirty plates, foreign plates, no camera access — but the default path should be the fast one. Reading the plate correctly is also what keeps one vehicle's history in a single record; a plate typed two different ways looks like two different cars and the history splits.

2. The queue belongs on one board

Waiting — in progress — ready — delivered. Four states, one screen. Who is washing which car, and how long a job has been sitting, should be readable at a glance. On a tablet those columns should sit side by side; a board you can read from three metres away removes the question “where has that car got to?” rather than answering it.

3. Pricing belongs to the vehicle class

A hatchback and a panel van are not washed for the same money. The system should hold a price and a duration per service per class, plus a commission rate per person — and the class list should not be fixed, so you can add motorcycle, light commercial or tractor yourself. The duration field matters more than it looks: the ready-time estimate comes out of it.

4. The ready time should not be a guess

Instead of saying “about half an hour”, the system should say it. A good one starts from the theoretical duration on the price list, then learns from the durations that actually happened, and counts the jobs already in the queue. Once the times you give start holding, customers stop asking.

5. Customer contact has to live inside the job

Telling an owner their car is ready should not mean switching to another app. In practice two channels work together: a one-tap WhatsApp or SMS message, and a QR code created with the job. A customer who scans it watches their position, status and estimated ready time live on their own phone — no download, no sign-up. The second one is what ends the “how much longer?” calls.

6. Vehicle and plate history has to be kept

When the same plate arrives a second time, the system should know: which visit this is, when the car was last in, which service it usually takes. That is what lets you say “last time we did the full interior” — and it is the foundation under anything that brings customers back, such as a loyalty and rewards program.

7. Bookings and a channel for new customers

Most washes find customers through their location and their sign. Software adds value if it adds a channel: your business appears on a map, a customer picks a time and sends a request, you confirm from your phone. If a system offers this, ask two things — is there a limit that stops request spam, and can you switch off appearing on the map entirely.

8. The till, expenses and reporting

One number has to be certain at the end of the day: the one that should match the cash in the drawer. That requires collections split into cash and card, expenses entered on the same day, and work done on credit staying out of the till. If credit work is counted as a collection, the evening count always looks high and a real shortfall becomes invisible. Period reporting is a separate job: revenue, expenses, most frequent vehicles, staff comparison — PDF for the accountant, CSV for your own arithmetic.

9. Customer accounts and contract work

Fleets, corporate agreements and the customer who says “put it on my tab” exist at every wash. A customer who pays later needs an account: the job is booked as debt, a payment is entered when the money arrives, and the balance follows on its own. For arrangements like “four washes a month”, the system should count the remaining allowance — and which services are included should be your decision, because wax and engine bays usually sit outside the deal.

10. Commission and payroll

If the commission rate lives on the service, and the person is picked when the job is opened, then payroll is not calculated at month end — it has already accumulated. How many jobs each person did, what they earned and their average job value should simply be waiting. Staff seeing only their own earnings is the right default.

11. Offline work and sync across devices

This is the line that divides field software from office software. Intake, delivery and the till must run on the device itself and sync to the cloud when the connection returns. Browser-only systems stop when the line drops, and the queue goes back to paper that minute. Equally, a job opened on a phone should appear on the tablet and the computer within seconds, and no device should overwrite another's data.

12. Phone, web and TV — which do you actually need?

The phone is mandatory; the rest depends on the site. If there is a computer, a browser view gives you keyboard speed. If there is a waiting area, turning that television into a live queue screen answers “how long?” on the wall — and on that screen amounts must never appear, because no customer should read their own total next to a stranger.

Not a feature list but one flow: a car's journey through WashPro

Counting features one by one can mislead; the real difference is whether one step's output is used by the next without being typed again. Below is a car's path through WashPro. At each step we've marked what happens on its own and what waits for someone to tap.

1. DiscoveryAUTOMATIC
   A business with a saved location is listed on the Tanrikulu Apps map; it can be hidden from the map.
2. Booking requestCUSTOMER
   The customer picks plate, service and time on the map or in the app and sends a request without an account.
3. ApprovalMANUAL
   The request lands in the pending list; the business approves or declines. An approved booking opens as a job in one tap, already filled in.
4. Plate intakeAUTOMATIC CONFIRM MANUAL
   The plate is read by the phone camera, offline; the attendant confirms it. A returning plate brings the customer's details and history with it.
5. Staff assignmentDEFAULT
   The job goes to the active staff member on that device; it can be changed when opening.
6. Ready-time estimateAUTOMATIC
   Calculated from the real times measured per service over the last 45 days and the jobs ahead in the queue; without enough history it starts from the service duration.
7. Live tracking for the customerAUTOMATIC
   The job's QR code shows the queue position, status and estimated time on the customer's phone. Staff move the status forward; the page reflects it by itself.
8. Handover and stockHANDOVER MANUAL STOCK AUTOMATIC
   Staff hand the car over (with online payment, handover happens by itself when the payment lands); if consumables are linked to the service, stock drops at that moment and the “how many days left” forecast updates.
9. PaymentMETHOD MANUAL
   Cash, card, transfer, on account or online. With online, the customer gets a link and a QR code; the job is handed over automatically the moment the payment lands.
10. LoyaltyCOUNTER AUTOMATIC
    A paid handover moves the campaign counter; the customer sees progress on the same QR page (and the Wallet pass on iPhone). A free wash is suggested at handover; staff confirm using it.
11. Till, commission and reportsAUTOMATIC
    Payments go to the till by method, the job to the staff member's commission, consumables to the stock forecast; the owner gets an end-of-day summary in the evening.

The weakest links in a chain are usually the manual steps, so we haven't hidden them. What matters is that even a manual step never asks for the same information twice. Total cost, including what sits outside the subscription, is broken down in our car wash software pricing guide.

Not every wash is the same business

“Car wash software” describes three quite different operations, with genuinely different needs:

• A fixed site. Queue, capacity, waiting area and shifts drive everything. That is mostly what this page describes.
• Mobile washing and valeting. No premises; instead of a pin on the map there is a service area, and every job is tied to an address. Detail here: mobile car wash software.
• Detailing studios. Jobs run for hours, before-and-after photos are evidence, and vehicle history is the basis of the next quote. Detail here: auto detailing software.

One app can run all three, but weight your decision towards the points that match your own setup.

Six questions to ask before you choose

1. What happens when the internet drops?If the answer is “it stops”, it is not field software. Get the answer by turning the connection off and trying it, not from a salesperson.
2. Whose data is it?Is there an export (CSV/PDF), and can you take your history with you if you leave? Ask on day one, not on the last day.
3. What can staff see?Staff not seeing pricing, reports or somebody else's earnings is not a limitation — it is the correct default.
4. How hard is a second site?In many systems adding a branch later becomes a data migration. Ask even if you have one site today.
5. What makes the price go up?Per vehicle, per user, or flat? Know how the bill behaves in your busiest month before you sign.
6. How long is setup?Can the service list, vehicle classes and staff be set up in one evening, or is it a project? An operator has no time to run a project.