Updated: 2026-02-20
In trading, Reduce-only is an order flag that ensures the order can only reduce or close an existing position, not increase it. This glossary entry explains why reduce-only matters, how traders use it, and how to track it with evidence instead of vibes.
Quick definition
Reduce-only: an order flag that ensures the order can only reduce or close an existing position, not increase it.
Reduce-only is an order flag that ensures the order can only reduce or close an existing position, not increase it. The practical version is: can you define it as a field you can log and audit later?
Most trading terms become confusing when they are used as vibes instead of variables. Your goal is a definition that helps you decide size, stop, entry timing, or whether to skip the trade.
Traders sometimes confuse Reduce-only with close position. Treat them as separate variables in your journal so your reviews stay honest.
Reduce-only prevents accidental position flips and unintended increases during volatility. It is a simple safety rail that prevents operational errors.
If Reduce-only never changes your decision, it is just jargon. The term earns its place when it improves your process consistency under real market pressure.
A useful mental model: plan first (risk and invalidation), execute second (order type and fills), review last (tags and metrics).
Use it to make one decision pre-trade. Example decisions: where the stop goes, whether to take partials, how to scale size, or whether conditions are too thin to trade.
Write the rule in one sentence, then run it consistently for a week. Consistency matters because it creates comparable data for review.
If the rule fails, adjust slowly. Do not rewrite the whole system after one bad session.
Log whether exits were reduce-only and whether any accidental size increases occurred. Operational mistakes should be tracked separately from strategy mistakes.
Use tags so you can slice results by regime and behavior state. The same term behaves differently when volatility changes or when you are fatigued.
Your review question should be binary: did this variable improve outcomes or reduce rule breaks? If not, simplify.
You are short 1 BTC and place a buy order for 3 BTC without reduce-only. If it fills, you end up long 2 BTC, which is not what you planned.
The point of an example is not to predict price. It is to show what you would log before the trade and what you would audit after the trade.
Leaving reduce-only off during partial exits and accidentally adding risk when you intended to de-risk.
The fastest way to improve reduce-only is to remove one failure mode at a time. If you try to fix everything, you will fix nothing.
Reduce-only matters most when volatility is high and the book is thin. That's where small execution errors compound into expectancy drag.
Before you trade, decide what matters more: price control (limits) or fill certainty (markets/stops). Then trade the choice consistently for one week so your data is comparable.
If you change order types every time you feel stressed, your metrics will lie to you.
Reduce-only is an order flag that ensures the order can only reduce or close an existing position, not increase it. In practice, it matters when it changes a concrete decision like size, stop placement, or whether you skip a trade.
They are related but not identical. In your journal, track Reduce-only as its own variable and treat close position as a separate context factor so you can audit each cleanly.
Log whether exits were reduce-only and whether any accidental size increases occurred. Operational mistakes should be tracked separately from strategy mistakes.
Leaving reduce-only off during partial exits and accidentally adding risk when you intended to de-risk.
See plans and run one weekly review loop with Tiltless: edges, leaks, and enforceable next actions.
