How to track comps and voids at a bar without accusing anyone

Track comps and voids by person, shift and reason every week, and require a reason and an approver on every one. That is the whole method. The rest of this piece is how to run it so it finds money without turning the bar into a courtroom.

What is the difference between a comp and a void?

They get lumped together, and they should not be. Toast's own support documentation draws the line clearly: a comp waives the charge for an item the guest received but is not paying for, and a void removes an item, check or payment as if it never happened.

That difference matters because the two go wrong in different ways.

A comp is a real drink that really left the bar. It costs you the product and the sale. A comp with a good reason is hospitality. A comp with no reason is a drink you gave away without deciding to.

A void should mean the drink was never made: a wrong button, a guest who changed their mind before the pour. A void on something that was made and served is not a correction. It is a comp recorded as if the drink never existed, and it disappears from the numbers that would have told you.

Why one night's numbers tell you nothing

A busy Saturday with a birthday table, a spilled round and a regular who got looked after will show a lot of comps. That night is fine. Looking at it alone invites exactly the wrong conversation.

The signal is the pattern across weeks. The same bartender, the same shift, the same reason, or no reason at all, repeating. One high night is noise. The same shape for six weeks is a process, and a process can be changed.

This is the same logic as calculating bar variance: the number points you at a place to look, and the explanation is what recovers the money.

The four patterns worth a question

1. Voids after the drink was served

Voids clustered late in a check, or after a payment, are worth a look. Most will be honest corrections. The ones that are not are usually a comp someone did not want to ask for.

2. Comps with no reason

A blank or catch-all reason means nobody decided anything. Fix the setup before you judge the people: if the reason list does not fit how the bar actually works, staff will pick whatever is first.

3. One person far from the team

Compare each bartender against colleagues on comparable shifts, not against the venue average. A Friday closer and a Tuesday opener should not be held to the same number. The person at the far end of the distribution is a conversation, not a conclusion.

4. Approvals that are not really approvals

If one manager code approves every comp from one terminal in one hour, the approval step exists on paper only. Toast, for example, lets you remove the void permission from a server job so that a manager has to complete the void. That control only works if the manager is actually looking.

Set up the POS before you review anything

A review is only as good as what the register records. Three settings do most of the work.

• Reasons are required. A short list that matches real situations: guest recovery, regular, staff error, kitchen or bar error, manager decision. Void reasons in Toast have to be configured before staff can select them.
• Approval is required above a threshold you choose. Low enough to catch the pattern, high enough that the bar can still look after a guest without a manager hunt.
• Reports are turned on. Square, for example, has comp and void reports that track items removed from bills, but comp and void have to be enabled first.

A weekly review that fits in one sitting

Run it on the same day every week, as part of the weekly operating rhythm.

1. Pull last week's comp and void report by employee, shift and reason.
2. Mark anything unexplained: no reason, a void after payment, an approval that does not fit the timeline.
3. Compare each person with their comparable shifts, not with the whole bar.
4. Pick one thing to ask about, and write down who will ask and by when.
5. Check last week's question. Did the pattern change? If you never check, the review becomes a ritual.

How to have the conversation

Open with the pattern and a question, never a charge. "Your Tuesday voids after close have been higher for a month. Walk me through a couple of them." Most of the time the answer is a training gap, a broken reason list or a guest situation nobody told the manager about. All three are fixable, and none of them needed an accusation.

This is the same principle as fair, visible accountability: when everyone knows the numbers are reviewed the same way for everyone, the numbers tend to improve before anyone is spoken to.

Where software helps, and where it does not

Everything above can be run by hand from the reports your POS already has. Do it by hand first. You will learn what you actually want from a tool.

Software earns its place when the review stops happening because nobody has the hour, or when you run more than one venue and need the same standard everywhere. CoreTAP reads comps and voids per person and shift from the POS and routes the pattern to the manager who can ask about it. If you already run this review every week and act on it, you are getting most of the value without us.