# Rooms & attributes A property is *where* a guest stays; a **room** is *what* they book. Rooms and the attributes attached to them are how you describe what travellers actually buy — capacity, layout, amenities, view, accessibility. ## What a room defines | Element | What it says | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Type** | The room's class — Standard, Deluxe, Suite, Family, Villa. | | **Name** | The full label travellers and partners see (*Deluxe Sea View, Double Occupancy*). | | **Capacity** | Adults, children, infants — minimum and maximum. | | **Layout** | Bed configuration (twin, double, king, sofa-bed), room size, floor. | | **Room-level amenities** | Sea view, balcony, kitchenette, accessible bathroom, in-room safe, etc. | | **Meal-plan eligibility** | Which meal plans can be booked with this room. | | **Default rate plans** | The rate plans available against the room — typically a *BAR* (Best Available Rate, the industry-standard public refundable rate), a *Non-Refundable Europe* discounted variant, a *Member Saver* for logged-in members, and any packages you sell. | | **Multilingual content** | Description, captions, room-specific images per language. | A property typically sells across several room types. Each is its own canonical record; they share the property but stand on their own for content, pricing, and inventory. ## Attributes — the typed labels Beyond the basics, attributes describe what makes a room appealing or filterable. Three kinds: * **Hotel-level amenities.** Pool, spa, parking, restaurant — they apply to the property as a whole and any room benefits from them. See [Categories](/console/catalog/categories.md) for the related classification level. * **Room-level features.** Sea view, balcony, kitchenette, accessible bathroom — they apply to the specific room. * **Multi-language amenity labels.** *Free WiFi* / *Ücretsiz WiFi* / *WiFi gratuit* — the same canonical attribute, shown to a traveller in their language. Attributes are a typed set, not free-text. The canonical taxonomy lives in your organization; partner amenity codes are mapped into it. See [Attribute mapping](/console/mapping-and-curation/attribute-mapping.md). ## Adding a room A typical room-creation pass: 1. **Type and name.** Pick the room type from your catalog (or create a new type if you genuinely have a new class), set the name travellers will see. 2. **Capacity and layout.** Adults, children, beds, room size — the things a traveller filters on. 3. **Room-level amenities.** Pick from your canonical attribute taxonomy; add new attributes if you have them and they are real. (Avoid creating duplicates that already exist under a slightly different name — see [Attribute mapping](/console/mapping-and-curation/attribute-mapping.md).) 4. **Meal-plan eligibility.** Decide which meal plans can be sold with this room. 5. **Default rate plans.** Bind the room to the rate plans you sell against it. 6. **Content.** Description, images, captions — multilingual where you operate in multiple languages. See [Images & content](/console/catalog/images-and-content.md). For a small property with 3 room types, this is roughly 5 minutes per type. For a larger property with 8+ room types, the room template surface lets you copy-and-vary — define one Deluxe Sea View carefully, then create variants from it (Deluxe Sea View Twin, Deluxe Sea View King) in seconds each, without re-entering capacity, amenities, or meal-plan eligibility. ## Room lifecycle Rooms have their own lifecycle alongside the property: * **Active** — bookable. * **Paused** — temporarily out of inventory; existing bookings stay valid. * **Retired** — no longer sold; bookings and history are preserved. When you retire a room, the platform keeps a record of how many of which rate plan / meal plan / mapping bound to it; this is what makes "we used to sell that room" answerable. ## Filling rooms in fast — the chain case If you operate many properties with similar rooms, the room template surface scales: * **Define a canonical room template once** — *Deluxe Sea View* with all its standard attributes. * **Apply it to every property that has the room type** — variations like specific capacity or named bed configuration are layered on per property. * **Adragent can drive this** — *"Apply our standard Deluxe Sea View template to every Antalya property with a sea-facing block."* This is what keeps your catalog consistent across hundreds of properties without manual repetition. Concretely: a 40-property chain rolling out a new in-room amenity (say, *Bluetooth speaker*) updates one template and Adragent applies it to the matching rooms across all 40 properties on confirmation. ## Adragent and rooms Common phrases that map to Adragent room operations: * *"Add a Deluxe Sea View room to Hotel Sunrise with a 2-adult / 1-child capacity and the standard sea-view amenities."* * *"Show me every Deluxe room without an in-room safe across the Europe properties."* * *"Pause the King Suite room on the Marina property for the renovation in October."* * *"List every property where the room descriptions are missing Spanish translations."* Read operations return immediately; writes preview before applying. ## Where to next * **The classification of the property as a whole** → [Categories](/console/catalog/categories.md) * **Multilingual content beyond labels** → [Images & content](/console/catalog/images-and-content.md) * **How partner amenity vocabularies map to your taxonomy** → [Attribute mapping](/console/mapping-and-curation/attribute-mapping.md) * **The rate plans rooms attach to** → [Rate plans](/console/pricing-and-availability/rate-plans.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://adrasis.gitbook.io/console/catalog/rooms-and-attributes.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.