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

# 实体床位与双层床

实际床家具描述家具及其容量. 一个可以单独预订的床位是租房单位. 在设施或库存目录中选择一张床并不创造一个可预订的实际床家具空间.

## 定义一个床

1. 开放 实际床家具 定义从床管理在地板和房间的定义.
2. 选择一个单床,双床或一张床,设置为2,3或4层.
3. 检查床号码,房间和楼层.
4. 调整床型,物理结构,层次和尺寸数量.
5. 检查每个空间的代码,位置和客人容量.
6. 复习 活动和单独预订,以及房间的租用模式.
7. 选择保存床.

选择预设仅会填入表单字段。 必须保存后才会创建记录。

## 床床的例子

双层床包含上、下两个实体床位。 请分别为下铺和上铺设置编号。 一张双人床可以是一个床位，但可容纳两个人。 床位数量与可住人数不是同一指标。

## 从房间表格中添加床

房间创建/编辑表格允许您选择床型和数量. 这些被添加到现有的实际床家具中. 要更换现有床,请编辑记录,而不是添加另一个.

保存后,检查定义列表中的床位代码和 [3D 视图](/zh-cn/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-cn/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.