Channel manager Live

AxisRooms

The connector the two Asar hotels trade through today — sixteen of nineteen endpoints built, real bookings from six OTAs since 10 September 2026, every push acknowledged.

AxisRooms is the channel partner the first hotels went live with. The connector speaks their PMSXchange interface: rates, inventory and restrictions out; bookings, modifications and cancellations in; a pull of what they sold for the days the push did not deliver; and the no-show and cancellation told back.

What the mapping looks like

Each PMS room type is mapped to the channel's room by number, and each OTA the channel connects is on record by its identifier, so the sync log can be matched line by line against the extranet's own booking report. The mapping follows the partner's sheet, hotel by hotel, and is corrected where the sheet and the hotel disagree.

What is running

Bookings from Go-MMT, Booking.com, Agoda, Expedia, Cleartrip and Desiya, applied inline at two hotels.
Rates, inventory and restrictions pushed on change, each acknowledged.
The inbound log, the push log and the sync report, hotel by hotel.

What is still with the partner

Mapping every plan on the channel side for each hotel, and enabling the pull endpoint on production. Both are their step; the product does not wait on them to trade.

The connector is a module. A second channel partner is a second module against the same registry, not a second product.

More on Channel manager

The channel managerPart of the product, not a second subscription: rates, inventory and restrictions out; bookings, modifications and cancellations in; every call kept. A booking arrives, and is on the chart in the same requestThe channel's booking is applied inline — guest, room, price, tax and payer — and the acknowledgement says whether it landed, and if not, why. What is pushed, and whenRates, rooms and restrictions go the moment they change. The channel is told more than we have on purpose, and told less when the house keeps rooms back. A queue that is not moving says soEvery push has a status, an attempt count and the error; a queue that has stalled is a sentence on the screen, not a silence. The sync logEvery call both ways, hotel by hotel, with the request body and the response body — a dispute with a channel is settled by reading. The OTA is who we collect from, not who the invoice is forAn OTA that collected from the guest is the payer; the guest is still the person on the invoice; the commission is what the channel said, never a silent zero. An oversell is not a failureAn overbooking allowance per type, and a booking that lands into a full type goes on the chart waiting for a room — visible, draggable, decided by the desk. The channel's credentials live in the productThe connection's keys are in an encrypted vault the application role cannot read, with a trail that survives a key change.