Classic Limit Order
A Classic Limit Order is the simplest conditional order in QZAR: it submits one buy or sell when a price or market-cap target is reached. The wallet, amount, execution settings, expiry, and optional TP/SL exit are saved with the order.
Use Classic when you have one target in mind. For entries spread over time, a confirmation range, or a moving trigger, choose one of the other order types.
Triggers
The trigger can be an absolute value or a percentage change from the current value. Every order also has an expiry time.
Create an order
- Find a token or pool and open the trade menu
- Choose Buy Limit order or Sell Limit Order
- Select one or more wallets and set the amount per wallet
- Choose the Trigger type
- Enter an absolute target or percentage change
- Set the expiry
- Review source tokens and settings
- Optionally configure TP/SL under Auto-sell settings
- Submit the order, then open Orders to confirm it is pending
Entry and exit lifecycle
| State | Meaning |
|---|---|
| Entry: Pending | Waiting for the trigger |
| Entry: Processing | Triggered and being submitted |
| Entry: Executed | Entry transaction completed |
| Entry: Failed | Triggered, but execution did not complete |
| Exit: Pending | Entry completed and TP/SL exit is waiting |
| Exit: Processing | Exit condition triggered |
| Exit: Executed | Exit transaction completed |
| Canceled / Closed | No further automatic action is expected |
Closed orders can also identify whether they ended manually, by Take Profit or by Stop Loss.

Manage an order
Open Orders, select an item, and review:
- Current market price and trigger
- Selected wallets and per-wallet status
- Amount, source token, slippage, mode, fee, etc
- Expiry and created time
- Entry and optional exit conditions
Depending on its current state, QZAR can show actions such as execute now, sell now, duplicate, edit exit settings, change notifications, or cancel.


Why a reached price may not fill
A chart position may not always be executable at the reached market level. The order still needs a valid route, sufficient balance, acceptable slippage, and enough fee priority when it is triggered. The observed value can change before the transaction is executed.
Practical safeguards
- Use smaller orders in thin pools
- Set an expiry so outdated assumptions do not remain active indefinitely
- Recheck open orders after depositing, withdrawing, or moving wallets into groups
- Cancel duplicate orders before creating replacements
- Verify a reported failure on-chain before manually repeating the trade
Other order types
The remaining order pages focus only on the behavior that differs from Classic:
| Order | Use it when |
|---|---|
| DCA | You want scheduled deals, but only inside a price range |
| TWAP | You want scheduled deals regardless of price |
| Range | A value must remain inside a band before one trade is submitted |
| Trailing Stop | The trigger should follow a move through several levels and react to a reversal |