Restaurant people, helping restaurant people.

What third-party delivery is really costing your restaurant

Sales volume is not the same thing as healthy margin. Here's how to add up what the platforms actually cost, and decide on purpose.

Delivery platforms did something real for independent restaurants: they put your menu in front of people who would never have found you. That part of the bargain still holds. The problem is that most operators only see one side of the ledger, the sales, while the costs scatter themselves across half a dozen places where they're hard to add up.

The costs that show up on the statement

The commission is the number everyone knows about, and it's significant on its own. But look at the rest of the statement: marketing and promotion programs you opted into during a slow month and never turned off, sponsored placement, delivery-fee subsidies, refund adjustments that come out of your side, and processing. Individually each line looks tolerable. Together they decide whether a delivery order actually made you money.

The costs that never show up on the statement

Packaging is a real cost of goods on every delivery order. And good packaging, the kind that protects your food's reputation, isn't cheap. Labor is in there too: somebody bags, checks, stages and hands off every order, usually during the same rush your dining room needs them. And there's the subtle one: the mistakes. A remade order or a refund on a delivery ticket costs you the food twice and the guest's confidence once.

Why the mix matters more than the volume

Delivery doesn't just add orders, it changes what people order. Items that travel well get more popular; items with your best margins may not be the ones that travel well. If your delivery mix leans toward lower-margin items, while carrying commissions and packaging on top, a great delivery week can quietly be your worst-earning week. Volume feels like health. Contribution is health.

What deliberate operators do differently

They price the delivery menu for the channel it lives in, rather than copying the dine-in menu and donating the difference. They trim the delivery menu to items that travel, execute cleanly and carry margin. They review every promotion the way they'd review a new hire: is it still doing the job it was hired for? They push regulars, gently and consistently, toward ordering direct. And they read the platform statement monthly, all of it, the way they read the P&L.

None of this says get off the platforms. It says know what they cost, decide on purpose, and make the channel earn its keep like everything else in the building.

Working through this in your own restaurant? Start a conversation. If we can help, we'll tell you how.

When food costs move faster than your menu prices

Old recipe costs are nostalgia. A practical way to re-cost, re-portion, re-source and, only then, reprice.

Every operator knows the feeling: the invoices creep up week after week, but the menu got priced last spring. For a while you absorb it. Then one day you cost out a dish you sell fifty times a week and realize you've been making a few points less on it than you thought. For months.

Old recipe costs are the quiet danger

A recipe costing from a year ago isn't information, it's nostalgia. When ingredient prices move, the menu's economics move with them whether you're watching or not. The operators who stay ahead re-cost their top movers on a schedule. Not the whole book every week, just the items that carry the volume, because that's where a small drift becomes real money.

Percentages lie a little; dollars don't

Food-cost percentage is a useful habit, but it can steer you wrong on its own. A dish with a higher percentage can put more actual dollars in the drawer than a "better" one. Contribution margin is what pays the rent. Before repricing anything, know both numbers for your best sellers: what it costs as a percentage, and what it leaves behind in dollars.

Three levers, not one

Price is the lever everyone reaches for first, and sometimes it's right. But there are usually two quieter levers worth pulling first. Portion and spec: is the drift on the plate, not the invoice? A half-ounce of protein creep across a busy month is a real number. And sourcing: is this ingredient worth a conversation with a second vendor, a substitution the guest will never notice, or a make-versus-buy look? The best pricing decision is often the one you avoid needing.

When you do reprice

Reprice deliberately, not defensively. Move the items whose value the guest already believes in. Round to price points that read naturally. Watch the mix afterward. If an item's orders hold, the guest just told you something. If a dish can't carry an honest price anymore, that's not a pricing problem; that's menu engineering telling you the item may not belong. And a shorter menu that executes beautifully usually out-earns a long one that limps.

Costs moving is the weather; it's not an emergency. The emergency is not looking. A menu that gets honest attention every month doesn't need panic pricing in any single week.

Working through this in your own restaurant? Start a conversation. If we can help, we'll tell you how.

The owner is every department

