In summary
What you need to know
Choose deposit amounts, write fair policies and manage payments, cancellations and refunds.
- Use conditional deposit rules
- Explain terms before checkout
- Create a consistent exception workflow
- Best for
- Hospitality operators reviewing no-shows & deposits
- Reading time
- 4 min read
- Last reviewed
- 2 August 2026
Share this guide
A booking deposit converts a reservation into a clearer commitment. It can protect high-demand inventory, but only when the amount, policy and guest communication feel fair.
01
When deposits make sense
Common use cases include tasting menus, large groups, special events, peak sittings and scarce premium areas. A venue does not need one rule for every booking; conditional policies often protect revenue with less impact on conversion.
02
Choose the model
A fixed per-person deposit is easy to explain. A percentage can suit packages with known value. A card guarantee may feel lighter but requires a clear charge policy. Decide whether deposits are deducted from the final bill, refundable or transferable.
Deposit model comparison
Choose a structure the guest and finance team can both understand
The right model depends on the value at risk, the booking type and how the amount is reconciled after service.
| Model | Best fit | Operational requirement |
|---|---|---|
| Fixed per person | Groups and tasting menus | Accurate party-size changes |
| Percentage | Known packages | Clear final-bill deduction |
| Card guarantee | Peak tables with lower friction | Documented charge decision |
| Full prepayment | Ticketed events | Refund and transfer workflow |
03
Communicate before payment
Display the amount, deadline, cancellation window and refund terms before the guest confirms. Repeat them in the receipt and reminders. Avoid hiding important terms in a general policy page.
04
Build an exception process
Weather, illness and operational closures need human judgment. Define who can refund or move a deposit, record the reason and keep an audit trail. Fair exceptions protect trust without weakening the general policy.
05
Procurement and operating depth
Reconciliation deserves its own workflow. Each deposit should connect to one booking, one payment status and a clear outcome: credited to the bill, refunded, transferred or retained under the accepted policy. Managers should be able to explain any difference between the booking ledger, payment-provider balance and point-of-sale total. Review unmatched transactions daily during launch, then at a cadence suited to volume.
Venue-specific application
A realistic operator example
For a €75 tasting menu, a restaurant considers a €25 per-person deposit deducted from the final bill. A four-person booking therefore pays €100 at confirmation. The venue states the cancellation deadline before payment, repeats it in the receipt and gives managers a documented exception process. In the monthly review, it separates retained deposits from recovered tables so the same protected revenue is not counted twice.
- Choose fixed, per-person, percentage or card-guarantee logic
- Display terms before the payment action
- State whether payment is credited, refundable or transferable
- Limit staff access to payment details
- Create refund and exception permissions
- Reconcile deposits against final bills and cancellations
What to measure
Signals that belong in this review
Next operational step
Use the relevant UpSalt workflows
- Use conditional deposit rules
- Explain terms before checkout
- Create a consistent exception workflow