The Table Minimum Nobody Hits

Bottle service runs on a number quoted before anyone walks in: the table minimum.

A VIP host texts a price, a guest agrees, and a table is held. Then the night happens, and at some point after last call somebody works out whether the table actually hit the number.

In most rooms that reconciliation is informal, inconsistent, and done under fatigue. Which means the minimum functions as a sales tool rather than a floor.

What a miss actually is

Three different things get called "the table didn't hit."

A short spend. The guest bought less than the minimum. Whether they owe the difference depends on what the host told them, and the host is not there at 03:40.

A comped short spend. The table came close, someone waived the rest to keep the guest happy, and the waiver was recorded as a comp with no reference to the minimum it was covering.

A minimum that was quoted low. The table hit the number easily and the number was below what that section should have produced on that night. This is the expensive one and it never shows up as a miss.

Only the first is a shortfall. The second is a pricing decision made by whoever was on the floor. The third is a pricing decision made by the host at the moment of the quote.

Grouping all three under "we hit our numbers" is how a room loses money on a full night.

The number worth tracking

Actual spend divided by quoted minimum, per table, tracked as a distribution.

Not the average — the shape.

A healthy distribution clusters just above 1.0, with a tail above it. Most tables hit the number and some substantially exceed it.

A distribution clustered well above 1.0 across the board means your minimums are set too low. Guests are spending far past the floor, which means the floor was not doing any work. That is money left in the quote.

A distribution with a lump below 1.0 means either your minimums are too high for those sections, or your hosts are quoting to close the booking rather than to price the table.

The average conceals all three. Two rooms with identical averages can be in completely different positions.

The host incentive problem

Hosts are usually compensated on booked tables or on the revenue those tables produce.

If the incentive sits on bookings, the rational move is to quote low — a booked table at a soft minimum pays better than an empty one at a firm minimum.

If it sits on revenue, the incentive is better aligned, but only if the revenue attributed to the host is the actual spend rather than the quoted minimum. Attributing the quote rather than the spend rewards optimistic quoting, which is the opposite of what you want.

The check is simple and rarely run: for each host, the average ratio of actual spend to quoted minimum. A host consistently below 1.0 is quoting high and creating shortfall conversations. A host consistently well above is quoting low and leaving money in the room.

Neither is a performance problem in isolation. Both are useful information about how the incentive is landing.

Where comps hide it

The most common way a shortfall disappears is that it becomes a comp.

The table is short, the manager waives it, the POS records a comp with a reason code like "VIP" or "management discretion," and no field anywhere connects that comp to the minimum it was covering.

Three months later the comp report shows a category, and the minimum report shows tables hitting their numbers, and neither one shows that a specific amount of shortfall was written off table by table.

One field fixes it: a comp against a table with a minimum should carry a flag for whether it was covering a shortfall. That single flag turns two unrelated reports into one answerable question — how much minimum did we waive last month, and who waived it.

Section pricing that has not moved

Minimums tend to be set once and inherited.

Rooms change. A section that was the best seat in the house when the DJ booth was on the other side is now the section people leave. The minimum on it has not moved in two years because nobody owns the number.

Run spend per section against minimum per section once a quarter. Where the ratio has drifted far above 1.0, the minimum is stale and underpriced. Where it sits below, the section has lost whatever made it worth the number.

That is a thirty-minute exercise that most rooms have never done, and it is usually the single largest recoverable amount in bottle service.

The night-of-week trap

A minimum that is right for Saturday is not right for Thursday, and a lot of rooms run the same number across both because it is simpler to quote.

The cost is asymmetric and worth stating plainly. On the slower night the minimum is too high and you lose the booking entirely — a table that would have spent something spends nothing, because the quote scared them off. On the busier night the minimum is too low and you leave money in the quote.

Both errors come from one number doing two jobs.

Three numbers to hold

Spend-to-minimum ratio distribution, by section, monthly. The shape, not the mean.

The same ratio by host. Shows how the incentive is actually landing.

Waived shortfall, monthly. Requires the comp flag above. Without it this number does not exist anywhere in your reporting, and it is real money.

Where the record has to sit

The quote lives in a text thread. The table lives in a reservation tool. The spend lives in the POS. The comp lives in a different part of the POS with no reference to any of the others.

That is four systems for one table, which is why the reconciliation happens by memory at the end of a long night — and why the answer to did our minimums work last month is a shrug in most rooms.

tasteck keeps the reservation, the quoted minimum, the actual spend, and the comps against the same table record, so the distribution is a view rather than a rebuild.

The minimum is already being quoted. Whether it is a price or a guess depends on whether anyone can see what happened to it.