> For the complete documentation index, see [llms.txt](https://support.backpack.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.backpack.exchange/support-docs/cn/jiao-yi-suo/jiao-yi/ding-dan-lei-xing/fen-duan-ding-dan.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://support.backpack.exchange/support-docs/cn/jiao-yi-suo/jiao-yi/ding-dan-lei-xing/fen-duan-ding-dan.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.