25 August 2026 · TechSlideITS
Running a restaurant across dine-in, takeaway and delivery
Three channels sharing one kitchen is now normal. The operational problems it creates are not, and most of them show up as timing.
A kitchen that once served one room now serves three channels with different expectations. Dine-in guests are watching. Takeaway customers are waiting nearby. Delivery orders are on a clock nobody in the restaurant controls.
Most of the resulting problems present as timing, and most are actually sequencing.
Priority is a decision, not an accident
When three orders arrive together, the kitchen decides an order of work — and if nobody has set a rule, that decision is made per ticket by whoever is at the pass.
The choices are legitimate but different. Delivery has an external clock and a rating attached. Dine-in has a guest watching the door. Takeaway sits between.
What matters is that the rule is explicit and understood, because an implicit rule produces inconsistency and makes every channel occasionally feel deprioritised.
Packing is a stage nobody plans for
A dine-in dish is finished when it is plated. A delivery order is finished when it is packed, checked, labelled and handed over — and that stage frequently has no dedicated person or space.
The result is packing happening at the pass, competing with plating, during service. Where delivery volume is meaningful, a separate packing point is usually the highest-return change available, and it requires space rather than software.
Manual aggregator entry
Orders arriving on a platform tablet and being typed into the POS by hand during service costs time and introduces errors in exactly the situation where an error is most expensive — the customer is remote, the mistake is discovered after delivery, and the resolution is a refund and a rating.
Whether integration is worth it depends on volume. Below a certain share, it solves a problem you do not really have. Above it, manual entry is a tax on every order.
Channel-wise profitability, which is the real question
Delivery revenue is not comparable to dine-in revenue. Commission, packaging and discounts come off it, and none apply to a dine-in cover.
Comparing gross revenue by channel therefore flatters delivery. The comparison worth making is contribution after channel-specific costs — commission, packaging, promotional discounts — against the kitchen capacity each channel consumes.
Restaurants that run this calculation sometimes find a channel is buying revenue rather than profit. That does not necessarily mean stopping; it might be worth it for reach. But it should be a decision rather than a discovery.
What to measure per channel
- Order to ready time, separately for each channel
- Packing time for delivery and takeaway specifically
- Order accuracy, since remote errors cost more than nearby ones
- Contribution after channel costs, not gross revenue
- Share of kitchen capacity consumed at peak by each channel
The menu question
Not every dish travels. Items that arrive soggy, separated or cold generate complaints, refunds and poor ratings that attach to the restaurant rather than to the dish.
A delivery menu that is a subset of the dine-in menu is a common and sensible answer. It is a smaller decision than it sounds and prevents a category of problem entirely.
If you want channel-wise reporting from one kitchen, see RestoPOS or book a demo.
Frequently asked questions
By an explicit rule that everyone understands, not per ticket at the pass. Delivery has an external clock and a rating attached, dine-in has a guest watching, takeaway sits between — any of those can be the priority, but an implicit rule produces inconsistency and makes every channel occasionally feel deprioritised.
Because it is a stage most kitchens never planned for. A dine-in dish is finished when plated; a delivery order is finished when packed, checked, labelled and handed over. Without a dedicated point, that competes with plating at the pass during service.
It depends on what share of orders arrives through platforms. Manual entry from a tablet into the POS during service costs time and introduces errors where they are most expensive — discovered after delivery, resolved with a refund and a rating. Above a certain volume that is a tax on every order.
By contribution after channel-specific costs — commission, packaging and promotional discounts — against the kitchen capacity each channel consumes, not by gross revenue. Comparing gross flatters delivery, because none of those costs apply to a dine-in cover.
Often not. Dishes that arrive soggy, separated or cold generate complaints, refunds and ratings that attach to the restaurant rather than the dish. A delivery menu that is a deliberate subset of the full menu prevents a whole category of problem.