ZagTrader

FIX Protocol Tag 11: ClOrdID

Unique identifier for the order, assigned by the firm that sends it (buy side, broker or other intermediary). It must be unique within a trading day, and firms that send multi-day orders should keep it unique across days. Every cancel or replace request carries a new ClOrdID.

Tag number
11
Data type
STRING
FIX versions
FIX 4.0 to 5.0 SP2
Used in
43 message types

Practical notes on ClOrdID

ClOrdID is the identifier the client gives to each order request: the New Order Single and every cancel or replace that follows.

  • Every request needs a new ClOrdID. A cancel or replace carries its own ClOrdID and points at the order through OrigClOrdID (41).
  • Most venues require ClOrdIDs to be unique for at least the trading day; many expect uniqueness for the life of the session.
  • Execution Reports echo the ClOrdID of the request they answer, which is how the client matches them.

Common mistakes

  • Reusing the ClOrdID of a rejected order. Many venues reject the new order as a duplicate.
  • Generating IDs from a counter that restarts with the process.

See also:FIX order lifecycle explained

Tag 11 in each FIX version

Values and message usage as defined in a specific version.

Data type

STRING: Text of printable characters. It cannot contain the SOH delimiter.

Example

11=ORD-20261020-0001

Illustrative value. In a message, fields are separated by the SOH character (0x01), often shown as | or ^ in logs.

Decode a message with this tag

Message types that use tag 11

Covers every version from FIX 4.0 to 5.0 SP2, including fields reached through components and repeating groups. The version pages above show whether the tag is required in each message.

Field and message data comes from the QuickFIX data dictionaries for FIX 4.0 to 5.0 SP2 and FIXT 1.1, used under the QuickFIX Software License. This product includes software developed by quickfixengine.org (http://www.quickfixengine.org/). Enumerated value names are converted to plain text for reading.