Limit orders at Kraken, Coinbase and Bybit: price, fills and fees

Limits across the three platforms: a price boundary, not a guaranteed trade

A buy limit sets the maximum price the buyer accepts; a sell limit sets the minimum price. On Kraken Pro, Coinbase Advanced and applicable Bybit products, that boundary does not commit the exchange to filling the entire quantity. It also does not make every fill maker. Possible outcomes include immediate execution, resting on the book, a partial fill, rejection or cancellation under additional instructions.

This distinction matters when moving from a simple purchase with an all-in quote. An order book contains other participants' instructions and available quantity at each level. The entered price is a condition for trading, while average price and executed quantity come from the fills that actually occur. An asset holding or position starts with execution, not merely with a row appearing among open orders.

The comparison concerns order-book interfaces and distinguishes spot from derivatives rather than copying options between them. It is not a ranking of matching speed or liquidity quality: no orders were submitted and no latency measurements were performed.

Start with the Kraken review, Coinbase review and Bybit review. Then define the price boundary, intended quantity and permitted waiting period for an order. All three answers are needed to understand its outcome.

Kraken Pro, Coinbase Advanced and Bybit: documented controls

Identify both the product and the setting on each platform. A menu available in futures does not prove that the same option exists in the same form for spot. The table presents documented behavior without filling unknown fields or assuming identical accounts.

These similarities do not erase differences in display, minimum size, quantity precision or supported validity. Check those on the order screen and in the product documentation. A contract unit should not be copied into a spot asset quantity, and every entered decimal should not be assumed acceptable without rounding.

Check market status too. Coinbase documents statuses that can restrict trading, so displaying a pair is not permission to trade it. An option unavailable in an account calls for clarification, rather than an alternate route to circumvent the restriction. This comparison explains order logic; it does not establish account or product eligibility.

A limit example: maximum price and average fill price

Assume an imaginary spot order book. The intended purchase is 0.05 BTC with a limit of USD 40,000 per BTC. Sellers offer 0.02 BTC at USD 39,980 and another 0.03 BTC at USD 40,000. If those quantities remain available when the order arrives, both portions satisfy the price boundary and can execute.

The first portion costs USD 799.60 and the second USD 1,200. Together they deliver 0.05 BTC for USD 1,999.60 before fees. The average price is USD 39,992 per BTC. That is below the entered limit without requiring the order to wait on the book. Such an order can take existing liquidity and be classified as taker.

The example is neither a market quote nor a forecast of execution at any provider. Sellers can cancel and other orders can arrive between viewing the book and submission. Inspect the fill history afterwards rather than copying the pre-submission screen price into the records.

Net asset receipt can also differ from executed quantity if the fee is collected in the purchased asset. Record fill quantity, notional and the fee in its own currency separately. Do not collapse these into a single figure called “price” without defining its denominator. This preserves the distinction between a limit, an average fill and the total acquisition cost when comparing executions.

The boundary concerns a fill's unit price, not necessarily all-in cost after charges. A purchase inside the limit can therefore cost more than quantity multiplied by price alone. Check how the ticket expresses quantity and funding: selecting an asset quantity is not always selecting a total spending budget. Budget control needs room for applicable charges and review of the quoted total. No common balance-reservation rule is asserted across providers; this is a display and account-condition check. It also helps investigate discrepancies: a correct fill price with different total spending need not violate the limit, but may reflect an added fee.

Partial fills at Kraken, Coinbase or Bybit: what remains open

In the same example, suppose only the first 0.02 BTC is available. Of the requested 0.05 BTC, 0.02 BTC has executed, leaving 0.03 BTC. That remainder may rest, cancel or prevent the original order from being accepted, depending on execution and validity instructions. A “partially filled” label is not necessarily a fault to repair with another identical order.

Before acting again, check cumulative executed quantity, open remainder and order status. Resubmitting the entire request while the previous remainder is live can create more total exposure than intended. A cancellation request is not itself proof of completed cancellation: a fill may occur while the request is processed. Establish status from confirmation and history, not user intention.

Average price must be weighted by each fill's quantity. A simple average of two prices is appropriate only when their quantities are equal. Check whether fees appear per fill or are summarized per order, so they are not counted twice.

For spot, the result is a partial asset balance plus money that may remain reserved for the open order. For futures, inspect position status and closing instructions separately. A partially executed entry does not automatically make a previously prepared exit suitable; its quantity must correspond to existing exposure and the product rules.

Limit-order fees: maker and taker roles on each fill

Maker and taker describe a fill's relationship to the book. An order that executes immediately in part and leaves a resting remainder can contain both roles. Coinbase Advanced explicitly distinguishes the immediate portion charged as taker from a remainder later filled as maker. One rate therefore cannot be selected merely because the ticket says Limit.

