A no-show is not one empty table. It is a table you turned other people away from, held for ninety minutes, and prepped for.

A deposit policy is the most direct tool restaurants have against that, and the one most likely to be written badly. Set it too hard and you lose bookings. Set it too vaguely and you lose the argument at the door.

In this article

• Decide What the Deposit Is For

• Not Every Table Needs One

• Pick the Shape of the Charge

• Write the Cancellation Window in Plain Language

• Show It Before They Confirm, Not After

• Apply It to the Check, Visibly

• Tell People Where the Booking Came From

• Deposits Are Not the Only Lever

• Handling the Card Details Properly

• Enforce It the Same Way Every Time

• Watch What It Does to Bookings

• Where Peblla Fits, and Where It Does Not

Decide What the Deposit Is For

A deposit is not a penalty and it should not read like one. It is a commitment device, and the guests it is aimed at are the ones deciding between three restaurants on a Friday.

That distinction changes the wording. A charge described as protection against no-shows sounds defensive. The same amount described as coming off the final check sounds like a head start.

The mechanics can be identical. The booking rate is not.

Not Every Table Needs One

The instinct is to apply a deposit everywhere. Almost no restaurant should.

Deposits belong on the bookings that are expensive to lose: large parties, private rooms, prime weekend slots, and holidays. A two-top on a Tuesday costs you very little when it vanishes, and asking for a card will cost you more bookings than it saves.

• Party size above a threshold you set, usually six or eight.

• Private and semi-private rooms, where the whole room is held.

• Specific date ranges: holidays, restaurant weeks, event nights.

• Peak windows on Friday and Saturday, if your data shows the loss.

Pick the Shape of the Charge

There are three normal shapes, and they suit different rooms.

A flat amount per booking is simplest and reads well for a bar or a casual room. A per-person amount scales with what you are actually holding and is the usual choice for large parties. A percentage of an expected spend fits prix fixe and event menus where the number is already known.

A steakhouse holding a private room for twelve is protecting a different number than a taqueria holding a six-top, and the policy should say so rather than applying one figure to both.

Write the Cancellation Window in Plain Language

The window is the part guests actually read, and the part staff have to defend. Make it a single sentence with a number of hours in it.

Twenty-four hours is the common default and is defensible almost anywhere. Forty-eight is reasonable for private rooms and holidays. Anything longer needs a reason a guest would accept out loud.

Say what happens on each side of the line. Cancel before the window and the deposit is released. Cancel after it, or do not arrive, and it is retained. Ambiguity here is what turns a policy into a dispute.

Show It Before They Confirm, Not After

The single biggest predictor of a deposit dispute is when the guest first learned about it.

The amount, the window and what happens to the money all belong on the booking screen, above the confirm button. A guest who reads it and books anyway has agreed. A guest who finds it in a confirmation email has been ambushed.

This is also the honest test of the policy. If you would rather guests did not see it until later, the policy is too aggressive.

Apply It to the Check, Visibly

The deposit stops feeling like a charge the moment it appears on the bill as money already paid.

Whoever closes the check needs to see the collected amount, the amount still available and the amount applied, on one screen. When those three numbers are visible, the conversation at the table is short.

On a handheld the same three numbers should be readable at the table, so nobody walks back to a terminal to check what was already paid.

It should also come off the check automatically rather than being remembered. A policy that depends on a server recalling a deposit from four weeks ago will fail on the night it matters.

Tell People Where the Booking Came From

A deposit lands differently depending on how the guest reached you. Someone who found you on a map listing and booked in twenty seconds has less invested than a regular booking from your own site.

Put the same terms on every channel so the answer never depends on where they started. Connecting your booking page to search and social explains how one booking page ends up on the listings and posts guests already use, and the deposit terms should travel with it.

Where you can vary is the threshold, not the wording. A large party arriving through any channel is the same risk to the room.

What you should never do is quote a different amount on the phone than the booking page shows. That is where staff lose the argument, because the guest is right.

Deposits Are Not the Only Lever

Before widening a deposit policy, check whether the loss is really no-shows. Often it is a room that turns slowly, or a booking book that says full while tables sit open.

