> For the complete documentation index, see [llms.txt](https://docs.hotcake.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotcake.app/hungerapp/bills/ye-ji-tong-ji-luo-ji.md).

# 業績統計邏輯

## 業績分類

1. <mark style="color:blue;">**服務（技術）業績：點擊報到後，會連動預約資料進行結帳**</mark>
2. 商品業績：銷售商品給會員
3. 票券業績：銷售票券給會員
4. 儲值業績：會員儲值（入金）

{% hint style="danger" %}
業績要被夯客系統自動計算，需要透過<mark style="color:blue;">**結帳**</mark>來完成！
{% endhint %}

## 銷售票券的業績計算

> 會員購買10張美甲券 $10000（套餐包堂），業績是怎麼計算的？\
> （該票券有設定 額外業績 $900)&#x20;

1. **執行票券結帳，將票券銷售給客人**

該位服務人員(設計師)會納入 「票券業績」$10000、營收收入$0

2. **會員來店消費，使用票券抵用當次消費**

該位服務人員(設計師)會納入 「服務業績」$900、營收收入$0

***

## 服務業績的結帳在哪？

點開預約並報到後，服務結帳的按鈕就會出現！

<figure><img src="/files/eLR8kjZl6bm9jr8gcRLt" alt=""><figcaption></figcaption></figure>

## 請問其他業績的結帳在哪？（商品、票券、儲值金）

<figure><img src="/files/3nMOypcdfrTN8Q7NPuRx" alt=""><figcaption></figcaption></figure>


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hotcake.app/hungerapp/bills/ye-ji-tong-ji-luo-ji.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.