Key takeaways
- Every extra tablet is another screen to watch, another menu to update and another place an order can be missed.
- There are three main routes to one screen: native EPOS integrations, order middleware and a kitchen display system fed by either.
- Choose on menu sync, modifier and allergen mapping, outage handling and support hours, not on the demo.
- Connecting systems widens your attack surface, and hospitality lags other sectors on cyber security basics.
The counter full of tablets
It usually happens one platform at a time. The first delivery app arrives with a tablet, then a second, then a third, then your own online ordering, each with its own chime, its own printer and its own menu to keep up to date. Delivery, takeaway and click-and-collect now make up about a fifth of restaurant spending[1], so for many kitchens those tablets carry a serious share of the night's orders.
The costs are easy to miss because they are spread across the evening: an order accepted late because nobody heard the chime, a dish sold out in the kitchen but still live on one app, an order re-keyed into the EPOS with a modifier dropped, or a short-handed team spending time watching screens instead of cooking. Hospitality businesses reported worker shortages more often than the economy as a whole in October 2026, 11.6% against 8.3%[2], so attention is the scarcest resource on the counter.
Three routes to one order flow
| Route | How it works | Best for | Watch for |
|---|---|---|---|
| Native EPOS integration | Your EPOS connects directly to each platform; orders arrive in the till and print to the kitchen | Sites already on an EPOS that supports your platforms | Not every platform may be supported; menu sync can be partial |
| Order middleware | A separate service collects orders from all platforms and sends them to your EPOS or printer, and pushes menu changes out | Multi-platform kitchens, virtual brands, groups | An extra monthly cost and another supplier to manage |
| Kitchen display system | Screens on the line show every order from the EPOS or middleware, with timers and bump-on-ready | Busy kitchens with several stations | Needs a reliable feed from one of the routes above |
| Keep the tablets, add process | One person owns the tablets; menus updated on a schedule | Very small operations on one or two platforms | Still relies on attention at peak |
For most single-site takeaways and restaurants on two or more platforms, the real choice is between native EPOS integrations and middleware. A kitchen display system is an add-on that makes either work better at peak.
Decision criteria that matter more than the demo
When the ONS asked accommodation and food businesses what influenced their use of AI tools, ease of integration and use was the factor cited most often, at 25.5%, ahead of business knowledge and affordability[3]. That matches what operators report: the systems that last are the ones the team can run on a Friday without the supplier on the phone.
- Menu sync: can you change a price, a description or availability once and have it update on every platform?
- Sold-out sync: when the kitchen marks an item unavailable, does it disappear everywhere within a minute or two?
- Modifiers: do heat levels, removals and add-ons arrive on the ticket in the same words the kitchen uses?
- Allergens: do allergen notes arrive in a field the kitchen will see, not lost in a comments line? For online and phone orders, allergen information must be provided before purchase and on delivery[4].
- Order acceptance: can orders be auto-accepted, and what happens if the internet drops mid-service?
- Reporting: can you see sales, refunds and fees by platform in one place?
- Support: are support hours the same as your trading hours, including Friday and Saturday night?
- Contract: what is the minimum term, the notice period and the cost per site or per platform?
Bring phone, walk-in and own-website orders into the same flow
Consolidation is often planned around the delivery apps alone, leaving phone orders on a notepad and website orders on yet another screen. The kitchen then works from two or three sources at once, which is exactly the problem you set out to solve. Aim for every order, whatever the channel, to arrive in the same format on the same printer or kitchen screen, in the order it needs to be cooked.
- Key phone orders straight into the EPOS while the caller is on the line, not on paper for later.
- Connect your own website ordering through the same EPOS or middleware as the apps.
- Use the same dish names, numbers and modifier wording on every channel so tickets look identical.
- Show the channel on each ticket in large type, so the packer knows whether a rider, a driver or a walk-in customer is collecting.
When every ticket looks the same, the kitchen stops caring where an order came from and simply cooks the queue. That is the real gain from consolidation: one sequence, one set of habits and one place to look when something goes wrong.
Questions to ask before you sign
Ask for a reference site like yours
Speak to an operator of similar size and cuisine using the same EPOS and platforms, and ask what went wrong in the first month.
Test the modifiers
Place test orders with your most complicated dishes through every platform and read the printed tickets.
Test an outage
Ask what happens to orders if the broadband fails. Is there a fallback to the tablets or a mobile data back-up?
Check the menu mapping work
Find out who maps your menu, how long it takes, and who updates the mapping when you change dishes.
Get the costs in writing
Ask for every fee: set-up, per site, per platform, per order, hardware and support.
Switching without losing a Friday
- Pick a quiet week, never the week of a bank holiday or a big match.
- Clean up your menu first: consistent dish names, numbers and modifier wording across all platforms.
- Run the new system in parallel with the tablets for at least a few quiet services.
- Train every person who works the pass or counter, including weekend-only staff.
- Keep the tablets charged and in a drawer for the first month as a fallback.
- Review missed, late and refunded orders weekly for the first six weeks and compare with before.
Example: a fictional pizza and wings kitchen in Sheffield ran three delivery apps and its own website from four tablets and two printers. After moving to middleware that sent every order to the EPOS and a single kitchen printer, the owner removed three tablets from the counter, set sold-out items once from the till, and stopped re-keying orders. The first fortnight surfaced several modifier mapping errors, which were fixed before the busiest weekend.
Virtual brands and multi-site kitchens
If you run a virtual brand from the same kitchen, or several sites on the same platforms, the case for middleware gets stronger. Each brand has its own menu on each platform, and without a central system every price change or sold-out item has to be made several times over. Mistakes multiply in the same way: an item switched off on one brand stays live on another, and the kitchen receives orders it cannot cook.
- Map every brand's dishes back to the same kitchen recipes so tickets show what to cook, not just the brand's menu name.
- Keep allergen information linked to the recipe, so a change flows through to every brand that uses it.
- Check that reports split sales and fees by brand and by site, so you can see which ones actually make money.
- Agree who in the business is allowed to change menus, and keep a simple log of changes.
Security when systems start talking
Connecting platforms, middleware and EPOS means more logins, more devices and more places for something to go wrong. In the government's 2025 survey, 30% of food and hospitality businesses identified a cyber breach or attack in the previous year, and only 25% had sought external cyber security guidance, against 42% of businesses overall[5].
- Food and hospitality
- All businesses
Source: Department for Science, Innovation and Technology, 2025[5]
Show the data
| Item | Food and hospitality | All businesses |
|---|---|---|
| Identified a breach or attack in the last 12 months | 30% | 43% |
| Sought external cyber security guidance | 25% | 42% |
- Give each person their own login where systems allow it, and remove access the day someone leaves.
- Turn on two-step verification for platform partner portals and the middleware dashboard.
- Keep the EPOS and order devices on a separate network from guest Wi-Fi.
- Do not let suppliers keep permanent remote access; grant it when needed.
- Check that payout bank details on each platform cannot be changed without a second check.
When the tablets are fine
Consolidation is not always worth it. A café on one platform with a dozen orders on a busy day may be better served by a clear rule: one person owns the tablet, the menu is checked every Monday, and sold-out items are switched off at the same time as the board is updated. Revisit the decision when you add a platform, launch a virtual brand or see missed orders creeping up.
For related reading, see cutting delivery order errors at the pass, delivery app promotions and speeding up the café morning coffee queue.
Frequently asked questions
Can I get all delivery app orders on one screen?
Yes. Either through your EPOS if it integrates with each platform, or through order middleware that collects orders from every platform and sends them to your EPOS, printer or kitchen display.
Is delivery middleware worth the extra cost?
It usually pays off when you run two or more platforms, virtual brands or several sites, because it saves re-keying and keeps menus in sync. On one platform with low volume, a clear tablet routine may be enough.
What happens to orders if the internet goes down?
It depends on the system. Ask suppliers about offline fallback, mobile data back-up and whether the platform tablets can take over. Keep them charged for the first months after switching.
References
NIQ (CGA by NIQ) (2026). Restaurants' delivery sales strengthen in September after tough summer (Hospitality at Home Tracker) (opens in a new tab) ↑
Office for National Statistics (2026). Business insights and impact on the UK economy, wave 166 dataset (opens in a new tab) ↑
Office for National Statistics (2026). Business insights and impact on the UK economy, wave 165 dataset (AI sheets) (opens in a new tab) ↑
Food Standards Agency (2026). Allergen guidance for food businesses (opens in a new tab) ↑
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