Cloudbeds builds its own POS, and room charges post straight to the folio

Cloudbeds has launched its own point of sale system for hotel restaurants, bars, spas and shops. It is in pilot with selected customers, with no general availability date given.

The pitch is the one every PMS vendor moving into POS makes. When outlet sales sit outside the core system, someone re-enters the purchase, someone checks by hand whether a charge belongs on a room, and finance pulls two sets of revenue reports. Charges get missed. Cloudbeds POS puts the outlet on the same platform as the rooms, so a drink at the bar posts to the guest's folio directly.

What is in it

Managers set up outlets on desktop: menus, products, opening hours, staff permissions and automatic promotions, configured per outlet. Staff then take orders and payments in a mobile app on a phone or tablet.

Orders support modifiers and discounts, and can be sent to kitchen and bar printers. Payments cover cash, Tap to Pay, Pay by Link and room charges, and a bill can be split across several methods. Charges post to guest folios or to house accounts, so reception can review a room-charged purchase alongside the rest of the stay.

There is an offline mode. Staff can keep taking orders, accepting cash and applying discounts without a connection, and the data syncs when the connection returns. For anyone who has run a poolside bar on patchy wifi, that is the line in the announcement that matters most.

Outlet sales then appear in Cloudbeds reporting next to accommodation revenue.

Adam Harris, Cloudbeds CEO and co-founder, said the system "closes that gap and extends our unified platform into that daily activity."

What the announcement does not say

Quite a lot, and it is worth being clear about it. There is no pricing, no indication of which plan or tier the POS lands on, and no list of regions. Payment methods like Tap to Pay are country-specific in practice, so the absence of a regional list is a real gap for anyone outside the US. Hardware is mentioned only as kitchen and bar printers. No third-party integrations are named, and no pilot customers.

Most importantly, it is a pilot. Nobody can plan a 2027 F&B migration on this yet.

The awkward timing

A month ago Cloudbeds announced a partnership with Oolio to connect three third-party POS systems for Australian hotels and pub groups. Before that it deepened its Lighthouse integration. Now it ships a POS of its own.

That is not a contradiction, and vendors do run both tracks for years. But if you are an Australian hotel that signed up for the Oolio route in September, it is a fair question to put to your account manager: which of these two is the one Cloudbeds expects you to be on in two years, and what happens to the other.

The wider context is that this is now a race. Mews POS went live in North America on 1 September and Accor made it the group's food and beverage standard at the end of that month, with 850 properties already running it. Shiji has sold Infrasys POS for years. The PMS vendors have worked out that the folio is the moat, and that whoever owns the outlet owns the rest of the guest's spend.

For operators

If you run outlets and you are already on Cloudbeds, ask to join the pilot and ask three things before you do: what it costs, whether your card terminals and printers are supported in your country, and what the migration off your current POS actually involves. A native POS that posts cleanly to the folio removes a genuine daily annoyance. A pilot with no pricing and no GA date is not yet a plan.