How to run a prepaid supper club without empty seats

Why does a prepaid cover fix the no-show problem?

Because the loss a no-show causes is the food and the labour, and both are already paid for. A reservation transfers no risk: the restaurant buys the produce, rosters the staff, and finds out at eight o'clock whether the guest meant it. Selling the cover moves that decision to the moment of booking, when the guest is committed and nothing has been ordered yet.

It is worth being exact about what bindro does and does not add here. It takes the money at booking and holds it until two days after the dinner. It will publish a deposit plan on the seat type and take the deposit at checkout, and it will keep that deposit if the table never arrives, once the service has been delivered. What it will not do is collect the balance of a plan automatically or raise a new charge against a card with nobody present — both are the same switch and it is set in no environment. Your no-show policy is the refund policy you publish; where it states a share to keep on a late cancellation, the platform applies that share itself rather than queuing the decision for you during service.

How many covers should one sitting hold?

Size the sitting to the pass, not to the room. Count the plates the kitchen can send at the standard the menu promises in the fifteen minutes around a course change, and work back from there — most set-menu services land between sixteen and thirty covers a sitting. If the arithmetic tells you fifty, check whether it assumed a chef who never speaks to a table.

Two sittings beat one long service for a set menu, because the second sitting absorbs the drift from the first and the kitchen resets between them. Bindro models each sitting as its own timed slot with its own cover count, and covers move only under a row lock inside the confirming transaction, so the last seat at the eight-thirty is sold exactly once no matter how many people are on the page at the time.

• Count plates at the pass, not seats in the room.
• Two sittings, ninety minutes to two hours apart, for a fixed menu of four courses or more.
• Keep the later sitting slightly smaller — it inherits every delay of the night.
• Publish each night as its own dinner if you want that night's money on its own schedule.

When should the on-sale open?

Announce first, sell at a stated time a few days later. A stated on-sale concentrates demand into a moment you have staffed, which is much easier to handle than a trickle you have to keep watching, and it lets regulars plan around it.

The lead time modelled for ticketed dining is sixteen days, which is a useful planning horizon: far enough out that people can arrange a table of four, close enough that the night still feels real. An on-sale two months ahead mostly buys you cancellations to process.

What should the cancellation line actually say?

Say the thing you will actually do, in one sentence, on the listing. "Covers are prepaid; we can refund up to seven days before the dinner, and after that we will move you to another night if we can" is a policy a host can apply at ten past seven without checking with anybody.

Both halves of that sentence are things bindro can carry out. A refund is issued from the console, or by the guest from the signed link in their confirmation email, and reverses your proceeds first, then tax, then the platform fee. A move to another night is a deferral: the guest gets a credit worth what they paid, good for a year at your restaurant, and the value leaves your balance until they spend it. Only you can start that one, and the seat they vacated stays counted against the sitting, so raise the cover count if you want to resell it.

How should the door be run on the night?

One person on the list, at the door, on a phone. Ticketed dining checks in by name list: front of house finds the booking and marks the guests in, or scans the code in their email if that is quicker. Whoever does it needs a connection — offline check-in is not enabled for this vertical — so test the signal at the host stand before the first sitting rather than at ten past seven.

Brief the floor on two limits so nobody promises otherwise. There is no re-entry: a seat admits once. And a door-staff login is shown names and admissions only, so what the guest wrote about allergies is read before service by somebody with guest-record access, and the sheet for the pass is still built the way it always was — by asking, and by writing it down yourself.

• One host, one device, one list; check the signal before service.
• A seat admits once — no re-entry on this vertical.
• Door staff see a name and an admit; they do not see money or anyone else's booking.
• Build the allergy sheet outside bindro and confirm it at the table.