> 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/zh-tw/zhu-su-she-shi-guan-li/beds.md).

# 實體床位與雙層床

實際床傢俱描述傢俱及其容量. 一個可以單獨預訂的床位是租房單位. 在設施或庫存目錄中選擇一張床並不創造一個可預訂的實際床傢俱空間.

## 定義一個床

1. 開放 實際床傢俱 定義從床管理在地板和房間的定義.
2. 選擇一個單床,雙床或一張床,設定為2,3或4層.
3. 檢查床號碼,房間和樓層.
4. 調整床型,物理結構,層次和尺寸數量.
5. 檢查每個空間的程式碼,位置和客人容量.
6. 複習 活動和單獨預訂,以及房間的租用模式.
7. 選擇儲存床.

選擇預設僅會填入表單欄位。 必須儲存後才會建立記錄。

## 床床的例子

雙層床包含上、下兩個實體床位。 請分別為下鋪和上鋪設定編號。 一張雙人床可以是一個床位，但可容納兩個人。 床位數量與可住人數不是同一指標。

## 從房間表格中新增床

房間建立/編輯表格允許您選擇床型和數量. 這些被新增到現有的實際床傢俱中. 要更換現有床,請編輯記錄,而不是新增另一個.

儲存後,檢查定義列表中的床位程式碼和 [3D 檢視](/zh-tw/zhu-su-she-shi-guan-li/three-dimensional-view.md). 如果銷售板上沒有床,請檢查房間的租用方式,以及是否可以單獨預訂床.


---

# 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/zh-tw/zhu-su-she-shi-guan-li/beds.md?ask=<question>&goal=<user_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.