Book a demo Sign in
Selling online

Mapping room types and rate plans

Nothing is sent for anything unmapped. Map the hotel, then each room type and rate plan.

AxisRooms has its own ids for your hotel, your room types and your rate plans. Mapping is saying which of theirs is which of yours.

The connection box: the channel manager, client id, key, environment.
The connection box: the channel manager, client id, key, environment.
Registering a hotel: show what will be sent, then register and map.
Registering a hotel: show what will be sent, then register and map.

Do this

The connection, once for the whole account:

  1. Channel manager — AxisRooms is the one installed.
  2. Client ID — theirs for Asar as a whole; every hotel uses the same one.
  3. Access key — the key they issued. It is encrypted before it is stored and never shown again unless somebody asks, and that is recorded.
  4. Environment — sandbox or live, so nobody has to work out from a hostname whether a push is about to reach real OTAs.
  5. Save connection.
  6. Check the key with AxisRooms — confirmed by them rather than by us.

Then each hotel:

  1. Hotel code — ours.
  2. Show me — what will be sent: the hotel, its room types, its rate plans, under our codes.
  3. Read the plan. Nothing is sent until you have seen it.
  4. Register and map. Registering the same hotel twice is safe.
  5. The hotel appears under Connected hotels with its mapping counts.

Only what is marked for the OTAs is sent. Each room type and rate plan says on its own form whether it is for the OTAs or internal; Register sends the ones marked for the OTAs and lists nothing else, and a type or plan saved as "for the OTAs" after the hotel is registered is registered and mapped on its own, without coming back here.

Nothing unmapped is ever sent. An unmapped room type is one the channel manager has never heard of, and inventing an id for it would sell a room that does not exist.

Map in this order:

  1. The hotel — until this exists, the hotel is simply not connected and nothing is queued for it.
  2. Each room type you sell online.
  3. Each rate plan.

Then use Preview to see exactly what would be sent, without sending it. It is the only way to check a mapping before anything is live, and it stays useful afterwards — "what did we send" is the first question when an OTA and the hotel disagree.

The OTAs by number

AxisRooms names each OTA by a number (Expedia 2, Booking.com 9, Agoda 13, Go-MMT 23, and so on) and those numbers are on record, so a booking, a push and a log line all say the OTA's name rather than its id.

More in Selling online

What the channel manager doesAxisRooms carries the OTAs. We send it rates and availability; it sends us bookings. When an OTA booking arrivesIt lands on the chart by itself, at the OTA price. What cannot be applied waits on a list with the reason. What the channel sent, and what became of itThe CM Log on Operations reads in four tabs — reservations, inventory, rates, cancellation — the bookings the channel delivered and the pushes we sent it, each with its fate. The Channel sync log report is every exchange with AxisRooms, both ways, hotel by hotel. The revenue engine: a recommended rate with its reasonsEvery night of every room type is scored against what is on the books; the engine proposes a price with the reasons, a manager approves or rejects it, and an approved price goes to the channel manager the same minute.