SofIA with the PMS you already run.

Two adapters today. A third would use the same door, and none is connected yet.

SofIA does not call Cloudbeds directly. It asks the hotel adapter.

Hotelisimo PMS

Availability, hold, changes, cancellation, and the payment link are written in Hotelisimo. The calendar, reservations, housekeeping, and rates live in this panel.

Cloudbeds

The reservation stays in Cloudbeds. Hotelisimo keeps the conversation, the order, and the task. Casa Mädi runs this way, in production.

Casa Mädi

A PMS that is not connected yet

Mews and Opera are not connected. The code treats them as the built-in PMS until a dedicated adapter exists. There is no third PMS today.

How a hotel goes live

The PMS first. Then SofIA on the guest channel.

Hotelisimo PMS

The calendar, reservations, housekeeping, and rates live in this panel. The stay is stored here.

Cloudbeds

The reservation stays in Cloudbeds. Hotelisimo keeps the conversation, the order, and the task. Casa Mädi runs this way.

SofIA

It connects to WhatsApp, Instagram, and Messenger. It checks availability, places the hold, and sends the payment link. The charge is confirmed in the PMS.

Who opens the panel

Each role sees its own work. The guest does not open the panel. They write on WhatsApp, Instagram, or Messenger.

Owner and manager

Reservations, rates, stop-sell, the menu, inventory, and the team. They can sell over a stop-sell.

Front desk

The stay file, walk-ins, orders, and tasks. Front desk cannot sell over a stop-sell.

Kitchen

Sees orders and turns a dish on or off. Kitchen does not edit the menu.

Housekeeping

Works tasks. The native PMS Housekeeping board is separate: checklist, photo, and blocks.