NerveDocs

Reservations

Availability and ARI distribution

Queue a rate, availability, restriction or stop-sell change over a date range and watch it reach every connected channel.

Last updated

Who this is for: Owner — requires crs.availability.write. The default Manager bundle does not carry it: a Manager can see this screen's delivery history but cannot push a change. Where: Reservations → Availability

ARI is Availability, Rates and Inventory — the three things every channel needs kept current. This screen is where you send a change out and then watch it land, one card per connected channel.

It is deliberately a queue rather than a fire-and-forget. A push that failed is visible, retried and eventually flagged; it is never silently lost.

Note

On staging, delivery runs against an in-process stub. Queueing, delivery status, retry and failure are all real — the wire call to the OTA is simulated, so nothing reaches a live channel.

Push a change to every channel#

  1. Open Reservations → Availability.
  2. Choose the Change kind — Rates, Availability, Restrictions or Stop-sell.
  3. Set From and To to cover the dates affected.
  4. Select Distribute.

The screen confirms how many changes were queued. One change set is created per mapped channel, so a property with three connected channels gets three deliveries to watch.

Tip

Push the widest range that is actually correct, in one go. A fortnight in one change set is one delivery to watch and one thing to retry; fourteen daily pushes are fourteen.

Watch a delivery#

Each channel card lists its recent changes: the kind, the date range it covers, how many attempts it has taken, and its status.

Status Means
queued / pending Accepted, not yet sent
delivered The channel acknowledged it
failed It did not get through and retries are exhausted

A delivery that fails is retried automatically with a backoff, with the attempt count rising on the row. Persistent failure ends at failed rather than disappearing.

Select Refresh on a card to re-read that channel's history without reloading the page.

Deal with a failed delivery#

  1. Find the failed row and note its kind and date range.
  2. Check the channel itself — a certification that has lapsed, or a mapping that no longer resolves, is the usual cause. See connecting a channel.
  3. Fix the cause.
  4. Queue the same change again for the same range.

Important

A failed ARI push means the channel is still selling the old truth — the old price, or a date you meant to close. Until it clears, treat that channel as out of step with the house. A failed stop-sell is the urgent case: it is the one where the gap costs you a room you cannot honour.

Know what this screen does not do#

Queueing a change distributes state; it does not author it. What the channels are told comes from the catalog and the restrictions, so a stop-sell you have not applied is not sent just because you queued a stop-sell change.

What a channel may be told about availability in the first place — cut-offs, the booking window, price guardrails — is set on distribution settings.

With no channels connected the screen says so and there is nothing to push: distribution needs somewhere to distribute to.

What's next#