POS for Car Washes in Kenya : Prices & Features

A POS for car washes in Kenya is built for a yard where a boda, a tuk tuk, a saloon, an SUV and a 14-seater matatu all arrive in the same hour, and each one pays a different price for a different mix of water and wax. Most car wash owners run the yard on a ruled exercise book: car in, price whispered, cash pocketed somewhere between the gate and the tap. The book only knows what was written, and the writing is optional.

This guide is written for owner-operators: the estate car wash with two wash bays, the highway yard with a detailing corner, the wash that serves a matatu sacco every night, the outfit with five washers on piece-work.

It covers the day-one tests, the monthly fees in KES, offline selling when power and network fail, driver accounts, fleet credit, loyalty, and the questions to ask before you pay any deposit. Keep one thing in mind as you read: every POS for car washes in Kenya looks flawless in a demo. The truth shows up on a Saturday morning when the queue reaches the road and every washer has a different story about who paid.

Read it with your own yard in mind. Tick the tests you would run, write down the fees you would accept, and ignore anything that sounds like it was designed for a supermarket shelf. By the end, you will know whether a POS for car washes in Kenya earns its place at your gate, or whether your exercise book deserves one more disciplined quarter.

Why a Retail Till Is Not a Car Wash Till

A retail till sells items that sit on a shelf until someone pays. A car wash sells a service performed on a moving, muddy object that arrives in fifteen shapes, and the price depends on both. A boda is KES 100, a saloon with an engine wash is KES 550, a matatu on the sacco account is a nightly promise. A till built for barcodes has no shape for any of that.

The deeper break is trust. In a shop, the item and the money meet at one counter. In a yard, the service happens twenty metres from where the money lands, performed by staff whose earnings depend on each car. A POS for car washes in Kenya has to tie every car to a ticket, every ticket to a washer, and every payment to a record, or the yard runs on rumour.

Then there is the quote problem. Without a system, the price lives in the washer’s head and moves with the customer’s face. The classic leak is not dramatic: a washer quotes KES 400, pockets 200, and reports a KES 200 wash. Multiplied by thirty cars a day, that “small discount” is a salary leaving the yard.

Costs behave differently too. A shop’s cost sits in the stock it bought. A wash’s cost sits in water, power, soap and labour per car, none of which a retail till has ever heard of. You cannot manage a cost per wash you cannot see.

Finally, the queue is the product. Cars line up at the gate, order matters, and Saturday morning is a traffic event. A POS for car washes in Kenya has to be fast at a gate, not at a checkout counter, and it has to survive water spray, sun and dust while doing it.

None of this means retail software is bad. It means it was tuned for shelves, and your business is measured in cars, crews and credit.

Who Should Buy a POS for car washes in Kenya

This category fits estate car washes, highway yards, wash-and-detailing outfits, night washes serving matatu saccos, and car washes with a small shop or waiting area attached. If vehicles arrive, get serviced by someone other than you, and pay at or after the gate, you are in the right place.

You benefit most if three things are true. You wash more than fifteen vehicles on a normal day. You have washers or a yard supervisor, which means handovers, commissions and trust questions exist. And you hold credit somewhere — matatu crews who pay Friday, taxi drivers on weekly accounts, or a company whose fleet washes monthly on invoice.

You should wait if you run a single-washer boda wash point with eight bikes a day, because a notebook will carry that honestly. You should also wait if your wash lane is owned and metered by a petrol station’s own head-office system, since your records have to live inside theirs.

Multi-yard owners are a special case. If you run the main yard plus a second site and learn about problems at month end, a POS for car washes in Kenya with per-yard records and one owner dashboard changes how you sleep. The same sacco should be one account across both gates, not two.

One honest warning before we continue. Software does not fix a yard where nobody records cars. If washers can still skip the ticket, the priciest system in the world becomes a very expensive receipt pad. Decide that every car gets a ticket, or save your money.

What a POS for car washes in Kenya Should Do on Day One

Do not accept a slideshow. Ask the vendor to load your real service list on a device in front of you and run five tests while you watch. Any hesitation, any “that comes in the advanced training”, and you have your answer.

