OCO Orders: Linked Cancellation and Partial Execution

What one-cancels-the-other means

A common OCO arrangement pairs an upper sell limit with a lower conditional sell instruction for the same intended quantity. The group coordinates alternatives within the product. Its name alone does not establish whether the lower instruction becomes a market order or a limit order, or whether the other leg disappears on triggering, partial filling or full filling.

The Binance.US OCO guide, for example, describes cancellation of the other order when one is partially or fully filled. Treat that as a documented implementation rather than a universal rule for every service. Before submitting a group, identify the exact event that changes its other leg and what remains active afterward.

Read five fields in a ten-unit example

Assume a hypothetical asset is referenced at 100 and you hold ten units. Your supported OCO group links a sell limit at 110 with a stop-limit sell triggered at 95 and limited at 94. These figures explain fields, not suitable trading levels. Assume the service accepts this combination and all quantity, balance and precision requirements are met.

The lower fields do not mean selling at both 95 and 94. One is a trigger; the other constrains the resulting execution price. Also, two alternative legs do not necessarily mean reserving twenty units. Reservation mechanics belong to the product. Check its balance display instead of adding the two displayed leg quantities and calling the result your exposure.

Scenario one: three units sell at the upper limit

Suppose suitable buying interest fills three units at 110, producing gross proceeds of 330 before fees. In this scenario the group cancels the opposite stop leg upon the partial fill. Seven units remain unfilled on the upper leg, subject to that instruction’s remaining lifetime. They no longer necessarily have the original linked stop instruction.

Write down the actual outcome: three sold, seven unsold, and a separate status for each leg. A summary label saying the OCO was processed does not turn all ten into cash. Nor does the disappearance of the lower leg establish that the upper one filled completely. The fill list, not the group’s abbreviated label, measures execution.

If you later change how you manage the remaining units, reconcile existing open instructions first. A new ten-unit group based on the original amount would ignore the three already sold. Start from the confirmed holdings and remaining target, including any independent trades or asset-denominated fees that changed the available balance. Do not infer availability solely from the initial group quantity.

Scenario two: the stop triggers without a sale

Now suppose the trigger condition at 95 occurs, but available buyers afterward offer only 93. A sell limit of 94 cannot accept 93. Depending on the product, the triggered lower leg can therefore remain unfilled. If its linkage rule cancels the upper leg at triggering, you may have one active instruction and no sale at all.

That is a coherent operational result: the cancellation rule worked while the surviving order could not find an acceptable execution. Review the order list for active instructions, the fills for completed sales and the balance for available holdings. These are related records, but none should be used as a substitute for the others.

A lower leg that becomes a stop-market instruction has a different price behavior. The illustrative 94 floor would not automatically exist in that arrangement. Execution can differ from the trigger, subject to the product’s protections. The stop-market versus stop-limit guide explains this distinction. Verify which instruction your actual group creates.

Two independent orders do not establish a link

Submitting one sell order at 110 and an unrelated stop at 95 does not by itself cause either to cancel the other. They might also compete for reserved balance, or be governed by different account features. A genuine relationship should be supported by documented product behavior and identifiable group membership, rather than a visual arrangement that merely places two rows together.

For an external automation service, ask where the rule runs. A platform-native group can be different from software that waits for a notification and then sends a cancellation request. Connectivity and event-processing delays matter to the second arrangement. Closing a local program does not prove that every instruction it previously submitted has disappeared from the exchange.

Keep group and leg records together

Save the group identifier and both order identifiers, original quantity, cumulative executed quantity and active remainder. Include creation, triggering, fill and cancellation times when available. A cancellation can result from the user, the linkage rule or another operational event. Its reason matters when determining whether the group still matches the intended instruction.

For each fill, record quantity, execution value and fee currency. Three units sold tells you quantity, but it does not establish net proceeds. A quote-currency commission reduces those proceeds directly; a fee in another asset needs separate accounting or a documented conversion. For the arithmetic of multiple fills, use the weighted average fill guide rather than averaging prices without their quantities.

Cancel and replace using the confirmed remainder

After a lost submission response, look for the existing group before sending another. The server may have accepted it even though your device never received confirmation. Search by available identifiers, pair and time, then check both legs and fills. A connection error describes communication uncertainty, not necessarily rejection of the trading instructions.

The same principle applies to cancellation. A fill can occur before the server processes the cancellation even if its notification arrives later. Recalculate the intended remaining quantity from the final record. Read the scope of a cancel-all action carefully, since it can affect instructions beyond the group currently on screen.

1. Confirm that the product supports the required linked order types.
2. Identify which event cancels the opposite leg.
3. Check quantity, precision, available balance and reservation rules.
4. Separate a trigger from the resulting order’s price constraint.
5. Save group and leg identifiers, then reconcile fills after every change.

Keep automation and economic outcomes separate

The upper level is not guaranteed profit, and the lower level is not automatically a maximum possible loss. Either needs an appropriate execution mechanism and sufficient matching liquidity. Linked cancellation manages instructions; it does not validate the selected prices, remove commissions or eliminate the need to monitor the remaining quantity.

If the next step is withdrawal, use the transfer fee calculator for that separate cost. If the purpose is simply educational monitoring, the watchlist can record an asset without creating a live sale instruction. The practical test for an OCO group remains concrete: know which units sold, which instructions remain and whether the surviving arrangement still matches your intention.

Continue reading