What a hospitality POS needs to do (vs. retail POS)

Retail POS systems are built around a simple transaction: scan items, take payment, print receipt. Hospitality is considerably more complex, and that complexity is baked into every element of service.

A hospitality POS must handle covers management – tracking tables as logical units with seat counts, open and close states, and a graphical table map that reflects your actual floor plan. Staff need to see at a glance which tables are occupied, how long they've been open and how many covers are seated.

Course management is equally critical. A table-service restaurant takes orders in sequence: starters, mains, desserts. The POS must hold back courses and release them to the kitchen at the right moment. Getting this wrong means food arriving in the wrong order, or the kitchen cooking everything simultaneously and ruining timing.

Kitchen routing sends different items to different output points. A beer goes to the bar printer; a steak goes to the kitchen. In more complex operations, cold starters might route to a larder section while hot mains go to the main kitchen line. The POS handles all of this automatically, based on item configuration.

Then there's service charge handling, bill splitting by item or cover, tip recording and – in hotel environments – room charge posting, where a guest's restaurant spend posts directly to their room folio without cash changing hands.

Systems like Square and Shopify POS are capable retail tools. But they weren't designed for table service. They lack native table maps, course sequencing and PMS integration. For a coffee shop or grab-and-go operation they may be adequate, but for any seated restaurant or hotel F&B operation, they're the wrong tool.

The vendor landscape

The hospitality POS market divides broadly into enterprise platforms and mid-market cloud systems. Understanding which tier you're buying in is the first decision.

Oracle MICROS Simphony is the dominant enterprise platform. It's used across branded hotel groups, large restaurant chains, stadiums and high-volume F&B operations. The feature set is extensive – handles virtually any operational complexity you can describe. The downsides are real: implementation is expensive, licences aren't cheap and you'll need Oracle-certified engineers for installation and major changes. Support quality varies by region and partner. The integration ecosystem is very wide, which matters for hotels running multiple third-party systems. If you're running a branded hotel or a multi-site restaurant group with serious volume, Simphony is likely to be your shortlist entry point.

Lightspeed Restaurant is the platform we see most frequently in independent restaurants and boutique hotels across the UK and Europe. It's cloud-based, has a clean interface and is realistically priced for operations that aren't running at enterprise scale. The integration ecosystem is decent, with Mews and Guestline PMS integrations available. It's well-suited to single-site or small-group operations. Where it starts to strain is genuine multi-outlet complexity – a hotel with five or six different F&B outlets, each with distinct menus and routing requirements, is a stretch.

Agilysys InfoGenesis is strong in US hotel resorts and large F&B complexes. It's less common in the UK market, but relevant for operators with US ownership, brand standards that mandate it, or properties that are part of a US-headquartered group.

NCR Aloha sits in a similar enterprise tier to Oracle. It has reasonable UK chain presence but is less common in hotel environments. Worth knowing about if you're operating in sectors where it's established.

EPOS Now is a UK-based platform popular with smaller independent hospitality operators. Accessible price point and straightforward to set up. For a simple pub or casual dining operation without complex routing requirements, it can do the job. For anything more involved, you'll hit its limits quickly.

TouchBistro is iPad-based, originally Canadian and growing steadily in the UK. It handles mid-size restaurant operations well and has a good user experience. The integration ecosystem is more limited than the enterprise platforms, which matters if you need to connect to other systems.

Revel Systems is US-focused and iPad-based. It has enterprise ambitions but primarily serves the mid-market. Less common in UK hotel environments.

Core evaluation criteria

Before shortlisting vendors, be clear on what you're evaluating against. The criteria that matter most:

PMS integration: why it matters for hotels

In a hotel, a guest's spend shouldn't require them to pay separately at each outlet. They should be able to charge a restaurant dinner, a spa treatment and a round of drinks at the bar to their room, settling everything at checkout. This is room charge posting, and it requires a live two-way integration between your POS and your property management system (PMS).

The integration must do several things: verify the guest is actually in-house before accepting a charge, post the transaction to the correct room folio in real time, and allow the front desk to see an accurate outstanding balance at any point. Some integrations are one-directional only – they post charges but don't return balance information. That creates reconciliation problems.

Oracle MICROS Simphony integrates natively with Opera PMS – both are Oracle products, and the integration is as close to seamless as this kind of thing gets. Lightspeed has verified integrations with Mews and Guestline. Other combinations may or may not have a working integration, and "we can build one" from a vendor is not the same as a tested, live integration with a reference site you can call.

If your hotel runs a PMS that isn't on a vendor's integration list, treat that as a disqualifying factor unless you have the budget and appetite for a custom integration project – which is a significant undertaking, not a minor configuration task.

