Scan, and that is the whole setup
The attendant shows a QR on their own screen and the guest scans it with the camera. No app, no store, no account.
Scan. Park. Pay. No app.
Valet without the paper ticket — or the app download.
ValoPal turns every valet stand into a digital system of record. The guest scans a QR from the attendant's screen and gets a live pass they can pay from — no app, no download, no phone number required. Every key, every hand-off and every payment is timestamped to one ticket.
- No guest app
- Phone number optional
- Card, cash or booth-recorded payment
- Apple Wallet live pass
One car, one night
Valet stands run on memory, paper stubs and trust.
Follow one arrival from the curb to the hand-off. The moments that do the damage all happen while cars are still arriving.
- 01Arrive
A key changes hands before anything is verified
A stub is torn, keys go on whichever hook is free, and the description of the car lives in the attendant's head. Nothing written down says which attendant took it or what the car looked like when it arrived.
Drop-off
- 02Scan
Scan, and that is the whole setup
The attendant shows a QR on their own screen and the guest scans it with the camera. No app, no store, no account.
The guest side
- 03Parked
A pass with live status
The pass shows where the car is: parked, on its way, ready. It updates as the attendant works, without anyone refreshing anything.
The guest side
- 04Ready
A car is released before payment clears, or to the wrong person
At the rush, a car is fetched from a description and handed over on a nod. Whether the guest paid, and whether the person collecting is the person who dropped off, are decided in the moment by whoever is on the curb.
Pick-up
The universal QR loop
Every object in the loop carries a code.
The guest's pass, the key peg, the aisle sign. ValoPal binds them all to one ticket record and timestamps every scan. That binding is what makes 'who had this car, and when' answerable instead of reconstructed.
Guest pass
Scanned from the attendant's screen
Key tag
Scanned when the keys are hung
Parking spot
Scanned at the aisle sign
Plate
Read at intake and at release
They all resolve to
One ticket record
The guest side
Your guest downloads nothing.
The pass is a web page, so the only thing the guest needs is the camera they already use.
A pass with live status
The pass shows where the car is: parked, on its way, ready. It updates as the attendant works, without anyone refreshing anything.
The differentiator
Apple Wallet live pass
Give a phone number and you also get text updates and an Apple Wallet pass that updates itself on the lock screen as the car moves through the flow. The phone number stays optional.
Pay from the pass, or at the booth
Settle by card on the pass, or hand it over at the booth. Either way the ticket records the amount, the method and the time.
Three independent dimensions
Where the car is, how it was paid, and who checked it.
"Ready — paid cash — unverified" is a normal Tuesday. Because these are stored separately, a ticket can be in any combination and the record never has to invent a fake status.
Car state
Parked → on its way → ready → closed
Payment
Unpaid · paid by card · recorded at the booth (cash, Venmo, Zelle)
Verification
Awaiting manager check · verified · flagged
Built for the curb
A PIN on a wet phone in a dark driveway.
The parts of a shift that people usually improvise — hanging keys, photographing a car, working with no signal — are handled by the app, so the record survives a bad night.
Damage
A dent appears and nobody can say when
There is no picture of the car at intake, so a claim comes down to two recollections. The stand either pays or argues, and neither outcome is based on evidence.
AI-detected damage notes
Intake and release photos are checked and findings are written to the ticket with the time and a confidence score.
AI-detected — not an inspection
Key tags the app assigns
The tag is assigned automatically when the ticket is created and is read-only from then on. The attendant hangs the keys on the tag they are given rather than picking a hook.
Works when the signal does not
Tags are reserved ahead of time so they cannot collide, and every path keeps working behind a queued banner until the phone reconnects.
Escalation, not a backlog
A manager check never holds up the curb. Tickets waiting on one get more prominent the longer they wait, instead of quietly piling up.
No phone, same record
A name-based walk-in path is one tap away — same photos, same key tag, same record, marked as the exception it is.
For multi-location operators
The second property is configuration, not a migration.
ValoPal is organised as operator → location → stand from the first line of the schema, so growth is a settings change rather than a rebuild.
Locations are data, not deployments
Adding a property or a second stand at the same property means adding rows and assigning staff, not standing up another system.
Per-location settings
Tip presets, accepted payment methods, waiver text, branding and retention period are set per location, because a rooftop restaurant is not a convention hotel.
One record across the portfolio
Every stand writes to the same shape of record, so a regional manager compares locations without anyone exporting and reconciling by hand.
What falls out of the record
The reporting is a by-product of the workflow, not a second job for your staff.
Because every scan is an event with a time on it, operators get reporting without anyone filling in a form at the end of a shift.
- Arrivals by hour and by day of week
- Average stay
- Request-to-ready time
- Occupancy against key capacity
- Payment mix and tip rate
- Throughput per attendant
Start with one stand.
Our first pilot is running at a single stand with a regional parking operator. We onboard one property, one stand, one shift — then hand you the record.