Mobile car wash software: route planning and scheduling for a business with no address

Mobile washing does not get two things for free that a fixed site solves by existing: where the customer finds you, and where the job was done. There is no sign, no address, no waiting area. Software written for a fixed site never even asks those questions — which is why most mobile operators end up using half of the app they bought.

This page is about what mobile work specifically needs: a service area instead of a pin, a job record tied to an address, customers who arrive by booking, and a till that works in the field. The same applies if you run mobile detailing rather than a quick wash — mobile detailing software has to answer the same two questions, and only the length of the job changes. For the general mechanics that any wash shares, see car wash management software; what follows sits on top of that.

On a map, a mobile business is not a pin

A fixed wash is a point: the customer drives to it. A mobile business is a service area: you drive to the customer. That difference has to be built into the foundation of the software, not bolted on later as an extra field.

The setup that works in practice looks like this: you set the business type to mobile, a setup sheet opens, you pick the province from a list and tick the districts as chips. Leave the districts empty and you are treated as covering the whole province. The app proposes a starting point from your location and you correct it. The result is that a customer on the map sees the mobile washers who serve their own location — and you never need an address of your own.

Every job carries an address

At a fixed site “where is the car?” is not a question; the car is there. In mobile work it is a field the record has to hold. In properly built mobile car wash software the address of the vehicle goes onto the job — and it is not just a note:

• The day is planned around addresses, and the distance between two jobs becomes visible.
• The ready message changes: the car is already next to the customer, so nobody is asked to come and collect it.
• When you return to the same address, the earlier record means something — the residential car park, the office garage, the covered bay.

Bookings are the channel, not a feature

A fixed wash gets passing trade. A mobile business has none; the work arrives by appointment. That makes the booking flow the channel itself rather than an add-on.

A flow that works has these steps: the customer sees the washers covering their location, picks a time slot and sends a request with their plate; you get a notification; you confirm or decline; the customer learns the outcome immediately and follows the booking on their own phone. The question worth asking here is about abuse protection: if requests from the same plate or the same phone number are not rate-limited, it is only a matter of time before the board fills with noise.

Route planning: a day is not a queue, it is a route

On a fixed site the day is a queue: cars arrive and go in one after another. In mobile work the drive sits between two jobs — and driving is production time too. The difference between two stops next to each other and two stops twenty minutes apart is one job more, or one job less, by the end of the day. So the day plan in mobile car wash software should not be a list of times but a schedule: arrival time, departure time, and the drive minutes and kilometres of each leg.

The software cannot set the order on its own, because a time given to a customer is a promise. The honest behaviour is to show both: the plan built from the promises, and the shorter suggested order built from drive times. The suggestion states how many minutes it saves and marks, stop by stop, which appointment you would be late to and by how much. The operator decides — “I save twenty-five minutes but I am ten minutes late to that customer” is a decision made knowingly. Route optimisation should ask, not apply itself.

Mobile detailing makes this sharper. A full valet or a machine polish can take two or three hours, so the length of each job moves the whole day far more than the drive does. Scheduling only works if job durations come from your own past work rather than a fixed guess — then the arrival time you promise the third customer of the day is one you can actually keep.

That is why being able to correct the plan by hand is not a comfort but the job itself:

• Drag to reorder — and the order you set survives closing and reopening the app. An order kept only in memory is gone the next morning.
• Pin a stop's time — arrive early and you wait until that time; the stops below it are recalculated.
• Add a break — lunch, fuel, your own errand. It takes up the day, the customer never sees it, and nobody drives anywhere.
• Choose where and when you set off — from the business, or from wherever you are.
• Override the job and the drive time — bridge closed, school run, that road stops at this hour. The estimate is a starting point, not the last word.

When the plan is approved the jobs land on the board in that order and each appointment's estimated arrival is recorded. Customers without the app you still tell yourself; the software says how many people you need to message, it does not do it for you. An appointment with no location does not enter the plan at all — that is honesty rather than a gap: you cannot compute a drive time to a place you do not know.

There is not always a signal in the field

This is the technical reality mobile work meets most often: underground car parks, basements, industrial estates with no coverage. If intake, delivery and the till do not run on the device itself, the day stops there. The correct behaviour is that the record is created on the phone and syncs to the cloud when the connection returns. If you work with a crew, the same rule covers them: jobs opened on two phones have to merge without one overwriting the other.

The money is taken in the field

In mobile work the point of collection is not a till — it is the side of the car. Three things follow from that:

• Cash or card is chosen at delivery. One tap while the money changes hands, instead of trying to remember in the evening.
• Credit work stays out of the till. A corporate customer gets an account: the job is booked as debt and enters the till on the day the money actually arrives. Otherwise the day's number always reads high.
• Expenses go in the same day. Fuel and consumables are a mobile operator's largest cost; totted up at month end they tell you nothing about a given day.

Crew and commission

Starting alone and growing to two or three teams is common in mobile washing. The software should be ready for it: staff join the same business by invite, every record shows who opened it and who delivered it, and the commission rate is set per staff member. How many teams work at once should be part of the business setup, because capacity is calculated from that number.

Keep the door to a fixed site open

Plenty of businesses start mobile and later take premises. Ask this before you choose: when you switch the business type to fixed, do customers, pricing, credit accounts and past jobs stay where they are? If they do not, growing turns into a data migration project.

A short checklist

1. Can you publish a service area?At province and district level, without being forced into a single address.
2. Does every job carry an address?As a field of the record, not as a free-text note.
3. Are booking requests rate-limited?The same plate or phone should not be able to flood you.
4. Does the day plan account for drive time?A schedule rather than a list of times: arrival, departure, minutes and kilometres.
5. Does the customer learn you are on the way?Without you texting each one, and with an arrival time rather than just “soon”.
6. Does it work with no connection?Do not take anyone's word for it: put the phone in flight mode, open a job and deliver it.
7. Does data survive a switch to a fixed site?If you plan to grow, ask today rather than later.