How to Automate Tip Pooling with Toast POS (Step-by-Step)

If you're running a restaurant on Toast POS and still calculating tip pools by hand — on paper, in a spreadsheet, or on a calculator at the end of every shift — I feel you. I was doing the same thing at Pizza Harbour for months before I decided there had to be a better way.

The math isn't hard. I covered exactly how tip pooling calculations work in my guide to calculating tip pools. The problem isn't the math — it's doing it every single day, accurately, under pressure, at the end of a long shift when you just want to go home. That's where mistakes happen. That's where money gets lost. And that's where automation changes everything.

This post walks you through how to go from manual tip pooling to automated tip pooling when you're using Toast as your POS. I'll cover what Toast can and can't do natively, where the gaps are, and how we solved it at Pizza Harbour.

What Toast POS Gives You Out of the Box

Let's give Toast credit where it's due — it captures a lot of the data you need for tip pooling. When employees clock in and out through Toast, you've got their hours. When customers pay and leave tips on credit cards, Toast captures those amounts. When servers close out their checks, the tip data is right there in the system.

The problem is that capturing tip data and calculating tip pool distributions are two very different things.

Toast does offer a product called Toast Tips Manager, which handles tip pooling and distribution. If you're already paying for the full Toast ecosystem — payroll, scheduling, the works — Tips Manager might make sense for you. But for a lot of independent restaurants, especially smaller operations like mine, adding another Toast module means another monthly cost on top of what's already a growing bill.

And if you're not on Toast Payroll, the integration story gets more complicated. You end up exporting data, importing it somewhere else, and the "automation" starts feeling a lot like extra steps with extra software.

The Manual Tip Pooling Problem

Here's what manual tip pooling looked like for me at Pizza Harbour before I automated it:

End of every shift: Pull up the Toast sales summary. Write down total tips collected for carryout orders (delivery tips go straight to drivers — I explained our model in my tip outs vs tip pooling post). Then pull up time entries to see who worked and for how long. Then grab a calculator.

Now apply the weighting formula. Employee A worked 6 hours at 100% weight. Employee B worked 4 hours at 50% weight. Employee C worked 8 hours at 80% weight. Calculate the weighted hours, divide the pool, figure out what each person gets. Write it down. Double-check the math because it needs to add up to the penny. (If you want to see this calculation in action, try our free tip pool calculator.)

Total time: 15–20 minutes on a good night. Longer if there were shift changes, early clock-outs, or any discrepancies between what Toast says and what actually happened.

Per week: That's roughly 2 hours of manager time just on tip calculations.

Per month: 8+ hours.

Per year: Nearly 100 hours spent on something a computer should be doing.

And that's assuming you never make a mistake. Which you will. Because you're tired, it's 11 PM, and you've been on your feet for 10 hours. When tip calculations are wrong, you either overpay (costing you money) or underpay (costing you trust with your team). Neither is acceptable.

What You Actually Need to Automate Tip Pooling

To go from manual to automated, you need a system that can do four things:

1. Pull tip data from your POS automatically. No exporting CSVs. No copy-pasting. The system connects to Toast and pulls credit card tips and auto-gratuities automatically — broken out by order type, revenue center, or whatever categories matter to your tip pool rules. For cash tips, employees declare them directly in the AnchOps mobile app, specifying what they're taking home and what goes to the pool.

2. Pull hours worked from your time clock. The system needs to know who worked, what role they worked, and exactly how many hours they clocked. This is critical for any hours-based or weighted distribution model.

3. Apply your specific tip pool rules. Every restaurant is different. At Pizza Harbour, delivery tips go to drivers, carryout tips go into the pool, and the pool is distributed by weighted hours. Your restaurant might have a completely different model — maybe servers tip out to bussers at a flat percentage, or you run a straight equal split. The system needs to be flexible enough to handle your rules, not force you into a one-size-fits-all model.

4. Calculate distributions automatically and accurately. Down to the penny, every shift, with no manual intervention. And produce a record you can reference later for payroll, for taxes, and for any employee who has a question about their tips.

