Skip to content
Genesis Ark

01 / Order management

Available

One order book of record, from first instruction to final fill

Qubit's order management system holds the state of every order your desk touches: parent and child, staged and live, manual and electronic. Every change is timestamped, attributed and recoverable after a restart.

Layer
Core
Works on its own
No
Interfaces
Blotter, REST, WebSocket, FIX
Fig. 1. Order blotter: a parent order with its child orders and fills. Illustrative composition with sample data.

01 / The problem

When order state lives in five places, nobody knows the real position

A client sends an order over FIX. A trader works it on two exchange consoles and a router. A partial fill arrives on one venue while another venue's WebSocket reconnects. By the afternoon, the blotter, the router's log and the exchange history disagree, and the only way to answer "what did we do for this client" is to rebuild it by hand.

An OMS fixes this by being the one place where an order's state is decided. Every other system reads from it.

02 / What it does

What the OMS handles

  1. 01

    Full order lifecycle

    One state machine for every order, from pending new to filled, canceled, rejected or expired, with the same states in the blotter, the API, FIX and reports.

  2. 02

    Parent and child orders

    A parent order can be worked manually, by an algorithm or by the smart order router. Every child order links to its parent, so fills, average price and remaining quantity roll up correctly.

  3. 03

    Care orders and staging

    Client orders can arrive as staged instructions that a trader accepts, works and fills, rather than going straight to market.

  4. 04

    Amend and cancel

    Amend price or quantity, cancel one order, or cancel all orders for an account, instrument or venue, with each request tracked as its own state.

  5. 05

    Allocations

    Split a block fill across sub-accounts or client accounts at average price, by fixed quantity or by percentage, before booking.

  6. 06

    Blotters that traders can work from

    Filter by account, trader, instrument, venue and state. Drill from a parent order into every child order and every fill.

  7. 07

    Idempotent order entry

    A client order ID is unique per session. Resending the same request after a timeout returns the existing order instead of creating a new one.

  8. 08

    Recovery by design

    Order events are written to a persistent log before they are acknowledged. After a restart, state is rebuilt from the log and reconciled with each venue.

03 / How it works

The life of an order

Fig. 2. The stages below, in order. Each one writes to the audit trail.
  1. 01

    Receive

    An order arrives from the Qubit blotter, the REST or WebSocket API, or a FIX session. Qubit assigns an internal order ID and stores your client order ID beside it.

  2. 02

    Validate

    The order is checked for completeness and instrument rules (tick size, lot size, minimum notional), then sent to pre-trade risk.

  3. 03

    Route or stage

    Accepted orders go to a venue, an algorithm or the router. Care orders wait in a trader's queue.

  4. 04

    Track

    Each venue acknowledgment, partial fill, fill, cancel and reject updates the order. Child order events roll up to the parent.

  5. 05

    Book

    Fills update the position ledger in the same step and flow to post-trade for reconciliation and settlement.

04 / Specifics

Technical specifics

Order states

Pending new, new, partially filled, filled, pending cancel, canceled, pending replace, replaced, rejected, expired, and suspended (for orders paused by a kill switch or a halted venue). The venue state "unknown" is used while a venue session is being reconciled after a disconnect.

Order types

Market, limit, stop market, stop limit, and post-only limit (rejected or repriced if it would take liquidity, depending on the venue). Algorithmic parent orders are described on the Algorithms page. Order types a venue does not support natively can be held and triggered by Qubit.

Time in force

Good till canceled (GTC), immediate or cancel (IOC), fill or kill (FOK) and good till date or time (GTD).

Order attributes

Client order ID, account, trader, instrument, side, quantity in base or quote currency, limit and stop price, time in force, venue or routing instruction, free-text notes and tags for downstream reporting.

FIX messages (order entry and drop copy)

NewOrderSingle (35=D), OrderCancelRequest (35=F), OrderCancelReplaceRequest (35=G), OrderStatusRequest (35=H), OrderMassCancelRequest (35=q), ExecutionReport (35=8), OrderCancelReject (35=9).

Controls on the order book

Cancel on disconnect per session; mass cancel by account, instrument or venue; and the kill switch at firm, desk, trader, account, instrument or venue level.

05 / Controls and audit

What you configure, and what gets written down

Configurable

  • Cancel on disconnect, per session
  • Mass cancel scope: account, instrument or venue
  • Kill switch at firm, desk, trader, account, instrument or venue level
  • Allocation method: average price, fixed quantity or percentage
  • Care order staging into a trader's queue
  • Free-text notes and tags for downstream reporting

Logged to the audit trail

  • order received · internal and client order ID
  • state change · old state, new state
  • amend · old and new values, user or session, venue response
  • cancel and mass cancel requests
  • venue acknowledgment, partial fill, fill, reject
  • allocation of a block fill
  • kill switch activated and released

06 / Where it fits

Works on its own
No. Order management is the center of the core platform and ships with it.
Needs the core
It is the core, together with the execution gateway, accounts and permissions, the position ledger, pre-trade risk and the audit trail.
Who uses it
Brokers and banks running client flow, OTC desks, asset managers and funds with execution traders, exchanges routing client orders to external liquidity.

FAQ

Questions we get asked

  • Can our existing front end send orders to the Qubit OMS?

    Yes. Any front end can enter and manage orders through the REST and WebSocket APIs or a FIX session. The Qubit blotter is optional for desks that already have their own screens.

  • What happens to working orders if a venue disconnects?

    Qubit marks that venue's open orders as unknown, blocks new orders to it, reconnects, and pulls open orders and recent fills from the venue. It applies any missed fills, corrects order states and only then reopens the venue for trading.

  • How are partial fills on several venues shown?

    On the parent order, as one cumulative quantity and one average price, with each child order and fill one click away. Fees are kept per fill so TCA and reporting can show cost by venue.

  • Can a trader take over an order that an algorithm is working?

    Yes, with permission. The trader can pause the algorithm, amend or cancel its working child orders, and resume or cancel the parent.

  • Does the OMS keep a full history of amendments?

    Yes. Every amendment is its own event with the old and new values, the user or session that sent it and the venue's response.

Make one system the source of truth for your orders

A scoping call with an engineer, then a demo on sample data that mirrors your venues, desks and limits.