On Bitget, a Post-only order can cancel because it would immediately take liquidity; an IOC order can fill partly and cancel the rest; an FOK order must fill completely at once or cancel. A canceled label therefore does not always mean that nothing traded. Check filled quantity, individual executions and remaining exposure before placing another order.
Last verified: September 10, 2026. This guide explains execution conditions, not a trading recommendation. Available options and labels depend on the Bitget product, account and interface. Use the current order ticket and official documentation for your account; a translated page does not establish regional eligibility.
Bitget order conditions at a glance
| Condition | Execution rule | What happens to unfilled quantity? | Main trade-off |
|---|---|---|---|
| GTC | A limit order may execute now or wait | Normally remains open until filled or canceled, subject to platform rules | Waiting orders still need monitoring |
| Post-only | Only enter the book as maker; cancel if immediately marketable | May rest if accepted without an immediate match | Maker execution is prioritized over immediate execution |
| IOC | Execute immediately as much as possible within the limit | Cancel the remainder | Partial exposure can remain |
| FOK | Execute the full quantity immediately within the limit or none | Cancel the entire order if full execution is unavailable | No partial fill, but the desired trade may not happen |
These are execution conditions, not profit protections. Bitget’s UTA enumeration defines the conditions separately from position mode and Reduce-only. Do not confuse whether an order may increase exposure with how long it remains executable.
Why a Post-only order cancels immediately
Post-only protects the maker instruction: it cancels instead of immediately matching a resting opposite-side order. A normal limit order is not automatically a maker order. If a buy limit crosses an available ask, or a sell limit crosses an available bid, it can take liquidity. Bitget explains this cancellation behavior in its futures order-type guide.
Illustration, not a live quote: assume the best bid is 99 USDT and the best ask is 100 USDT. A Post-only buy at 100 USDT would immediately match the ask and therefore cancel. A buy at 99 USDT may rest instead, but a changing order book can alter the result before the exchange receives it. The last traded price alone does not describe the available opposite-side liquidity.
If immediate execution is essential, recognize the conflict with a maker-only instruction rather than repeatedly submitting the same price. Do not remove Post-only merely to make an error disappear: first reconsider price, urgency, fees and the risk of leaving an existing position open. Maker status does not guarantee profit or a particular discounted fee rate.
IOC versus FOK: the same order book, different result
Consider a hypothetical buy for 10 units with a limit of 100 USDT. Assume only 6 units are immediately executable at that price or better, and ignore fees and other validation limits for the illustration:
- IOC: 6 units execute and the remaining 4 are canceled.
- FOK: the full 10 cannot execute immediately, so the order cancels without a fill.
- GTC: 6 units may execute immediately and the remaining 4 may stay open.
The practical danger is reading an IOC cancellation as a zero position and resubmitting all 10 units. If that second order fills fully, total purchases become 16 units, not 10. For this example only, 10 minus 6 leaves 4 units of the original target. In a real account, reconcile other fills, open orders and current positions before deciding whether any replacement is appropriate.
FOK is an all-or-none execution condition, not a promise that the exchange can fill the trade. Liquidity visible on screen can disappear. Conversely, canceling an IOC remainder does not reverse completed executions. Bitget’s order-status best practices explicitly describe an IOC transition from partial execution to cancellation.
Check these records before submitting again
- Confirm the exact Bitget product, account, symbol and order ID.
- Read the selected execution condition, side, original quantity and limit price.
- Check cumulative filled quantity and individual trade records, not only the final status.
- Compare current exposure with all other open orders. For futures, verify whether the instruction was opening or closing.
- Read the cancellation reason or error message. A rule-based cancellation is different from a margin or account-access rejection.
- If the result is unclear, resolve it in order history or with official support before retrying. Preserve a timestamp with its time zone, but never share a password, API secret or one-time code.
For saved evidence, follow the Bitget transaction and order-history export guide. If the order never passed margin, size or account validation, use the separate Bitget futures order-rejection checklist. This page focuses on execution conditions after submission rather than repeating those account checks.
API users: an order ID is not proof of a fill
The current UTA order endpoint exposes timeInForce independently of orderType and reduceOnly. Its documented default is GTC when the limit-order time-in-force value is omitted. This is an API rule, not evidence that every web or app ticket shares that default. See the current order-management reference for your integration.
A successful submission response and assigned order ID acknowledge receipt; inspect subsequent order status and fills. Bitget also instructs clients to query the existing order using its client order ID after specified timeout or unknown-error responses. Do not convert an uncertain response into an automatic duplicate order. Field names and cancellation labels differ across endpoints, so match the documentation to the account and API version.
FAQ
Does a canceled Bitget IOC order mean no trade occurred?
No. The canceled part can be only the unfilled remainder. Completed fills still count, so inspect executed quantity and current exposure.
Does FOK allow a partial fill?
No. Under the documented FOK condition, full immediate execution is required; otherwise the entire order cancels. IOC is the condition that permits immediate partial execution.
Will Post-only guarantee my position closes?
No. It can cancel or wait instead of executing immediately. Confirm actual remaining exposure; do not treat a maker-only order as an emergency-exit guarantee.
Can I use these instructions in every region and product?
This guide does not establish availability. Check your actual Bitget account and current product terms. Korean and other language versions explain the same mechanics; they do not authorize access to restricted products or bypassing regional controls.
Methodology, affiliation and risk disclosure
BitQED is an independent educational publisher, not Bitget support. The linked official documents were checked on September 10, 2026. Definitions come from Bitget; the hypothetical order-book example and verification checklist are BitQED’s explanation. Platform documentation and interfaces can change.
BitQED may receive compensation through affiliate links elsewhere on this site. This article contains no signup offer, guaranteed rebate or VIP entitlement. Crypto trading involves market, custody and regulatory risks; leveraged positions can be liquidated and lose their margin rapidly. Choosing an execution condition does not remove these risks. This is not investment advice.
Bitget Convert vs Spot: Fees, Quotes and Net Amount
For a fill-by-fill check of the fee actually charged, see Bitget Fees Higher Than Expected? Maker, Taker and Trade History Checks