Two cheaper levers usually come first. A reminder before the booking recovers people who simply forgot, and a standby list means a cancellation inside the window is refilled rather than lost.

A short reminder sent through your text channel costs almost nothing and removes a meaningful share of the problem without asking anyone for a card.

Use deposits for what reminders cannot fix: the bookings that are large enough, or scarce enough, that losing one ruins the night.

Handling the Card Details Properly

A deposit means holding payment information, and guests are right to care how that is done. Take it through the same payment flow that runs your checks rather than writing a number on a booking sheet.

Never store card details in a notes field, on paper, or in a messaging thread. If a policy requires anyone to write a number down, the policy is wrong.

A group running several rooms should apply one process everywhere. Guests will judge the whole brand by whichever location handled it worst, and a single connected system that keeps the booking, the deposit and the check on one record is what makes that consistent.

Enforce It the Same Way Every Time

A policy that is waived whenever someone complains is not a policy, and staff learn that faster than guests do.

Decide in advance who can waive a deposit and on what grounds, then let them do it without escalation. One named manager, a short list of acceptable reasons, and a note on the record is enough.

A coffee shop taking event bookings and a full-service dining room can run the same rule. What breaks consistency is not the room, it is having no answer written down.

Watch What It Does to Bookings

Deposits trade volume for reliability, and the trade is not always worth it. Watch the ratio for a month before you widen the policy.

The numbers to compare are bookings made, bookings honoured and covers actually seated. A policy that cuts no-shows in half while cutting bookings by a third has not helped you.

If the loss is showing up as slow turns rather than empty tables, the answer may be pacing rather than deposits, and how turn time and pacing work is the better place to start.

Where Peblla Fits, and Where It Does Not

With Peblla Table you set the deposit yourself: a flat amount, a percentage or a per person charge, applied only to the party sizes, table types and date ranges you choose, with your own cancellation window. The guest reads the terms before confirming, and the collected amount comes off the check in Peblla POS rather than being remembered by a server.

It does not decide the policy for you, and it should not. Whether a six-top on a Saturday needs a card is a judgement about your room and your neighbourhood, not a setting. A system will only make a bad rule consistent.

If you rarely take large parties and almost never lose a table, you do not need any of this. Deposits earn their place when prime time is the constraint, when private rooms are part of the business, or when a single no-show costs a whole evening of that room.

Frequently Asked Questions

How much should a restaurant deposit be?

Enough to signal commitment and small enough not to lose the booking. Many restaurants land between fifteen and twenty-five dollars per person for large parties, and a higher flat figure for private rooms. The right number is the one that changes behaviour without changing whether people book at all.

Is a no-show fee the same as a deposit?

No, and the difference matters to guests. A deposit is money taken at booking and applied to the final check, so a guest who arrives has lost nothing. A no-show fee is charged only after a table is missed, which is harder to explain and more likely to be disputed on the card.

What is a reasonable cancellation window?

Twenty-four hours is the common default and is easy to defend. Forty-eight hours is reasonable for private rooms, holidays and set menus where you buy product in advance. Longer windows need a reason the guest would accept, otherwise they read as an excuse to keep the money.

Will asking for a deposit cost me bookings?

Some, yes, which is why it should not apply to every table. Applied narrowly to large parties, private rooms and peak windows, most restaurants see the reliability gain outweigh the lost volume. Applied to every two-top on a quiet Tuesday, it usually does not.

Should staff be allowed to waive a deposit?

Yes, but decide in advance who can and on what grounds. One named manager, a short list of acceptable reasons, and a note left on the booking is enough. What damages a policy is not the occasional waiver, it is waiving it differently depending on who is asked.

Can a deposit be used on anything on the bill?

Usually it applies to food and drink on the check. Restaurants commonly exclude automatic gratuity, and it is worth stating that explicitly in the terms rather than discovering it at the table. Whatever you decide, it should be written on the booking screen before the guest confirms.

If prime time is where you are losing tables, the useful next step is to walk through a deposit policy with the Peblla team and set the party sizes, amounts and windows against your own weekend rather than a template.