Room-service billing for small hotels: a practical setup guide.

Why most hotel PMS have no room-service module

Hotel management systems in India — Menson, IDS, eZee, Hotelogix, RezNext — are architecturally built around the reservation. Rooms, rates, guests, folios, night audit. Room service didn't fit that model, so it was left out, and the assumption was that a hotel with real F&B would either have a separate restaurant POS at reception or handle it in cash.

That works when your F&B is a single restaurant taking dine-in orders from walk-ins. It falls apart the moment guests order to their room. There is no tab per room, no way to add the ₹450 dinner to the folio, no dedicated kitchen ticket, and no way to reprint the bill three days later when the guest disputes a line item.

The five components of a working setup

A room-service billing system for a small property (10–50 rooms) needs exactly five things. In the order you should install them:

1 · A menu database

Not a printed card. A structured list — item name, category, price, tax rate, availability toggle, cost price (for margin tracking), optional variants (half/full), and optional modifiers ("no chilli", "extra cheese"). The menu database is the spine everything else hangs off. If the item isn't in the database, the staff will fall back to writing it on a slip.

2 · An 80mm thermal printer, next to the kitchen

An A4 laser printer at the front desk is not a room-service system. A guest orders → the kitchen sees a printed ticket within 3 seconds of the order being placed → a bill prints when the guest asks for it. The thermal printer is the physical layer that binds the software to the operation. Any 80mm printer works — TVS RP-3200, Epson TM-T81, Everycom EC-58. Silent, USB or network, no dialog.

3 · Per-room open tabs

Every occupied room gets an open tab from check-in. Orders accumulate against that tab. At checkout the tab settles — either paid at the counter or transferred to the room folio. Without a per-room tab you cannot answer the question "what did room 204 order this stay?" and that is the whole point of the system.

4 · An order flow that survives 11pm

The clerk at 11pm with a room service call needs to place an order in under 60 seconds. That means: type-ahead item search, no menu drilling, no forced field validation, one-click "charge to room" as the default. If your software takes 40 clicks to place an order, staff will stop using it — and start writing on slips again.

5 · A bill format that guests trust

A printed bill with the hotel's name, GSTIN, FSSAI, room number, date, itemised list, tax breakup and total. Two copies — customer and hotel. Reprintable at any time. If a bill is disputed a week later, the staff should be able to search by bill number and reprint identically in under 20 seconds.

Offline-first vs cloud: why this matters for hotels

Restaurant POS can survive on cloud SaaS because a busy restaurant will usually escalate a connectivity outage to whoever bought the software and fix it. Hotels can't. A 20-room property in a hill station or a coastal town has flaky internet for hours at a stretch, and the night clerk is not going to call IT support. A room-service system that stops taking orders when the WiFi drops is worse than a notepad.

A sample room-service bill

What NOT to do

• Don't try to add room service into your PMS. If the PMS didn't ship with it, retrofitting it via "custom charge" tickets is worse than a separate system. Half the fields you need aren't there.
• Don't run it in Excel. Excel is not multi-user, not printable to thermal, and not GST-compliant. It will look fine until the first month-end audit.
• Don't rely on WhatsApp orders. Chat is fine for taking the order; it is not a bill. A guest disputing a charge cannot be shown a WhatsApp message as evidence.
• Don't buy a full restaurant POS for room service alone. You'll pay for table-management, kitchen displays and delivery flows you won't use. A focused room-service tool is smaller, cheaper and better fit.