Use cases

Hotel F&B: poolside and room service QR ordering

Use one QR menu across the restaurant, the pool bar, and room service. Brand colors and a private slug.

QR ordering for hotel F&B, from the pool bar to the room

Boutique hotels run three F&B operations at once: a restaurant on a service rhythm, a pool bar where guests do not want to leave their lounger, and room service where the phone has been the only ordering channel for thirty years. The job of a QR menu here is to give the guest a single, branded ordering surface across all three, without forcing the F&B team onto a new POS. MobiTaste Pro covers ten outlets, the REST API, and 36 months of audit retention for $60 a month.

The outcomes you should expect

Ten outlets on Pro for $60 a month. One QR menu per outlet means the pool bar, the restaurant, and room service each get a discrete order stream while sharing one organization account.
Brand colors and a private subdomain (CNAME) on Growth and above. A guest scanning at the pool sees your brand, not ours; the URL reads menu.yourhotel.com.
Waiter approval keeps room service from becoming a prank channel. A QR on the in-room card waits for staff approval before the kitchen sees the order, which protects the late-night prep line.

Why the hotel context is different

Three things change when you move from a standalone cafe to a hotel. First, the guest expectation is brand consistency, because they paid for the room and the brand. Second, the order may arrive from a room number rather than a table number, which means table tokens need to span outlets without leaking between them. Third, group IT may want SSO and a signed DPA before the system goes live.

MobiTaste handles the first two on Growth and Pro. Each outlet (restaurant, pool bar, room service) is its own restaurant under your organization. They share a brand color palette and a CNAME, but each one has its own menu, table list, and audit log. Cross-outlet reporting rolls up at the organization level. Pricing on the pricing page covers the math for multi-outlet groups.

The third item, SSO and the DPA, sits on Enterprise. We sign a DPA on request, run on EU infrastructure, and keep guest data tenant-isolated by design. The data security guide lays out the mechanism.

Room service and the approval gate

Room service is the F&B channel most exposed to abuse. A guest checks out, takes a photo of the in-room QR, and could in theory submit orders against the next occupant. Waiter approval closes that loop. Every first order from a session waits for staff, and idle session expiry resets the cart after 30 minutes of inactivity, so the next guest opens a clean cart.

For the pool bar the same gate matters in a different way. A guest at the pool wants a drink without leaving the lounger, and a server can approve the order on a roaming tablet without breaking the flow. The kitchen never sees an unapproved ticket, and the audit log records who approved what for the morning F&B review.

The kitchen view is a kanban: new, in progress, ready. A pool bar runs the same screen as the main kitchen but filtered to its own outlet. Cooks read the ticket in the kitchen’s preferred language even when the guest browsed in English, because language is set per outlet, not per guest.

Two questions F&B managers ask

How does this integrate with the PMS? The REST API on Pro exposes orders and table state, with webhooks on order events. A PMS that can consume webhooks (Mews, Cloudbeds, and others) reads the order stream directly. Direct PMS connectors are on the roadmap; until they ship, the webhook is the supported path.

What about brand controls? A hotel on Growth or above sets logo, brand color, and a CNAME for the menu domain. The guest scans and lands on your brand, not on a MobiTaste-branded page. About the company and contact details sit on the about page.

Start with the outlet under most pressure

Pick the outlet that loses the most service to “we are slammed, we will be right with you”. For most hotels that is the pool bar in summer or the breakfast room on a check-out morning. Print QRs for one outlet, run it for a week, then expand. The other audience pages sit on the use-cases hub.

Integrations

Does MobiTaste replace my POS or work next to it?

It works next to most POS, not in place of. The QR system handles guest-facing menu and orders; your POS handles payment, end-of-day, and accounting. Owners with a strict POS keep both. Owners without one often skip a POS for the first year.
Does MobiTaste integrate with Adisyo or Menulux?

Not natively at launch. We export orders as CSV that imports into Adisyo. A native Adisyo webhook is on the roadmap for Q3 2026. Menulux uses the same export route. Tell support which integration matters and we will prioritize it.