> For the complete documentation index, see [llms.txt](https://dasus.gitbook.io/dasus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dasus.gitbook.io/dasus-docs/trading/scale-orders.md).

# Scale Orders

A scale order splits one order into several limit orders spread across a price range, placed in a single step. Instead of one big limit at one price, you ladder your entry or exit across levels and build or unwind the position gradually as price moves through the range.

Scale is one of the **Pro ▾** order types in the [Pro terminal](https://dasus.gitbook.io/dasus-docs/the-app/web-terminal.md), on perps and spot alike (and, with whole shares, on [prediction markets](https://dasus.gitbook.io/dasus-docs/trading/outcomes.md)).

## Why use scale orders

* **Better average price** — you never commit the whole size at one point; fills average out across the levels you set.
* **Less market impact** — several smaller resting orders are absorbed more gently than one large one.
* **No manual laddering** — ten limit orders by hand is slow and error-prone; here a few parameters build the whole ladder and send it at once.
* **Discipline** — you define the range and the sizing before the market moves, not level by level as it does.

{% hint style="info" %}
Scale orders are **limit orders**: they fill only at your prices or better, and may fill partially, fully or not at all. If price never enters the range, nothing executes. For time-based execution use a [TWAP](https://dasus.gitbook.io/dasus-docs/trading/twap.md) instead.
{% endhint %}

## Parameters

| Field                   | What it does                                                                                                                                                                              |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Size**                | The total size, in the coin or in USDC, split across the ladder                                                                                                                           |
| **Start / End**         | The two ends of the price range, in the quote token; either can be the higher one. **Mid** fills in the current price                                                                     |
| **Total Orders**        | How many limit orders the size is split into: **2 to 20**                                                                                                                                 |
| **Skew**                | How the size is weighted along the ladder: `1` = equal sizes; `2` = the last order (at the End price) is twice the first, growing linearly in between; `0.5` = the last is half the first |
| **TIF**                 | GTC, IOC or ALO (maker), applied to every sub-order                                                                                                                                       |
| **Reduce Only** (perps) | Every sub-order can only reduce the position                                                                                                                                              |

## Rules

| Rule                  | Value                                                                                                                                          |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Number of orders      | 2–20 (Hyperliquid's batch limit per request)                                                                                                   |
| Spacing               | Prices evenly spaced from Start to End                                                                                                         |
| Minimum per sub-order | **$10** — checked on the smallest sub-order at its own price. The button reads *Each scale order must be ≥ $10* until it passes                |
| Sending               | One batch. Hyperliquid judges each sub-order on its own: if some are accepted and some rejected you see *k of N orders placed* with the reason |
| Order Details         | **Start**, **End**, **Order Value** at the ladder's weighted average price and, on perps, **Margin Required**                                  |

## Example: buying a dip

BTC is at $65,000 and you want to accumulate a long if it pulls back, without guessing where the dip ends. You place a buy scale order with Start $64,000, End $61,000, 6 orders, size 0.6 BTC and skew 2:

| Order | Price  | Size       |
| ----- | ------ | ---------- |
| 1     | 64,000 | 0.0667 BTC |
| 2     | 63,400 | 0.0800 BTC |
| 3     | 62,800 | 0.0933 BTC |
| 4     | 62,200 | 0.1067 BTC |
| 5     | 61,600 | 0.1200 BTC |
| 6     | 61,000 | 0.1333 BTC |

* **Price dips to $63,000 and bounces:** only the top two orders fill. You hold a small position with a good entry; the other four keep resting.
* **Price sweeps the whole range:** all six fill and your average [entry price](https://dasus.gitbook.io/dasus-docs/trading-concepts/entry-price-pnl.md) sits below the middle of the range, because the skew put more size at the cheaper levels.
* **Price never enters the range:** nothing fills. Cancelling resting limit orders costs nothing — fees apply to fills only; see [Fees](https://dasus.gitbook.io/dasus-docs/the-app/fees.md).

## Monitoring and cancelling

Each sub-order is an ordinary limit order in the **Open Orders** tab, where you can:

* see which levels have filled and which are still resting;
* **Modify** or **Cancel** individual sub-orders to reshape the ladder;
* use **Cancel All** to clear the book — note that it cancels **every** open order shown in that tab (all perps or all spot orders), not just the ladder.

Filled sub-orders behave like any fill: they update the position, its entry price and [PnL](https://dasus.gitbook.io/dasus-docs/trading-concepts/entry-price-pnl.md), and appear in Trade History.

{% hint style="info" %}
A scale entry on a leveraged market adds exposure as price moves *against* the direction of your ladder. Keep an eye on margin and on the [liquidation price](https://dasus.gitbook.io/dasus-docs/trading-concepts/liquidation.md) as levels fill, and consider a [stop loss](https://dasus.gitbook.io/dasus-docs/trading/tp-sl.md) on the resulting position.
{% endhint %}

## Tips

* **Match the ladder to your thesis.** A wide range with many orders suits gradual accumulation; a tight range with few orders behaves like a single limit order.
* **Use skew on purpose.** Skewing size toward the far end gives a better average if the whole range fills, but smaller fills if price only grazes the near end.
* **Watch the minimum.** With a small total size, fewer orders keep every sub-order above $10.
* **Use ALO for the maker rate.** A scale ladder sent as ALO is rejected level by level if a level would cross the book, so keep Start on the right side of the current price.


---

# 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://dasus.gitbook.io/dasus-docs/trading/scale-orders.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.