Test 1: Ring a saloon wash with an engine wash and interior vacuum in one ticket, in under twenty seconds. Vehicle type, services, plate, washer. Four taps and a print. If the assistant hunts through menus, your Saturday queue will drown this system before lunch.

Test 2: Put a matatu on the sacco account. Wash the 14-seater, post it to “Nairobi sacco” on credit, and open the account to show the running balance with its age. If fleet credit cannot be tracked per vehicle and per account, your nightly sacco business stays a handshake with a monthly surprise.

Test 3: Punch a taxi driver’s ninth wash. The driver washes daily; the system should stamp the loyalty wash by phone number and show the free tenth wash waiting. Paper punch cards get lost, shared and forged, and your daily customers are exactly the ones who deserve the reward.

Test 4: Kill the network mid-queue. Switch off the router or flip the tablet to airplane mode and wash five cars. Tickets must continue, receipts must print, and you should see a visible queue of unsent records waiting to push. A frozen gate means the system was built for offices with fibre and standby generators.

Test 5: Run the three eTIMS actions. Issue one invoice with a buyer PIN, issue one credit note against it, then disconnect and send an invoice from the offline queue. If the vendor fumbles any of the three, compliance becomes your problem instead of theirs. Confirm your current eTIMS duties with KRA or your accountant before signing anything.

Bring your own price list and a real sacco name to the demo. Salespeople move fast on their own sample data, and their shortcuts hide exactly the corners your yard will fall into. If the system passes all five, book a second visit on a Saturday morning. Vendors send their sharpest staff to demos; your quiet Wednesday at noon tells you nothing about your loudest day.

How a POS for car washes in Kenya Survives Blackouts and Dead Networks

A blackout stops your pressure washers, but it does not have to stop your business. The yard keeps taking cars, the queue keeps forming, and the records of who owes what still matter. The system’s job during a blackout is to keep selling and keep counting while the pumps rest.

Insist on seeing the offline queue with your own eyes. Every ticket taken without network should sit in a visible list with a timestamp, waiting to push when signal returns. If the screen just spins, your records are resting on a hope.

Tickets must print offline too. A thermal printer connected by Bluetooth to the tablet keeps working through a blackout, and the paper slip is what you will count against cash when the lights return. Customers forgive a blackout; they do not forgive a car released with no receipt and a price argued from memory.

Morning matters here more than at most counters. Taxi drivers arrive at 5:30 a.m. before their shift, and the network is often still half-asleep with them. A POS for car washes in Kenya that sells and prints before sunrise without a signal keeps the pre-shift rush inside your yard instead of sending it next door.

Ask what happens when power dies mid-ticket. A half-taken order, a wet car and a watching queue is a normal yard moment. The system should resume cleanly, mark the interrupted ticket, and never charge twice when you retry it.

Power planning matters as much as network planning. A small UPS keeps the router alive through short cuts, a charged power bank carries a tablet through the day, and a solar panel suits yards far from a reliable meter. Ask the vendor what runtime their own car wash customers actually get on battery.

Make the drill a habit. On the first Monday of every month, pull the router mid-queue and let the yard sell through a full hour of blackout, not a polite minute. That rehearsed reflex is what keeps your gate moving while the yard next door writes numbers on a wheel spanner.

Finally, check recovery. When the network returns, the queue must send everything in order and mark each record clearly as delivered. Silent syncing breeds double tickets and missing money. You want to see it, not believe it.

M-Pesa, Cash and Fleet Credit at the Gate

Money arrives at a car wash through four doors: cash at the gate, M-Pesa, driver accounts paid weekly, and fleet accounts invoiced monthly. The system must keep those doors separate, because mixing them is how a busy yard stays broke.

At the gate, split payments must live on one ticket. A driver pays part cash and part M-Pesa for a full service; the system takes both on a single receipt without creating two phantom washes. STK push should match itself to the bill so nobody types reference codes while three cars wait.

