What Is a Bracket Order in Futures? Entry, Stop and Target, Linked
A bracket order is an entry with a stop and a profit target attached, linked so the first one to fill cancels the other — and it is built by your platform or your broker, because CME's documented Globex order types do not include it.

A bracket order is an entry order with a stop and a profit target hung off it, arranged so that filling the entry puts both exits into the market at once and filling either exit removes the other. Sierra Chart's documentation, which calls the arrangement attached orders, says a parent order with one stop and one target attached "is commonly known as a bracket order".
The exchange did not sell you this. CME's client systems documentation lists five order types for futures and seven qualifiers to put on them, and a bracket is none of them: it is a structure your charting platform, or your broker's servers, assemble out of ordinary orders. Which is why two traders on the same contract can have brackets that behave differently under stress.
What is a bracket order in futures trading?
A bracket order in futures is one entry order plus the exits attached to it. Sierra Chart's documentation names the parts: the order you actually submit is the parent, and everything attached to it is a child or attached order. Children act as price targets, as stops, or as one of each, and a child is always on the opposite side from its parent — attach anything to a buy, and the children are sells.
Children related to each other are siblings. When a parent carries both a target and a stop, those two siblings go into a group the documentation labels OCO, for order cancels order, and that grouping is what makes a bracket a bracket.
One child is enough. Sierra Chart permits as few as one, so a bare entry-plus-stop is a legal configuration, with no OCO pair in it because there is nothing for the stop to cancel. Nesting is the configuration that is out: an attached target or stop cannot itself carry attached orders, and the documented workaround is to send a second standalone order on the same side at that price, then bracket the new one.
Does CME Globex accept a bracket order as an order type?
CME's own documentation does not list a bracket among the order types Globex accepts. The client systems wiki, read on 19 November 2026, gives five order types available to futures: two that can sit on the book at a price (limit, market-limit), one market order carrying a price cap (market order with protection), and two that stay off the book until a trade triggers them (stop order with protection, stop-limit). The companion iLink page lists the same five by their tag 40 message codes.
Separately, Globex accepts seven order qualifiers — the duration-and-quantity instructions that ride along with an order type. A qualifier carries three attributes, of which only one is required: a duration. Display quantity and minimum execution quantity are both optional, and an order submitted with no duration stated is treated as a day order. There is more on what each duration does in time in force in futures.
Across the article text of all three of those CME pages on 19 November 2026 — Order Types for Futures and Options, iLink Order Types and Order Qualifiers — there is not one case-insensitive occurrence of "bracket", "OCO" or "order cancels order".
What does OCO mean on a bracket order?
OCO stands for order cancels order, and in a bracket it means the target and the stop are tied so that resolving one resolves the other. Per Sierra Chart's documentation, a full fill on one active child causes the other member of its OCO group to be cancelled. A cancel on either member takes the second one out as well.
Partial fills are handled by arithmetic rather than by cancellation. A child that fills part of its quantity has its group partner's quantity reduced by the amount filled, and the partner stays working for the remainder. On the parent side the same logic applies: a partial fill on the entry activates the children at the quantity that actually filled.
Who performs the cancelling depends on the connection. Where the trading service supports server-side OCO, the documentation says the service handles the cancel and the sibling's quantity adjustment — though Sierra Chart has to be told to hand that job over, through a global trade setting named Use Server Side OCO Orders.
A child's duration is set independently, as Day or Good till Canceled, and a child left as a day order is cancelled at the end of the day, in simulated and non-simulated trading alike.
How are the stop and target prices set on a bracket?
The prices are set as offsets — a distance from the parent's price. Sierra Chart's documentation specifies each attached order with one or more offsets, defines an offset as how far the child's price sits from the parent order price, and gives four units to express it in: ticks, a fixed price distance, a percentage, or an actual price, the last of which abandons the offset idea and names the level outright.
Offsets are always typed as positive numbers. The software works out the direction from two things: which side the parent is on, and what kind of child it is. That gives four rules, which fall out as a grid:
| Child order type | Parent is a buy | Parent is a sell |
|---|---|---|
| Limit or market-if-touched (the target) | offset added to parent price | offset subtracted |
| Stop, stop-limit or trailing stop | offset subtracted from parent price | offset added |
Two wrinkles follow. A market-order parent has no price to measure from, so offsets come off the last trade price, with a percentage offset computed from quote data and rounded to the nearest tick. And once the parent fills, the children can be re-pointed at the actual fill price to hold the distance you asked for, which happens only when a global setting for it is enabled, and does not happen at all on a server-managed bracket.
Can a bracket order have more than one target?
Yes, and the constraint that shapes everything is per-group. Sierra Chart's rules allow one target and one stop inside an OCO group, which caps a group at two orders, so scaling out at two prices takes two groups. The platform supports eight numbered groups plus a special All setting.
Using more than one group splits the parent. The entry quantity is divided into that many linked orders, up to eight, and the totals have to fit: group quantities summed cannot exceed the parent quantity, and inside a group the target and stop quantities are forced to match automatically. A separate rule states the same ceiling from the other side — whichever is larger, the summed targets or the summed stops, has to come to no more than the main order quantity — and an order coming to less is still submittable.
The All setting is the shortcut for one stop covering several targets. A stop set to All OCO Groups is split into one stop per group holding an opposing order: one All stop against targets in groups 1 and 2 produces two stops and no more, each taking its group's quantity. One of Sierra Chart's two stated reasons for splitting rather than combining is that server-side OCO requires identical quantities within a group; the trade-off is that separate stops can be moved independently and a common stop cannot.
Another platform sets the ceiling lower: Quantower's Local SL/TP offers a simple stop-and-target pair or a tiered scheme capped at three tiers.
Where does a bracket order actually live?
A bracket can be held in three places, and which one decides what survives a crash. Sierra Chart's documentation describes all three: the platform on your own machine, the trading service handling only the OCO link, or the service handling the whole bracket. Which one you get depends on the connection.
| Platform-managed | Service-managed OCO | Service-managed bracket | |
|---|---|---|---|
| Where children sit before the entry fills | inside the platform, inactive, quantity 0 | inside the platform | sent to the service with the parent |
| Who cancels the sibling | the platform | the trading service | the trading service |
| What a dropped connection does | orders already sent keep working, with the OCO link lost | orders already sent keep working, and the cancel is the service's to perform | the platform has no part in managing them once they are sent |
| How you can tell | Trade Activity Log, Order Action Source: "Client side bracket order" | same field: "Server side OCO order" | same field: "Server Side Bracket Order" |
Before the entry fills, platform-managed children sit inactive at quantity zero, and Sierra Chart sends them only on a real-time fill notification — a late or historical status update does not count. Our R|Trader Pro setup notes cover the server-side half: brackets, trailing stops and OCO orders held at Rithmic survive the laptop dying. Our Sierra Chart setup page covers the same gap from the platform side: children hanging off an entry that is still unfilled are held inside the platform, and go out when the entry does.
With server-side brackets, Sierra Chart sends parent and children together and then says it has no responsibility for managing them, and that "Normally, this will be safer", with an immediate caveat: the external service may not manage them exactly as the platform would. Quantower's connection table shows uneven ground, giving server-side brackets single and multiple on one futures routing connection, single only on Rithmic, and neither brackets nor OCO on one crypto spot connection. Where a connection has nothing native, Quantower's Local SL/TP fills the hole on the platform side, and its documentation is blunt about the cost: closing the platform permanently deletes every local stop and target, and losing a connection deletes the ones belonging to it with no restore on reconnect. ATAS puts a comparable warning about locally simulated OCO in front of you at first connect.
When does a bracket order fail to protect a position?
Sierra Chart documents the conditions under which attached orders may not behave as expected in live trading, and opens that list by saying the conditions are uncommon and that they cannot occur in the platform's own trade simulation mode. Both qualifiers are stated for the whole list, so they apply to every item below. They come to three problems.
The stop arrives after the market has already gone past it. The entry fills, the market runs against the new position, and by the time the stop is transmitted its price is on the wrong side of the market. Exchanges normally reject a sell stop at or above the current market, and a buy stop at or below it; the documentation gives the rejection text as "Sell order stop price must be below last trade price". The preconditions it names are a tight stop, a fast market against the entry, and an exchange that rejects. One documented response is a setting that resends a rejected stop child as a market order against the position the parent opened; where the bracket is managed on the platform side, a target still working is cancelled when that market order fills.
A quantity increase is rejected. When an entry fills in pieces, the children are sent at the first fill's quantity and then modified upward. The page documents two causes for the modification failing. One is a simultaneous fill: the child being increased fills before the pending modification is performed, so the modification is rejected. A setting exists to reactivate a child whose modification was rejected during a fill. The other is a position limit on the account or insufficient margin, which can reject either the initial transmission or the increase, with the rejection logged in the Trade Activity Log.
The platform was switched into simulation mode first. With children held client-side and the entry not yet filled, turning on trade simulation mode before that fill means the children are never sent to the live trading server.
What does a bracket order mean on a funded futures account?
On a simulated funded account, a bracket's stop is what holds one trade inside the gap from your balance down to your drawdown line, which is monitored in real time and liquidates the account on a touch. That makes the stop offset the number to set first.
The arithmetic is plain multiplication: a stop N ticks from the entry on C contracts risks N × C × the tick value. On our published instrument figures as of 19 November 2026, ES is $12.50 a tick and MES $1.25, so forty ticks on two ES and forty ticks on twenty MES both risk $1,000 — the same money, reached at the mini ceiling and the micro ceiling a $25K account gets under our published contract limits. Turned round, it sizes the trade: a $500 budget over a forty-tick MES stop is ten contracts, and over an eighty-tick stop, five.
Scaling out across OCO groups does not change that total. Group quantities sum to no more than the parent quantity, so splitting one entry across two groups cannot put more contracts on than sending it as one — and those limits count everything open at once, not per trade and not per instrument, with anything above the ceiling rejected platform-side.
One rule a bracket cannot satisfy for you is the flat time. Nothing here stays open past 4:45 PM ET, or past 12:45 PM ET on a shortened session, and whatever is still open at that moment is closed automatically, the result counted into balance and drawdown. A resting target is a hope about the close.
FAQ
Is a bracket order a real exchange order type?
No. On the three CME client systems pages that enumerate Globex order types and qualifiers, read on 19 November 2026, the words "bracket", "OCO" and "order cancels order" do not appear in the article text at all. Those pages list five futures order types, and Globex supports seven qualifiers. A bracket is assembled above the exchange, out of those components, by your platform or by your broker's servers.
What happens to the other side of a bracket when my target fills?
It is cancelled. Sierra Chart's documentation says a full fill on one child in an OCO group causes the other member to be cancelled, and that a cancel on either member removes the second as well. A partial fill behaves differently: the sibling's quantity is reduced by the amount filled and it keeps working for the rest, so a half-filled target leaves a half-sized stop in place.
Will my bracket still work if I close my charting platform?
It depends entirely on where the bracket is held. Children already transmitted to a trading service keep working through a lost connection. Children still waiting on an unfilled entry sit inside the platform, and Sierra Chart's documentation says a fill noticed only after reconnecting — a historical indication rather than a real-time notification — does not activate them. Quantower is blunt about its own local stops and targets: closing the platform permanently deletes all of them.
Can I use one stop for two profit targets?
Yes, through the All OCO Groups setting. Sierra Chart splits a stop set to All into one order per group that holds an opposing order, so one All stop against targets in groups 1 and 2 becomes two stops, each sized to its group. The documented trade-off is adjustment: separate stops can be moved independently of each other, whereas a common stop set this way cannot, unless the link between them is explicitly removed.
Sources
- CME Group Client Systems Wiki — Order Types for Futures and Options
- CME Group Client Systems Wiki — iLink Order Types
- CME Group Client Systems Wiki — Order Qualifiers
- Sierra Chart — Attached Orders Feature
- Quantower documentation — Order Types (connection capability table)
- Quantower documentation — Local SL/TP
- Lumen Futures — Instruments and tick values
- Lumen Futures help center — Contract limits
- Lumen Futures help center — Trading hours and the flat time
- Lumen Futures help center — Drawdown explained
- Lumen Futures help center — Sierra Chart setup
- Lumen Futures help center — R|Trader Pro setup
- Lumen Futures help center — ATAS setup
Educational content about futures markets and simulated trading. Not investment advice, and not a solicitation to trade. Trading futures involves substantial risk of loss. Read the full risk disclosure.