Voids, refunds and comps

The manager does not have to be standing there.

A void, a refund, a comp, a price override. On most systems that means finding a manager — or handing out a code that everybody ends up knowing, which is the same as having no control at all.

On the manager’s phoneAn example request, wherever they actually are

Dana · Register 2 · just now

Refund $24.60

“Wrong order sent out — customer waited 40 min”

Approve Decline

Whoever answers, it is on the record — who asked, who decided, and why.


What it does

Asked for, answered, and on the record.

It finds the manager on shift

The request goes to whoever is actually working, on their own device, with what is being asked and why — not to a shared inbox nobody reads.

Answered from wherever they are

From the office, the make line, or a watch. The point is that the queue at the counter does not wait for somebody to walk over.

The rules are yours

What needs approval, from whom, above what amount, and whether a manager may approve their own — settings, not our opinion of how your shop should run.

Every decision leaves a trail

Who asked, who approved, for how much, and why. The classic quiet losses — the no-sale drawer pop, the unexplained refund — stop being invisible.

Staff can appeal a rule

If a rule is blocking a job that genuinely needs doing, the person can ask for it to be changed rather than working around it — and the ask goes up the chain in the app.


Why it matters

Why the shared manager code is the problem.

  1. 01

    A code everybody knows is not a control

    Every shop with a manager override code has a shift where somebody watched it being typed. Once it is shared it is not an approval, it is a formality.

  2. 02

    The cost is the queue, not the void

    Waiting for a manager is a minute of somebody’s shift and three people watching it happen. That is what makes staff want a workaround.

  3. 03

    You want the trail more than the block

    Most voids are legitimate. What you actually need is to be able to look back and see the pattern — which is the thing a shared code destroys.



Book a demo

Try to get something past it.

Ask for a refund you should not get and watch where it goes and what it leaves behind.

Book a demo
  • A refund request reaching a manager on another device
  • The same request approved and recorded
  • The rule changed live, then applied
  • The trail of who asked and who said yes