Resolve reservation and channel-manager differences

Saving in Holidario and synchronizing with the channel manager are separate steps. A delay does not authorize creating another reservation.

An OTA reservation is missing#

1. Follow Find and verify a reservation.
2. Check team, property, dates, guest, and reference.
3. Verify state on the correct OTA.
4. Review channel-manager alerts.

Do not create a manual replacement. You may duplicate occupancy and amounts when the original event arrives.

A manual reservation has no external identifier#

A direct reservation is saved locally and then created in the channel manager.

1. Wait a few minutes and reload the same reservation.
2. Confirm that source is Holidario and its reference is unique.
3. Review Channel information and the external identifier.
4. Ask an administrator to check connection and operation mapping if it remains empty.

Do not repeatedly change the reference or create a second reservation. The system can recover an earlier external creation using the original reference.

An edit does not match#

1. Record dates, guest, amounts, and reference in Holidario.
2. Compare the same reservation in the connected channel.
3. Identify which side received the authorized instruction.
4. Avoid further changes until the correct source is established.

A successful save only confirms the local change. Holidario does not yet show detailed pending or failed synchronization status on the reservation page.

An OTA cancellation does not match#

Do not repeat the cancellation or try to rebuild the reservation. Booking.com and Airbnb cancellation need specific reconciliation; escalate immediately with evidence from both states.

Locally free dates cannot be booked publicly#

Holidario periodically selects a short stay that the local calendar considers available and that respects the minimum stay. It then anonymously attempts to reach the public checkout on every configured storefront: Airbnb, Booking.com, and the Holidario booking website when enabled.

The check does not sign in as the host, query the channel manager, or submit any reservation or payment.

The Public booking unavailable alert identifies the platform and dates that failed to reach checkout after a second confirmation. A provider security page, technical block, or incomplete response does not create this discrepancy.

1. Open the correct public listing without signing in and search for the exact reported dates.
2. Check minimum stay, occupancy, published-listing state, sellable rates, and any intentional pause of the booking website.
3. Correct the setting in the authorized system for that platform. Do not open dates or create a test reservation merely to remove the alert.
4. Wait until the reported date range is checked again. That discrepancy resolves automatically when its public checkout accepts the same stay.

This check detects dates that are locally free but blocked for the guest. It does not yet confirm the inverse case—dates occupied locally that a platform continues selling—which requires a separate overbooking-risk check.

Evidence for support#

• internal ID and external reference;
• property, operation, and platform;
• dates and state on both sides;
• external identifier when present;
• action, user, and approximate time;
• screenshot without unnecessary personal data.

Expected result#

The difference is identified without duplicating a reservation, and a responsible person can reconcile it using references from both systems.