> For the complete documentation index, see [llms.txt](https://docs.ezorderly.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ezorderly.com/guide/dashboard/sales-analysis.md).

# 銷售分析

### 商品類別銷售趨勢 <a href="#page_title" id="page_title"></a>

1\. **調整產品結構之參考**：若有過去熱銷的產品類別近期營收下滑，就要調整其內部的產品組合，以獲得最大營收；而若有近期銷售成長的產品類別，則可以考慮拓展新品項。

2\. **看出特定產品類別的熱銷檔期**：可以看出特定時間、季節、節慶前後，是否有哪個商品類別熱銷，以調整行銷資源分布。

＊注意：須設定商品類別後，本圖表才會顯示資料，不同顏色代表不同商品類別，游標靠近後會顯示名稱。

![商品類別銷售趨勢](/files/PmNeyEjlbczvJx3KnyYC)

### 商品類別排行 <a href="#page_title" id="page_title"></a>

1\. **比較不同商品類別銷售情況**：從本圖可以檢驗不同類別的銷售成績，是否達到品牌原本設定的目標。

2\. **挖掘熱銷商品類別**：可以看出主要帶來營收的商品類別，了解目前的會員對什麼商品類別最感興趣。

![商品類別排行](/files/NXzuFC11GOgIlQ6gt5Da)

### 商品銷售表現 <a href="#page_title" id="page_title"></a>

1\. **找到黃金商品**：從圖中可以看出主要帶來營收的黃金商品，也是顧客偏好的商品，不僅須加強注意安全庫存，避免缺貨影響業績，更可用以調整銷售策略，判斷是否投注更多行銷資源。

2\. **銷售數與銷售額交叉分析**：若銷售數很高，但銷售額排名不理想，可以考慮調整商品定價，提升產品利潤空間。

![商品銷售表現](/files/PcOB9zyiQCzT3mAEcQN0)


---

# 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.ezorderly.com/guide/dashboard/sales-analysis.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.
