Availability: Live room inventory by date (room type + room level) with allocation #10

New Issue

androidlover5842 · 2026-02-09T17:25:52+05:30

androidlover5842 commented

2026-02-09 17:25:52 +05:30

Goal

Provide a reliable availability view and allocation workflow:
- room-type level inventory by date
- drill down to room-level occupancy and conflicts
- allocate rooms to bookings (pre-assign or check-in)

UX

Calendar/range view:
- Choose date range.
- Show counts per room type: available/occupied/out-of-order (if supported).
- Drill down to list of rooms with statuses and stays.
Allocation:
- From booking: select room(s) for the stay dates.
- Block allocation if room is occupied; show which booking/stay blocks it (if API returns).

API / Data

Reuse existing availability endpoints already used in booking flows (e.g. room availability range).
Ensure booking details + active stays + booking lists update from Room after mutations (no direct UI list mutation).

Engineering requirements

Follow Room DB sync rule.
No duplicated availability mapping logic across screens: extract a shared mapper/repository if needed.

Acceptance

Front desk can see availability for any date range and allocate rooms without guesswork.

Goal - Provide a reliable availability view and allocation workflow: - room-type level inventory by date - drill down to room-level occupancy and conflicts - allocate rooms to bookings (pre-assign or check-in) UX - Calendar/range view: - Choose date range. - Show counts per room type: available/occupied/out-of-order (if supported). - Drill down to list of rooms with statuses and stays. - Allocation: - From booking: select room(s) for the stay dates. - Block allocation if room is occupied; show which booking/stay blocks it (if API returns). API / Data - Reuse existing availability endpoints already used in booking flows (e.g. room availability range). - Ensure booking details + active stays + booking lists update from Room after mutations (no direct UI list mutation). Engineering requirements - Follow Room DB sync rule. - No duplicated availability mapping logic across screens: extract a shared mapper/repository if needed. Acceptance - Front desk can see availability for any date range and allocate rooms without guesswork.

androidlover5842 added the feature ux api room-db-sync availability labels 2026-02-09 17:25:52 +05:30

androidlover5842 added this to the TrisolarisPMS Roadmap project 2026-02-09 17:26:18 +05:30

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: androidlover5842/TrisolarisPMS#10