Accommodation Management

Property management with bed-level granularity for mixed-accommodation models — private rooms, shared dorms, gender-separated beds, real-time availability, and seasonal descriptions.

-62%
— Reduction in double-booking incidents with real-time bed-level tracking
artidal-pms · accommodation overview
Occupancy rate
78%
▲ 6% this week
Beds filled
15/21
Check-ins today
3
Bungalow A2/2 beds
FULL
Shared Dorm 15/6 beds
AVAILABLE
Shared Dorm 24/6 beds
AVAILABLE
Private Suite2/2 beds
FULL
Treehouse1/2 beds
AVAILABLE
Beach Cabin0/3 beds
VACANT

Beyond Room-Night Inventory

Traditional property management systems are built around a simple abstraction: one room, one night, one guest (or one couple). This abstraction works for city hotels but falls apart for experience hospitality properties with mixed accommodation models. A typical surf camp in Taghazout might offer 4 private bungalows (bookable as a unit), 2 twin rooms (bookable per person with single-occupancy surcharge), 3 shared rooms with 4-6 beds each (bookable at bed-level with optional gender separation), and 1 dormitory with 12 beds (bookable at bed-level with a per-bed rate). That is four fundamentally different inventory models under one roof — and the PMS needs to handle all of them simultaneously.

Artidal's Accommodation Management module is purpose-built for this reality. It treats the room and the bed as distinct, first-class inventory entities with independent availability, pricing, and booking rules. A private room is booked as a unit with a per-room or per-person rate. A shared room exposes individual beds as bookable entities, each with its own availability, gender assignment, and pricing. A dormitory operates at bed-level by default. This granularity means that when a guest books a bed in a 6-bed shared room, only that specific bed is marked as occupied — the remaining 5 beds retain their own availability and can be independently booked, gender-filtered, or blocked for maintenance.

Room Types, Categories, and the Accommodation Hierarchy

The module organises accommodation in a three-level hierarchy: Property → Room Category → Room (→ Bed, for shared accommodation). Room Categories define the template — name, description, base amenities, photos, pricing model (per-room or per-person), and maximum occupancy. Individual Rooms inherit from their category but can override specific attributes: a particular bungalow might have a sea view that commands a premium, or a ground-floor room might be accessible and flagged accordingly.

This hierarchy supports the mixed-accommodation model that is standard in experience hospitality. A retreat centre might define categories like 'Private Suite,' 'Shared Twin,' 'Women's Dorm,' and 'Mixed Dorm' — each with different pricing, amenities, and booking rules. When the operator creates a new package, they reference room categories (not individual rooms), so the package is compatible with any room in that category. Specific room assignment happens at or near check-in, using either automatic allocation (first available, preference-matched) or manual selection by staff.

The room category system also supports upgrade paths. When a guest's requested category is full but a higher category has availability, the Booking Engine can offer an automatic upgrade suggestion with the price differential clearly displayed. This is a common revenue recovery strategy in surf camps where private room demand frequently exceeds shared room demand during couples' travel seasons.

Real-Time Availability and Calendar Management

The availability calendar is the operational heartbeat of any accommodation business, and in experience hospitality it is significantly more complex than a hotel grid. Availability must be tracked at bed-level (not just room-level), across multiple booking sources (direct, OTA, manual), with calendar blocks for maintenance, seasonal closures, owner-use periods, and staff accommodation. A single incorrect availability entry — a bed showing as available when it is actually blocked for a group booking on another platform — can cascade into a double-booking that damages the guest relationship and the property's reputation.

Artidal's availability engine operates in real-time, with sub-second updates when a booking is created, modified, or cancelled. The engine supports multiple block types: confirmed bookings (with guest and booking reference), maintenance blocks (with reason and expected duration), seasonal closures (affecting entire room categories), owner blocks (for properties where the owner uses rooms during off-season), and OTA sync blocks (with channel reference for bookings received via Booking.com or Airbnb channel managers). Each block type is visually distinguished on the calendar, giving the front desk team an instant understanding of not just what is occupied but why.

For properties that use channel managers (Siteminder, Rentals United, Beds24), Artidal provides a two-way sync API that updates external channels when availability changes internally and receives incoming bookings from external channels. The sync operates at the room-category level (since most OTAs do not support bed-level inventory), with internal allocation of OTA bookings to specific beds handled by Artidal's assignment logic.

Seasonal Descriptions, Photos, and Contextual Content

A detail often overlooked by PMS platforms is that accommodation descriptions are not static. A surf camp room described as 'Wake up to the sound of the ocean and step onto the beach for your morning session' is misleading in January when the beach is 200 metres away due to seasonal erosion and the morning session is cancelled for swell. A mountain retreat's 'Cosy chalet with wood-burning fireplace' is irrelevant in summer when guests care about the terrace and the hiking trails, not the fireplace.

Artidal supports seasonal description overrides at the room-category level. Operators define date ranges with alternative descriptions, photos, and amenity highlights that automatically swap into the Booking Engine and Guest App based on the guest's travel dates. The winter description of a Moroccan riad emphasises rooftop warmth and cultural excursions; the summer description highlights the pool and the proximity to surf breaks. This contextual content ensures that the accommodation presentation matches the actual guest experience — a small detail with measurable impact on booking conversion and post-stay satisfaction.

The same seasonal system applies to photos. Operators upload season-specific photo sets, and the Booking Engine displays the set that matches the guest's selected dates. A retreat centre in the English countryside shows autumnal grounds and fire-lit common rooms for October bookings, and wildflower meadows and outdoor yoga platforms for July bookings. This prevents the common problem of a guest booking based on summer photos and arriving in winter to a property that looks nothing like the images.

