Works with your camera
Vendor-neutral: plate events arrive through the API connector.
Your licence-plate camera reads the car; GetCarWashPOS answers in the same moment — member or not, which plan, paid up or past due — so members roll through and everyone else meets the pay station.
License plate recognition (LPR) at a car wash uses a camera and recognition software to read a car's plate as it enters. The plate is matched to a customer record, so members are recognised without a tag. GetCarWashPOS receives the plate read from your LPR vendor through an integration and returns the member status; the camera and recognition service are third-party.
Sample outcomes; the exact screen depends on how your LPR vendor displays responses.
| Plate read | Answer from the POS | What the attendant does |
|---|---|---|
| TXK·4821 | Member · Ultimate club · active | Nothing — the car goes through |
| KHI·7310 | Member · Deluxe club · past due | Asks to update the card at the pay station |
| DXB·55K | Not a member | Sells today's wash or the club |
| (no read) | No match | Searches by phone or name |
The same order the software asks for it.
Pick an LPR camera and recognition service that can send plate reads to an outside system (webhook or API). We tell you on your demo which vendors we have connected so far.
Our onboarding desk connects the vendor's plate events to your GetCarWashPOS account using the API connector.
Each member's vehicles carry their plates. Imports from your old system bring plates across.
When a plate is read, the POS looks up the vehicle and returns active, past due or not a member to the lane screen.
Bad read, dirty plate or temporary tag? The attendant searches by plate, phone or name at the pay station.
Vendor-neutral: plate events arrive through the API connector.
Several plates per member, history per plate.
Active, past due or not a member — in the time the car rolls forward.
Company vehicles recognised and charged to the fleet account.
Every wash logged against the plate for reports and disputes.
Plate data lives in your account and exports with everything else.
Plates are personal data in many jurisdictions. GetCarWashPOS only stores the plates you attach to customers and the visits you log; it does not store camera images. Your privacy notice should say why you read plates (membership checks) and how long you keep visit history.
A camera at the entrance captures the plate and recognition software turns it into text. That text is sent to the POS, which looks up the vehicle, finds the member and returns the status to the lane — usually in the time it takes the car to roll to the gate.
No. You buy the camera and recognition service from an LPR vendor; GetCarWashPOS receives the plate reads through its API connector. We help you connect it during onboarding.
Any vendor that can send plate events to an outside system by webhook or API can be connected. Ask on your demo which vendors we have already connected and what the setup involves for yours.
The POS returns no match and the attendant searches by plate, phone or name at the pay station. You can also add common misreads (for example O vs 0) as extra plates on the vehicle.
Yes. Fleet vehicles carry their plates on the fleet account, so a read charges the wash to the account automatically.
If most of your volume is members, LPR speeds the gate and removes tags that fall off. For a hand wash or detail shop, plate lookup at the pay station is usually enough.
The LPR integration is available on Tunnel ($89/mo) and Network ($129/mo per site). Plates on customer records work on every plan.
Plates are stored as text exactly as the recognition service returns them. UAE plates with Latin letters and numbers and Pakistani plates in Latin characters work as normal; what your camera vendor returns for other scripts depends on that vendor.
Start the 21-day trial, or book a 30-minute demo on your own wash menu with someone from the desk for your country.
No contract · Free import of your menu and members