Channel manager Live

The sync log

Every call both ways, hotel by hotel, with the request body and the response body — a dispute with a channel is settled by reading.

"Have we made a log for the attempt to push inventory and all, succeeding or failing?" The rows had been kept since the first month; now they are read.

What is kept

Every push: the endpoint, the body sent, the status, the attempts, the response body, the time.
Every inbound call: the payload the channel sent, whether it was accepted, what it became, the time.
Every pull the hotel made of the channel — what the channel says it sold — beside what the channel pushed.
The channel's own identifiers for the hotel, the rooms and the OTAs, so a row can be matched to the extranet's report by number.

Where it is read

The channel sync report per hotel, both directions, filterable by day and by kind; and the operations log, which reads every log the system keeps on one page. A partner's IP addresses are on the rows — they are masked on this site and nowhere else.

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 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. AxisRoomsThe 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.