Skip to content

Handle bookings held for review

Screen /channel-exceptions · Roles: Admin, Channel Setup

Most Airbnb events apply themselves. Anything that changes money, conflicts with an existing booking, or cancels a stay is held on Bookings to Review for a person - because those are exactly the events where an automatic write could move money or nights you would not have moved.

Bookings to Review - the status chips over the queue; empty when every channel event applied itself

  1. Start on the “Needs review” filter - it is the morning question. The other chips (Applied · Closed · In flight · All) are history: a retried event moves to Applied, so “what happened to that booking last week” stays answerable.

  2. Read the reason on the row. It is written in plain words - the most common ones are below.

  3. Act where the action is. Open booking → takes you to the affected booking; Open on Airbnb ↗ takes you to the reservation on the channel - accepting or declining a reservation request, and accepting an alteration, genuinely finish on Airbnb, because the channel offers no API for them.

  4. Click Retry once the underlying issue is fixed (for example, after resolving a date conflict). A retry that fails says so; the row never silently pretends it worked.

  • Guest cancelled - the nights were released automatically; the refund is yours to make. Money never moves on its own.
  • Cancelled during the stay - the nights were not released; decide manually.
  • The channel changed what this stay pays - nothing was re-priced automatically.
  • The new dates collide with another booking - resolve the conflict, then retry.
  • A cancellation arrived for a booking we never ingested, a multi-room reservation, missing stay dates, or an unreadable amount - nothing was written; investigate first.
  • What syncs, and which way - the routine flow this queue is the exception to.
  • The count of waiting items also shows on the Airbnb screen’s “Channel bookings to review” card, even at zero.