> 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/xiao-shou-she-ding/hu-bie-yu-ju-wei-ding-jia-liu-cheng.md).
# 戶別與車位定價流程
此階段為銷售前置的必要作業，目的在於將實體的房屋與車位轉換為系統可銷售的項目，並賦予明確的價格。設定完成後，所有售價與狀態資料將自動同步至銷售系統的「銷控總覽」，確保前後台數據即時連動。
### Part 1. 戶別金額管理
**路徑**： 後台系統 > 建案管理 > 戶別金額管理
**操作流程**：
系統提供兩種設定方式，您可依據作業習慣擇一執行：
* **方法一：Excel 批次匯入**
1. 點擊畫面上方的 **範本下載**，取得標準表單。
2. 於檔案中建置各戶別對應的金額資訊並存檔。（*注意：底價不會顯示於銷售前台，僅為內部備註用，系統將以售價為主要參考。*）
3. 點擊 **戶別匯入** 按鈕，上傳該檔案即完成批次定價。
* **方法二：系統批次修改**
1. 點擊畫面上的 **售價批次修改** 按鈕。
2. 直接於系統介面中批次選擇戶別，並輸入或調整各戶別售價，最後點擊 **送出**。
***
### Part 2. 車位金額管理
**路徑**： 後台系統 > 建案管理 > 車位管理
**操作流程**：
1. 初次建置建案時，需要新增車位，點擊畫面 **新增車位+** 來設置該建案的車位資料。（**亦可於第二點-Excel批次匯入，檔案建置時，將車位一同匯入系統。**）
2. 車位的定價，同樣提供兩種操作模式：
1. **方法一：Excel 批次匯入**
1. 點擊畫面上方的 **範本下載**，取得標準表單。
2. 於檔案中建置車位編號與對應金額資訊並存檔。
3. 點擊 **車位匯入** 按鈕，上傳該檔案即完成批次定價。
2. **方法二：系統批次操作**
1. 若為單筆或小量建置，請先點選 **新增車位+** 建立車位基底資料。
2. 接著點選 **批次操作** 按鈕，於介面中統一設定車位售價並儲存。
---
# 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 dynamically 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/xiao-shou-she-ding/hu-bie-yu-ju-wei-ding-jia-liu-cheng.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 `build a script that syncs our docs to a CMS` 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.
