The Tabs That Walk at Close

Ask an owner how many tabs walked last month and you usually get a shrug and a guess. Ask a closing bartender the same question and you get a number, because they are the one who eats it.

The gap between those two answers is the whole problem.

A walked tab is not a mystery. It is a recorded transaction with a card on file or a name attached, and it either got settled or it did not. The reason nobody knows the number is that in most rooms it never gets counted — it gets absorbed, shift by shift, into a category called "that's just what happens."

What actually counts as a walked tab

Be precise here, because three different things get called the same name and they need different fixes.

A true walk — the guest left without settling and cannot be charged. No card on file, or the card was already returned.

A declined close — the card on file failed when the bartender ran it at close. The guest is gone, the charge did not go through, and now it is a collections problem.

A stranded tab — the tab is still open in the POS the next morning because nobody closed it, but the guest actually paid, or the card on file works fine and was simply never run.

The third one is the largest category in most venues, and it is not a loss at all. It is a closing-procedure gap that looks identical to a loss on the report.

If you do not separate these three, your "walked tab" number is mostly bookkeeping noise, and any fix you apply will be aimed at the wrong thing.

The number

Walked tabs as a percentage of total tabs opened. Not of revenue — of tab count, because a walked $40 tab and a walked $400 tab are the same failure of process.

Under 0.5% of tabs opened is a well-run close in a busy room.

Around 1% is common and usually means the card-on-file discipline is inconsistent — some bartenders take a card every time, some take one when it feels necessary.

Above 2% and something is structurally wrong: cards are being returned before close, the POS makes it easy to open a tab without a card, or one shift is running a completely different procedure from the others.

The absolute number matters less than the split by shift and by bartender. Walked tabs are almost never evenly distributed. In most rooms, one or two shifts produce the majority, and the reason is procedural rather than personal — those shifts are the ones with the worst ratio of open tabs to staff behind the bar.

Why the fix is not at the door

The instinct is to think of this as a security problem: someone left, stop them from leaving.

That framing produces bad answers. You end up with staff chasing guests into the street over a $60 tab, which risks an incident that costs far more than the tab, or with a policy that makes settling feel adversarial to the 99.5% of guests who had no intention of leaving.

The fix is at open, not at close. By the time the guest is walking out, every option you have is bad. The decisions that determine whether a tab walks were all made two hours earlier:

• Was a card taken when the tab was opened?
• Is the card still on file, or was it handed back mid-service?
• Does the tab have a name and a phone attached, or just a table number?
• Is the tab attached to a guest record, or does it disappear when the night closes?

Every one of those is a thirty-second decision at open. None of them requires confronting anyone.

The card that got handed back

This is the single most common cause, and it is almost always well-intentioned.

A guest asks for their card back mid-service. The bartender hands it over because the guest is a regular, or because refusing feels rude, or because the guest says they will settle at the end. The tab stays open. The guest leaves.

Nobody did anything wrong in a way that shows up on a report, and the tab is gone.

The workable rule is not "never return a card." It is: returning the card closes the tab. If the guest wants their card back, the tab settles at that moment and a new one opens if they keep drinking. That is one extra transaction and it removes the entire category.

It also gives the guest something they usually prefer — a settled bill and a fresh start, rather than an open number they have lost track of.

Pre-authorization and what it does not do

A lot of rooms respond to walked tabs by pre-authorizing a fixed amount on open.

That is worth doing, but be clear about what it buys. A pre-auth confirms the card is valid and holds funds. It does not guarantee the final charge will go through, it does not cover a tab that runs past the authorized amount, and the hold expires — sometimes within days, sometimes sooner depending on the issuer.

Pre-auth solves declined closes. It does not solve walks. A guest whose card was pre-authorized can still leave, and if the tab exceeded the hold you are collecting the difference from someone who is not there.

The useful version is a pre-auth plus a threshold: when a tab crosses the authorized amount, the POS flags it and the bartender either re-authorizes or settles. That turns an invisible drift into a visible moment.

The stranded tab problem

Before you spend anything on walked tabs, find out how many of yours are actually stranded.

Pull every tab that was open at close for the last month. For each one, check whether a payment exists against it. In most venues a meaningful share will have been paid — by cash, by a different card, by being merged into another tab — and simply never closed out in the system.

Those are not losses. They are reporting errors, and they are inflating the number you are about to react to.

The fix is a closing checklist that produces a zero: at close, open tabs must be zero, and any tab that cannot be settled gets recorded with a reason before the drawer counts. That single step separates real losses from paperwork, permanently.

What to do with the ones that are real

A genuine walk with a card on file is a collections question, and the answer depends on the amount and your card processor's rules.

What matters operationally is that it gets recorded against the guest, not just written off against the night.

A guest who walked a tab once is a mistake. A guest who has walked three is a pattern, and you cannot see the pattern if the record dies with the shift. When the tab is attached to a guest record, the fourth time they open one, the bartender knows before the first drink is poured.

That is not about refusing service. It is usually as simple as: this guest settles per round.

The three numbers to keep

Open tabs at close, nightly. Should be zero. Any night it is not, the reason gets written down that night, not reconstructed later.

Walked tabs by shift, monthly. Not to blame the shift. To find the procedural gap — it will be the shift where the tab-to-bartender ratio is worst, and the answer is usually staffing or a POS layout change, not discipline.

Card-on-file rate at open. The percentage of tabs opened with a card attached. This is the leading indicator; the walked-tab number follows it by about a month.

The part that has to be recorded

None of this survives on memory. The bartender who knows which guest walked last time will not be working the night it matters.

tasteck attaches tabs to guest records rather than to table numbers, so the history follows the person across visits and across staff. The closing report shows open tabs with a reason attached, which is what turns a vague monthly write-off into a list you can actually work through.

The goal is not zero walked tabs. It is knowing which of yours are real, which are paperwork, and which guest is doing it repeatedly — three questions most rooms cannot currently answer about a number they are already paying.