Feature Guide · Validations

The third party gets one job,
not your whole system.

A restaurant, retailer, office, or property partner can validate an eligible car from its own portal, with the pricing effect and billing boundary visible before it acts.

What it is

A partner-scoped way to apply a configured pricing modifier to an on-site session.

The operator defines the validation and agreement. The partner applies it from a narrow portal. The guest sees the resulting adjustment at checkout.

That separation is the design: a third party can perform its part of the transaction without becoming a user of the valet operation.

01

Who uses it

A validation is a three-party transaction: operator, partner, and guest.

Operator

Defines the validation and partner access

The valet company configures the pricing modifier, partner relationship, and whether that partner can manage validations.

Partner

Applies it to an eligible on-site car

Authorized partner users see their definitions and the relevant parked arrivals at the shared location.

Guest

Receives the adjusted checkout

The validation becomes a pricing modifier on the session; the guest sees its effect in the price breakdown.

02

The setup order

Commercial terms first, definition second, publication last.

1 · Agreement

Choose how validation usage is billed

Usage, validation, flat, and revenue-guarantee arrangements produce different partner notices and ledger treatment.

2 · Definition

Configure the pricing effect

The validation can describe a reduction or split supported by the pricing engine and is scoped to the partner and location.

3 · Access

Invite authorized partner users

The can-manage-validations permission governs creating, saving, archiving, and restoring validation definitions; publishing and session application follow the partner-at-location access rules.

4 · Publish

Offer a QR or guest-entry link when needed

A partner can publish a validation-specific link without exposing the operator console.

03

The daily loop

Apply the validation before checkout, from the partner's own surface.

Find

Choose an on-site session

The partner view subscribes to current arrivals at its location and presents recognizable vehicle context within the partner's scope.

Apply

Tag the session with the chosen validation

The pricing engine reads the tag at checkout and applies the configured modifier.

Explain

Show the partner's billing notice

The portal states whether each use is billed, included, or counted toward the agreement before the partner acts.

04

The edge cases

The portal keeps validation state explicit.

Removed before checkout

The tag can be taken off

An authorized partner can remove an applied validation while the session remains on site.

Archived definition

History remains distinct from active choices

Archived validations move out of the active list instead of disappearing into it.

Fullscreen

The same portal becomes a focused counter surface

Fullscreen changes presentation for a dedicated merchant station; it does not broaden permissions or data scope.

05

What it deliberately does not do

Partner access is intentionally narrower than operator access.

No operator console

The merchant does not enter valet operations

The portal exposes validation definitions and eligible arrivals, not company-wide sessions, staff, payments, or settings.

No universal billing rule

The agreement controls the ledger

Valletto does not assume every validation is billed per use; the partner notice reflects the configured contract.

06

What it connects to

A validation crosses three products without losing its identity.

Pricing

The configured modifier changes checkout

The canonical engine applies the validation with the other eligible modifiers.

Guest checkout

The adjustment is visible

The guest can see the validation in the price breakdown rather than receiving an unexplained total.

Partner billing

Usage follows the agreement

Where the contract requires it, the same application becomes partner ledger and invoice context.

Staged partner validation portal with an illustrative dining validation, a synthetic parked vehicle, a published QR link, and a billing notice.

Staged from the current Partner Validations and customer validation surfaces. Partner, vehicle, amount, and billing values are synthetic.

Where Valletto changes the math

Give the partner the one door they need.

The portal keeps validation fast for the merchant, legible for the guest, and scoped away from the rest of the operation.

Next: the Partner Portal guide follows the broader property relationship beyond validation.

Keep reading.

Feature GuidesRevenue

Subscriptions: Unlimited Valet at One Property

How a property-specific valet subscription turns a resident, employee, tenant, or member into a covered parker at one location.

Nov 14, 2025 · 8 min readRead
Feature GuidesRevenue

Passport: A Membership Across an Operator’s Portfolio

Passport is an operator-owned membership for regulars across covered locations - distinct from a subscription sold for one property.

Nov 11, 2025 · 8 min readRead
Feature GuidesIntegrations

Messaging: Texting Guests and Staff Without Getting Blocked

A practical guide to Valletto's transactional SMS, guest consent, STOP and HELP handling, 10DLC registration, and the delivery limits no software can promise away.

Aug 14, 2026 · 10 min readRead

When reading is not enough

See it on your drive.

Twenty minutes on your own property, with your own volumes. We would rather show you the parts an article can only describe.

or keep reading the journal