Booking & payment policies

Policies are the rules and terms attached to a booking. There are two kinds, both under Settings → Policies:

• Booking policies - the free-text terms guests see (dress code, house rules, what happens if they’re late).
• Payment policies - reusable rules for deposits, refunds and whether guests can change or cancel.

Booking policies

On the General panel you set your default booking policies - plain-text terms shown to guests at the point of booking. There’s a separate policy for each flow:

Policy	Applies to
Tables	Table reservations.
Guest list	Guest-list entries.
Events	Event bookings.

Keep these clear and specific - arrival windows, dress code, minimum spend expectations, and what happens if the party changes size. They appear to guests before they confirm.

Payment policies

On the General / Payment panel you build payment policies. Unlike the free-text booking policies, these are reusable - you name a policy once and attach it to access profiles, shifts and events wherever the same terms apply.

Each payment policy sets three things:

Setting	Options	What it means
Deposit	No / Hold	Whether a card hold is required. Hold authorises an amount on the guest’s card at booking, taken only if needed.
Refunds	None / Full / Partial %	If money is captured, how much is refundable - nothing, all of it, or a set percentage.
Modify / cancel	Any time / Never / Up to cutoff	Whether the guest can change or cancel their booking themselves, and until when. Up to cutoff ties changes to the booking window cutoff.

The deposit amount itself comes from the linked price list (per cover), not the policy - the policy only decides whether a hold is taken and how refunds and changes are handled.

Note

A deposit Hold authorises funds without taking them. Your team captures or releases the hold from the reservations floor. The full lifecycle is covered in Deposits & card holds.

Tip

Both policy panels support Copy from another venue, so a group can share a consistent set of payment policies and default booking terms.

Putting policies to work

1. Write your default booking policies for tables, guest list and events.
2. Build the payment policies you need - for example No deposit, Weekend hold, no refund, Event deposit, 50% refund up to cutoff.
3. Attach a payment policy (and, for tables, a price list) to the relevant access profile or shift.

See Deposits & card holds for how holds behave end to end.