The short rib went down at 7:40 on a Friday. Last portion out the window, and your line cook calls it: eighty-six the short rib. You wipe it off the specials board and move on.
Thirty seconds later the printer spits a ticket. Short rib, extra sauce, no sides. Then another one. DoorDash has no idea you're out. Neither does Grubhub. Neither does the UberEats tablet buried under a stack of to-go bags on a shelf nobody's looked at since six.
So now you've got three orders for a dish that doesn't exist, three refunds on the way, and in about twenty minutes a driver is going to be at your counter asking where the food is. Every one of those turns into a one-star and a customer who figures you flaked. You didn't. You just couldn't reach the apps fast enough.
Why the apps keep selling a dish you don't have
Each delivery app runs its own menu on its own tablet. The short rib you pulled off the board in the kitchen doesn't exist to DoorDash until somebody tells DoorDash. Same for the other two. Three apps, three tablets, three separate menus that have no clue what's happening on your line.
During a rush, nobody has a free hand to pick up three tablets and dig through menu settings. So the apps keep taking the order, the kitchen keeps getting tickets it can't fill, and the gap between you being out and the app knowing you're out is where the damage lives.
What one sold-out item actually costs you
It's never just the refund. One 86'd dish that keeps selling runs up a tab:
- The refund itself. You eat the full order value, and often the app keeps its fee anyway.
- A one-star review. The customer doesn't know your kitchen ran out. They know they paid and got nothing.
- A driver standing around. They took the trip, there's no food, and that's a strike that can push you down the ranking the app shows hungry people nearby.
- Your time. Somebody has to cancel the order, message the customer, and calm down the driver, all mid-rush.
Do that three or four times on a busy Friday and you've handed back a chunk of the night's profit, plus a handful of reviews that cost you orders for weeks.
86 one item across every app in seconds
The fix is to stop managing three menus by hand. You want one place where you hit a button, mark the short rib sold out, and all three apps go dark on it at once. Two common ways to get there:
- Through your POS. If your register (point of sale, the system you ring orders on) connects to the delivery apps, you 86 the item once on the POS and it pushes to DoorDash, UberEats, and Grubhub for you.
- Through an aggregator. An aggregator is one dashboard (or one tablet) that sits on top of all three apps. You change the menu there once, and it updates everywhere.
Either way, the move takes seconds and it happens from one screen, not three. When the short rib comes back tomorrow, you flip it on the same way. Nobody has to remember which tablet is which.
Not sure whether your POS already does this? That's a two-minute phone call to whoever sold it to you. Plenty of owners are paying for the feature and never turned it on.
Slammed? Pause the whole menu, not your sanity
Some nights it's not one dish. The kitchen is thirty tickets deep, the dining room is full, and every new delivery order just makes the wait worse for everybody. That's when you want a pause button for the whole operation.
Most apps call it busy mode or pause orders. It stops new delivery orders for a set stretch (say, 30 or 45 minutes) without taking your restaurant offline for good. From one dashboard you can pause all three at once instead of fishing out each tablet.
Used right, it protects the orders you already have. Better to go quiet for half an hour than to take ten more tickets you'll send out cold and late.
Sync your hours and prices so the apps stop lying
The sold-out dish is the loud problem. The quiet one is an app promising things you can't deliver on a normal day.
- Hours. If the apps show you open until 11 but the kitchen closes at 10, you'll take orders nobody can cook. Sync your real hours once, and set them to follow holidays too, so Thanksgiving doesn't surprise you.
- Prices. When you raise the price of a platter in house, the apps should move with it. Otherwise you're selling delivery at last year's price and eating the difference on every order.
- Seasonal items. Pull the summer menu when summer ends, in one place, so it isn't still live in October taking orders you stopped making.
When your POS or aggregator drives the menu, these updates ride along automatically. You change it once where you already work, and the apps match. No more three-tablet archaeology on a Sunday night.
Where this won't save you
This is plumbing, not magic, and it's worth knowing the edges before you lean on it.
- Syncs aren't always instant. A change can take a minute or two to land everywhere, so 86 the item the moment the last one fires, not after the next ticket prints.
- A few setups still need one tablet touched by hand. Ask straight out whether yours is fully connected or only partly.
- Promotions you build inside an app (a platform discount, a free-delivery deal) usually live there, not in your POS, so you'll still manage those in the app.
- Somebody still has to push the button. The tech makes it one tap from one screen. It can't read your line cook's mind.
Getting your POS and the apps talking is a one-time job, not a nightly chore. If that sounds like one more project you don't have hands for, it's the kind of setup we wire up for NYC kitchens so you can stop living on three tablets.
Worth doing this week
- Tonight, time yourself 86'ing one item on all three tablets. If it takes more than ten seconds total, you've found a real problem.
- Call your POS vendor and ask one question: does this push menu changes and 86's to DoorDash, UberEats, and Grubhub? If yes, have them turn it on.
- If your POS can't, price out an aggregator. One dashboard over all three apps, often under a couple hundred a month, and it pays for itself the first busy Friday.
- Set your real hours and holiday hours on all three apps right now, while it's slow. Future-you, mid-rush, will be grateful.
- Show whoever runs the pass where the pause button is, so busy mode isn't a thing only you know how to find.