Consider a hypothetical immediate notional of USD 800 and another USD 1,200 filled later. For teaching only, assume a 0.3% taker fee and a 0.1% maker fee. The charge is USD 2.40 + USD 1.20 = USD 3.60. These rates are not a Kraken, Coinbase or Bybit schedule and must not be used to plan an account charge.

Check the rate applicable when the order is placed and the pair-specific rules. Account tier, channel and product can alter the outcome; Coinbase Advanced can even have identical maker and taker rates. “Maker is always cheaper” is therefore not a rule for every pair.

Comparing interfaces should include whether each fill can be understood, rather than only whether the button exists. Accurate cost review requires notional, time, liquidity role and fee. Recording an intention to be maker does not replace the actual classification.

Post-Only across the platforms: preventing immediate execution and its trade-off

Post-Only asks a limit to join the book instead of immediately matching an existing order. Kraken describes cancellation of an immediately matching instruction; Coinbase Advanced describes rejection; Bybit describes cancellation. The practical result protects the liquidity-providing condition. It does not ensure that the user receives the asset or closes exposure regardless.

Suppose the price observed before submission allowed the order to rest, but the opposite side moved before it arrived. Without Post-Only, it might execute as taker within the price limit. With the setting enabled, it may be rejected or cancelled. That is an expected consequence of the rule, rather than necessarily a server fault. Understand the cancellation reason before submitting another instruction.

The option fits a willingness to accept waiting risk in order to retain maker classification. Someone needing to reduce exposure at a particular time must recognize that the rule can prevent execution precisely when prices move quickly. This is not a recommendation to disable it; it identifies the execution-certainty trade-off.

Do not confuse a personal order setting with a market status in which the entire exchange allows only orders that join the book. Those are different layers of conditions. Even when the setting avoids a taker fee under the applicable schedule, it neither guarantees profit nor limits position losses during the wait.

Limit validity: IOC, FOK and resting on the book

Price and quantity do not define a complete instruction without validity. GTC describes an order remaining live until execution or cancellation under product rules. IOC attempts immediate execution of available quantity and cancels the remainder. FOK requires a complete immediate fill or cancellation. Coinbase Advanced also documents a specified-time option. Not every order-type and validity combination exists in every market.

For example, when only part of the quantity is available within the limit, IOC can leave a partial purchase without an open remainder. FOK can leave no execution because the full-quantity requirement was not satisfied. Those outcomes are not contradictory: the instructions differ. Check the chosen setting rather than the outcome preferred afterwards.

Long validity can leave an order active after its original reason has changed. Record when it should be reviewed and who is responsible for cancellation. A planned asset purchase and an order forgotten on the book are different workflows even if their numerical boundaries are identical.

Documentation of a particular Bybit futures option does not establish that it exists on Kraken Pro or Coinbase for the same product. Compare the actual instruction conditions: what must execute immediately, what can remain and what cancels the request. These matter more than similarly named checkboxes in different interfaces.

Ordinary limits, stops and derivatives: keeping conditions distinct

An ordinary limit defines a price at which an order may execute. A stop adds a condition that activates a later action, and a stop-limit submits a limit instruction once triggered. The trigger price is not the guaranteed trade price. If the market passes the limit boundary, an exit can remain unfilled after its trigger has occurred.

This matters particularly when an instruction is intended to manage risk. Adding the word Stop does not create a guaranteed maximum loss. Trigger reference, quantity and execution rules depend on the product. The stop-market versus stop-limit guide separates activation from execution.

For futures, also establish whether an instruction opens or reduces a position. Settings such as Reduce-Only are documented for particular Bybit contexts rather than as a universal field across all markets. A spot sell should not be copied as though it necessarily closes futures exposure. A direction or quantity error can produce a different action from the intended one.

A provider comparison around orders should begin with the task: buying an asset below a maximum price, selling above a minimum price or reducing exposure under a specified market condition. Then choose a supported configuration. A familiar label saves learning only when it describes the same behavior in the same product and quantity unit.

Checking an order across the three platforms: before and after fills

Before confirmation, read the instruction as a complete sentence: buy or sell, product, quantity, price boundary, validity and Post-Only condition if selected. Check that the total fits the intended balance and exposure. Spot and futures require different checks for balances, collateral and risk; switching between them calls for a fresh review.

After confirmation, look for an order identifier and the system's accepted status. A rejected instruction does not create a new asset merely because the form was completed. For an accepted order, inspect fills, remaining quantity and fee currency. Following a disconnect or ambiguous message, establish status before submitting again so an already accepted request is not duplicated.

A reader seeking price control can find it in limits on the three examined platforms, subject to the product. A reader specifically requiring maker classification should check Post-Only and accept cancellation risk. A reader needing the full quantity immediately must understand validity conditions and the possibility of no execution.

Choosing an interface is not choosing an asset or obtaining guaranteed execution quality. Proper records explain the outcome without guessing: the limit was a condition, fills determined the result and the applicable rules determined fees. That keeps the comparison useful even when button names look similar and screen figures change.