How to Manage Delivery Driver Tips with First Delivery and Toast POS

If you're running delivery through First Delivery — using a mix of your own in-house drivers and third-party networks like DoorDash and Uber Eats — you already know how powerful that setup is. You get the best of both worlds: your own drivers for the orders that matter most, and overflow capacity from third-party fleets when you need it.

What you might also know is that tip management just got a lot more complicated.

At Pizza Harbour, switching to First Delivery was transformative for our delivery operation. We could send orders out with our own drivers when they were available and seamlessly route overflow to third-party networks — all from one platform. But the tip reconciliation that came with it? That nearly broke us.

The Tip Problem Nobody Warns You About

Here's what happens when you run a hybrid delivery operation through First Delivery:

Third-party deliveries (DoorDash, Uber, etc.): The customer tips through the ordering platform. First Delivery handles paying the third-party driver. The store never touches that tip. Clean and simple.

In-house deliveries: The customer tips on the order, and that tip needs to go directly to your driver. The store is responsible for making sure that happens.

Now here's where it gets messy. At the end of every day, you've got a mix of orders — some delivered by your team, some delivered by third-party drivers. The tips associated with those orders need to be routed completely differently. In-house driver tips go to your drivers. Third-party driver tips are already handled by First Delivery. And if you're also running a tip pool for your in-store team on carryout and dine-in orders, you need to make sure delivery tips don't accidentally end up in that pool.

Before I automated this, here's what reconciliation looked like at Pizza Harbour:

Step 1: Pull up the First Delivery dashboard. Figure out which orders went to in-house drivers vs. third-party.

Step 2: Cross-reference with Toast to see the tip amounts on each order.

Step 3: Separate in-house delivery tips from third-party delivery tips.

Step 4: Make sure in-house driver tips are allocated to the right driver.

Step 5: Make sure third-party delivery tips are excluded from any store-side calculations.

Step 6: Calculate the in-store tip pool separately, making sure only carryout and dine-in tips are included.

Step 7: Double-check everything because one wrong sort means a driver gets shorted or overpaid.

Every night. After a full shift. When you're exhausted and just want to go home.

And the volume matters. On a busy Friday night at Pizza Harbour, we might run 20-30 deliveries — some in-house, some third-party. That's 20-30 individual tip transactions that need to be routed to the right person or excluded from the pool entirely. Miss one and the math is off for everyone.

Why This Is Harder Than Regular Tip Management

If you're running a restaurant without delivery, or with only in-house delivery, tip management is straightforward. Tips come in through Toast, you distribute them according to your rules, and you're done. I wrote a full guide on how to automate that process.

But First Delivery adds a layer that Toast alone can't handle. Toast sees every order and every tip. It doesn't inherently know which deliveries were fulfilled by your driver vs. a DoorDash driver. So if you're pulling tip reports from Toast, you're looking at a combined number that includes tips you don't need to pay out — because First Delivery already handled them.

That means you need a system that can talk to both Toast and First Delivery, understand which orders went where, and route tips accordingly. Without that, you're doing it manually. And manually means errors.

How We Solved It at Pizza Harbour

This is one of the core reasons I built AnchOps. The tip reconciliation problem with First Delivery and Toast was costing me hours every week and I knew it was only a matter of time before a mistake caused a real issue with my team.

Here's how it works now:

AnchOps connects to both Toast POS and First Delivery. It pulls order data, tip data, and delivery assignment data from both systems automatically.

It knows which deliveries were in-house and which were third-party. Because AnchOps has visibility into First Delivery's routing, it automatically identifies which orders were fulfilled by your drivers and which were sent to DoorDash, Uber, or another network.

In-house driver tips go directly to the driver. No manual sorting. No cross-referencing dashboards. AnchOps sees that Order #1234 was delivered by your driver Mike, and the $5 tip on that order goes to Mike.

Third-party delivery tips are automatically excluded. AnchOps knows that Order #1235 was delivered by a DoorDash driver, so it excludes that tip from any store-side calculations. First Delivery already handled paying that driver — the store doesn't need to touch it.

The in-store tip pool stays clean. Carryout and dine-in tips go into the pool. Delivery tips stay out. The pool distributes according to whatever rules you've configured — by weighted hours, by role, however your restaurant operates. I covered how to set up your tip pool rules here.

All of this happens automatically, every day. I don't reconcile anything. I don't cross-reference dashboards. I don't sort orders by delivery type. AnchOps handles it, and I can see the full breakdown anytime I want.

The Numbers

Let me put this in perspective:

Manual reconciliation time: 20-30 minutes per day on a busy delivery night. That's 2-3 hours per week, 8-12 hours per month.

Error risk: Even one misrouted tip per shift — say a $7 third-party delivery tip accidentally gets included in your in-store pool — throws off every employee's payout for that shift. Multiply that across a week and you've got angry employees and a trust problem.

With AnchOps: Zero minutes on tip reconciliation. Zero errors from manual sorting. Every tip routed correctly, every shift, automatically.

What If You're Not Using First Delivery Yet?

If you're dispatching deliveries to third-party networks like DoorDash, Uber Eats, and Grubhub without First Delivery, you're probably juggling multiple apps — switching between tabs, re-keying delivery information, and manually managing which orders go to which network. It's slow, error-prone, and it gets worse as your delivery volume grows.

First Delivery centralizes all of that. One platform to dispatch to your in-house drivers or any third-party network, without needing a separate app open for each one. No re-keying addresses. No copy-pasting order details. Just route the delivery and move on.

It was a game-changer for our delivery operation at Pizza Harbour. But if you're considering First Delivery, know that tip management complexity comes with running a hybrid fleet. That's not a reason not to switch — the operational efficiency gains are massive. It's just something you should plan for. And ideally, automate from day one.

What If You're Using First Delivery Without AnchOps?

If you're already on First Delivery and Toast but handling tips manually, here are some tips to make the process less painful:

Build a daily reconciliation spreadsheet. Create columns for order number, delivery type (in-house vs. third-party), tip amount, and driver name. Fill it in at the end of each shift. It's tedious, but it gives you a clear record.

Use First Delivery's reporting to identify delivery assignments. First Delivery's dashboard shows you which orders went to which fleet. Use this as your source of truth for sorting tips.

Never pull total tip numbers from Toast alone. Toast will show you all tips including third-party delivery tips that you don't need to pay. Always cross-reference with First Delivery data before calculating any distributions.

Audit weekly. Pick one day per week and re-check that week's tip routing from scratch. Catch errors before they compound.

Wrapping Up

Running a hybrid delivery operation through First Delivery and Toast is one of the smartest moves an independent restaurant can make. The savings on delivery commissions alone make it worthwhile. But the tip management complexity it creates is real — and it's a time sink that grows with your delivery volume.

You can manage it manually with spreadsheets and cross-referencing. Or you can let AnchOps connect to both systems and handle the routing automatically — in-house driver tips to your drivers, third-party tips excluded, and your in-store pool calculated cleanly.

However you handle it, don't ignore the problem. Inaccurate tip distributions cost you trust with your team, and in a labor market where good restaurant employees are hard to find, that trust matters more than most owners realize.