Order ticket
An order ticket is the form a trading platform uses to send an order by hand: instrument, side, quantity, order type and price, submitted to the broker with a click. It only works while a broker connection that permits order routing is live.
Senzoukria · Glossary · Updated September 2026
What the ticket contains
The ticket is the manual half of order routing. Every field it shows maps to a field the broker expects, so a missing or stale value is a reason to stop rather than guess.
- Instrument: the exact contract, including expiry, that the chart is subscribed to.
- Side: buy or sell. On a futures ticket, selling with no position opens a short.
- Quantity: the number of contracts, subject to the account's own maximum.
- Order type: a market order takes whatever the book offers; a limit order rests at a price.
- Flatten: a single control that closes the open position and cancels working orders on that instrument.
What a sent ticket does not prove
- A click sends a request. The fill, partial fill or rejection is what the broker reports afterwards.
- A market order on a thin book can fill several ticks away from the last price shown on the ticket.
- A ticket that opens does not establish that the account permits routing; that is a separate account-level permission.
- Quantity limits set in the application never replace the exchange or firm limits applied at the broker.
In Senzoukria
The desktop exposes the ticket in two places: the Trading screen and the Quick ticket on the chart, which can be shown from Settings (Quick ticket on the chart). The quick ticket has BUY MKT and SELL MKT buttons, a Quantity field with increase and decrease controls, a LAST price readout and a Flatten button. Until a live tick has arrived, it shows Waiting for a live tick and the send buttons are not meaningful.
The guided tour states the dependency directly: the order ticket needs a live broker connection. On the Trading screen, the desk shows four stages (Connection, Account, Position, Protections) and each stage lights up only from what the broker actually reports. A stop counts as protection only when the broker lists it among the working orders.
Common mistakes
- Reading the LAST price on the ticket as the fill price of a market order.
- Sending from a ticket attached to the wrong expiry after a contract roll.
- Assuming a position is protected because a stop was typed, not because the broker acknowledged it.
- Leaving the ticket on one click in an account where a mis-click has real cost; see order guardrails.
Related
This page in other languages
Frequently asked questions
- Does the order ticket work without a broker connection?
- No. The ticket needs a live connection whose account permits order routing. With no broker connected, the chart can still draw history stored on the machine, but the ticket has nothing to send to and the quick ticket waits for a live tick.
- What does Flatten do on the ticket?
- Flatten requests the closing of the open position on that instrument and the cancellation of its working orders. It is a request to the broker, not a guaranteed fill; the resulting position should be read back from the broker report before assuming the account is flat.
- Is the chart quick ticket the same as the Trading screen ticket?
- They share the same routing path and the same guards from Settings, including order confirmation and maximum quantity. The quick ticket is a compact market-order panel on the chart; the Trading screen adds the desk stages, positions and the exit orders received for each position.