Review orders and cancel the open ones on a venue in the Console

The Orders tab lists every order submitted to the venue, for review and export. A venue operator also uses it to cancel the open orders that match the screen's filters, for example when an incident leaves orders that must go before the venue is safe to use again.

The venue's Orders tab with each order's instrument, client, side, quantity, status and placed time — The “Orders” table of a trading venue, with the “Filter”, “Client” and “Export” controls above it.

The table has “Instrument”, “Client”, “Side”, “Quantity”, “Status” and “Placed (UTC)” columns. Each row also shows the order's type, filled quantity and validity. The “Filter”, “Client” and “Export” controls sit above the table.

Before you start

The Venue operator role on the venue. Cancelling orders is a venue operator's task.
A second venue operator, when the venue asks for one. The “Trading venues” row under “Approvals” on General decides whether a mass cancel needs a second venue operator. An exception there can turn it on or off for one venue. With the row on, the cancel waits for a second operator. With the row off, it runs as soon as the proposer confirms with their wallet verification. Cancelling all of one participant's orders never waits for a second person. Blocking a participant waits for one only while the “Administration” row protects the “Freezing” group. A venue operator or venue submitter wallet can also cancel any order, or all of one wallet's orders, directly on the venue contract, with no second person.

Steps

Find and export orders

Filter the “Orders” table by instrument, client, side, type, validity, status, reason, or date, and download the filtered rows as CSV or XLSX from the Export menu. When more than 1,048,575 orders match, the XLSX download is refused with that limit, so export CSV or narrow the filters. The Orders tab shows times in UTC. An order that arrives while you read raises the count on a button over the top of the table, such as “3 new”, and the rows move only when you select it.

The Quantity and “Filled” columns show the order size in the instrument's base token, in the table and in the row details. Sorting by either column groups the orders by instrument and sorts each group by amount.

Propose a mass cancel

The cancel uses the instrument, client, side, type and validity filters, and with none set it covers every open order on the venue.

Select Cancel orders below the table. The control stays disabled while the screen also filters by trading member, status, close reason or placed date, because the cancel cannot honour those filters. A line of text beside the control names the filter to clear.
Read the count in the sheet. It shows how many open orders match, with one row for each instrument. Orders that still hold their balance and have not reached the order book appear in their own row, so the rows add up to the total. When no open order matches, the sheet says so and you cannot propose.
Enter a “Reason” of 5 to 500 characters and type the venue's name in the field that reads “Type” and the venue's name “to confirm”. Select Propose cancel and confirm with your wallet verification. The second operator sees the reason, and every cancelled order carries it to the participant.

Hand the proposal to a second operator

On a venue whose row is on, a second venue operator decides the proposal on the Mass cancellations tab. On a venue whose row is off, the cancel runs at once and leaves a batch on Mass cancellations for download.

Open an order

Select Open order in a row's details on the “Orders” table to read the whole order: its facts, its “History” and its “Fills”. A limit order shows its “Limit price”. Prices in the facts, the history and the fills read at the instrument's price step with the quote token, the same digits as the order book, for example “5.0000 EUROC”. An open order with no fills says “No fills yet”, and a closed one says “No fills”. A fill's trade reference opens the batch that holds that trade on Settlement instructions.

Read an order's trading member

Every order on the venue has a trading member: the broker the venue operator assigned to the participant that owns the wallet, or the participant itself when it has no broker. Assign a broker on Participant access. The “Orders” table shows the member in a Trading member column and in the order details, and a “Trading member” filter keeps the orders of one trading member. Once you choose a client or a trading member, the word “Client” or “Trading member” stays beside the name you chose, so the toolbar shows what each filter holds. A broker shows as the member with “via broker” beside it. The settlement instructions and the held fills name the member of the buyer and of the seller.

The platform works out the member as of the moment of the order, not as of today. Assigning, changing or clearing a broker therefore changes the member of later orders only. Every earlier order keeps the member it had when it was placed, and the Trading member filter follows the same rule. A trade, a held fill and a trade bust use the time of the trade, the fill and the bust. The audit log still holds each broker change with its reason. A wallet that several participants share has no member.

The platform kept only the current broker before this change, so an earlier broker is not recoverable. Orders from before a participant's current broker was assigned show the participant itself as the member.

Only venue operators see trading members. A trader or a broker never sees a trading member, another participant's name, or the counterparty's wallet or order. This holds for their orders, trades, activity and events, in the screens and in the Platform API. The settlement record on the network still names both wallets to anyone who reads it.

Troubleshooting

Cancel orders is disabled

Clear the trading member, status, close reason or placed date filter that the control names. When no open order matches the other filters, the sheet says so and you cannot propose.

API routes

The tab reads orders through the trading venue routes in the v2 API reference.