OTOCO Orders Explained: Enter and Exit in One Submission

OTOCO, or One-Triggers-OCO, connects an entry order with the exits that should become active after that entry fills. It lets you define an entire trade upfront: entry, profit target, and stop-loss, submitted together as a linked structure rather than three unrelated orders. The useful part is not that OTOCO makes the trading decision for you. It is that the relationship between the entry and the exits can be defined before the position exists.

The mechanic, in plain terms

An OTOCO order has two parts. The first is an entry order, typically a limit or stop order at the price you want to get in. The second is an OCO pair: a profit target and a stop-loss linked so that when one exit executes, the other is canceled according to the OCO instructions. The OCO exits do not begin working independently before the entry. They are contingent on the entry order filling. The sequence is:

1. The entry order is submitted.
2. The entry fills.
3. The linked OCO target and stop become working.
4. If one of those exits executes, the other is canceled.

Schwab and thinkorswim use the term "First Triggers OCO" for this type of structure. OHLCX calls the workflow OTOCO, or One-Triggers-OCO. The terminology differs, but the core relationship is the same: one entry triggers a linked pair of exits.

A worked OTOCO example

Say a stock is trading at $48, and you want to buy if it breaks above $50, with a profit target at $56 and a stop at $47 once you're in. An OTOCO structure could be configured as:

• Entry: Buy stop for 100 shares at $50
• Profit target: Sell limit for 100 shares at $56
• Protective stop: Sell stop for 100 shares at $47

Before the entry fills, the $56 target and $47 stop are waiting as the contingent OCO pair rather than working as independent exits on a position you do not yet own. If the entry never fills, the OCO exits never become working exits for a new position. If the entry fills, the $56 target and $47 stop become active as a linked pair. From there:

• If the $56 limit order executes first, the $47 stop is canceled.
• If the $47 stop triggers and its resulting order executes first, the $56 target is canceled.

The whole sequence was defined before the position opened.

The $50 entry is not necessarily a $50 fill

There is an important detail in this example. A standard buy stop at $50 uses $50 as the activation price. Once triggered, it generally becomes a market order. If the stock moves quickly through $50, the actual entry can occur above that price. The same principle applies to the protective stop. A $47 stop is a trigger, not a guarantee that the position will exit at exactly $47. OTOCO coordinates the order sequence. It does not guarantee the prices at which those orders ultimately execute.

Why attach the exit to the entry?

The alternative is straightforward:

1. Submit the entry.
2. Wait for it to fill.
3. Notice that it filled.
4. Build the target and stop.
5. Submit the exits.

That can work. But it leaves the exit workflow dependent on the trader returning to the position after the entry. OTOCO removes the need for that separate manual step because the exit instructions have already been defined as part of the order structure. This is different from saying OTOCO removes execution risk or guarantees continuous protection. It does not. Broker processing, market conditions, gaps, liquidity, and order behavior still matter. What it does is make this instruction explicit ahead of time: If this entry fills, activate these exits. That is the practical value of the structure.

What should you decide before submitting an OTOCO order?

Because OTOCO connects several parts of the trade, the trader needs to define more than an entry price. Before sending the structure, you should know:

• What triggers or fills the entry
• How large the position should be
• Where the profit target belongs
• Where the protective stop belongs
• Whether those levels still make sense if the entry executes away from the trigger price
• What order types are being used for each leg

That last point can matter more than it first appears. If the intended entry is $50 but a stop order fills at $50.40, the original $56 target and $47 stop now represent slightly different distances from the actual fill than they did from the planned trigger. The linked structure executes the instructions you submitted. It does not automatically decide whether those instructions still represent the risk/reward relationship you intended.

OTOCO vs. OCO: what is the difference?

A standalone OCO starts with a position that already exists. The trader has the position and wants two linked exits, commonly a target and stop. OTOCO starts one step earlier. It includes the order that creates the position and then triggers the OCO exits after that entry fills. The distinction is: OCO: existing position → target + stop OTOCO: entry → target + stop If you're already holding the position, adding another entry simply to create an OTOCO structure would not solve the problem you actually have. A standalone OCO is usually the more direct structure for adding linked exits to an existing position.

When is an OTOCO order useful?

OTOCO can make sense when the trader already knows the intended entry and exit structure before entering the trade. For example:

• A breakout entry where the target and stop are already defined
• A limit entry where you do not want to return later to attach the exits manually
• A trade where the entry should only be followed by one specific target-and-stop structure
• A workflow where defining the exit before the entry goes live is part of the trading process

It is less useful when the trader intentionally wants to decide the exit only after seeing how the position develops. That is not a flaw in OTOCO. It simply means the order type should match the plan.

How OTOCO fits into the OHLCX exit workflow

OHLCX supports OTOCO as an Entry + Bracket structure alongside OCO, TSP, TRIM, and TRIMMER. The exit flow can be selected while the order is being structured, before the entry is sent. With OTOCO, the trader defines the entry and its linked target-and-stop structure ahead of time. OHLCX carries those user-defined instructions into the broker-connected execution workflow. The platform does not determine:

• Whether the trade should be entered
• Where the target belongs
• Where the stop belongs
• Whether the risk/reward relationship is appropriate

Those decisions remain with the trader.

What OTOCO does not solve

An OTOCO order can coordinate entry and exit instructions. It cannot make the underlying trading plan correct. It also does not eliminate:

• Slippage
• Gaps
• Liquidity constraints
• Partial fills
• Execution away from a stop trigger
• Market risk
• Poor position sizing
• A target or stop that does not fit the setup

A linked order structure is still only as useful as the instructions inside it. OTOCO's job is more specific: Define what should happen after the entry before the entry happens. That is what separates it from entering first and building the exit afterward.