Track availability

Open a project → Availability to view room nights by room type and stay date. Reading availability requires dedicated access; managing it is a separate permission and is available only while the project is not archived. Availability is different from bookings and booking summaries: bookings describe reservation records, while Availability describes date-based inventory facts.

Read availability data

Choose a start date, end date, and optionally a room type, then select Apply filters. The date range is bounded to one year so the result stays within a clear scope.

The summary shows:

• Expected facts: room-type/date combinations expected within the selected scope.
• Recorded facts: combinations that currently have availability data.
• Missing facts: combinations without a record. This does not mean zero.
• Total available room nights and out-of-order room nights across recorded facts.
• The source cutoff indicating when the latest source data reflected by the result was updated.

Each row identifies the stay date, room type, available/out-of-order room nights, source type, source update time, and data version. Manual, Import, and Connector labels describe the provenance of the displayed fact only; they do not prove that an external OTA import or synchronization has been configured for the project.

Record manual availability

If you have manage access, select Add availability. The room catalog must be available and the project must not be archived.

1. Add one or more rows; one save supports up to 1,000 rows.
2. For every row, choose a room type, stay date, available room nights, and out-of-order room nights. Counts must be non-negative integers.
3. Optionally add an internal source reference. Do not place guest data, credentials, or secrets in this field.
4. Do not add duplicate room-type/stay-date rows in the same request, then select Save.

If the room catalog is unavailable or the project is archived, the create/edit form can be disabled even though authorized historical data remains readable.

Correct and review history

Select View on a row to inspect the current fact and its change history. A user with manage access can use Correct to update counts, a source reference, and a correction reason.

• A reason helps collaborators understand why the numbers changed.
• The app checks the current version before saving. If a conflict occurs, reload the fact and history, then review the latest data before submitting a new change.
• Changes remain in history; do not treat the displayed value as a replacement for the context of earlier corrections.

Interpret data safely

• A missing fact is not proof that no rooms are available. Complete the data or verify the source before drawing a conclusion.
• Do not derive availability from booking summaries, and do not use this table as a booking confirmation or room hold.
• Availability does not configure connectors, import data, or publish values to an external OTA channel.
• Archived projects provide only authorized historical context and do not allow new manual entries or corrections.

See also property and room setup, bookings and summaries, and access rights.