> 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/faqs.md).

# FAQs

### **Does placing a Scaled Order count as a market order or a limit order?**

A Scaled Order is made up of multiple **limit orders** distributed across a selected price range. It is not a market order.

***

### Scaled Order vs. TWAP

<table data-header-hidden><thead><tr><th></th><th width="253"></th><th></th></tr></thead><tbody><tr><td>Feature</td><td><strong>Scaled Order</strong></td><td><strong>TWAP (Time-Weighted Average Price)</strong></td></tr><tr><td><strong>Execution Logic</strong></td><td>Places multiple <strong>limit orders</strong> at predefined price intervals within a chosen price range.</td><td>Splits a large order into smaller <strong>market orders</strong> when executed evenly over a fixed time period.</td></tr><tr><td><strong>Control Factor</strong></td><td>Controlled by <strong>price levels</strong>.</td><td>Controlled by <strong>time</strong>.</td></tr><tr><td><strong>Execution Guarantee</strong></td><td>Execution not guaranteed – only orders at reached price levels will fill.</td><td>Full order is typically executed as long as liquidity exists.</td></tr><tr><td><strong>Primary Objective</strong></td><td>Cost averaging and laddered entry/exit across multiple price levels.</td><td>Minimize market impact and achieve an average price over time.</td></tr><tr><td><strong>Market Dependency</strong></td><td>Highly dependent on price movement; orders fill only if the market hits your levels.</td><td>Less dependent on price movement; trades are executed over time regardless of volatility.</td></tr></tbody></table>


---

# 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/faqs.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.