Crypto futures platforms often place small checkboxes next to the order ticket, but those flags can change the risk profile of a trade. Reduce-only and post-only are two of the most useful examples because they constrain what an order is allowed to do after it reaches the exchange.
Kraken explains that a reduce-only order is allowed to execute only if it reduces the number of open contracts in an existing position. If the order size is larger than the open position, the quantity may be reduced to the open size. That makes it useful for exits, staged take-profit orders and stop workflows where the trader does not want to accidentally flip direction.
Post-only is different. Binance and Kraken describe it as a limit-order instruction intended to add liquidity. If the order would immediately trade as a taker, it is rejected or canceled instead of crossing the spread. That can help fee-sensitive traders, but it can also mean the order does not fill during a fast move.
The practical workflow is to decide the job first. Use reduce-only for orders whose only purpose is closing or trimming a position. Use post-only when maker execution is more important than immediate entry. Do not use post-only for urgent stops, because the order may fail to execute if it would cross the market.
These flags are risk controls, not signals. They cannot fix oversized leverage, poor stop placement or illiquid contracts. They simply reduce one class of execution error when the trader already has a clear plan.
Sources:
- Kraken Support: derivatives order types
- Binance Futures: types of order
- Binance.US: post-only, iceberg and time-in-force
- Cube Exchange: what is a post-only order
- Bybit Help Center: reduce-only order
Risk notice: Futures and perpetual contracts are leveraged products. Order flags can reduce execution mistakes but cannot remove market, liquidity or liquidation risk.
原创文章，作者：financial transaction，如若转载，请注明出处：https://www.fanbi.net/archives/1753
