Every venue that rolls out QR ordering eventually has the same meeting. Revenue is up, the queue is shorter, and a group of servers wants to know where their tips went.
It is a fair question and most operators are unprepared for it, because tip policy was written for a world where one identifiable person took the order, delivered it and was thanked. Self-service ordering breaks all three links. The guest orders themselves, a runner may deliver, and the thank you goes to a payment screen.
This is the part of mobile ordering that vendors do not want to discuss and that determines whether your rollout is welcomed or resented. It is worth getting right before launch rather than after the first payout.
The Federal Rules, Plainly
Start with what the law actually says, because a surprising amount of venue tip policy is inherited rather than checked. The Department of Labor's tip regulations under the Fair Labor Standards Act set the floor, and state law can be stricter.
The core provisions from the 2020 Tip Final Rule, which took effect on 30 April 2021:
- An employer cannot keep employees' tips under any circumstances. There is no exception for administrative cost, breakage or credit card fees at the federal level.
- Managers and supervisors may not keep tips received by employees, including through tip pools. They are not prohibited from contributing to a mandatory pool, and they may keep tips a customer gives them directly for a service the manager or supervisor directly and solely provided.
- An employer that does not take a tip credit may include non-tipped employees in the pool. Cooks and dishwashers are the examples the Department itself uses.
- A mandatory pool the employer collects generally must be fully redistributed within the pay period. Holding tips across periods is not permitted.
One more piece of history matters because it is frequently cited as current and is not. The 2021 Dual Jobs Rule, effective 28 December 2021, required tipped employees to receive full minimum wage whenever untipped supporting work exceeded 20 percent of the workweek or 30 continuous minutes. On 29 October 2024 a federal court vacated that revision, reinstating the Department's original dual jobs regulation. If your policy documentation still references an 80/20 test as binding federal law, it is out of date.
This is not legal advice
The summary above reflects the Department of Labor's published guidance, including Fact Sheet 15. Tip law varies materially by state, several states prohibit tip credits entirely, and enforcement actions in this area are common. Have counsel review any policy change before you implement it.
Why QR Ordering Breaks the Old Assumption
Traditional tip allocation rests on attribution: the tip belongs to whoever served the guest, possibly shared with support staff who made that service possible. Self-service ordering scrambles the attribution in three distinct ways.
The order has no taker
Nobody wrote it down. The guest entered it. Whatever work went into that transaction was done by whoever set up the location, keeps the area stocked and delivers the item.
The service is now split
Production happens in the kitchen. Delivery happens by whoever is available and nearest, which with routed assignment may be a different person each time. There is no single server who owns the table for the night.
The tip arrives detached
A tip entered on a payment screen belongs to the transaction rather than to a person. Somebody has to decide who it belongs to, and if no one decides explicitly, the default will feel arbitrary to staff.
Three Models That Work
There is no universally correct answer, but there are three defensible structures, and the choice should be driven by how your service actually runs.
| Model | How it allocates | Suits | Weakness |
|---|---|---|---|
| Assigned location credit | Tip goes to the staff member assigned to that seat, suite or cabana at the time of the order | Premium areas with dedicated coverage | Breaks down when coverage is dynamic or someone else delivers |
| Area and shift pool | All tips from an area pooled and split across staff working that area that shift, usually by hours | General admission, concourses, in-seat service | Strong performers subsidise weaker ones, which needs managing |
| Outlet-wide pool including support | All tips pooled across front and back of house per the applicable rules | Operations where production quality drives the guest experience | Most exposed to compliance error, and the least intuitive to servers |
The practical guidance from watching venues do this: match the pool boundary to the unit of teamwork. If a guest's experience in a suite depends on one attendant, credit that attendant. If it depends on four people covering a concourse together, pool the concourse. Policies that cut across how the work is actually organised are the ones that generate grievances.
The Design Details That Decide Whether Staff Accept It
Compliance keeps you out of trouble. These details decide whether the rollout is welcomed.
- Decide before launch and say so in writing - The worst version is launching QR ordering, letting tips accumulate, and then deciding. By then everyone has formed an expectation and any answer disappoints someone.
- Show staff the tip data - Per-transaction tip rates by location, visible to the people affected. Suspicion thrives on opacity, and the numbers are usually less alarming than people assume.
- Do not let the technology look like the cause of a pay cut - If QR ordering shifts volume away from a tipped role, address that directly and in advance. Staff who feel the tool took money from them will find ways to route guests away from it, and they are very good at this.
- Be deliberate about the prompt - Default tip percentages, whether tipping is presented before or after the total, and whether a convenience fee appears alongside it all measurably change behaviour. Listo's Mobile Order and Pay carries a fixed one dollar per transaction fee that can be paid by the guest or absorbed by the operator, and that choice is worth making consciously.
- Audit the pool quarterly - Confirm nobody excluded by the rules is receiving from the pool, and that distribution is happening within the pay period. Enforcement in this area is active and back-pay findings are common.
What Happens to Tips When Service Gets Faster
There is a version of this conversation that goes better, and it is worth knowing it exists.
Tips scale with volume as well as with rate. If faster service means a guest orders three times instead of twice, the tipped total can rise even if the percentage per transaction falls. At Ford Field, Levy reports each Listo service request generates more than 100 dollars in food and beverage revenue. At Great Wolf Lodge Niagara, cabana revenue rose 30 percent and average guest spend rose 9 percent after deployment. On volume like that, a well-designed pool can leave staff better off, and demonstrating this with your own data in the first month is the single most effective thing you can do to build support.
The reverse is also true, and worth saying plainly. If you introduce self-service without addressing allocation, tipped staff will conclude the change was made at their expense, and in many cases they will be right.
The Runner Problem Nobody Solves in Advance
There is one allocation question that comes up in almost every venue rollout and is almost never anticipated: the person who delivers a QR order is frequently not the person assigned to that location.
This is a direct consequence of routing working properly. If a request goes to the nearest available staff member rather than to a fixed section owner, then over a busy night deliveries get distributed across whoever had capacity. That is exactly what you want operationally and it makes location-based tip credit incoherent, because the credited person may have delivered none of the orders.
Three workable responses. Credit the deliverer rather than the location, which is the most defensible and requires that your system record who completed each task. Pool by area and split by hours worked, which accepts the ambiguity rather than fighting it. Or restrict dynamic routing in premium areas specifically, keeping fixed ownership where tips are largest and letting routing float everywhere else.
The reason to decide this deliberately is that the data exists either way. A platform that records who accepted and completed each request has an answer to who did the work. If your policy does not use that data, staff will eventually ask why not, and the version where you have to reconstruct it retroactively is considerably worse than the version where you set the rule up front.
Multi-State Operators and the Complication of Scale
For groups running venues in several states, the temptation is a single national tip policy. It rarely survives contact with the detail.
Several states prohibit the tip credit entirely, which changes who may be included in a pool. Some set higher minimum cash wages for tipped employees. Some regulate mandatory service charges and their disclosure specifically. A few have their own rules about what may be deducted from credit card tips. A policy that is compliant in one state can be a back-pay exposure in another while looking identical on paper.
The practical approach used by the larger concessionaires is a common framework with state-level schedules: one document describing the pool structure, allocation basis and reporting, plus an appendix per jurisdiction covering minimum cash wage, credit eligibility, permitted pool participants and service charge treatment. It is more work to maintain and it is the only version that survives an audit.
Worth flagging for anyone operating under a concessions contract: your agreement with the venue may itself constrain tip and service charge treatment, and those clauses are easy to overlook when the operating team designs a policy independently of the people who signed the contract.
Service Charges Are a Different Instrument
Some venues respond to this by replacing tips with a mandatory service charge, and it is worth understanding what that actually changes.
A mandatory service charge is generally not a tip. It is revenue to the business, which means the employer can distribute it at their discretion, including to managers, and the tip pooling restrictions do not apply in the same way. That flexibility is why operators like it. The trade-offs are that guests notice, some resent it, and staff income becomes a function of your distribution policy rather than of guest generosity, which cuts both ways.
If you go this route, the details that matter are disclosure to the guest, clarity to staff about how distribution works, and correct treatment for wage and overtime purposes, since service charge distributions are typically wages rather than tips. This is squarely a question for counsel and your payroll provider rather than something to design from a blog post.
A Short Checklist Before You Launch
- Written policy, dated, stating who is in each pool and on what basis it splits.
- Confirmation that no manager or supervisor receives from a pool.
- Confirmation that distribution happens inside the pay period.
- State law reviewed, particularly if you operate in more than one.
- Tip prompt design decided, including default percentage and fee presentation.
- A first-month reporting plan showing staff what actually happened.
- Counsel sign-off before the first guest scans anything.
None of this is exciting work and all of it is cheaper than the alternative. We cover the guest-side mechanics of QR ordering, pre-ordering and payment on our Mobile Order and Pay page, and the operational trade-offs between self-service and staffed service in our comparison of Listo and mobile ordering.
Frequently Asked Questions
Who gets the tip when a guest orders through a QR code?
That is a policy decision, not a technical one, and it should be made deliberately. The three workable models are crediting the staff member assigned to that location, pooling by area and shift, or pooling across the whole outlet. What matters legally is who is in the pool and who is excluded, and what matters practically is whether staff believe the split reflects the work.
Can an employer keep any part of a tip?
No. Under the Department of Labor's tip regulations, an employer cannot keep employees' tips under any circumstances. Managers and supervisors also may not keep tips received by employees, including through tip pools, although they are not prohibited from contributing to a mandatory pool. A manager or supervisor may only keep tips they receive directly from a customer for a service they directly and solely provided.
Can back-of-house staff be included in a tip pool?
Under the 2020 Tip Final Rule, an employer that does not take a tip credit may include employees who are not tipped employees, such as cooks and dishwashers, in a tip pool. The rules differ depending on whether a tip credit is taken, so this is worth confirming against the current regulation and your state law before changing anything.
What happened to the 80/20 rule?
The 2021 Dual Jobs Rule required tipped employees to receive the full minimum wage whenever untipped supporting work exceeded 20 percent of the workweek or 30 continuous minutes. It took effect on 28 December 2021. On 29 October 2024 a federal court vacated that revision, which reinstated the Department's original dual jobs regulation.
Does mobile ordering reduce tips?
It changes where they come from rather than removing them. Guests tipping through a payment screen tip at rates that depend heavily on how the prompt is designed and what the default is. The risk is not that guests stop tipping. It is that the revenue arrives detached from any individual, and if you have no policy it will feel to staff like the technology took their income.
Should the operator or the guest pay the transaction fee?
Either is workable and the choice affects perception more than economics. Listo's Mobile Order and Pay carries a fixed one dollar per transaction convenience fee that can be paid by the guest or absorbed by the operator. Making it visible to the guest alongside a tip prompt is worth thinking through, because two additions to a total read differently from one.
.png)