Kitchen display systems and order flow

A kitchen display system (KDS) replaces paper dockets with a screen mounted in the kitchen – or at a specific station within it. Orders appear on the screen as they're sent from the POS, organised by course, with colour-coding that changes as time passes to flag items approaching or exceeding target preparation times.

The advantages over paper are meaningful: no illegible handwriting, no lost dockets, clear visibility of what's outstanding versus what's been prepared, and a digital record of kitchen throughput times for performance analysis. In a busy service with multiple covers running simultaneously, a well-configured KDS reduces errors and improves pace.

Some POS platforms include KDS functionality natively. Lightspeed offers its own KDS product that integrates cleanly with the restaurant POS. Oracle Simphony connects to various KDS solutions. Third-party options like Fresh KDS can also work with certain platforms. If KDS is a priority – and for any serious F&B operation it should be – confirm the specific integration before you commit.

Consider routing carefully. A hotel restaurant might need KDS screens at the hot section, the cold section, the pass and the bar – each showing only the items relevant to that station. Configuring this correctly at setup is important. Retrofitting routing logic after go-live is more difficult than getting it right from the start.

Hardware considerations

The hardware decision is more consequential than many operators realise. Enterprise platforms like Oracle Simphony and Agilysys typically use dedicated hospitality terminals – purpose-built for the environment, PoE-powered (no separate power adaptor, just a network cable), with better resistance to heat, moisture and the general abuse that a busy kitchen or bar will inflict on equipment. They cost more upfront and have a longer useful lifespan.

iPad-based systems carry a lower initial hardware cost. An iPad and a stand is significantly cheaper than a dedicated terminal. But consumer devices in commercial environments have higher replacement rates. Screens crack, charging ports wear out, and you're dependent on Apple's product cycle for any hardware continuity planning.

Payment terminal compatibility matters. In the UK, EMV (chip and PIN) compliance is mandatory. Confirm that your chosen payment processor and card reader combination is supported by the POS. Many platforms have preferred or exclusive payment partnerships – understand the processing fees as part of your total cost calculation, not as an afterthought.

Kitchen and bar printers also need consideration. Thermal receipt printers at the bar and pass remain the standard in most operations, either alongside or instead of KDS. They need to be on a reliable, wired network connection – not Wi-Fi, which introduces the possibility of missed dockets. Budget for printer redundancy in high-volume outlets: a printer failure during a busy service is a serious problem.

Multi-outlet and multi-site deployments

A single-restaurant operation and a hotel with restaurant, bar, room service and pool bar have fundamentally different POS requirements, even if the underlying platform is the same product.

Multi-outlet deployments need centralised menu management – the ability to make a price change or add a new item once and have it propagate correctly across all outlets rather than requiring manual updates at each terminal. They need consolidated reporting that gives you a single view of total F&B revenue alongside outlet-by-outlet breakdowns. And they need outlet-specific kitchen routing, so that a room service order doesn't appear on the restaurant kitchen screen.

Oracle Simphony handles this well – it was designed for this kind of complexity. Mid-market platforms can manage it to varying degrees. If you're evaluating Lightspeed or TouchBistro for a multi-outlet hotel, test the specific scenario rather than relying on a general capability claim from a sales team.

Multi-site deployments – where you're operating multiple independent properties under one group – add another layer. Centralised menu management, group-level reporting and consistent configuration across sites all require careful architecture. Enterprise platforms have more mature tooling here. Expect this to be a significant implementation project regardless of which platform you choose.

Implementation and ongoing support

The platform you buy is only part of what you're acquiring. The implementation quality and the support model you're tied into matter just as much.

Enterprise platform implementations (Oracle Simphony, Agilysys) require certified installation engineers. These aren't systems you configure yourself from a SaaS dashboard. Budget for a proper implementation project with discovery, configuration, training and go-live support. Cutting corners here creates problems that are expensive to fix after the fact.

Cloud-based mid-market platforms are more self-serviceable, but "more" doesn't mean "entirely". A rushed or poorly configured setup will frustrate staff and produce unreliable data from day one. Invest in proper staff training – particularly for managers who'll be running end-of-day reconciliations and making menu changes.

Before signing any contract, be clear on what happens when something goes wrong in a live service. What's the support SLA? Is there a UK-based phone number? Is out-of-hours support included, or is it an add-on? A POS that's down during dinner service isn't just an inconvenience – it's a revenue and reputation problem. Know what your options are before you need them.

Route B helps hospitality operators evaluate and implement POS systems. Get in touch to discuss your requirements.

Get in Touch