When should a restaurant set its deposit cancellation cutoff, 24 or 48 hours?

The cutoff is really a question about your rebooking speed

A cancellation cutoff exists for one reason: to give you enough notice to put someone else in the seat. So the right window is the amount of lead time your restaurant needs to refill a cancelled table with reasonable confidence. A busy neighborhood place with steady walk-ins and an active waitlist can often refill a two-top with a few hours' notice. A destination restaurant where most guests plan a week out and drive in from elsewhere may need a full day or two to find a replacement party. The cutoff should reflect your reality, not the policy you saw on a hotel booking page. Related: Which Bookings Need a Deposit

Think about it per table type rather than for the whole book. A four-top on a Friday probably needs a day of notice. A private room or a party of twelve may need three days or more, because the alternative buyer for that space is another group that also plans ahead. Weekday lunch may not need a deposit at all, which means the cutoff for those bookings is moot. Writing down how long each kind of table typically takes to rebook, based on what your host team actually sees, gives you a defensible answer before you pick a number. Related: How do you train front-of-house staff to take reservation deposits by phone?

Keep reading: Why No Shows Hurt Restaurants So Much, How a Deposit Changes Behavior, Making Deposits Guest Friendly. See how HoldTabl helps you no-show deposit collection for restaurant reservations.

Why 24 hours is the default and when it is wrong

A 24-hour cutoff is common because guests already understand it from other industries, it feels fair, and it is short enough that most people do not feel trapped when they book. For a la carte dining with a healthy waitlist, it works well: you lose only the cancellations that come in the same day, and those are the ones a deposit is meant to discourage anyway. It also keeps the policy simple to state in one sentence, which matters more than most operators expect when a host is explaining it on the phone to a guest who is already a little annoyed. Related: Handling Deposits Fairly

It is the wrong choice when your table is expensive to hold and slow to resell. Tasting menus with food ordered days ahead, holiday seatings, large parties, and private dining all fall into this category. A 48 or 72-hour window, or in some cases a week for large events, is easier to justify because the guest can see why you need the notice. The mistake is applying a long window to everything. A 72-hour cutoff on a Tuesday two-top feels punitive, and guests who feel a policy is unreasonable are more likely to book elsewhere or to dispute a charge later. Related: Deposits and Large Parties

Set the cutoff at a time of day your team can actually enforce

A cutoff expressed purely in hours creates awkward edge cases. If a reservation is at 7:30 on Saturday, a 24-hour window ends at 7:30 on Friday, right in the middle of service, when nobody at the host stand is looking at cancellation timestamps. Many restaurants find it easier to set the cutoff as a time of day, such as noon or close of business on the day before, so the rule is unambiguous and the team can review the next day's book at a predictable moment. It also gives guests a clear deadline they can remember without doing arithmetic.

Whatever you choose, make sure your booking system records the cancellation timestamp automatically and that the confirmation message spells out the deadline in plain words with the actual date and time. A guest who cancels at 11:50 a.m. against a noon cutoff should get a refund without a conversation. A guest who cancels an hour after the deadline should get a consistent answer. Ambiguity here is where fairness complaints and chargebacks come from, and a precise, visible deadline removes most of them.

Consider a graduated window before you consider a long one

If your instinct is to push the cutoff out to protect revenue, a graduated structure is often a better compromise than a single long window. Full refund before 48 hours, partial refund between 48 and 24 hours, and no refund inside 24 hours gives guests a reason to cancel as early as possible while still leaving room for the genuinely last-minute situation. It is also easier to defend when a guest complains, because they can see they were treated proportionally rather than with a hard cliff.

The tradeoff is complexity. Every additional tier is one more thing a host has to explain and one more place your booking software has to get the math right. Keep the tiers to two or three, print the schedule in the confirmation, and make sure refunds at each tier are processed automatically rather than by someone remembering to do it. If your team cannot explain the structure in one breath, simplify it. A clear 24-hour rule applied consistently beats a clever three-tier schedule applied inconsistently.