> For the complete documentation index, see [llms.txt](https://docs.proliquid.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proliquid.xyz/terminal-sections/trade-form.md). # Trade form Place supported orders for the selected market and trading account

Trade form default market order view for the selected market.

The Trade form is where you place orders from Terminal for the active trading account. This page explains shared controls that appear across order types. If you are choosing between execution styles, start with the [order types overview](/order-types/overview.md). For order-specific behavior, use the pages for [Market](/order-types/market-orders.md), [Limit](/order-types/limit-orders.md), [Scale](/order-types/scale-orders.md), [Chase](/order-types/chase-orders.md), [Iceberg](/order-types/iceberg-orders.md), [TWAP](/order-types/twap-orders.md), [Trailing stops](/order-types/trailing-stop-orders.md), and [Burst](/order-types/burst-orders.md) orders. ## Margin

Trade form margin mode selector for isolated or cross margin.

Margin mode lets you switch between isolated and cross margin for the selected market. * **Isolated** limits margin to the specific position. * **Cross** uses account collateral according to the active exchange's cross-margin rules. ## Leverage

Trade form leverage selector for the selected market.

Leverage changes the exposure supported by your margin for the selected market. Higher leverage reduces required margin but leaves less room for adverse price movement. Check [Account](/terminal-sections/account.md) and [Positions](/terminal-sections/positions.md) after changing leverage, especially if you already have exposure on the market. ## Portfolio

Trade form portfolio mode selector for Classic or Portfolio margin.

Portfolio mode lets you switch between supported account modes where available. Account-mode behavior is an exchange-level mechanic; use the active exchange's documentation for exact rules. ## Order type

Trade form order type selector for switching execution styles.

The order selector changes the form between supported Proliquid order types.

Order type	Use when
Market	You want fast execution with a slippage guard.
Limit	You want a specific price or time-in-force behavior.
Scale	You want a ladder of limit orders across a range.
Chase	You want maker-only execution that follows the market.
Iceberg	You want to reveal one maker-only clip at a time at a fixed price.
TWAP	You want to split execution over time.
Trailing stop	You want a stop to activate after a selected price.
Burst	You want aggressive execution split into batches.

## Quantity and notional Quantity is the order size in the base asset, such as BTC. Notional is the order value in the quote currency, such as USDC. By default, the Trade form shows both inputs. To simplify the form, use Quantity / notional inputs in [Terminal settings](/settings/terminal.md) and show only Quantity or only Notional. ## Submission checklist Before submitting, confirm market, side, size, price or slippage, reduce-only state, TP / SL, and margin settings. After submission, monitor [Open orders](/terminal-sections/open-orders.md), [Open icebergs](/terminal-sections/open-icebergs.md), [Open TWAPs](/terminal-sections/open-twaps.md), [Open chases](/terminal-sections/open-chases.md), [Positions](/terminal-sections/positions.md), and history panels. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.proliquid.xyz/terminal-sections/trade-form.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.