Enforcing a Minimum Without Losing the Table

Setting a minimum takes five minutes. Enforcing one takes a conversation at 1am with people who have been drinking, and that conversation is where both the money and the goodwill go.

Most venues have a minimum. Very few have decided what happens when a table falls short.

The four outcomes when a party is under

They order up        the intended outcome. Least common
They pay the shortfall  works once. Rarely brings them back
You waive it         costs the gap, and the next table hears about it
It becomes a dispute  costs the gap, the goodwill, and an hour of a manager

The third and fourth are the common ones, and neither is a policy — they are what happens when there is no policy.

The gap is visible long before closing

At any point in the night you can compare what the table has spent with how much of the night is left. A table at half the minimum with an hour to go is a different situation from the same table with ten minutes to go — and only one of them is still fixable.

Almost nobody looks until the bill. By then the only remaining moves are the expensive ones.

Four ways to close a gap early

One — tell them where they are, once, without pressure. Most parties under a minimum do not know it. A neutral update at the right moment converts far more often than a demand at the end.

Two — offer something worth the gap. A bottle they actually want at the gap amount is an easier yes than "you owe us the difference."

Three — let them shrink the table. Moving a party to a smaller area with a lower minimum keeps the guest and frees the premium space. This requires knowing what is free right now, which is a records question.

Four — decide in advance what a waiver costs. If you will waive, waive early and deliberately. A grudging waiver at closing buys nothing — the guest already had the bad experience.

What makes a minimum unenforceable

Nobody knew it            not stated at booking, not on the table
It varies by who is asking staff enforce it differently
It is unreachable          set for a night that no longer exists
The gap appears at the end  no one was watching during the night

The second line is the one that ends up in a review. Enforcement that depends on who is working is not a rule; it is a lottery, and guests describe it as one.

Measure the policy, not the incidents

Tables under minimum, by night and by area
Average shortfall
How it was resolved (ordered up / paid / waived / disputed)
Whether under-minimum parties came back

The fourth line decides whether the minimum is set right. If parties that hit the minimum return and parties that fell short do not, the minimum is filtering — which may be exactly what you want, or may be losing you a segment you could serve at a lower tier.

⚠️ Do not raise a minimum to fix a shortfall problem

If tables consistently fall short, the minimum is above what that room bears on that night. Raising it increases the shortfall and the number of arguments.

The lever is usually the tier structure — a lower minimum on the nights or areas that keep missing — not a higher number on the same table.

The system we built

tasteck is a booking and analytics system for night venues, built by people who ran them for sixteen years and grew from ¥200 million to ¥1.2 billion a year — six-fold, by attacking the business with systems rather than by pushing harder on sales.

What it does here: bookings held per table with times, so what is free right now is visible when a party needs moving. Settlement broken out by line, so spend against a minimum is a running figure rather than a closing surprise, and the mix inside it is visible. Guest history per person, so whether under-minimum parties return is a query.

What it does not do: it does not set minimums, does not enforce them, does not alert your staff, and has no minimum-spend feature. The running total is available; the policy and the conversation are yours.

The output no one else produces

tasteck outputs the maximum you can spend on each marketing channel next month, as an amount in your currency.

A minimum is a filter on who walks in, and channels are what decide who arrives to be filtered. If a channel reliably delivers parties that fall short, you are paying twice — once to acquire them and again in the argument at the end of the night. The ceiling is computed from the lifetime value of the guests each source actually delivered, so a channel that fills tables which cannot clear the minimum carries a low ceiling for a reason you can finally see.

Nothing else in the nightlife category produces that figure.

Ask it from ChatGPT

tasteck connects to ChatGPT over MCP: ask your numbers as a question and the answer comes back in the chat — how many tables fell short last Saturday, what the average shortfall was, whether those parties came back. → Setup guide

Multi-language is built in, the operating surface itself, with your language set during onboarding.

From $34 a month for up to two locations. Thirty days free on every plan, cancel any time. → Pricing

Start this month

1. Count tables under minimum, by night and by area. Most rooms have never counted.
2. Record how each was resolved. Four outcomes, one word each.
3. Check the return rate of parties that fell short against those that did not.
4. Decide your waiver policy in advance, including who may grant it.
5. If shortfalls cluster on one night, lower that night rather than raising the number.

Read next

• The VIP Room That Earns Less Than the Floor
• Bottle Service: The Numbers Behind Table Management
• Pricing a Night Out Without Guessing
• Comps and House Accounts: What They Actually Cost
• Nightclub Software

---

On benchmarks. No target minimum levels, acceptable shortfall rates, or waiver thresholds appear in this guide. We do not have a dataset broad enough to publish them, and they vary enormously by city, format and price point. One month of your own shortfalls, split by night and area, will tell you whether the number or the night is wrong.