Odoo for Car Wash
Odoo rollouts for car wash and detailing operators
Single sites, forecourt washes and detailing chains. Bay allocation, monthly wash plans, staff commission, and fleet accounts billed from real jobs.
A car wash is a queue with a price list attached. Everything that goes wrong is a sequencing or an evidence problem: which bay takes the next car, whether the plan in the glovebox is still valid, who did the work, and what the vehicle looked like before it went in. An Odoo rollout here starts on the forecourt with the job and the payment, then adds plans, accounts and commission once the job record is reliable.
Where it hurts today
Bays are allocated by whoever shouts loudest
At peak nobody knows which bay frees up next or how long the job in it takes. Cars are washed out of order, the customer who booked waits behind a walk-in, and the site looks busier than it is earning.
The monthly plan lives in the glovebox
Unlimited and multi-wash plans are sold on a card with no way to check validity at the entrance. Staff wave people through rather than argue, so the plan gets used past expiry and shared between vehicles.
Damage claims have no before record
A scratch is reported after collection and nothing captured at arrival can prove it was already there. The site pays out or loses the customer, and the same argument recurs a few times a month.
Commission is rebuilt from a notebook
Who washed which car, and which extras were upsold, is reconstructed on a Sunday night. Payroll is late, staff dispute the figures, and the incentive stops driving behaviour because nobody trusts it.
Fleet accounts pay against a pile of job slips
Taxi firms, dealerships and corporate fleets settle monthly. The invoice is typed from slips, the customer queries half of it, and the discount that was agreed verbally reappears in every negotiation.
The modules that carry the load
Each one is here for a reason specific to car wash, not because it appears on a standard module list.
- ๐งพ Odoo POS (Point of Sale)
Payment at the desk or on the forecourt, with the service, the vehicle and the operator captured on the same ticket instead of on a slip.
- ๐ Odoo Appointments
Booked slots against bay capacity and real service durations, so the queue is planned rather than negotiated at the entrance.
- ๐ Odoo Subscriptions
Monthly and unlimited wash plans that renew, expire and can be validated on arrival instead of taken on trust.
- ๐ Odoo Sales
Fleet and dealership accounts with agreed rates and terms, quoted once and applied to every job that account brings in.
- ๐ฆ Odoo Inventory
Chemicals, foam, wax and consumables drawn against wash volume, which is the only way to see cost per wash rather than a monthly chemicals bill.
- ๐ผ Odoo Accounting
Daily takings, plan billing and monthly account invoicing landing in one ledger, with the job detail still attached when a customer queries a line.
- ๐ Odoo Attendance
Shifts and hours per operator, which is the base the commission rules are calculated against instead of a notebook.
How the rollout runs
- 1 The forecourt
Service menu with a realistic duration per service, bays, operators, the payment flow and the receipt. Traded live for a week including a weekend peak, because a car wash system that slows the entrance will be abandoned by Saturday.
- 2 Plans and accounts
Wash plans with terms and renewal, validation at arrival, then fleet and dealership accounts with their rates. Existing plan holders are migrated with true expiry dates, which is usually the first time the site learns how many are running past them.
- 3 Staff, consumables and commission
Operator assignment per job, commission rules written down and calculated from job data, and chemical usage against wash volume. Run one month in parallel with the notebook before anyone is paid from the system.
- 4 Booking and reporting
Online booking, reminders, and reporting on revenue per bay, per service and per hour of the day. This is what tells the operator whether to add a bay or reprice the peak.
What to have ready before kickoff
Projects that slip usually slip here, not in the build. Bring these to the first workshop.
- โ The service menu with the time each service actually takes in a bay, measured rather than estimated.
- โ Plan terms as sold: price, duration, what counts as unlimited, and whether the plan is tied to one vehicle.
- โ A list of current plan holders with expiry dates, including the ones you suspect have run out.
- โ Fleet and dealership accounts with the rates agreed and who signed off on them.
- โ Commission rules in writing: per wash, per upsell, or a percentage, and what happens when two operators share a job.
- โ Hardware per lane: terminal, receipt printer, and whether the site takes card at the bay or only at the desk.
Where it connects
Systems we most often connect on car wash projects. The full list is on the integrations page.
Car Wash & Detailing
For the feature view of bookings, wash packages, bay allocation and staff commission, read the solution page.
Open the Car Wash & Detailing solutionQuestions we get asked
Can monthly wash plans be checked at the entrance? +
Yes. A plan is held against the customer and the vehicle, so scanning or searching the plate at arrival shows whether it is live, expired or already used today, and what the plan includes. That single check is usually what pays for the project on a busy site.
How is staff commission calculated? +
From the job record: which operator was assigned, what service was sold, and which extras were added. Rules can pay per wash, per upsell or as a percentage, and a shared job can be split. Because it comes from the same data as the invoice, the figure is arguable in one direction only.
Can we capture vehicle condition before the wash? +
Yes. Photos and noted damage are attached to the job at arrival, against the plate. It takes seconds at the entrance and it ends the claim argument, which for most sites is the difference between paying out and not.
We wash for taxi fleets and a dealership on account. How does that bill? +
The account carries its rates, jobs accumulate against it during the month, and one invoice is raised with the vehicle, date and service behind every line. Queries are answered from the job, not from a slip somebody has to find in a drawer.
How long does a single-site rollout take? +
A single site typically runs in a 4 to 8 week band. Multi-site operators add roughly a week per site for hardware and training, since the second site copies the configuration of the first rather than repeating the design work.