NerveTài liệu

Đặt phòng

Bookings from every channel

Every booking that reached the property, who collects the money — and the repair queue for the ones a missing mapping held back.

Cập nhật lần cuối

Who this is for: Owner, Manager, Read-only — requires crs.booking.read; retrying a held booking requires crs.channel.manage. Where: Reservations → Bookings

Bookings is the arrivals door for everything the property did not type in itself: pushed by a connected channel, or taken through the direct booking widget. Each one materialises downstream as a Front Desk stay with an open folio.

This screen is where you check that happened — and find the ones where it did not.

Ghi chú

On staging, channel traffic runs against an in-process stub. Ingestion, modification and cancellation all behave as specified; nothing reaches a live OTA.

Read a booking row#

What you see What it is
Guest name and a monospaced code The booking's id on the channel — quote it in a channel dispute
Arrival → departure The dates as the channel sent them
An amount The booking total in its own currency
channel-collect or property-collect Who takes the guest's money
VCC The channel supplied a virtual card
confirmed / cancelled Its current state

Payment collection is the field to read first. It decides whether the desk takes money at check-out or whether the channel already has it — and it is carried onto the folio, so the answer travels with the stay rather than living only here.

Reconcile a repeat, a change or a cancellation#

A channel re-sending or amending a booking is normal, and Nerve absorbs all three cases without your help:

  • The same booking again is idempotent — matched on the channel's booking id. No duplicate stay, no duplicate folio.
  • A modification reconciles onto the existing stay: dates change, and no second stay appears.
  • A cancellation moves the stay to cancelled and handles its folio accordingly.

So a row you already dealt with, arriving twice, is not a problem to fix.

Clear the repair queue#

When a booking's channel room or rate has no mapping, Nerve refuses to guess. The booking is held — no stay is created — and it appears above the list under Held for mapping repair, with a count.

Each held row names the reason: Unmapped room, Unmapped rate, or Unmapped room & rate. A row that has been waiting a while is badged aging.

  1. Read which side is unmapped.
  2. Add the missing mapping on the channel.
  3. Held bookings replay automatically once the mapping exists — or select Retry on a row to re-resolve it now.

Quan trọng

A held booking is a guest who thinks they have a room. It exists, it is not lost, and it is not on the rack. Work this queue before the arrivals list — a held booking for tonight will not appear in arrivals until its mapping is added.

Recover a booking that never arrived#

If a channel's push was missed entirely, it will not be in the held queue either — nothing reached the property. Use Recover on the channel to poll its revision feed and pull back anything missing. See connecting a channel.

What's next#