An independent traffic record
Build a consistent view of gate activity alongside manual service records. Automated counting needs site-specific validation.
CRAFTDUKA SMART CAR WASH
Know how many vehicles visit your car wash, understand your busiest hours, and get business activity reports delivered to WhatsApp.
Open for pilot/demo enquiries. Automated counting and reports are in development/testing.
Our product ambition. Current scope: camera-to-WhatsApp proof of concept; vehicle counting under development.
THE VISIBILITY GAP
When you are away from the site, a closing total rarely tells the whole story. Manual reports may miss arrival patterns, busy periods and interruptions in coverage.
An independent traffic record can help you ask better questions: When do vehicles arrive? Which hours deserve closer attention? Are service records and traffic being compared fairly?
Vehicle movements are not paid washes. Visitors, suppliers, quotations and return crossings all matter. Revenue comparisons need supporting POS or transaction records.
HOW IT WORKS
The intended workflow. Image delivery is demonstrated; tracking, persistent counting and automated reports are being developed or tested.
A suitable entrance view observes the access route. Camera and stream compatibility are assessed first.
The intended system follows vehicle movement and checks direction across a configured boundary.
Time-stamped crossing events would build an activity history, with coverage gaps made visible.
The reporting goal: concise activity summaries and authorised requests without watching hours of footage.
EXPLORE THE REPORTING CONCEPT
Switch the sample day or chart direction. Every number below is demo data, illustrating the planned experience.
| Hour (EAT) | Entries | Exits |
|---|---|---|
| 8:00 | 2 | 1 |
| 9:00 | 4 | 3 |
| 10:00 | 7 | 6 |
| 11:00 | 9 | 8 |
| 12:00 | 6 | 6 |
| 13:00 | 4 | 5 |
| 14:00 | 8 | 7 |
| 15:00 | 11 | 9 |
| 16:00 | 7 | 8 |
| 17:00 | 4 | 5 |
How was activity at the gate?
Sample report · Sample day A
62 entries · 58 exits
Peak entry hour: 15:00–16:00 EAT
These are vehicle movements, not completed washes or revenue. Sample coverage: 08:00–18:00 only.
All figures are invented sample data. This dashboard and automated reporting are product concepts under development, with no live camera connection or client results.
BUILT AROUND OWNER QUESTIONS
Build a consistent view of gate activity alongside manual service records. Automated counting needs site-specific validation.
Camera image delivery is demonstrated in the proof of concept. Remote count summaries are the next reporting goal.
Use validated arrival patterns to investigate queues and plan staffing. Traffic alone does not reveal service demand.
Proposed event storage would support comparisons across equivalent periods, with outages and rule changes identified.
Compare traffic with completed services and transactions. Review visitors, returns and timing before drawing conclusions.
Multi-location views are on the roadmap. A first pilot should establish reliable rules and useful reports at one site.
WHERE IT COULD FIT
A scoped pilot starts with your layout, existing equipment and operational question. Sites in Kenya and East Africa have different access and connectivity needs.
Understand arrival patterns while the owner is away.
Establish consistent counting rules before a future branch view.
Separate wash access from general forecourt traffic.
Account for appointments, repeat visits and long service stays.
Compare movements with job and account records over agreed periods.
RECORDING + OPERATIONAL CONTEXT
Traditional CCTV remains useful. AI adds a layer of analysis, subject to compatible access, camera conditions and accuracy validation.
| Capability | Traditional CCTV | Smart monitoring |
|---|---|---|
| Daily review | Review recorded footage to understand activity. | Proposed event summaries reduce repeated manual counting after validation. |
| Vehicle counts | Manual counting, unless suitable recorder analytics are already available. | Direction-aware counting with rules for repeat crossings and reversals. |
| Business records | Visual context within the available footage. | Time-stamped movement records; service and payment data remain separate. |
| Accuracy and outages | Depends on the view, recording quality, power and retention. | Also depends on detection, tracking and counting rules; gaps must be reported. |
| Remote reporting | Depends on the camera or recorder’s remote features. | Camera-to-WhatsApp images demonstrated; automated count reports in development. |
A TRANSPARENT DEVELOPMENT PATH
A V380 camera connects to Hermes Agent and camera images are sent through WhatsApp. This establishes an early image delivery path.
It does not validate automated counting, every camera brand or commercial deployment readiness.
Vehicle entry/exit logic, persistent event records, historical views and automated count summaries require further development and site-specific validation.
POS reconciliation and multi-location analysis are future directions. Feature availability, pilot scope and costs will be agreed individually, with no published launch dates.
Possibly. We need the exact camera and recorder model, available stream access and a sample view of the entrance. The proof of concept used a V380 camera; that does not establish compatibility with every V380 model or other brands. We assess access, image quality and positioning before recommending reuse or replacement.
WhatsApp delivery and remote access need a working internet connection. Local processing and buffered event storage are possible deployment approaches, but their availability and recovery behaviour must be agreed and tested during a pilot. A connection outage must appear as missing coverage, rather than zero vehicles.
That depends on entrance and exit geometry, shared access, lighting and obstructions. One suitable view may cover a controlled gate; separate lanes or entrances may require additional views. A site assessment determines the scope. More cameras alone do not guarantee better counts.
The technical proof of concept connects a V380 camera to Hermes Agent and sends camera images through WhatsApp. Automated count summaries, schedules and on-demand business reports are intended features undergoing development and testing. The preview on this page illustrates that proposed experience.
No. A vehicle can enter for a quotation, a delivery, parking or a return visit. A completed wash needs a service record; payment needs a transaction record. Entry counts can support reconciliation, but cannot establish revenue, theft or employee wrongdoing.
Choose a stable, sheltered view that shows vehicles before and after the counting boundary, with minimal overlap and glare. Avoid pointing unnecessarily at neighbouring premises or public areas. Test busy periods, rain, evening light and vehicles reversing before accepting a position.
An initial consultation establishes your gate layout and reporting needs. A technical review checks camera access, power and connectivity. A scoped pilot would then configure the view and counting rules, compare results with manual observations, and agree reporting and support. Timing depends on the site and feature readiness; no standard installation duration is promised.
Explain what is counted, why it is useful, who can see records and how staff can correct exceptions. Keep monitoring proportionate to vehicle activity. Avoid facial recognition or individual productivity scoring for this purpose. Counts should start a fair discussion supported by service records, never an automatic accusation.
Before a pilot, agree processing location, authorised recipients, retention, deletion, access controls and any third-party services. Images can contain identifiable people or number plates. Prefer aggregate reports and collect only what is necessary. Review applicable Kenyan data protection requirements; this page does not claim a settled production data architecture or compliance certification.
CraftDuka welcomes pilot and demo enquiries in Kenya and East Africa. Participation depends on technical fit and development readiness. Pricing has not been published. Request a scoped proposal covering hardware, installation, processing, connectivity, WhatsApp delivery, validation and support; there is no implied free pilot or guaranteed deployment date.
LET’S ASSESS YOUR SITE
Tell us your location, number of access points, camera model and the reports you need. We will discuss technical fit, what can be demonstrated today and whether a scoped pilot is appropriate.
No published price list or guaranteed installation timeline. Hardware, validation, processing, connectivity, messaging and support affect scope.
Our existing enquiry form will open with Smart Car Wash selected. Share camera model details; keep passwords and customer images out of the form.
Request a Smart Car Wash DemoBook a Consultation Read our privacy policyTHE SMART CAR WASH FIELD GUIDE
Understand AI vehicle counting for Kenyan car washes: camera requirements, WhatsApp reports, practical limits, privacy and a responsible pilot checklist.
Read the guideA practical guide to entrance camera placement, vehicle detection and tracking, virtual counting lines, duplicate prevention and manual accuracy checks.
Read the guideBuild fair car wash accountability with shift records, service logs and traffic reconciliation. Understand exceptions and protect staff privacy.
Read the guideCompare traditional CCTV recording with AI vehicle event analysis, including camera compatibility, accuracy, deployment options, privacy and running costs.
Read the guidePlan useful WhatsApp car wash reports with entry and exit counts, peak hours, missing-data warnings, recipient permissions and future POS reconciliation.
Read the guideMeasure car wash profitability with traffic, completed jobs, average ticket, labour and resource costs. Includes an illustrative KES ROI method and practical plan.
Read the guideKNOW MORE. PLAN BETTER.
Explore a practical monitoring pilot with CraftDuka in Kenya.
Request a Smart Car Wash Demo