Driver accounts are the daily credit reality. Uber and taxi drivers wash every morning and pay every Friday; the account should show their balance every time they arrive, age in buckets of current, 30, 60 and 90 days, and follow them to the gate. A POS for car washes in Kenya that puts the balance on the screen at check-in collects faster than any phone call you will ever make.

Fleet money deserves its own lane. The sacco whose five matatus wash nightly, the company whose vans wash monthly — each needs a ledger of its own, an invoice with a buyer PIN when compliance applies, and a collection date the system actually remembers. Crews that “pay Friday” every day of the week are a hole you tolerate by choice; the system at least shows you the size of the hole per account, per month.

Refunds need discipline, because a scratched car is an argument with money attached. Every refund should need your PIN, land back on the same M-Pesa number it came from, and sit in a logged record with a reason. Refunds paid in cash while the ticket stays on the books is how gates leak quietly for years.

End-of-day reconciliation becomes simple arithmetic. Cash counted, plus M-Pesa received, plus fleet collections, must equal what the screen says the yard earned. When the numbers disagree, the gap sits in one report with a timestamp instead of in an exercise book that disagrees louder.

Change float is the quiet killer at a gate selling KES 250 washes and collecting KES 5,000 fleet payments in the same hour. Track your opening float in the system and keep a fixed coin box, or the desk will round against itself before the Saturday wave arrives.

What a POS for car washes in Kenya Should Cost Every Month

Kenyan vendors price in three broad bands. Entry-level software runs KES 500 to KES 3,000 per month and covers one gate, basic services and daily sales. Mid-tier systems run KES 3,000 to KES 7,000 and add accounts, loyalty, commissions and richer reports. Platform-level tools run KES 7,000 to KES 15,000 and suit owners of several yards who need one dashboard.

Most single-yard owners should start in the entry band and upgrade when accounts and commissions demand it. Do not pay platform prices for features you will never open. The money saved in year one buys a spare tablet, a battery pack and a shade structure for the desk.

Hardware depends on your appetite. A full setup — terminal, receipt printer, cash drawer and a yard-proof second screen — lands between KES 60,000 and KES 120,000. A lean kit — a good tablet, a Bluetooth thermal printer and a small cash drawer — does the job for roughly KES 25,000 to KES 70,000, and most yards never need more.

Installation and training typically cost KES 30,000 to KES 40,000 for a full setup with a trained team, and a yard deserves most of that budget. Loading the service matrix, setting up fleet accounts and washer commissions, and training the gate and the yard is real work. A vendor who quotes half that and finishes in an afternoon will leave you half-trained.

Demand renewal prices in writing before you pay any deposit. The classic trap is a cheap first year followed by a renewal letter that doubles the fee. If the number is not printed in the contract, treat it as open until you sign.

Ask what “free updates” means in year two. Some vendors charge for every new feature, some bundle everything, and some quietly raise the monthly fee after a promotion ends. The honest ones will show you the renewal clause without being asked twice. A POS for car washes in Kenya that needs annual prepayment to show its true price is telling you something.

Weigh monthly against annual payment too. Paying a year upfront often unlocks a discount, but it hands the vendor your leverage. Monthly payments keep both sides honest while you learn the system’s real character.

One more question: what is not included? Reminder SMS, extra users, receipt rolls, holiday support and data recovery all attract separate charges at some vendors. A KES 2,500 plan that bills KES 500 per support call is not a KES 2,500 plan.

Services and Pricing: From a Quick Wash to a Full Detail

Your service list is the system’s engine, so build it the way your yard actually prices: vehicle type by service. Boda, tuk tuk, saloon, SUV, matatu, tipper down one side; wash, wax, engine, underbody, interior down the other. The crossing point is a price, and the matrix should live in the software, not in twelve heads.

Speed keys decide your Saturday. The top six orders — saloon wash, saloon full service, boda wash, matatu nightly wash — should each be one tap. At 9 a.m. your gate attendant is not browsing a menu; they are firing the orders the queue has already decided on. A POS for car washes in Kenya with clumsy service keys will cost you more in queue time than it charges in fees.

