Post-only and reduce-only orders on crypto (spot and futures), what they mean, when to use them, and why they get rejected

You place a limit order, you expect it to sit there calmly, then the exchange throws it back like a bounced payment. It usually happens with post-only reduce-only orders, because these two flags are strict, and the matching engine doesn’t care about your intention. Post-only is about how you enter the order book (maker behavior). Reduce-only is about what your order is allowed to do to your position (close only, not open). They sound similar because both are “safety” toggles, but they protect different mistakes. This guide explains what they mean on spot and perpetual futures, when they help, and why they get rejected (including the annoying edge cases like partial fills and mark price triggers). Post-only orders (spot and futures): “Let me be a maker, or cancel me” Photo by AlphaTradeZone A post-only order is a limit order with one extra rule: it must not execute immediately when it hits the matching engine. If it would fill right away (even a tiny amount), the exchange cancels or rejects it. Think of the order book like a queue at a shop. Post-only means “I will stand in the queue, I won’t cut to the front.” If your price would cut to the front (cross the spread), the system refuses it. On spot, post-only is mostly used to avoid taker fills and to keep fee behavior predictable (maker vs taker). If you want the fee intuition to be clearer, see the XXKK 2026 fee structure and maker vs taker guide. On futures/perps, it’s the same logic, but it matters even more because spreads can jump fast, and your “safe” price can become marketable between click and accept. Typical rejection text is boring and direct: “Post only would execute immediately” “Post-only order would be filled” Also, some venues offer a “smart” mode that auto-adjusts the price to stay maker, instead of rejecting. Crypto.com describes that behavior in Smart Post-Only Orders. Other exchanges just cancel it and make you re-place. Reduce-only orders (mostly futures): “Close my risk, don’t flip me” Reduce-only is a position rule, not a book rule. It tells the exchange: this order can only reduce an existing position. If the order would increase exposure (or open a new position), it must be rejected or auto-shrunk. This is why reduce-only is mainly a futures/perpetual feature. In spot, you don’t have a long/short position in the same mechanical way (unless you’re in margin products, which varies per platform). Common uses: Take-profit limit orders that should never turn into a new short. Stop-loss orders that should never “reverse” you during a wick. Cleanup orders when you’re de-risking after partial closes. A key detail: reduce-only interacts with position mode. One-way mode: you have one net position per symbol. Reduce-only is usually simple: it can only shrink that net size. Hedge mode: you can hold long and short at the same time (separate position sides). Some exchanges require an explicit positionSide, and some restrict reduceOnly in hedge mode in certain APIs. Binance’s derivatives API notes this kind of constraint in its futures new order parameters. Exchange docs explain the “shrink, don’t grow” promise in plain terms, but wording differs: Bybit: Reduce-Only Order OKX: Reduce-only Typical rejection text: “ReduceOnly order rejected” “insufficient position” “would increase position” When to use post-only vs reduce-only (and when not to) These flags aren’t magic profit switches, they’re more like guardrails. Use them when your biggest risk is the order doing the “wrong kind of fill”. Here’s a practical mapping you can keep in your head: Flag What it does When to use Common rejection reason Post-only Forces maker behavior (no instant fill) Passive entry, providing liquidity, fee control Post-only would execute immediately Reduce-only Can only reduce an existing position Take profit, stop loss, closing leg of a hedge Insufficient position, would increase position A simple example that matches real life: You are long 0.5 BTC perp, and you place a sell limit for 0.5 with reduce-only as take profit. Good. Later, you manually close the position early, but forget the take-profit order is still open. Without reduce-only, that resting sell can open a new short if price rallies into it. With reduce-only, it should get rejected (or auto-reduced to zero), depending on venue rules. Post-only is not for emergencies. If you need out now, post-only is like insisting the door must open slowly. In fast markets, you may get nothing, and watch price run away. If you’re still getting comfortable with basic order flow, it helps to re-check how limit vs market behaves on a normal spot screen (order book, bids/asks, open orders). This walkthrough stays simple: XXKK spot trading order types explained. Why post-only and reduce-only orders get rejected (plus the tricky edge cases) Most rejections come from the engine protecting the rule you selected, not from a “bug”. The problem is traders read the chart, while the engine reads the book and your position ledger. Fast rejection reasons you’ll see Message (typical) What it usually means Quick fix Post only would execute immediately Your limit price crosses the spread (or equals best opposite) Move price one or more ticks away from top of book ReduceOnly order rejected Order would open/increase a position Check side, positionSide, and current position size insufficient position You’re trying to reduce more than you have (after fills) Reduce quantity, cancel overlapping close orders would increase position Reduce-only sell on a short, or buy on a long, or wrong hedge side Correct direction, verify one-way vs hedge mode invalid price tick/lot size Price or size doesn’t match the market increments Use the pair’s tick size and step size order would trigger immediately Your stop trigger is already hit (often by mark price) Move trigger away, confirm trigger type (mark/last) Some exchanges publish these failure buckets openly. For a futures-focused list of failed order causes, Phemex has a clean summary in Summary of Failed Orders in Phemex Futures. Edge cases that make good orders fail 1) Partial fills change what “reduce” means.Reduce-only is checked against your remaining position, not your original plan. If you were long 1.0, your stop reduced 0.6 already, then your old take-profit reduce-only sell for 1.0 may now be “too big”. Some venues auto-adjust, others reject, others leave it resting but cap the executable size. 2) Order amendments can flip a post-only into a taker.You place post-only safely, then you edit price closer. If the new price crosses the spread, it can get canceled on amend. Many people read this as random, but it’s consistent: post-only is re-validated on change. 3) Crossing the spread is not always obvious.Hidden liquidity and rapid top-of-book moves mean your price can become marketable during the milliseconds between submit and match. A post-only buy set “at the bid” can still execute if the ask falls into it. Result: reject. 4) Mark price vs last price triggers can surprise you.On perps, stops often use mark price to reduce manipulation. So your reduce-only stop might trigger even when last price looks untouched, or it might not trigger when last price spikes. If your stop triggers and closes the position, your remaining reduce-only orders can start failing with “insufficient position”. 5) Hedge mode needs correct position side.In hedge mode, a reduce-only order must target the correct side (LONG vs SHORT). If you send a reduce-only sell but your short is the one open (or the platform reads it that way), the engine sees “would increase position” and rejects. Risk and behavior note Order flags are exchange features, not universal law. Matching rules, trigger price choices, and whether an exchange auto-resizes reduce-only orders can differ. Before using real size, read your venue’s docs, for example Bybit’s Post-Only Order explanation and the reduce-only pages linked earlier, then test with small quantity. Crypto trading involves real loss risk, and futures trading adds liquidation risk. This is not financial advice. Conclusion Post-only protects you from accidental taker fills, reduce-only protects you from accidental position flips. If you treat post-only reduce-only orders like seatbelts, not turbo buttons, they do their job quietly. When you get a rejection, don’t fight the message, translate it: check spread crossing, tick size, and position size first, then check mark vs last triggers and position mode. The engine is strict, but it’s also predictable once you learn what it’s checking.