Nerve文档

预订

Connecting a channel

Connect a distribution channel, map its rooms and rates to yours, certify it, and recover anything its feed missed.

最后更新

Who this is for: Owner — requires crs.channel.manage. The default Manager bundle does not carry it: a Manager sees the channels and their mappings, and can change none of it. Where: Reservations → Channels

Connecting a channel is the highest-friction task in the product, and the order matters: connect, then map, then certify. A channel cannot go live before it is certified, and certification will not pass without valid mappings.

This is also the screen the rest of the section leans on. A held booking and a failed ARI delivery are usually both a mapping problem, and both are fixed here.

注意

On staging, every channel runs against an in-process stub. Connections, mappings, certification, pushes and bookings all behave as specified — nothing reaches a real OTA, and no OTA credentials are involved.

Connect a channel#

  1. Open Reservations → Channels.
  2. Select Connect channel.
  3. Enter the Code — the machine identifier, like booking_com.
  4. Enter the Name — what your team will read, like Booking.com.
  5. Select Connect.

The channel appears as a card, uncertified. It is connected and it is not yet selling anything.

Map rooms and rates#

A mapping binds one of your room categories or rate plans to the channel's own identifier for it. Without them, the channel is speaking about rooms Nerve cannot recognise.

  1. Select Discover options on the channel card. It fetches the channel's real rooms, listings and rates — the actual ids to map against, rather than ids typed from a spreadsheet.
  2. Map each of your room categories to the channel's room.
  3. Map each rate plan you want sold there to the channel's rate.

Mappings show as badges under Room & rate mappings, each carrying its kind and external id, plus:

  • the occupancy it is priced for, where the channel maps per occupancy;
  • a star for the primary occupancy — the one that carries the restrictions;
  • read-only, where the channel owns that entity and will not accept writes;
  • a count of rate modifiers on the mapping.

Some channels do not offer an API to map through. For those the button reads Map via and opens the channel's own consent flow in an embedded, single-use session. That token is a capability for that one mapping session, not a login, and it is not reusable.

重要

Map every room and rate you intend to sell there before certifying. An unmapped room or rate does not fail loudly at push time — it fails when a guest books it, and the booking lands in the repair queue instead of on the rack.

Certify a channel#

  1. Select Certify on the channel card.

Certification checks the connection end to end and is refused while mappings are missing or invalid — that refusal is the feature, not an obstacle. The card's certification badge turns to certified on success; a failure says why.

Re-map and certify again after any change to the mapped catalog.

Read a channel's health#

Each card carries two badges and sometimes a third:

Badge Means
connected The transport is up
certified / uncertified Whether it may go live
error The last exchange failed — investigate before trusting anything from it

Recover missed bookings#

If a channel's push never arrived, nothing is held anywhere — the booking simply is not there.

  1. Select Recover on the channel.
  2. Read the result: it reports how many bookings were pulled back from the channel's revision feed.

Use it after any outage on either side, and any time a guest quotes a confirmation number the property has never seen.

When an external channel manager is the master#

If one is connected, a banner says it masters mappings. This screen renders read-only and server-side writes are refused — map in that system instead.

What's next#