Combos deserve their own keys too. Wash plus wax plus vacuum is your highest-ticket moment, and a one-tap combo raises it measurably. Track combo sales as their own line so you know whether the pairing is actually working.

Every ticket should carry three things a book never holds together: the plate, the washer and the services. The plate settles arguments at the exit, the washer drives commissions, and the services drive your revenue mix. Three fields, entered once, feeding every report you will ever read.

Off-peak pricing is a lever retail never has. A Monday-to-Wednesday discount on full services flattens the Saturday crush and fills dead hours, and it should be a time-windowed rule in the system — visible, logged, and expiring on schedule — instead of a whisper at the gate.

Upsells belong on the ticket screen where the money is. Air fresheners, dashboard polish, tyre shine: small lines that lift the average ticket when they are offered systematically. If the offer lives only in the washer’s charm, only the charming shifts sell it.

Review the matrix quarterly. Water and power costs move, competition moves, and the pricing that carried last year may be feeding the leak this year. A POS for car washes in Kenya that reports revenue per service per vehicle type turns that review into evidence instead of memory.

Loyalty, Driver Accounts and the Morning Rush

A car wash lives on repeat customers. The taxi driver who washes every dawn, the sacco that washes nightly, the estate regular who arrives every Sunday — retention is the whole game, and loyalty is how you measure and feed it.

The standard structure works: every nine washes, the tenth is free. Phone-number lookup keeps it simple — no card, no stamp, no forging. A POS for car washes in Kenya with phone-number loyalty will show you exactly who your dailies are, by name, by wash count and by month.

Watch the repeat rate as a report. The share of customers on their fifth wash or more tells you whether the scheme is alive or decoration. If it never moves, the problem is the reward, not the software. Free engine washes convert better than free exterior washes, and only a report will tell you that.

Driver accounts are loyalty with money attached. The morning driver should arrive, be recognised, see his balance, wash, and leave — in under three minutes. When the account is visible at the gate, drivers stop “forgetting Friday” and start settling on sight, because the screen already knows what they owe.

The morning rush deserves its own workflow. Between 5:30 and 7:30, the yard sells speed: pre-shift express washes, tickets fired ahead of the cars. The system should have an express key, a queue order you can see, and a report on how the wave actually ran. A POS for car washes in Kenya that shows the rush hour by hour lets you staff it properly instead of staffing it by hope.

Saturdays need the same attention from the other side. The Friday-evening and Saturday-morning wave is a staffing question — how many washers on the line, who collects, who releases cars. The heatmap answers it from data.

If you sell drinks or snacks to the waiting customers, run them as a small retail line with stock counts. It is a genuine second income at a captive audience, but only if it is recorded like one.

Fleet Contracts, Saccos and Corporate Accounts

Three customer shapes behave nothing like the walk-in saloon, and each earns its own lane: matatu saccos, company fleets and institutional vehicles. A register book treats them all as strangers with cash. Your system should treat them as accounts with contracts.

Matatu saccos are the volume anchor. Five 14-seaters washing nightly, posted to one account, itemised per vehicle per night. The system should hold the sacco’s vehicles under one ledger, generate a weekly or monthly invoice, and age the balance in the same current, 30, 60 and 90 day buckets as everyone else. A POS for car washes in Kenya that itemises per matatu ends the monthly argument about who washed what when.

Contract rates live in the system, not in a negotiation at the gate. The sacco’s negotiated nightly rate, the corporate fleet’s monthly rate, the institution’s per-vehicle rate — each should apply automatically when the right account is selected. Manual rate memory is how one generous evening becomes a permanent discount.

Company fleets add a layer: which vehicle belongs to whom. Delivery vans, staff cars and pickups should carry plate-level records under the corporate account, so the invoice itemises cars and the manager can verify it against their own log. Headcount and fleet size change; the account should change with them without a phone call.

Institutional vehicles — county tippers, NGO vehicles, school buses — wash irregularly but pay formally. These are exactly the customers whose invoices need a buyer PIN when eTIMS applies, and whose payment cycles test your patience. The aging report is where that patience becomes policy.

