OCO (One Cancels the Other) links two orders so that when one order executes, the other is automatically cancelled. It’s a simple concept that helps you avoid “double execution” and manage trades more cleanly.
In plain English: “If this happens, cancel that.”
OCO is less about “strategy” and more about clean execution and risk management.
With OCO, you place two orders as a linked pair. The platform monitors them together:
OCO is often available on exchanges and advanced platforms. Some retail CFD platforms offer a version of it through “linked” stop-loss and take-profit settings.
You enter a trade and attach:
If your take-profit hits, the stop-loss is cancelled. If your stop-loss hits, the take-profit is cancelled.
You expect a big move but don’t know the direction. You can place:
OCO ensures only one side triggers, avoiding being filled on both sides in whipsaw conditions.
OCO does not remove risk. It removes operational mistakes — like leaving conflicting orders open or accidentally entering twice.
Before relying on OCO, understand how your platform implements it:
After placing OCO, always check your open orders list to confirm both legs are present and linked.
You buy EUR/USD at 1.1000. You set:
These are linked as OCO:
This prevents the common mistake of leaving the “other order” open and accidentally reversing or doubling your position later.
Try answering before expanding the model answers.
One Cancels the Other. It links two orders so that if one executes, the other is cancelled automatically.
Bracket exits (take-profit + stop-loss) and breakout entries (buy stop above + sell stop below).
Whether the OCO link is server-side or client-side, and how partial fills affect cancellation.
If you can explain these points, you understand how OCO reduces operational errors in trading.
MetaTrader supports attached stop-loss and take-profit orders on positions, which behave like an OCO relationship. Some brokers and add-ons also provide explicit OCO order tools.
No. Slippage is about execution and liquidity. OCO is about order relationships. If the triggered order is a stop (market), it can still slip in fast markets.
Ideally, the first execution cancels the other immediately. In extreme volatility or with client-side linking, edge cases can occur. That’s why server-side OCO is preferable and why you should monitor around major news.
You can, but it depends on your platform. Scaling out typically requires multiple take-profit levels and careful handling of the remaining stop-loss size.
OCO (One Cancels the Other) links two orders so that execution of one automatically cancels the other. It is widely used for bracket exits (TP + SL) and breakout entries (up or down), reducing operational mistakes and order conflicts.
Next lesson: Partial Fills.