How to set up a limit order on Kraken instead of market order?

Understanding Order Types on Kraken

1. A market order executes immediately at the best available price in the order book, prioritizing speed over price control.

2. A limit order instructs Kraken to buy or sell a specified amount of cryptocurrency only at a defined price or better—no execution occurs unless the market reaches that level.

3. Limit orders appear in the order book and contribute to market depth, unlike market orders which consume existing liquidity.

4. Kraken displays separate order books for bids (buy limit orders) and asks (sell limit orders), visible in real time on the trading interface.

5. Traders use limit orders to avoid slippage during volatile conditions and to enforce precise entry or exit discipline.

Navigating the Kraken Trading Interface

1. Log into your verified Kraken account using two-factor authentication before accessing trading features.

2. Select the desired trading pair—such as BTC/USD or ETH/USD—from the market selector dropdown menu.

3. Ensure you are on the “Advanced” trading view to access full order type options, including stop-loss and take-profit fields.

4. Locate the order entry panel on the right side of the screen; it contains fields for price, volume, and order type selection.

5. Confirm that the “Order Type” dropdown is set to “Limit” rather than “Market”, “Stop Market”, or “Stop Limit”.

Configuring Price and Volume Parameters

1. Enter the exact price at which you wish to transact—this must be entered manually and cannot be left blank for a limit order.

2. Input the quantity of cryptocurrency to buy or sell, denominated either in the base asset (e.g., 0.025 BTC) or quote asset (e.g., 1250 USD), depending on the selected display mode.

3. Verify that the “Total” field reflects the product of price and volume, adjusted for Kraken’s fee schedule based on your tier.

4. Check the “Fee Estimate” line to confirm applicable taker or maker status—limit orders placed away from the current best bid/ask qualify as maker orders and receive reduced fees.

5. Avoid using trailing stops or time-in-force extensions unless explicitly required; standard limit orders on Kraken default to “Good Til Cancelled” (GTC).

Execution and Order Management

1. Click the “Buy” or “Sell” button only after all fields are correctly populated—the action submits the order to Kraken’s matching engine.

2. Immediately after submission, the order appears under “Open Orders” in the account dashboard with status “Alive” and visible price, volume, and remaining size.

3. Monitor the “Recent Trades” panel to observe whether partial fills have occurred due to overlapping price levels in the order book.

4. Modify or cancel active limit orders directly from the “Open Orders” tab without requiring withdrawal confirmation or additional verification steps.

5. Kraken does not auto-convert unfilled limit orders into market orders upon expiration—cancellation is manual unless a custom time-in-force setting was applied.

Frequently Asked Questions

Q: Can I place a limit order while my Kraken account is under identity verification review?A: No. Kraken restricts all trading functions—including limit order placement—until Level 2 verification is fully completed and confirmed in the account settings.

Q: Why did my limit order execute partially instead of filling entirely?A: Partial fills occur when only a portion of your requested volume matches against existing counter-orders at your specified price; the remainder stays open until matched or cancelled.

Q: Does Kraken charge different fees for limit orders placed inside versus outside the spread?A: Yes. Orders resting inside the bid-ask spread act as takers and incur higher fees; those placed beyond current top-of-book levels act as makers and qualify for lower-tier rates.

Q: Is it possible to set a limit order that triggers only after another condition is met?A: Kraken supports stop-limit orders, but standalone conditional logic—such as price-based activation without a stop trigger—is not available in its native interface.