Software that inspects the bays, services the equipment, and closes the claim.

Car wash software is the system a fixed site wash uses to run the site in one place instead of paper and memory. It covers bay and equipment inspections, preventive maintenance, which means the regular servicing that stops a machine breaking down, daily opening and closing checklists, damage claims, staff schedules, and the membership records behind unlimited wash plans.

They do different jobs, and most washes need both running side by side. The point of sale takes payment, sells memberships, and works the lane. Operations software covers what happens between transactions: did the opening checklist get done, when was the vacuum last serviced, who owns the torn brush, and where does this damage claim stand. WashUp, one operations product we checked while writing this page, states plainly that it does not connect to the point of sale or the tunnel controller and runs alongside them. Buying one when your problem is the other is the common mistake.

The crew walks a set round and rates each item against written standards you set: brushes, wraps, pumps, vacuums, dryers, and the bay itself. Anything that fails becomes a tracked job with a photo, a priority, and a named owner, instead of a comment passed to whoever is nearby. For equipment with a gauge, the round records a reading, such as pressure on a pump, and the reading itself decides whether the item passes. The owner sees every open item at every site without driving to the lot.

On wash counts where the equipment allows it, and on dates where it does not. A conveyor or blower at a site washing hundreds of cars a day wears faster than the same machine at a quiet site, so a calendar alone services one too late and the other too early. The schedule should remind the team before the work falls due, turn clearly overdue when it is missed, and keep the completed work in that machine's history, so the third failure of the same part is visible as the third failure.

While the customer is still on the lot, on a structured form, not on paper in a folder. The form captures the vehicle, using a scan of the vehicle identification number where that helps, the damage area and how serious it looks, photos or video, and the customer's signature on the spot. The claim then moves through one visible path, under review, in progress, resolved, or denied, and the customer can follow it from a link instead of calling the site. A claim closed in days with a full record is a retention tool; a claim nobody calls back about is a cancellation waiting to happen.

Watch two signals. First, failed payments: retry the card, tell the member at once, and recover the payment before the plan lapses, because many lapses are an expired card, not a decision to leave. Second, visits: a member who has not washed in several weeks has usually decided to cancel before they do it, so a rebooking nudge, one message plus a small incentive, lands while there is still something to save. WashUp's own site puts average industry churn at 7.6 percent, citing the Rinsed 2026 Q1 Report, which is why the visit and payment signals are worth a system, not a monthly glance.

Define one authoritative record for the member, the vehicle, the plan, what the plan allows, the billing status, and any site override, pause, cancellation, and renewal. Each visit is checked against that record and keeps the plan version used. Sites that lose their connection follow a capped policy, meaning a set limit on offline visits, while duplicates, transfers, chargebacks, and disputed visits go to a staff review path instead of being decided at the lane.

Only when the controller, pay station, plate reader, point of sale, or vendor exposes a documented and permitted way to connect. We confirm the connection method, the access details, the commands it accepts, the safety states, and any warranty or vendor limits before committing to it, and we test what happens when the equipment fails to respond. An unavailable or restricted connection can change what the first release should include.

Treat vendor accuracy claims as claims. A plate read should look up the member and vehicle, and any reading the system is unsure about should go to authorised staff review, with the reason, the evidence, and a record of the decision. Entry must keep working when the connection drops, with a fallback the member can use, such as a code or a staff override. One change of plate vendor must not corrupt the membership record underneath.

As a separate shape of account: one company, a list of its vehicles and plates, and a single invoice, distinct from retail memberships. The fleet record needs its own rules for adding and removing vehicles, visit limits, and billing terms. Mixing fleet vehicles into household memberships is how disputed visits and wrong invoices start.

Operations products are usually priced per location per month. WashUp, the operations platform we checked first-hand while writing this page, is listed on its GetApp page at $109 per location per month for every feature with unlimited users, with single features from $15 per location, the first 14 days free, and no setup fees; confirm current pricing on the vendor site before you budget, because the listing is a directory page and prices change. Point of sale and membership platforms price differently, often per site after a demo, so price every system for every location you run.

First phases start at $10000 for a bounded audit, proof of concept, or small first release. A full first release is a larger engagement: our build vs buy guide for car wash operators puts a first release covering plate recognition access, unlimited memberships, and a single-location point of sale at $100K to $180K over 12 to 16 weeks, and a full platform adding multi-location reporting, fleet billing, and a member app at $220K to $380K. Those bands cover the membership and lane side; an operations-first release scoped around inspections, maintenance, and claims is shaped on the call. Read the full breakdown in our guide to building car wash management software.

Buy a product when your sites run the standard routine and the product already covers it: inspections, servicing reminders, checklists, and claims are well served by maintained operations products. Own custom software when the product keeps forcing workarounds: your membership and lane records must reconcile with the operations record in one view, you run several sites or vendors whose records never match, your claim or inspection routine has steps no product allows, or you are bringing acquired washes onto one stack. If the rules of the operation are still changing every week, wait and settle them first.

It should be designed to. A crew member who cannot log an inspection or a fault where the signal is weak will go back to paper within a week. The app should store the round, the photos, and the readings on the device and send them when the signal returns, with a clear state for what is saved, what is waiting, and what failed. That behaviour has to be in the first release, not added later.

You judge what you can see, not the code. Every checkpoint is working software you click through yourself, tested against the workflow agreed at the start. Walk a morning inspection on a real phone. Close a test claim. Progress is reported in plain language: what changed, what's next, and what it costs. Because you own the code, the accounts, and the operating notes throughout, nothing about the work is locked inside our heads. Our job is to make the work checkable; your job is to check it against your business.

You own the code built for you and control where it lives, the cloud accounts, the data, analytics, and third-party subscriptions. Outside services and open-source pieces keep their own licence terms. The operating notes and handover material stay current so another capable team can take over.

We need one person who owns the workflow, access to the relevant users and systems, timely answers on business rules, and someone who can accept or reject each milestone. A weekly working session is usually enough once the scope is stable. Your team should not have to manage developers day to day. The team that scopes your project is the team that does the work: no handoff to another vendor after you sign, and you can talk to the people doing the work directly.