A reduce-only order is restricted by the exchange to only shrink or close an existing position — it can never open a new position or flip one to the opposite side, even if the order size would otherwise be large enough to do so. That restriction exists specifically to prevent an exit order from accidentally becoming a new entry.

Key takeaways

• Reduce-only caps an order's effect at zero position size — it will fill up to flat and then stop, never crossing into the opposite direction.
• Without reduce-only, an oversized 'closing' order on the wrong side can flip a long into a short instead of just closing it.
• Reduce-only is most valuable during fast-moving markets, when a stale mental math error is more likely and most costly.
• Automations and bots benefit from reduce-only on exit orders specifically, since a bug that doubles an intended close size becomes harmless instead of catastrophic.
• Reduce-only does not guarantee a fill or protect against slippage — it only constrains direction and final position size, not execution price.
• DRKN does not place reduce-only or any other order type; it reviews account exposure so you can decide what to close and by how much.

What reduce-only actually restricts

A normal order simply executes the size and side requested. If a trader holding a 2 BTC long submits a 3 BTC sell order without reduce-only, the exchange fills all 3 BTC: 2 BTC closes the long, and the remaining 1 BTC opens a new short. The trader intended to exit; the account ends up with an unintended short position instead.

With reduce-only enabled on that same 3 BTC sell order, the exchange fills only up to the amount needed to bring the position to zero — 2 BTC — and rejects or cancels the remainder rather than opening the unintended short. The setting does not change what the trader typed; it changes what the exchange is willing to execute with that instruction.

A worked example: an exit order gone wrong without it

A trader holds a 1.5 ETH long at $3,100, worth roughly $4,650 of notional exposure. Wanting to close the full position quickly during a fast move, they type a market sell order for 2.5 ETH by mistake — a stale size left over from a previous, larger position. Without reduce-only, the exchange fills all 2.5 ETH: 1.5 ETH closes the long, and 1 ETH opens a new short at the current fast-moving price.

The trader now holds an unplanned $3,100 short in a market moving quickly, discovered only when checking the account afterward — the opposite of what 'closing the position' was supposed to accomplish. With reduce-only enabled on that same order, the fill would have stopped at 1.5 ETH, closed the long exactly as intended, and left the account flat with no new exposure created by the typo.

When reduce-only matters most

• Fast, volatile markets, where quick manual order entry is more error-prone and a stale position size is easy to mistype under time pressure.
• Automations and bots with exit logic, where a code bug that miscalculates close size becomes a rejected extra fill instead of a new, unintended position.
• Closing a position across multiple partial orders, where reduce-only prevents the cumulative total from ever overshooting into the opposite side.
• Any situation where the trader's goal is specifically 'get to flat' rather than 'take a new directional view' — reduce-only enforces that boundary at the exchange level.

Common mistakes with reduce-only

• Assuming reduce-only protects against slippage or guarantees a fill — it only restricts direction and final size, not execution price or fill certainty.
• Leaving reduce-only off by default on exit orders in an automation, when it should typically be the default for any order whose purpose is closing exposure.
• Not realizing a reduce-only order can be partially filled and then effectively canceled for the remainder if the position was smaller than expected — leaving less closed than intended.
• Confusing reduce-only with a stop-loss or take-profit order type — reduce-only is a size/direction constraint that can be applied to many order types, not a trigger condition on its own.

Review your current exposure before placing a large closing order: DRKN can show your position size, leverage, and concentration on a connected, read-only Toobit account so you know exactly what 'closing' should mean for that position. It is educational risk guidance — it does not place reduce-only or any other order for you.

Reduce-only in cross margin vs isolated margin

The mechanics of reduce-only are the same in both margin modes — it still caps the order at flat and blocks any overshoot — but the stakes differ. In isolated margin, an accidental flip to the opposite side opens a new position with its own separate collateral and liquidation price, which at least stays contained to that one position's allocated margin. In cross margin, an accidental new position draws on the account's shared equity immediately, which can affect the liquidation distance of every other open position at the same time. That shared-margin effect is one more reason reduce-only is worth enabling by default on cross-margin accounts specifically.

Reduce-only and account-level risk review

Reduce-only prevents one specific execution mistake, but it does not tell you whether closing, trimming, or holding is the right decision in the first place — that is a separate, account-aware question covered in hold or close: a framework for live futures positions. Once you've decided to reduce exposure, reduce-only is the setting that keeps the mechanical execution of that decision from accidentally becoming a new position.

Checking this before your next fast exit

Confirm reduce-only is available and enabled on the order types you actually use for closing, before a fast market forces a rushed decision. This matters most for traders who size positions manually rather than through a formula — see futures position sizing: a simple formula for real accounts for how a consistent formula reduces the odds of a stale-size mistake like the one reduce-only is designed to catch.

Frequently asked questions

Does reduce-only cost anything extra to use?

Reduce-only is generally a free order setting on major venues, not a separate paid feature. Check your specific exchange's documentation for how it's implemented, since exact behavior can vary by platform.

Can I use reduce-only to open a new position smaller than expected?

No. Reduce-only only permits orders that reduce or close existing exposure — it will reject or limit any order that would result in a new or larger position in either direction.

Does DRKN set reduce-only on my orders automatically?

No. DRKN does not place orders of any kind. It reviews your account's current exposure and leverage so you can make an informed sizing decision when you place the order yourself on Toobit.