> For the complete documentation index, see [llms.txt](https://quteng.gitbook.io/ke-hu-wen-da-ji/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quteng.gitbook.io/ke-hu-wen-da-ji/xiao-shou/chang-jian-wen-ti/shi-yong-app-xia-ding-hu-bie-shi-ju-wei-gou-mai-shu-liang-da-dao-shang-xian-shi-wei-shen-mo.md).

# 使用App下訂戶別時，車位購買數量達到上限是為什麼？

銷售系統內，一處「購買限制設定」，提供下訂戶別時的車位選購數量限制設定。

#### **路徑**：

銷售系統 > 購買限制設定

***

#### **操作方式**：

1. 選擇建案後，前往 **銷售系統 > 購買限制設定** 頁面。
2. **強制購買車位**：您可以設定每戶必須要購買的車位數量。若設定為「不強制購買車位」，將參考「車位比」作為限制。

   <figure><img src="https://1264781745-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvNcUddmvlmoPF9rp4roy%2Fuploads%2FIqrHlfczRYZ219Z2Z03S%2Fimage.png?alt=media&amp;token=2d73cbc1-8f5c-4c0d-934a-4bea527de4e4" alt="" width="563"><figcaption></figcaption></figure>
3. **車位比**：指的是 **建案中「車位總數」與「房屋戶數」的比例**。 這是衡量建案停車位是否充足的重要指標。透過設定這個基準數值，來決定系統要對當前建案實際未售的車位比採用哪一套購買上限規則。
   * **車位比 > 1**：表示平均一戶可以分配到一個以上的車位，停車位較為充裕。
   * **車位比 = 1**：表示平均一戶剛好可以分配到一個車位。
   * **車位比 < 1**：表示並非每戶都能買到車位，可能需要抽籤或有特定條件才能購買。
4. **車位數比以上最多可購買車位數**：當建案的「實際車位比」大於或等於基準車位比數值時，每戶最多可以購買n個車位。
5. **車位數比以下最多可購買車位數**：當建案的「實際車位比」小於基準車位比數值時，每戶最多只能購買n個車位。


---

# 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://quteng.gitbook.io/ke-hu-wen-da-ji/xiao-shou/chang-jian-wen-ti/shi-yong-app-xia-ding-hu-bie-shi-ju-wei-gou-mai-shu-liang-da-dao-shang-xian-shi-wei-shen-mo.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.