Module

Reservations

Central reservations and distribution — bookings, one availability truth, channel connections, and the queue carrying every change out to them.

What it is

Reservations owns what is sellable and where it is sold. Availability is derived from live inventory with composition and holds already reflected; distribution rules are applied on top of it; the result is what a channel sees. Connecting a channel is a sequence — connect, map rooms and rates, certify — and every push after that is a queued change with a state you can read.

A booking, and the actions its state allows

Every reservation carries a status, and its card offers only the actions valid for that status — check out an in-house stay, check in or cancel a confirmed one. The state machine lives in the product rather than in the receptionist's head.

The Reservations list in Nerve. Each booking is a card headed by its confirmation code, naming the guest, room and dates, with a status pill and only the actions valid for that status — Check out for an in-house stay, Check in or Cancel for a confirmed one. — The card offers what the booking's state allows, and nothing else.

One availability truth, rules on top

Room-type availability comes from live inventory. Availability rules — an OTA ceiling, a minimum stay, a same-day cut-off — are applied over it, and a third panel shows what the channel actually sees. A ceiling shapes distribution without touching what the property can really sell.

Three stacked panels in Nerve deriving channel-facing availability: five free Double Rooms a night from live inventory, an “OTA ceiling” rule capping one channel at three, and the resulting three-of-five that channel sees. — A channel ceiling changes what a channel sees without touching real inventory.

Connect, map, certify — then watch the queue

A channel connection is not live until its rooms and rates are mapped and it is certified. After that, every rate and availability push is a queued row with its kind, its date span and its delivery state — so a change that did not land is visible rather than assumed.

A connected distribution channel in Nerve. A card for Booking.com carries “connected” and “certified” pills, above a room-and-rate mapping panel listing the mapped identifiers with a “Discover options” button. — A channel is connected, mapped and certified — in that order.

The distribution queue in Nerve. A control row picks what to push over a date range; below, each queued change is listed with its kind, its date span and its state — some still pending, some delivered after one attempt. — Every push to a channel is a row you can read, not a black box.

A villa is its bedrooms, and both are sellable

The composite-unit builder attaches component rooms to an entire-unit room, so a villa and the bedrooms inside it share one availability truth. Sell the villa and the bedrooms go with it; sell a bedroom and the villa does. This is the shape villa and short-let properties actually have.

The composite-unit builder on Nerve's Rooms and Units screen, with “Pick a unit” and “Pick a component” dropdowns and an Attach button, above an explanation that composing a villa from its bedrooms makes both shapes share one availability truth. — A villa and its bedrooms are two ways to sell one set of rooms.

What it means for an agent

The operations an agent needs are the ones a channel needs: read availability for a date range, read rate plans and restrictions, create a booking, cancel one. Because the availability a channel sees and the availability an agent reads come from the same derivation, an agent quoting a room is quoting the same room a partner would.

Go deeper

Every screen above is documented, operation by operation, against the shipped product.

Reservations documentation →

Wondering whether this is for a property your size?

← All features