What the channel sent, and what became of it
The CM Log on Operations is one row per booking the channel delivered, with its fate. The Channel sync log report is every exchange with AxisRooms, both ways, hotel by hotel.
Two questions, two places.
"Is the booking in the system?" — Operations → CM Log
- What happened — on the chart with our reference, refused with the reason, waiting, or cancelled.
- A booking that is NOT ON THE CHART says why, in words, right under it.
- Amount — the channel's total, with its tax on the line below and whether the guest paid the OTA or pays at the hotel.
One row per booking the channel sent to this hotel, newest first: the OTA and its booking number, the guest, the stay, the rooms, the money — with the tax on its own line ("₹2,699.33 + ₹134.97 GST") — and what became of it:
- on the chart, with our reference — click through to the booking;
- refused, and why, in words ("Arrival is in the past", "room type not mapped");
- waiting — arrived, not yet placed (the hotel is full for that type; it is placed the moment a room frees);
- a cancellation that found nothing to undo.
A booking is on the chart in the same second it is pushed. "Waiting" no longer means "the timer has not run yet"; it means the booking could not be placed, and the reason is beside it. When the OTA says the guest has a confirmation and this log has no row, the push never reached us — ask the channel to resend, and read the next section.
The hotel's own manager can open this tab. The Channel manager screen — the group's room, with the credentials and the mapping — stays the administrator's.
"Did we push, and did they take it?" — Reports → Channel sync log
- The summary for the hotel — per direction and kind, how many were OK, failed or waiting, and when each last succeeded or failed.
- Every exchange, newest first, with its outcome, the HTTP answer, the tries, and the reason for a failure.
Every exchange with AxisRooms, both directions, for every hotel your login may see: the inventory, rate and restriction pushes we sent and whether they were accepted, the bookings they sent us, the pulls we asked for, and the no-shows we reported. Each row carries when it was tried, the HTTP answer, and for a failure the reason the channel gave.
The same rows are on Operations → Log under *channel*, where a row opens to show the request we sent and the response that came back, pretty- printed. That is what to send us when a push has been refused for a day: the response says what the channel objected to.
Reading a refusal
- 401 "This channel is not mapped to axisrooms" — the key is fine; the room-type or rate-plan mapping on the channel's side is not. Their support fixes it; nothing at the hotel does.
- A push that keeps retrying backs off — four minutes, sixteen, an hour — and the row says when it will try next.
- A booking we took and could not apply is in both logs: the sync log says 200 (we answered the channel) and the CM Log says refused (we could not place it). To the hotel those are the same thing — a guest who is coming and is not on the chart — and the CM Log is the one that says what to do.