Managing Entries and Exits with OTO, OCO, and OTOCO Orders

Summary

This tutorial explains how linked conditional orders can coordinate an entry with profit-taking and stop-loss exits. A one-triggers-other setup holds secondary orders until a primary entry fills. A one-cancels-other link cancels one exit when its counterpart fills or is cancelled. Combining both creates an OTOCO bracket: an entry triggers a take-profit and stop-loss pair, and those exits cancel each other once one executes.

Examples use BTC perpetual orders to show queued exits, order labels, and proportional placement after partial entry fills. The interface allows one take-profit and one stop-loss per primary order, matches their size to the entry, and validates price direction; API users can construct more varied combinations without those checks. The tutorial lists supported exit order types and advises testing order behavior in a test environment, especially for API-created combinations. It describes order mechanics rather than a trading strategy, and does not address execution guarantees, slippage, or venue-specific risks beyond its stated validation differences.

Key ideas

• OTO orders activate secondary orders after the primary order receives a fill.
• OCO links two orders so that one is cancelled when the other fills or is cancelled.
• OTOCO combines an entry trigger with mutually linked take-profit and stop-loss exits.
• The interface supports one take-profit and one stop-loss per entry, with matching size and price checks.
• UI conditional orders can place proportional exit quantities after partial fills, while API combinations require careful construction and testing.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.