Iceberg Orders: Slicing Large Trades to Reduce Market Visibility
Summary
An iceberg order algorithm divides a large order into smaller visible orders and refreshes them as fills occur or market depth changes. The article describes three execution preferences: quick execution, a balance between price and speed, and seeking a better price. Its balanced example places successive buy orders from the midpoint between the best bid and ask down through bid levels. Users set order size, visible order count, total quantity, and a limit price; the example also pauses placement when the market moves above the buy limit.
The method aims to reduce the visibility and potential market impact of a large order, while allowing execution to adapt to changing book levels. The walkthrough is tied to one exchange interface and does not quantify slippage, fees, fill probability, or performance against alternative execution methods. Smaller displayed orders can still reveal activity over time, and the document provides no evidence that iceberg execution always improves price or avoids market impact.
Key ideas
- An iceberg algorithm exposes a portion of a larger order and replenishes orders as executions or book changes occur.
- Execution preferences trade off speed against price placement and queue position.
- Order size, visible order count, total quantity, and a limit price shape the execution instructions.
- A limit condition can pause new buy orders when the market rises above the specified price.
- Reduced visibility may lessen market impact, but execution quality and information leakage are not quantified.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.