> ## Documentation Index
> Fetch the complete documentation index at: https://docs.roomdoo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Wubook — connecting your channel manager

> How Roomdoo connects to Wubook to sync reservations, availability, and rates with OTAs, and what to do when something doesn't add up.

## How Roomdoo connects to Wubook

Wubook is the **channel manager** that connects Roomdoo to every OTA (Booking.com, Expedia, Airbnb, etc.). Roomdoo doesn't communicate directly with each OTA — it talks to Wubook, and Wubook handles the distribution to each channel.

Information flows in both directions:

* **From Roomdoo to Wubook and then to OTAs:** availability, prices, restrictions, sales closures, board services
* **From OTAs to Wubook and then to Roomdoo:** new reservations, modifications, cancellations

<Note>
  Everything you see in Roomdoo about channel quotas, rooms, and rates is kept in sync with Wubook automatically. In day-to-day operations, you don't need to log into Wubook to touch anything.
</Note>

## What gets synced with Wubook

| Data                                       | Direction              | When                                            |
| ------------------------------------------ | ---------------------- | ----------------------------------------------- |
| Availability (free rooms by type)          | Roomdoo → Wubook       | After every reservation, cancellation, or block |
| Rates and prices                           | Roomdoo → Wubook       | When you update a rate or plan                  |
| Restrictions (minimum stay, sales closure) | Roomdoo → Wubook       | When you change them in Roomdoo                 |
| New OTA reservations                       | OTA → Wubook → Roomdoo | As soon as the OTA confirms the reservation     |
| Cancellations and modifications            | OTA → Wubook → Roomdoo | As soon as the OTA records the change           |

Changes aren't instant: it usually takes seconds to a few minutes for them to propagate because they're processed in the background.

## Common support cases

<AccordionGroup>
  <Accordion title="I sold a room on Booking but it's not showing up in Roomdoo">
    The reservation has reached Wubook but hasn't arrived at Roomdoo yet. It usually takes a few minutes.

    If **more than 15-20 minutes** have passed and the reservation still doesn't show up:

    1. Check in the Wubook panel that the reservation has arrived there.
    2. If it's in Wubook but not in Roomdoo, there's an issue between Wubook and Roomdoo — [contact support](#when-to-contact-support) with the Wubook reservation code.
    3. If it's not in Wubook either, the issue is between the OTA and Wubook — check the Wubook panel or contact them.
  </Accordion>

  <Accordion title="I updated a rate in Roomdoo but OTAs are still selling at the old price">
    Possible causes:

    1. **The change hasn't propagated yet.** Prices take minutes to reach OTAs. Wait and check again.
    2. **The OTA caches prices.** Some OTAs show the previous price for a while until their servers refresh. This is out of Roomdoo's control.
    3. **The updated rate isn't correctly linked** to the equivalent rate in Wubook. If after several hours the price is still off, this could be it.

    To verify point 3, [contact support](#when-to-contact-support) with the rate you changed and the new price.
  </Accordion>

  <Accordion title="I have an overbooking — I sold more rooms than I have available">
    Overbooking usually happens when several OTAs sell the same room simultaneously and the closure didn't propagate in time. It can also happen if a room is blocked manually without it reaching Wubook.

    Immediate actions:

    1. Review **every affected reservation** for that day or night to understand the scope
    2. Decide which reservation to re-accommodate (room-type change, offer another property, cancel with compensation)
    3. Cancel or modify the reservation with the appropriate OTA
    4. Once resolved, check that availability lines up between Roomdoo and Wubook

    If this happens often, there's a misconfiguration or an underlying delay — [contact support](#when-to-contact-support).
  </Accordion>

  <Accordion title="A reservation came in duplicated (the same reservation appears twice)">
    This can happen if the OTA re-sends the notification or if the first attempt failed and two reservations were created. Identify which one is "the good one" (with the correct guest data) and cancel the other from Roomdoo. Don't delete it — void it so a record remains.

    If you see duplicates often, [contact support](#when-to-contact-support) — we need to look at how the notifications are arriving.
  </Accordion>

  <Accordion title="An OTA says it's closed for a date but Roomdoo shows availability">
    The sales closure may have been set **directly in Wubook** without it reflecting in Roomdoo, or the other way round. First check the real availability in Roomdoo (free rooms by type on that date). If Roomdoo has availability but the OTA says closed:

    1. Review restrictions in Roomdoo (minimum stay, sales closure)
    2. If everything looks fine in Roomdoo, [contact support](#when-to-contact-support) — there may be a restriction in Wubook that isn't managed from Roomdoo.
  </Accordion>
</AccordionGroup>

## When to contact support

Contact Roomdoo support if:

* A reservation **isn't arriving from the OTA to Roomdoo** after 15-20 minutes.
* There are **broken configurations** between rooms, rates, or board services in Roomdoo and Wubook.
* You've changed your **Wubook credentials** or need to reconnect the account.
* There are **repeated overbookings** with no clear cause.
* You need to **add or remove an OTA** from the setup (Booking, Expedia, etc.).

<Warning>
  Don't touch channel mappings directly in the Wubook panel if you're not sure what each field does. A wrong mapping can break the connection with several OTAs at once, not just the one you were trying to adjust.
</Warning>