Credit limits belong in the lane too. A 90-day balance should trigger a stop-wash flag at the gate, enforced by the system and not by whoever is on duty that evening. A POS for car washes in Kenya that waves through a deep account because the crew is friendly is donating your water.

Review this lane monthly. Fleet aging, sacco profitability, contract uptake — three numbers that tell you whether the volume business is growing or quietly bleeding. Fleets bring volume; only records bring the money.

Staff Permissions, Drawer Discipline and Audit Trails

A car wash runs on washers, a gate attendant and a yard supervisor, and the money lands at the gate while the work happens twenty metres away. That distance is the whole security problem, and the audit trail is your only neutral witness.

Set roles cleanly. The gate sells and takes payment, the yard supervisor records or verifies cars, and washers see their own counts and commissions. The gate cannot void, discount or edit prices without your PIN. Every override should be logged with a time and a name.

The washer quote is the classic leak, so close it structurally. Every car gets a ticket at entry with plate, washer and services; every exit matches a ticket. When tickets and cars reconcile daily, the KES 200 ghost wash dies of visibility. A POS for car washes in Kenya that ties cars to washers replaces suspicion with a number, and numbers are easier to discuss than accusations.

Washer commissions should live in the same records. If washers earn per car or per service, the system computes the commission from the tickets — no notebook, no negotiation, no “I washed more than the book shows”. Payday becomes a report the washers can audit themselves.

One drawer, one name, one shift. The count at handover should match the screen within seconds, and any difference should sit in a recorded line, not in a shrug. Yards with two collection points — gate and office — need two named drawers, not one shared tin.

Free washes need their own lane. The owner’s car, the staff vehicles, the landlord’s Prado — every free wash should be recorded as a staff line with a name. An honest log turns staff washes from a leak into a benefit you chose to carry, and teams behave better when the log is visible.

When the trail surfaces something, have the conversation early, calmly, with the log on the table. Owners who ignore a first small discrepancy teach the yard that records are decoration. The second discrepancy is always bigger. Frame the rules as protection, not policing: a clear permission wall means the honest washer is never blamed for a difference he did not cause.

Reports a Car Wash Owner Should Actually Read

Buy a system whose reports you will read in fifteen minutes a day, not one that exports forty spreadsheets nobody opens. Six lines carry almost all the value in a yard.

The first is money against tickets. Cash counted, plus M-Pesa received, plus fleet collections, must equal what the screen says the yard earned. When those disagree, the gap has a name and a timestamp, and that is the entire argument for a POS for car washes in Kenya over an exercise book.

The second is revenue per service and per vehicle type. Which mix actually feeds you — engine washes on SUVs, nightly matatu washes, full services on saloons — and which line just wets the yard. This is the report that decides your next price review.

The third is washer productivity. Cars washed, services delivered, commissions earned, per washer, per shift. A POS for car washes in Kenya that reports productivity per name turns staffing on the Saturday wave into arithmetic instead of guesswork.

The fourth is fleet aging. Each sacco, company and driver account, with its balance in current, 30, 60 and 90 day buckets, plus profitability per account. The volume customer who eats you in credit should be visible before the debt matures, not at Christmas.

The fifth is the peak heatmap. Cars by hour, day by day. Staffing the gate, scheduling the detail bay and setting off-peak discounts all fall out of this one view.

The sixth is the repeat rate. New customers versus returning customers, loyalty punch counts, lapsed dailies who stopped coming. The yard’s future walks in every morning; this report is how you see it before it parks across the road.

Set a rhythm and keep it. Fifteen minutes after close for the daily lines, thirty minutes on Sunday for the week, one hour at month end for mix, commissions and credit. Reports only earn their fees when they change tomorrow’s yard.

Hardware That Survives a Car Wash Yard

A car wash is the most hostile electronics environment in this entire series of guides. Water spray, soap mist, equatorial sun, dust from the compound, and hands that arrive wet from a pressure hose. Hardware choices decide whether this system lasts three years or three months.

