Cloudbeds connects to Oolio's three POS systems for Australian hotels and pub groups

Cloudbeds has partnered with Oolio, an Australian hospitality technology company, to connect its property management system directly to three point of sale platforms: Bepoz, Swiftpos and Idealpos. Oolio says it serves more than 22,000 venues.

The point of it is the guest folio. Charges from the restaurant, bar or bottle shop post to the room in real time over a direct API connection, staff can verify the guest and room before posting, and nobody re-keys a transaction into two systems at the end of service.

Who this is for

Cloudbeds is aiming this squarely at the Australian market, and specifically at operators who run accommodation and food and beverage as one business: independent hotels, resorts, pub groups and multi-venue operations.

That is a real gap. A pub with rooms above it has always been two systems pretending to be one, and the reconciliation happens on a spreadsheet at the end of the week. If your venue revenue is a meaningful share of total revenue, charge posting that works without supervision is worth more than most feature launches.

Sebastien Leitner, Cloudbeds' vice president of partnerships, framed it around hospitality businesses becoming more diverse. Kris Satish, Oolio's group chief executive, described it as removing manual steps between systems.

The questions the release does not answer

Three, and they all matter before you plan anything around this.

It does not say which Cloudbeds plans include the integration, or whether Oolio charges separately for the connection. It does not give a live date, so "partnership announced" and "available in your account" may not be the same week. And it treats Bepoz, Swiftpos and Idealpos as one thing when they are three separate products with their own histories, so ask whether all three support the same depth of posting, guest lookup and error handling, or whether one of them is further along than the others.

Also worth asking: what happens when a posting fails. Charge posting integrations are judged entirely on their failure behaviour, not their happy path. If a card declines at the bar or the room is already checked out, where does that charge end up, and does anyone get told.

The wider pattern

This is the second Cloudbeds announcement this month after it launched its own revenue management system, and it fits a direction the company has been signalling for a while: rather than building food and beverage itself, it is wiring in the POS systems that already own those venues.

For Australian operators that is the pragmatic answer, since replacing a working POS to suit your PMS is the wrong way round. The trade-off is that your stack now depends on a partnership rather than a single vendor's roadmap, which is fine while both sides are invested and less fine if one of them is acquired.

Australian operators already on Bepoz, Swiftpos or Idealpos should ask their Cloudbeds contact where they sit in the rollout queue.