At a big property there's a purchasing department, an HR department, an IT department, a marketing team. At an independent restaurant, all of those departments have the same name: yours.

Spend years inside large hotels and casinos and you learn something that independent owners feel every day without anyone naming it. When the POS goes down at a resort, somebody calls IT and goes back to work. When a supplier raises prices, purchasing handles the negotiation. When a cook quits, HR posts the job, screens the stack, runs the paperwork. The restaurant keeps being a restaurant because a building full of specialists is holding it up.

Now take away the building. The food is still excellent. The room is still warm. But the POS outage, the price increase and the open shift all belong to one person, usually between lunch and dinner.

Count your departments

Walk through an ordinary week. You negotiated with a vendor: that was the purchasing department. You interviewed a server and fixed a payroll issue: human resources. You argued with the internet company and updated the online menu: IT. You posted three times and answered reviews: marketing. You repriced two items after the invoice came in heavy: finance. You retrained a busser: the training department. Somewhere in there you also cooked, hosted, expedited and mopped.

None of that is failure. That's the actual job description of an independent owner, and nobody hands it to you when you sign the lease.

The trap is doing every job from scratch

The departments aren't the problem. The problem is running each one from a blank page, at eleven at night, in the fifteen minutes that department gets this week. The big properties don't out-cook you. They out-system you. Their departments run on order guides, checklists, templates, calendars and specs, so no decision starts from zero twice.

What shrinks the load

Systems shrink departments. An order guide turns purchasing from a negotiation into a routine. A real onboarding checklist turns hiring from a scramble into a sequence. A simple content calendar turns marketing from guilt into an hour on Tuesday. And borrowed help shrinks them further: a vendor who does part of the work, a peer who already solved it, or someone who has run these departments before and can set yours up so they run lighter. That's most of what consulting honestly is.

You opened this restaurant because of the food and the people, not because you wanted to run six departments before noon. The departments come with the dream. Carrying all of them alone doesn't have to.

Wearing too many of these hats this week? Start a conversation. If we can help, we'll tell you how.

The restaurant tech stack problem: when your systems don't talk to each other

POS, ordering, delivery, reporting, website: each made sense on its own. Together they became a part-time job. How to untangle it.

Walk into most independent restaurants and you'll find a POS from one company, online ordering from another, two or three delivery tablets, a reservation tool, a loyalty program someone signed up for at a trade show, and a website built by whoever built it. Each one made sense on the day it arrived. Together, they've become their own part-time job.

How you know the stack is broken

The signs are familiar. Somebody retypes delivery orders into the POS. The menu lives in four places and matches in none of them. Change a price and you get to change it four times. The "reporting" is three logins and a spreadsheet where a manager glues numbers together on Monday. And when something misbehaves, every vendor is sure the problem belongs to one of the others.

The real cost isn't the subscriptions

The monthly fees sting, but the deeper costs are operational: hours of duplicate data entry, orders lost in the gaps between systems, decisions made late because the numbers took a week to assemble, and a team that quietly stops trusting the tools. A disconnected stack doesn't just cost money. It hides information you need to run the business.

Fewer, better-connected systems

The direction of travel is almost always the same: fewer platforms, chosen for how well they talk to each other, anchored by the POS as the system of record. That doesn't automatically mean switching everything. Sometimes the fix is configuring what you already own properly, turning on an integration nobody set up, or dropping the one tool that duplicates another. Rip-and-replace is the last resort, not the first instinct.

Questions to ask before adding anything new

Does it integrate with the POS directly, or through promises? Where does the menu live, and how many places will a price change touch? What does the reporting actually show, and can the people who need it get to it without a ritual? What happens on day one when it breaks: who do you call, and will they point at someone else? And the quiet one: what is this replacing? If the answer is nothing, the stack just got heavier.

Restaurant technology should feel like a quiet employee who never calls out, not a second dining room full of demanding guests. If the systems are running you, it's worth an afternoon to draw the map and start untangling.

Working through this in your own restaurant? Start a conversation. If we can help, we'll tell you how.