Which software workflows does a pub with rooms need?
Choosing pub with rooms software starts with the handovers between accommodation, the bar and the kitchen. Test one complete stay before deciding which systems need to connect.
A pub with rooms needs workflows for reservations, arrival, food and drink charges, breakfast, staff handovers and departure. A property management system handles the accommodation record; an EPOS handles bar and restaurant sales. Decide which information must pass between them, who checks it and what happens when a transfer fails. Judge software by a complete guest journey, including exceptions, rather than a feature list.
Map six essential workflows
Start with how you trade. If guests settle every drink at the bar, room charging may be optional. If they expect one bill at departure, test a connected workflow. A restaurant table booking also needs its own confirmation: a room reservation does not automatically reserve dinner.
| Workflow | Information to carry forward | Evidence to request |
|---|---|---|
| Reservation | Dates, occupancy, rate inclusions and deposit. | Amend a booking and check the confirmation. |
| Arrival | Room readiness, arrival time and room-charge permission. | Show what the evening duty team can see. |
| Bar and restaurant | Open tab, guest identity and paid or room-charged status. | Trace one bill from EPOS to the guest account. |
| Breakfast | Guest count, included meals and paid extras. | Produce a usable list without billing breakfast twice. |
| Shift handover | Late arrivals, unresolved bills and the next action. | Find an outstanding task using the next shift's access. |
| Departure | Accommodation, extras, payments and remaining balance. | Explain the final bill and reconcile it with receipts. |
Mark each requirement as essential, useful or unnecessary. A documented manual handover can suit low volumes, provided someone owns the check; frequent room charges make integration worth testing.
Follow one guest through a 12-room inn
Illustrative example: The fictional Willow Inn in England has 12 rooms, a bar and a restaurant. Alex books two nights for two adults at £140 per night, breakfast included, and pays a £70 deposit.
Reservation
Reception checks the £280 stay, £70 payment and two breakfasts each morning. Dinner for two is confirmed separately.
Arrival
The duty host checks room 7 is ready, confirms the dinner time and explains the inn's room-charge policy.
Evening service
Alex pays £18 at the bar, then charges a £64 restaurant bill to the room. Staff check the guest and reservation before closing the tab.
Shift change
The evening team confirms the £64 charge reached the guest account. The £18 receipt is marked paid; any unresolved transfer has an owner.
Breakfast
The kitchen receives two covers for each morning. Included breakfasts add nothing to the guest balance; chargeable extras would be identified separately.
Departure
Reception checks open tabs with the restaurant, reviews the charges with Alex and collects the £274 remaining balance.
Check the arithmetic: £280 accommodation + £64 dinner − £70 deposit = £274 due at departure. Total guest spending is £362, including the £18 already paid at the bar. That bar payment must not be collected again.
All amounts are fictional guest-facing GBP totals, inclusive of any applicable VAT. This example checks the payment balance, not VAT allocation or revenue recognition; it is not a software quote.
Give each handover a named owner
Small inns often combine roles. Still, write down who completes each check and where the next person finds it.
Bar and restaurant
Confirm the guest, close the right tab and distinguish payments from room charges. Flag rejected or uncertain transfers before leaving.
Accommodation team
Check arrivals, room readiness, breakfast entitlement and outstanding balances. Confirm dinner reservations with the restaurant team.
Duty manager
Own unresolved charges and approved corrections. Review access permissions and compare the day's room charges with EPOS records.
Use named staff accounts where available. Test the access each role needs, including who may change charges or issue refunds. Avoid making every casual bar employee an administrator.
Ask for a demonstration you can score
Run the Willow Inn journey using sample data. Record each result as demonstrated, manual workaround or not supported, with an owner for follow-up.
- Can the evening host find Alex's arrival details and breakfast entitlement without a reception colleague?
- Can staff distinguish the £18 paid bar bill from the £64 restaurant room charge?
- What happens if Alex changes rooms after opening a tab, or two guests share a surname?
- How is a failed transfer identified, checked and recovered without duplicating the charge?
- Can reception find an unresolved tab before departure and show Alex the supporting receipt?
Ask who supports each connection during evening service, what the escalation route is and which manual procedure staff should follow during an outage. Do not assume the entire workflow works offline.
Test your setup with RoomRaccoon
Use the journey to assess hotel software integrations: identify your EPOS supplier and version, then request a demonstration of the data passed between the pub and accommodation teams.
Lightspeed's UK integration page lists RoomRaccoon compatibility with Restaurant K-Series and L-Series and describes transferring bar or restaurant bills to a guest's room bill. This is a partner integration; it does not establish support for every correction or exception.
RoomRaccoon's Lightspeed documentation describes reservation charges and says the connection uses an upgrade slot. Confirm current UK package eligibility, partner charges and setup requirements for your configuration.
Bring your EPOS version, breakfast policy and a sample guest bill. Ask the team to demonstrate the £18 paid-at-bar / £64 room-charge distinction and your busiest shift handover.
Discuss your pub and room workflowsFrequently asked questions
Can we keep our existing pub till?
Make that a selection requirement. Verify the exact supplier, version and supported connection. If it cannot transfer room charges, assess whether separately settled bills or a controlled manual process fit your service.
Does a room booking include a restaurant table?
Only if your booking process explicitly confirms one. Decide who checks availability, records the table reservation and updates the restaurant when a guest changes or cancels the stay.
What if the same person runs the bar and checks guests in?
Test both tasks under that person's permissions during a busy-service scenario. They should be able to find arrival details and record a clear handover without interrupting service to locate the owner.
Sources and further reading
Sources consulted on 10 November 2026. The journey and acceptance checks are illustrative; confirm your proposed configuration with the suppliers.
- Lightspeed UK: RoomRaccoon integration and compatible POS series.
- RoomRaccoon: Lightspeed integration and upgrade-slot information (document dated 11 June 2025).












