> For the complete documentation index, see [llms.txt](https://docs.interaktifotel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interaktifotel.com/en/property-management/beds.md). # Physical beds and bunk beds A physical bed describes the furniture and its capacity. A separately reservable bed space is a rental unit. Selecting a bed in the amenities or inventory catalog does not create a physical bed space that can be reserved. ## Define a bed 1. Open Physical Bed Definition from bed management within floor and room definitions. 2. Optionally choose a single bed, double bed or a bunk with 2, 3 or 4 levels as a preset. 3. Check the bed code, room and floor. 4. Adjust the bed type, physical structure, number of levels and dimensions. 5. Check each space's code, position and guest capacity. 6. Review Active and Separately reservable together with the room's rental mode. 7. Select Save bed. Selecting a preset only fills the fields. You must save to create the record. ## Bunk-bed example A two-level bunk groups two physical bed spaces. Track lower and upper levels with separate codes. A double bed may be one bed space with capacity for two people. Bed-space count and guest capacity are not the same measure. ## Add beds from the room form The room create/edit form lets you choose bed types and quantities. These are added to existing physical beds. To change an existing bed, edit its record rather than adding another one. After saving, check bed codes in the definitions list and the layout in [3D View](/en/property-management/three-dimensional-view.md). If a bed is missing from the sales board, check the room's rental mode and whether the bed can be reserved separately. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.interaktifotel.com/en/property-management/beds.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.