Traveloka, tiket.com, Agoda: Channel Manager Setup

Before you start: what you need

Your login for each extranet. TERA for Traveloka, the tiket.com partner extranet, and the Agoda partner portal (YCS).
Your property ID on each OTA. This is the number the OTA uses for your property. You can usually find it in the extranet or on your partner contract.
A list of your room types. For example: Deluxe Double, Twin, Family Villa. Write how many of each you have.
A list of your rate plans. A rate plan is one price with its rules, such as "Room only, free cancellation" or "With breakfast, non-refundable".
Your current bookings. Every future booking from every source, including WhatsApp and walk-ins.
Any old connection. If an OTA is already connected to another channel manager or calendar tool, note it. You will need to switch it off first.

What each OTA needs: the owner table

The steps are similar for all three. The details are a little different. This table shows what we know from how the connection works in Kiyo. Always check the OTA's own help page too, because OTAs change their screens.

OTA	What you give the channel manager	Who switches it on	What to watch	Where to check
Traveloka	Your Traveloka property ID	You, and sometimes Traveloka support needs to turn on the channel manager connection	In Kiyo's setup notes, only the RETAIL rate type can be mapped (see below)	TERA partner page (opens in new tab)
tiket.com	Your tiket.com hotel ID	You. Kiyo's setup notes say to email tiket.com support if you are moving from another channel manager	Turn off any old calendar sync for that property	tiket.com help centre (opens in new tab)
Agoda	Your Agoda property code	You, in line with your Agoda agreement	Once connected, update rates and availability in the channel manager, not in the portal	Agoda Partner Hub (opens in new tab)

Agoda's own help page says this clearly. If your property is connected to a channel manager, you update price and availability in that system. Changes made only in the Agoda portal may not hold.

tiket.com explains that its calendar sync tool and a channel manager are different things. Calendar sync only blocks dates for whole villas and apartments. A channel manager can also update allotment (how many rooms you give the OTA), rate plans and policies.

Step by step: connect your first OTA

Do one OTA at a time, starting with the one that brings the most bookings.

Set up rooms and rates in your channel manager first. Enter every room type, how many rooms you have, and each rate plan. The OTA side should match what you can really sell.
Check the OTA allows the connection. In the extranet, look for the connectivity or channel manager section. If you cannot find it, contact the OTA's partner support and say which channel manager you want to use.
Switch off any old connection. Disconnect the old channel manager or calendar sync for that property. Two tools sending updates to one OTA can send it mixed numbers.
Enter the property ID. In your channel manager, add the OTA and paste your property ID from that OTA.
Map rooms and rates. Mapping means telling the system "my Deluxe Double here is the Deluxe Double there". Match each room type and each rate plan. Leave nothing half-mapped.
Send availability and rates. Push your calendar to the OTA. Then open the extranet and check a few dates by hand.
Make a test booking or watch the first real one. Confirm it arrives in your channel manager with the right dates, room and price.
Check that the other OTAs close. When that booking arrives, the same room should close on your other connected channels.
Repeat for the next OTA. Only move on when the first one is clean.

Mapping rooms and rates without mistakes

Most connection problems come from mapping, not from the connection itself. Here are the common traps.

Room names do not match. Your system says "Garden Villa" but the OTA says "Villa with Garden View". That is fine. Mapping is about the room, not the name. Just be sure you link the right pair.

Room counts do not match. If you have four Deluxe rooms, but the OTA was set up with six, fix the number before you go live. Otherwise the OTA may think you have rooms you do not have.

Extra rate plans on the OTA. Over time, many properties create old promotions or test rates in the extranet. Decide which ones you still sell. Map those, and close the rest.

Traveloka rate types. In Kiyo's setup notes, only the RETAIL rate type on Traveloka can be mapped to a channel manager. If you sell other rate types there, ask Traveloka support how they should be handled before you connect.

Packages. A package (for example, room plus airport transfer) may be a separate product on the OTA. Check how each OTA treats it before you map it.

What stays in each extranet

A channel manager does a lot of the daily work. It does not replace the extranet for everything. Keep these jobs in your diary.

Job	Usually from the channel manager	Usually in the OTA extranet
Availability (rooms free per date)	Yes	Check only
Nightly rates	Yes	Check only
Minimum stay and close-out dates	Often yes	Check only
Photos and descriptions	No	Yes
OTA promotions and visibility programmes	No	Yes
Invoices and commission payments	No	Yes

Guest messages and reviews are a separate point. In Kiyo, messages and reviews from Traveloka, tiket.com and Agoda are not pulled in, so you answer them in each extranet. Kiyo pulls OTA messages and reviews only from Booking.com, Airbnb and Expedia, on Pro and higher plans.

How to test the connection

