Use the checklist as a go-live decision
Before opening a channel, check the seven decisions below. Then use the rest of this guide to resolve any room, price, booking, or responsibility that is still unclear.
| Decision | Ready means | Keep the affected offer closed when |
|---|
| Main operating record | Staff know where room, rate, and availability changes are maintained | Different people are maintaining contradictory versions |
| Room mapping | Every external category matches the room promise and inventory | Capacity, facilities, or inventory do not agree |
| Rate mapping | Each offer has the intended rate plan and supported conditions | The team cannot explain which terms the guest buys |
| Existing reservations | Direct and manual bookings are recorded for the opened dates | Known bookings are missing from the operating calendar |
| Outbound check | The channel shows the intended supported price and availability | The visible offer differs or an update is unresolved |
| Return check | The approved test returns the right booking details and reference | The stay arrives missing or attached to the wrong record |
| Exception ownership | A named person owns unresolved updates and the next check | Staff assume someone else is watching |
Read the table with the people who will run the connection. A receptionist should be able to explain which room can be sold and what to do when the channel disagrees. That is stronger evidence than an owner remembering how setup worked last week.
Keep the launch small enough to observe. Opening a carefully checked set of offers gives the team a clearer starting point than enabling every possible combination at once. Expand once the first configured path behaves as expected and the team understands it.
Decide which record your team will maintain
A channel manager connects the hotel's selling information to online travel agencies, or OTAs. It does not decide which room description is correct or which colleague owns a rate change.
Before connecting anything, agree where the team will maintain room types, available inventory, and the rates and restrictions supported by the connection. If one person changes a price in the hotel system while another changes it directly on a channel, the team can lose track of the intended offer.
Kiyo provides a place to manage that room and rate information and send supported updates to connected, mapped channels. Each channel still has its own capabilities and external dependencies. A connected badge is not proof that every setting has the same meaning everywhere.
The PMS versus channel manager guide explains the broader division of work. For setup, the important choice is simpler: your team must know which record it updates and which exceptions require work in a channel's own tools.
For an independent property in Bali, that agreement may involve only the owner and two receptionists. It still matters. A small team has less spare time to reconstruct why a rate changed or who last closed a room.
Separate a physical room from a room type
A physical room is the unit you assign to a guest. A room type is the category you sell. Several physical rooms may share one room type, provided they can fulfil the same promise to the guest.
Consider an illustrative property with four garden king rooms and two terrace suites. A channel may use different names for those categories. Mapping is the decision that connects each external category to the correct internal one. It is not a spelling exercise.
Check the promise behind the name: bed arrangement, maximum occupancy, meaningful facilities, and the inventory being sold. If an external category includes a private pool but your internal category does not, similar wording will not make the match correct.
| Offer on the channel | Matching hotel record | What must agree |
|---|
| Garden double room | Garden king room type | Actual bed arrangement, guest capacity, and room inventory |
| Terrace suite with breakfast | Terrace suite plus its breakfast rate | Room category and the meal inclusion |
| Garden room, non-refundable | Garden king plus the relevant rate plan | Room category and the separately managed booking terms |
These are fictional names to show the decisions, not a claim about a live property or a particular channel's settings.
Kiyo's channel setup matches the channel's room and rate-plan names to the relevant Kiyo room type and rate plan. That gives the team a clear match between the room sold and the room available. You can inspect the intended workflow on the Kiyo Channel Manager page.
What changes when the mapping lives with your bookings?
Without a clear match, reception has to remember that one channel's garden double uses the same four rooms as the hotel's garden king. A new colleague may open the wrong category or treat the two names as separate stock.
In Kiyo, the external room and rate plan are linked to the matching hotel room type and rate plan. The four rooms remain one pool of inventory, not four rooms invented again on every channel. When a connected channel's booking is received and processed, it joins the calendar with its source and reference.
Reception can therefore check which stay is using the room instead of comparing names from memory. Active connections and correct mapping are required, and channel updates can be delayed. The practical gain is fewer separate versions for staff to maintain, with the connection available to inspect when something disagrees.
Match the rate plan as carefully as the room
Two guests can book the same room type under different commercial terms. One rate may include breakfast. Another may have a different occupancy basis or cancellation condition. Matching the room while ignoring the rate can still sell the wrong offer.
Write down what each plan means before mapping it. Include the base occupancy, meal inclusion, relevant stay restrictions, and where its cancellation terms are controlled. Do not assume a direct-booking policy automatically governs an OTA reservation.
Kiyo supports room and rate-plan mapping and sends the rates and restrictions a connected channel accepts. The supported controls vary by channel. The useful buying benefit is the ability to relate the external offer to the correct room and price in Kiyo instead of maintaining an unexplained list of prices.
Keep the first configuration understandable. A small hotel does not gain useful choice from several rate plans nobody can explain. Start with the actual offers you intend to sell, then add another only when it serves a clear guest or commercial need.
The hotel pricing strategy guide helps with the commercial question of what to charge. This setup task is about making sure the price and conditions reach the intended offer.
Check the dates and capacity you are opening
A correct room match can still go wrong if the hotel opens dates it cannot honour. Before go-live, compare the planned availability with existing reservations, closed dates, and rooms that should not be sold.
Include direct bookings and reservations taken by phone or at reception. An OTA connection cannot discover a booking that remains only in a notebook. Kiyo's calendar depends on those manual bookings being recorded, alongside reservations successfully received from connected and mapped channels.
This is a useful reason to bring setup into the same operating system. The hotel can connect distribution to the calendar its team uses for the stay. The benefit depends on maintaining that record, not merely installing another tool.
For a property with several villas, pay particular attention to whether a listing sells one unit or a category with several units. Do not copy a quantity because another channel uses the same room name. Check what the guest is actually buying and how much inventory the listing represents.
Once the setup is working, the guide to managing room availability across OTAs owns the ongoing daily process. Keep this first review focused on the dates and offers you are about to open.
Prove both directions of the connection
The outward journey sends room information to the selling channel. The return journey brings a reservation and its later changes back to the hotel. Both need attention before the team relies on the connection.
For the outward check, compare a deliberately chosen room, date, price, and supported restriction with what the channel actually shows. A successful action inside one system does not by itself show what a guest can purchase on the other side.
For the return check, follow the provider's supported testing or onboarding process. A permitted test reservation should arrive as the right room type, dates, source, and booking status, with its external reference preserved. If a change or cancellation is part of that approved test, check the resulting reservation and affected availability too.
Do not create an ordinary paid guest booking merely to tick a box. Agree the allowed test method and who will reverse any test inventory or booking effects. The point is to prove the path without leaving the team an unexplained reservation to handle.
Kiyo's public channel-manager workflow describes incoming bookings, modifications, and cancellations updating the reservation record and affected inventory after processing. Its demo shows sample room-type sync and recent activity. Those are useful views for understanding the product; they are not a substitute for testing your own configured connection.
This distinction keeps the buying decision grounded. Choose a connected workflow you can inspect and support, then prove it with your property setup before promising staff that it is ready.
Give delayed or rejected updates an owner
External channels can delay or reject an update. An inactive connection, missing mapping, or unsupported setting can also prevent the result the hotel expects.
The useful setup question is what happens next. Who notices the issue? Who checks the affected dates? Who decides whether the hotel should pause sales while the discrepancy is investigated?
Kiyo's advertised workflow keeps connection, mapping, and delivery or retry context visible. That supports investigation: the team can look at the affected connection instead of assuming every channel accepted the change. It does not guarantee instant propagation or make double bookings impossible.
Agree a named owner and a backup before going live. At a small property, this can be the manager on duty and the owner. What matters is that an unresolved issue survives the shift change and has a next action.
The front desk handover guide is useful when an exception cannot be finished in one shift. Record the affected room and dates, the observed discrepancy, and who will check again. Avoid vague notes such as channel problem when the next receptionist needs to know whether a room can be sold.
If two guests already need the same room
If the hotel already has conflicting active reservations, use the double-booking response guide to protect the guests first. Once the immediate problem is controlled, trace the room mapping, missing entry, or channel update that needs attention.
Open channels with a team that knows the offer
Your next channel should add a way to sell the property, not another set of room names only one person understands. Start with the guest promise, map the room and rate, prove the supported return path, and name the person who owns exceptions.
Kiyo is a practical fit when you want connected channel updates to work from the same room and booking model your team uses each day. Explore its Channel Manager with those decisions in mind. The worthwhile result is a team that knows what is open, what has booked, and what needs attention.