Skip to content

Guides

Move a hotel to ZimmerStack

Your sandbox has passed. This is how a live hotel moves from its old channel manager to ZimmerStack, who does each step, and how you avoid a duplicate or a missed booking on the way.

One channel manager per OTA

Booking.com, Agoda and MakeMyTrip each connect a hotel to one channel manager at a time. A hotel cannot be on its old channel manager and on ZimmerStack for the same OTA, so there is no side-by-side run: your sandbox is the dry run, and the move is made one OTA at a time, each in minutes.

The steps, and who does each

  1. 1

    Add the hotel

    You. In the partner portal. ZimmerStack activates it, usually the same day, ready for your live key.
  2. 2

    Send its structure and a year of calendar

    You. With the live key: the room types and rate plans (PUT /catalog/room-types, PUT /catalog/rate-plans), then rates, availability and stay rules for the whole horizon. No OTA sees any of it yet. Wait for GET /sync to read IN_SYNC.
  3. 3

    Ask each OTA to switch, a day ahead

    The hotel. In each extranet the hotel names the connectivity partner we give you when the hotel is set up. Booking.com: Account → Connectivity provider, then accept the agreement; Booking.com approves it. Agoda: YCS → Property settings → enable channel manager mode, then choose it. MakeMyTrip and Goibibo: ask in InGo to change the channel manager; MakeMyTrip then issues an access token. These are the hotel's own logins; nobody at ZimmerStack needs them.
  4. 4

    Connect, match, start selling

    Us with you, for your first hotel. On the hotel's page in the partner portal: Connect a channel, type what the OTA gave the hotel, match every room and rate, then Start selling. Starting sends the hotel's whole calendar to that OTA, and from that minute its new bookings, changes and cancellations reach you by webhook. For your first hotel ZimmerStack's team does this step with you on a call, one OTA at a time; you run the next hotels yourself.
  5. 5

    Switch that OTA off in the old channel manager

    You. Once the OTA has moved, the old channel manager no longer reaches it; switching it off there stops it trying.

No duplicate and no missed booking

Feed both while you move
Until every OTA has moved, your system keeps sending availability to the old channel manager and to ZimmerStack. A booking from either side lowers your count; send the new count to both.
Upcoming bookings come again
When Booking.com, Expedia or Airbnb starts selling, we import the hotel's upcoming bookings from that OTA and send each as channel.booking.created. You already hold them from the old channel manager: match on channel.otaName with channel.otaReservationCode and treat a match as the same booking.
Older Agoda and MakeMyTrip bookings stay with you
Those OTAs offer no import, so a booking made before the switch is not in ZimmerStack. If the OTA changes one after the switch, it reaches you about an hour later as channel.booking.created and then channel.booking.modified: match it the same way. If the OTA cancels one, it reaches you about an hour later as one channel.booking.cancelled, with the booking's status cancelled and no created before it: match it the same way. A cancellation like that changes no availability here.
Move at a quiet hour
One hotel at a time, every OTA in one sitting. That evening, check each extranet's reservation list against your system.

Booking e-mails

The OTAs keep sending their booking e-mails to the reservation address set in their own extranet. Changing the channel manager does not change it, so a mailbox kept as a backup keeps working. ZimmerStack sends no e-mail of its own for an OTA booking: your system hears through the webhook (or GET /channel-bookings), and the hotel sees the booking on its bookings screen. Check each extranet's e-mail setting once after the move.

After the move