A connection can look fine and still have one wrong room. A 15-minute test catches it.

Pick a date about two weeks away with good availability.
Change the rate for one room type by a small amount in your channel manager. Push it.
Open each extranet and check that the new rate shows for that date.
Close that room type for one date. Check it closes on each OTA.
Open it again and check it reopens.
When the first real booking arrives, open it and check the dates, room, guest count and price against the OTA.

A worked example: a 12-room hotel in Yogyakarta

This is a made-up example, not a real property, and it does not promise a result.

Imagine a 12-room hotel in Yogyakarta. It has 8 Deluxe rooms and 4 Family rooms. It sells on Traveloka, tiket.com and Agoda, plus WhatsApp and walk-ins. Today the owner updates three extranets by hand every evening.

Day 1: get ready. The owner writes down the three property IDs, the two room types and the rate plans each OTA still sells. On Agoda, two old promotions nobody uses get closed.

Day 2: rooms and rates in the channel manager. They enter 8 Deluxe and 4 Family rooms, plus two rate plans: "Room only" and "With breakfast".

Day 3: Traveloka first. Traveloka brings the most bookings, so it goes first. While mapping, the owner sees that the Family room on Traveloka was set up with 6 rooms, not 4. They fix the count before going live. Without that fix, Traveloka could sell two Family rooms that do not exist.

Day 4: test. They change one rate, close one date and reopen it. Everything shows on Traveloka within the test.

Days 5 to 7: tiket.com, then Agoda. The same steps, one OTA at a time, with the same test each time.

Now the money and time side. If the evening update took about 20 minutes a day, that is around 10 hours a month of copying. Kiyo costs from Rp40k per room per month (opens in new tab), plus a base fee for the plan. On Starter, 12 rooms cost 12 × Rp40k = Rp480k, plus the Rp150k base fee, so Rp630k a month with the channel manager included. Yearly billing saves 20% on the whole monthly price, not just the room part.

The order matters: prepare, map one OTA, test, then move on.

Try the Kiyo rate calendar in the demo

Common problems and quick fixes

Bookings do not arrive. Check that the room and rate plan in the booking are mapped. An unmapped rate is the usual cause.
The OTA still shows old prices. Check that you pushed the update, and that no old tool is still connected.
A room shows open on the OTA but it is full. Check the room count on the OTA matches your real rooms, and that every booking is in your system.
Two guests for one room. In a connected setup, the usual cause is a booking taken outside the system (phone, WhatsApp or walk-in) and not entered right away. Read what to do if a guest is double booked (opens in new tab).

One team rule matters most: enter every WhatsApp, phone and walk-in booking straight away. Our guide on how to stop double bookings (opens in new tab) explains why.

Connecting the three in Kiyo and keeping them in sync

Kiyo is a PMS and channel manager for independent hotels, villas and guesthouses. It connects to 75+ OTAs, and Traveloka, tiket.com and Agoda are among its supported channels. Here is how the steps above work in Kiyo.

Connecting. You add each OTA by pasting its property or hotel ID. All three then use the same mapping screen, so after the first one, the other two look familiar. Traveloka support may need to switch the connection on first.
Availability. When a booking arrives from one of the three, or from your website or front desk, Kiyo works out how many rooms of that type are left and sends the new count to your other connected channels. The room locks automatically. When a guest checks out, the free room goes back out too.
Rates and rules. You set rates, rate plans, minimum and maximum stay, close to arrival, close to departure and stop sell in the Kiyo rate calendar, per date or in bulk. They go to the OTAs when you press Push to OTAs and confirm. Nothing goes out on its own.
Bookings. New, changed and cancelled bookings from these OTAs come into Kiyo. If a guest needs a change to an OTA booking, you make it in that OTA's extranet, not in Kiyo.
When something breaks. If a connection fails, you get a notice and Kiyo gets an alert at the same time.

What the Kiyo team sets up with you

We set it up with you, in Bahasa Indonesia or English, with a team that includes Indonesian staff. For these three OTAs, onboarding usually covers:

Your property IDs. We collect the Traveloka, tiket.com and Agoda IDs with you and check that each OTA allows the connection.
Rooms and rate plans. We enter your room types, room counts and rate plans in Kiyo, and help you decide which old OTA rates to close.
Mapping. We map each room and rate in Kiyo's mapping screen, one OTA at a time.
Testing. We run the rate and close-out test with you. On request, we can show a live last-room test, where one booking closes the room on your other channels.
After go-live. Your property gets its own WhatsApp group with the Kiyo team.

If you want to understand which jobs sit in the PMS and which sit in the channel manager, read PMS vs channel manager (opens in new tab).

Free setup. Pay from go-live, and if Kiyo isn't right for you in the first 14 days, we refund you in full.