The lean kit works: one good tablet as the gate till, one Bluetooth thermal printer, one small cash drawer, and a battery pack. Put the desk in a sheltered booth, out of spray line and out of the afternoon sun, and put the printer in a drawer, not on the counter. A POS for car washes in Kenya running on a well-placed tablet outlives a badly placed terminal.

Screens need tempered glass and a wipe-down routine. Wet fingers and dust make touchscreens lie about taps, and a screen that misreads a service turns into a queue argument. Wipe it at every shift change with the same cloth discipline as the yard’s tools.

If your yard has a second point — an office where fleets pay, or an exit where cars are released — a second device earns its place. Ticket at entry, payment at exit, both feeding one system. Two points that talk to each other end the “he paid at the other window” genre of argument permanently.

Buy spares before you need them: a second tablet with the software installed, a second printer, a month of receipt rolls, and a charging cable that lives at the yard. The day your only device fails is the day the gate goes back to the exercise book and the leaks come home.

Power protection is cheap insurance. A small UPS keeps the router alive through short cuts, a power bank carries a tablet through the day, and a solar panel suits yards far from a reliable meter. Ask the vendor which accessories their car wash customers actually buy twice.

Decide the night routine: wipe, charge, lock or carry home. Carrying the till home is the cheapest security system ever invented, but it needs a battery that lasts the evening and a case that survives a rucksack. A POS for car washes in Kenya that survives the routine is worth any small feature you gave up for it.

eTIMS and KRA Compliance From a Car Wash

eTIMS is KRA’s electronic tax invoice system, and in plain terms it means the invoices your business issues can flow to KRA electronically. The details depend on your registration status and turnover, and they change, so treat this section as a software checklist and confirm your actual duties with KRA, your accountant or your county office.

The three live demonstrations still apply. Ask the vendor to issue an invoice with a buyer PIN, issue a credit note against it, and send an invoice from the offline queue while disconnected. A system that cannot do all three in front of you is guessing.

Fleets are where compliance gets real. The monthly invoice to a sacco or a company is a business-to-business sale that needs a buyer PIN, and a contract adjustment needs a credit note against it. Test both against your real fleet list, not with a sample customer. A POS for car washes in Kenya that handles buyer PIN invoices automatically keeps compliance out of your month end.

Receipts for every walk-in build the habit that protects you when obligations change. The habit costs nothing when a receipt takes four seconds, and a system that prints compliant receipts by default makes the habit automatic.

Keep the records the system produces: daily Z-reads, void logs, credit notes, fleet ledgers and the offline queue history. When a question arrives from KRA two years later, you answer from a file instead of from memory.

Your county papers sit in the same drawer. The single business permit keeps the yard legal, and water-related requirements — borehole or county water connections — carry their own rules in some counties. Confirm the exact list with your accountant or the county office, because requirements differ from town to town.

Turnover tax sits alongside eTIMS in the same conversation. Ask your accountant to read your first month of system reports. Clean numbers usually reveal deductions you were missing.

Installation, Training and Support You Can Verify

Installation should happen on a normal trading day, not a Sunday when the yard is closed. Watching the vendor load your real service matrix, your real sacco accounts and your real washer names tells you more than any brochure.

Pick the go-live week carefully. Avoid the month-end fleet collections, avoid December, avoid the week the saccos change crews. You want your calmest trading week for the first run, because the gate will be slower than the book for three or four days.

Opening records decide whether the first week is truth or fiction. Every active driver account, its balance, and every fleet account’s standing must enter the system before the first wash, or the first week of aging is a novel. A POS for car washes in Kenya that walks you through opening balances properly starts earning its fee on day one.

Training must include the gate, the yard supervisor and the washers, not just you. If the washers are not trained to ticket every car, the system measures only what the gate sees. Ask for a second free session a week after go-live, when the real confusion shows up.

Run the exercise book in parallel for one full week. Every car and every shilling in both. On day seven, compare totals. This week costs you discipline and saves you from discovering a pricing mistake in month three.

