> 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/exchange/trading/order-types/scaled-order.md). # Scaled Order A Scaled Order is a trading strategy that places multiple buy or sell orders at predefined price intervals, either above or below the current market price. This creates a series of smaller orders that scale into or out of a position gradually, rather than executing a single large order. ### **When to Use?** * When you want to **average your entry or exit price** over a range instead of committing at one price point. * Suitable for traders who expect **gradual market movements** or who want to reduce the impact of volatility and slippage. * Often used to **ladder into positions** during uncertain market conditions or to **ladder out** when taking profits. *** ### **Key Points** * Helps reduce the risk of poor timing by spreading orders across different price levels. * Can be configured with the number of orders, price range, and distribution (equal or weighted). * Execution depends on market movements — some or all orders may remain unfilled if the price does not reach those levels. * Useful for both **long-term accumulation strategies** and **short-term trading in volatile markets**. --- # 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/exchange/trading/order-types/scaled-order.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 `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.