How We Solved It at Pizza Harbour

Full disclosure — this problem is literally why I built AnchOps. I was spending hours every week on tip calculations that should have taken zero time, and I couldn't find a solution that worked for my specific setup without buying into a full enterprise software suite.

Here's how it works now:

AnchOps connects to our Toast POS. It automatically pulls in order data, payment data, and tip amounts. I don't export anything. I don't log into Toast to pull reports. The data flows over automatically.

It pulls hours from our time clock. Every employee's clock-in, clock-out, and role assignment comes through. If someone worked as both a cook and a cashier in the same shift (which happens at a small operation like ours), the system knows.

I configured our tip pool rules once. Delivery tips go to drivers — excluded from the pool. Carryout tips go into the pool. The pool distributes by weighted hours, with each role assigned a specific weight. I set this up when I first connected AnchOps, and I haven't touched it since. If you're running a hybrid delivery operation with First Delivery, the tip routing gets even more complex — here's how to manage delivery driver tips with First Delivery and Toast.

Every day, the calculations just happen. I can see exactly what each employee earned in pooled tips, how it was calculated, and what the total distribution looks like. No spreadsheets. No 11 PM calculator sessions. No math errors that I have to fix the next day.

The time savings alone justified it. But the real win was accuracy and trust. My team can see their tip earnings clearly, and they know the math is consistent every single shift. That matters more than most owners realize — inconsistent or opaque tip calculations are one of the fastest ways to lose good employees.

What If You're Not Ready to Switch Tools?

I get it — maybe you're not ready to add another tool right now. If you want to make your manual process better while you're on Toast, here are some practical tips:

Build a spreadsheet template. Don't start from scratch every night. Create a Google Sheet or Excel template with your employees, roles, weights, and formulas already built in. All you need to enter each night is hours worked and total tips. I did this for months before building AnchOps — it's not perfect, but it's better than a blank page and a calculator.

Use Toast's labor reports to speed up data collection. Instead of manually checking each employee's time entry, pull the daily labor summary from Toast. It'll show you everyone who worked and their total hours. That saves you the most tedious part of the manual process.

Document your tip pool policy and share it with your team. Whatever method you use, write it down. Post it. Train on it. Half the tip disputes I've seen come from employees not understanding how the pool works, not from the math being wrong. I wrote a full guide on how to structure your tip pool policy if you need help here.

Audit yourself weekly. Pick one day per week and re-check that week's calculations from scratch. If you're making errors, you'll catch them before they compound. And if your math is clean, you'll sleep better knowing it.

The Cost of Doing Nothing

Let's be real about the cost of keeping tip pooling manual:

Time cost: 8–10 hours per month of manager time. What else could you do with those hours? Menu development? Marketing? Actually being present in your restaurant during service instead of hunched over a spreadsheet in the back office? You could be budgeting labor before you post the schedule instead of calculating tips after the fact.

Error cost: Even a small miscalculation — $5 per employee per shift — adds up to hundreds per month across your team. Sometimes it's in your favor, sometimes it's not. But the inconsistency itself is the problem.

Trust cost: This is the one nobody talks about. When employees don't trust that their tips are being calculated fairly, they disengage. They start watching the clock. They leave for the restaurant down the street that uses a transparent, automated system. In a labor market where good restaurant employees are hard to find, tip transparency isn't a nice-to-have. It's retention strategy.

Compliance cost: If your tip pool calculations are inconsistent or undocumented, you're exposed. If an employee files a complaint or your state's department of labor comes knocking, "I did it by hand every night" is not a strong defense. Automated, documented records are.

Wrapping Up

Toast POS captures the data you need for tip pooling. The gap is in turning that data into accurate, consistent distributions without burning hours of manager time every week. You can close that gap with a good spreadsheet, with Toast's own Tips Manager product, or with a purpose-built tool like AnchOps.

Whatever you choose, stop doing this on a calculator at 11 PM. Your time is worth more than that, and your team deserves better than math done on fumes. And if you're deducting credit card processing fees from tips, make sure you're doing it right — here's what the law says about credit card tip deductions.