Test support at your real hours. Call the support line at 6 a.m. as the pre-shift taxis arrive, and again at 10 a.m. on a Saturday, with a small question, and time the answer. Support that only answers weekdays between 9 and 5 does not understand car washes.

Call two reference customers who run yards, not shops. Ask them one question: “What went wrong in the first month, and how fast was it fixed?” Their pause before answering is part of the reference.

Agree in writing who does what when something breaks: response time, swap-out time for failed hardware, and who pays the courier. Written promises survive the honeymoon; verbal ones do not.

Questions to Ask Before You Pay Any Deposit

Walk into every vendor meeting with this list and tick answers in front of the salesperson. Vague answers are answers.

1. Show me a car wash — not a shop — using this system today. Reason: per-vehicle service pricing and yard trust break retail tills.
2. Ring a saloon wash with an engine wash in one ticket, in under twenty seconds, live. Reason: the Saturday queue is the whole business.
3. Post a matatu wash to a sacco account and show the aging balance. Reason: fleet credit is where your volume lives.
4. Punch a loyalty wash and show the free-wash trigger. Reason: your dailies deserve a reward that cannot be forged.
5. What exactly happens at the gate when power and network die together? Reason: this is your normal Tuesday, not a disaster story.
6. What is the full monthly cost including reminder SMS, extra users and updates? Reason: the advertised price is rarely the paid price.
7. Are renewal prices written into the contract? Reason: year-two surprises are the most common complaint in this market.
8. Can the gate’s login be blocked from voids and discounts, and can I see every override? Reason: your audit trail is only as strong as your permissions.
9. Demo the three eTIMS actions live, offline included. Reason: compliance failures land on your desk, not the vendor’s.
10. Can I export all my data if I leave, and in what format? Reason: your customer and fleet lists are the asset; do not rent them forever.

Ask each vendor to answer all ten in one sitting. Vendors who score ten clean answers exist — keep shopping until you find one.

FAQ: Buying a POS for car washes in Kenya

How much does a POS for car washes in Kenya cost in 2026?

Entry-level software runs KES 500 to KES 3,000 per month for one gate, mid-tier runs KES 3,000 to KES 7,000 with accounts, loyalty and commissions, and platform-level tools for multi-yard owners run KES 7,000 to KES 15,000. A lean hardware kit of tablet, printer and drawer adds roughly KES 25,000 to KES 70,000 once, while setup with training typically lands in the KES 30,000 to KES 40,000 range. Get the renewal price in writing before any deposit.

Can it track washer commissions automatically?

Yes, if every ticket carries the washer’s name and the system computes commissions from tickets rather than from a notebook. Ask to see the commission report in the demo, worked from the same tickets that produced the day’s sales — one source, no negotiation at payday.

Will it work during a blackout or when the network dies?

The system must, even though your pumps cannot. Tickets continue, receipts print over Bluetooth, and a visible queue pushes to the server when signal returns. Test it live in the demo by pulling the router mid-queue, because a gate that freezes without internet was built for offices with fibre and standby generators.

Can it run driver and sacco accounts properly?

It should hold each driver and each fleet under its own ledger, show the balance at the gate, age it in current, 30, 60 and 90 day buckets, and generate itemised invoices for fleets. Test it with a real account name and a real balance in the demo, not with sample data.

Do I need a barcode scanner or special equipment?

No. A car wash runs on speed keys, plate entry and your service matrix — no barcodes anywhere in the yard. Spend the budget on a second device for the office or exit point instead, if your yard has one, and on a sheltered, powered spot for the gate tablet.

Do I need eTIMS if my car wash is not VAT registered?

Your obligations depend on registration status and turnover, and they change, so confirm your situation with KRA or your accountant. What you can check today is the software’s ability: buyer PIN invoices for your fleet customers, credit notes and offline queue sending, all demonstrated live.

Can I run two yards from one account?

Platform-level plans around KES 7,000 to KES 15,000 per month typically cover multiple yards with shared accounts, per-yard takings and one owner dashboard. If you currently learn about problems at month end, a second window on your phone showing both gates live is worth the upgrade on its own.