Gender Separation and Cultural Sensitivity

Shared accommodation in experience hospitality regularly requires gender-aware bed allocation. A surf camp offering 6-bed shared rooms might operate them as mixed-gender by default but switch to gender-separated allocation during periods with high solo-female-traveller demand or during women-only retreats. A yoga retreat in India might maintain strict gender separation year-round for cultural reasons. A hostel-style adventure lodge might offer both mixed and gender-specific dorm options.

Artidal's bed-level inventory model supports configurable gender policies per room: mixed (any guest, any bed), female-only (only female guests can book), male-only (only male guests can book), and dynamic (the first booking sets the room's gender for the remaining beds in that date range). The dynamic mode is particularly useful — when a solo female traveller books a bed in a 4-bed room for a given week, the remaining 3 beds automatically become female-only for that period, preventing mixed-gender situations in shared accommodation without requiring the operator to pre-assign gender to every room for every date range.

This gender-aware allocation happens automatically during the booking flow. The guest indicates their gender preference, and the availability engine filters results accordingly. No staff intervention is required, and the guest sees only accommodation options that match their preference — eliminating awkward post-booking room reassignments.

Maintenance, Housekeeping, and Operational Overlays

Accommodation management extends beyond booking and availability into the operational reality of maintaining physical spaces. Rooms need cleaning between guests, mattresses need replacing, plumbing breaks, and renovations happen. Artidal's calendar supports maintenance blocks with categorised reasons (cleaning, repair, renovation, seasonal closure), expected durations, assigned staff or contractors, and status tracking (scheduled, in-progress, completed).

The housekeeping layer integrates with booking lifecycle events. When a guest checks out, the room status automatically transitions to 'Needs Cleaning,' and the housekeeping team sees the turnover on their dashboard. When housekeeping marks the room as clean, it becomes available for the next check-in. For same-day turnovers (common in surf camps with Saturday-to-Saturday cycles), the system enforces a minimum turnaround window to prevent the next guest from being assigned a room that hasn't been cleaned yet.

This operational layer is often where the gap between hotel-centric PMS platforms and experience hospitality needs becomes most apparent. A system built for a city hotel with professional housekeeping teams and standardised turnover processes doesn't account for the reality of a beachside surf camp where the same person who teaches the morning surf lesson might also be responsible for checking that the bungalow roof was repaired after last week's storm. Artidal's maintenance and housekeeping features are deliberately lightweight — they capture what needs to happen and track whether it happened, without imposing a rigid workflow that doesn't match the operational reality of a 15-person property.

Multi-Property and Branch-Level Configuration

For operators managing multiple properties, Artidal's Accommodation Management supports branch-level configuration with organisation-level oversight. Each property maintains its own room categories, inventory, pricing, and calendar — but occupancy reports, revenue analytics, and availability searches can be viewed across the entire portfolio. A guest searching for availability across a surf camp group's Bali, Morocco, and Portugal locations sees consolidated results with property-specific room descriptions and pricing.

Branch-level configuration extends to operational details: different check-in/check-out times, different minimum-stay requirements, different seasonal periods, and different housekeeping processes per location. This flexibility is essential for multi-country operators where local regulations, climate, and operational culture vary significantly. A surf camp in Bali operates on a fundamentally different rhythm to one in Cornwall, and the PMS must accommodate both without forcing a one-size-fits-all configuration.

— Capabilities

What it does

Bed-level inventory management

Track availability at individual bed level within shared rooms and dorms — not just room-level — with independent pricing, gender assignment, and blocking.

Mixed accommodation models

Support private rooms (per-unit), shared rooms (per-bed), twin rooms (per-person with single-supplement), and dorms simultaneously within one property.

Real-time availability engine

Sub-second availability updates across direct bookings, OTA sync, maintenance blocks, owner-use periods, and seasonal closures — with visual calendar distinction.

Seasonal descriptions and photos

Automatic date-range-based swapping of room descriptions, photos, and amenity highlights to match the guest's actual travel season.

Dynamic gender separation

Configurable gender policies per room — mixed, female-only, male-only, or dynamic (first booking sets gender for remaining beds in the date range).

Category-based room assignment

Guests book room categories; specific room assignment happens at check-in with automatic or manual allocation, supporting upgrade paths between categories.

Housekeeping and maintenance tracking

Lifecycle-triggered room status transitions (checkout → needs cleaning → ready), maintenance blocks with categorisation, and same-day turnover protection.

Channel manager integration

Two-way sync with Siteminder, Rentals United, and other channel managers — category-level OTA availability with bed-level internal allocation.

— Problems solved

What changes

01
PMS can't handle shared rooms at bed-level

Hotel PMS platforms treat rooms as atomic units — they can't sell individual beds in a 6-bed dorm or track gender-specific allocation within a shared room.

02
Double bookings from disconnected channels

Real-time availability with channel manager sync eliminates the double-booking risk from managing OTA and direct availability in separate systems.

03
Misleading seasonal content

Guests book based on summer photos and arrive in winter to a different experience — seasonal description and photo overrides ensure the booking matches the reality.

04
Manual room assignment chaos on changeover day

Category-based booking with automatic allocation and turnaround-window enforcement replaces the Saturday-morning scramble to figure out who goes where.

05
Gender complaints in shared accommodation

Dynamic gender policies prevent mixed-gender situations in shared rooms without requiring manual pre-assignment or post-booking room swaps.

06
Maintenance and cleaning falls through the cracks

Lifecycle-triggered housekeeping tasks and maintenance tracking ensure rooms are cleaned before reassignment and repairs are scheduled, not forgotten.

— See it in action

Ready to explore
Accommodation Management?