Feature grids are the worst way to pick car workshop software, because every vendor’s grid says yes. A far better test costs half an hour: take one job that actually rolled through your bay yesterday and try to enter it, end to end, into each shortlisted app until an invoice comes out.
Software that does not fit a workshop tends to break at the same handful of points. This article walks through six of them — what is reasonable to expect at each, and what you should ask a vendor to demonstrate live rather than promise.
What generic repair software gets wrong about cars
Most repair software is built around an object you can carry: a phone, a laptop, a small appliance. One serial number, one fault, one repair, collected.
A car breaks all three assumptions. Its identity is not one number but several — registration plate, VIN or chassis number, engine number, odometer, model year. A single visit usually contains several jobs at once: a service, plus brakes, plus air conditioning. And what leaves the workshop is labour and goods — oil, filters, pads — all of which must come off the shelf and land on the same invoice.
Software that has not planned for this will not stop you. It will simply make you type a plate and a mileage into a field labelled “Serial Number”, and from that day on your workshop history stops being searchable.
The one-job test
Pick a job that closed yesterday. Not a tidy example — a real one, with a vague customer complaint and parts that came half from your shelf and half from a panic run to the supplier. Enter it until the invoice prints.
The six points below are where that exercise usually stalls.
Point 1 — Vehicle identity: are the fields actually there?
Two white 2019 hatchbacks in the yard is not an unusual morning. What separates them is the plate, and once a car changes hands, the chassis number. Any credible car workshop software needs dedicated places for:
- registration plate — your everyday lookup key
- chassis number (VIN) and engine number — identity that survives a change of plate
- odometer — recorded at intake, so history has a reference point
- model year — the input behind a lot of parts decisions
In Automan these fields appear once you pick a vehicle Business Type, and the app’s own labels shift with it: Technician becomes Mechanic, Repair Item becomes Vehicle, Item Type becomes Vehicle Type. More on that on the auto repair shop page.
The test question is one sentence long: can you pull up that car’s service history by typing only its plate?
Point 2 — The customer’s words and the mechanic’s finding are two different things
“Noise when turning left” is a complaint. “Front left wheel bearing worn” is a finding. Give the software one text box and one of them disappears — usually the complaint, because the inspection result gets typed last.
You feel the loss three weeks later when the car returns with a similar noise. What you want to reread is the customer’s sentence, not the previous conclusion.
Automan’s seeded workshop catalogue keeps the two apart from the start, with complaint types already filled in — scheduled maintenance, engine, electrical, braking, suspension and steering, air conditioning — and sample symptoms such as “check engine light on” or “brakes feel weak”.
Point 3 — Estimates: what software can honestly do
The classic workshop sequence: the car comes in, gets partly stripped, only then does anyone know what is wrong, and only then does the owner get a phone call. The estimate is the bridge between “we don’t know yet” and “go ahead”.
Reasonable to expect: the estimated cost is recorded at intake and printed on the intake receipt, so the customer leaves with a number rather than a memory, and the gap between estimate and final cost can be compared afterwards.
Also reasonable to expect, and the part almost nobody tests: whether the job actually stops while it waits for an answer, or just carries a note while the work continues anyway. In Automan confirmation is a stage of its own — the job holds at Awaiting Confirmation until somebody decides, then moves to Confirmation Approved or Confirmation Rejected, with the outcome kept on the record. A car waiting on its owner does not sink to the bottom of the board.
What is worth being precise about — because this is the part most often oversold in a brochure — is who does the deciding. The phone call remains human work: your staff enter the outcome after reaching the owner. The customer can watch the status on the tracking page, but there is no approve button there for them to press. If a vendor claims the customer approves it themselves through a link, ask to see that live.
Point 4 — Labour and parts on one invoice
One maintenance visit might carry a scheduled service, a wheel alignment and balance, plus engine oil, an oil filter and an air filter. Three labour lines, three goods lines, one invoice.
Test two things at once: whether labour and products can live on the same document, and whether the parts consumed come off stock at that moment. If stock has to be adjusted by hand afterwards, drift is only a matter of time — the mechanics of that are covered separately in why parts stock drifts.
Point 5 — Handover: the things that came in with the car
A car arrives carrying property: registration papers, keys, a remote, a spare wheel, a jack, a tool kit, a warning triangle. Some of it stays, some goes home with the owner. Anything unrecorded becomes an argument at collection.
Serious software ships an accessories list and an intake condition checklist — body, glass and wipers, exterior lights, tyres and wheels, brakes, fuel level, odometer — that gets ticked at intake, not typed freehand by whoever happens to be at the counter.
Point 6 — After the car leaves
This is where software most often promises what it does not have. Three things are real and usable:
- an automatic follow-up a few days after collection, asking how the car is running — the most sensible route back to a returning customer;
- a reminder before the workmanship warranty expires, with built-in warranty options of 7 days, 14 days, 1 month and 3 months;
- a win-back message for customers who have not been back in a long time, triggered by how long since their last visit — not by mileage and not by a scheduled service date. Unglamorous, and the first thing a busy workshop stops doing by hand.
What does not exist, and what we will not claim: a next-service reminder based on mileage. The odometer is recorded, but nothing calculates “next service at 92,000 km” and no next-service date is stored anywhere. If a vendor offers this, ask to see it inside the product rather than on a slide.
If you only have time to check three things
| Priority | Question | Why this one first |
|---|---|---|
| 1 | Can you find history from the plate alone? | Without it, old data is dead weight |
| 2 | Labour + parts on one invoice, stock deducted live? | The single largest source of stock drift |
| 3 | Does the estimate print on the intake receipt? | The single largest source of price disputes |
Three yeses close most of the daily leaks in a workshop. Everything else can follow when you need it.
Four constraints to weigh before shortlisting Automan
We would rather you learn these now than in month two:
- Pricing is in Indonesian Rupiah — a free Lite tier and a Pro tier at Rp 15,000 per month. There is no separate USD price list; you convert. Details on the pricing page.
- Support runs in Indonesian, on Indonesian business hours.
- The seeded vehicle catalogue leans Southeast Asian — Toyota, Daihatsu, Honda, Suzuki, Mitsubishi, Nissan, Wuling, Hyundai. Every one of them can be deleted and replaced with your own, but the head start is smaller if you are outside that market.
- There is no offline mode. Automan needs a connection; there is no local queue that syncs later. For a workshop with unreliable connectivity, this is the first question, not the last.
None of those are dealbreakers for every shop, and all of them are cheaper to know up front. If the six test points matter more than the four constraints, start at the auto repair shop page or go straight to the demo.