Order

[[order]] places a “raw” buy (long) or sell (short) order. Unlike the standard entry block, it does not include automatic position management logic and simply executes the requested volume instruction.

Chaining after an Order block#

An [[order]] block submits an order request. That request is then processed by the engine through its order pipeline, and the position state is updated on the next candle cycle. Depending on when the strategy evaluates the next block, some position information may not be up to date yet.

You control when the [[order]] block chains to the next block with the wait_candles key:

• With wait_candles = 1, after a signal on a candle, the engine waits for the next candle before evaluating the next block, so position data (position, average price, and related fields) is up to date.
• With wait_candles = 0, the next block is evaluated on the same candle as the signal, making the chaining immediate.

By default, wait_candles is 1.

In all cases, wait_candles does not change how the order is executed. It only shifts when the strategy moves on to the next block.

Differences with the Entry Block#

While both blocks can be used to open a position, the Order block is characterized by a much more permissive and manual behavior:

In most cases, prefer [[Entry]]: it respects pyramiding and handles reversals cleanly. [[order]] is for advanced use and requires precise exposure control.

Order type#

The order type depends on whether limit and stop are provided. Without limit or stop, the block submits a market order. With limit only, it submits a limit order. With stop only, it submits a stop market order. With both limit and stop, it submits a stop-limit order. The stop level is the trigger. Once that level is reached, the order becomes a limit order at the limit price.

Block declaration#

A strategy can contain multiple [[order]] blocks.

Examples#

Minimal order#

This example places a basic long order with a fixed quantity and then moves to monitor_exit.

[[order]]
id            = "buy_order_1"
order_id      = "buy_1"
direction     = "long"
qty           = 1
next_block_id = "monitor_exit"

Stop-limit order#

This example places a long stop-limit order. When the market reaches stop, Whale-E activates a limit order at the limit price, then the strategy moves to next_step.

[[order]]
id            = "breakout_long"
order_id      = "long_bk"
direction     = "long"
stop          = "high + 10"
limit         = "high + 10"
next_block_id = "next_step"

OCA group across multiple orders#

In this example, the two [[order]] blocks create two distinct orders that belong to the same OCA group. If one order is filled, the other is cancelled. An OCA group therefore links multiple distinct orders. It is not the association between limit and stop inside a single block.

[[order]]
id            = "breakout_long"
order_id      = "long_bk"
direction     = "long"
stop          = "high + 10"
oca_name      = "breakout_grp"
oca_type      = "cancel"
next_block_id = "next_step"

[[order]]
id            = "breakout_short"
order_id      = "short_bk"
direction     = "short"
stop          = "low - 10"
oca_name      = "breakout_grp"
oca_type      = "cancel"
next_block_id = "next_step"

Block Parameters#

Local sizing priority#

In [[order]], the engine always follows the same priority:

1. if qty is defined, that absolute quantity is used
2. otherwise, if qty_percent is defined, that equity percentage is used
3. otherwise, the engine falls back to the global [backtest] configuration

In other words, qty and qty_percent make the global sizing inactive for that order.

Meaning of qty_percent#

In [[order]], qty_percent always means a percentage of equity.

When qty_percent is present, [[order]] is treated as a percent_of_equity order, even if [backtest].default_qty_type is fixed or cash.

For details about sizing price versus execution price, refer to Using Margin and Leverage in Whale‑E.