An order amendment changes permitted terms of a live order. Track total quantity, cumulative fills and the remainder through acceptance, racing fills and priority rules.
Order amendment
An order amendment is a request to change permitted terms of an existing trading order, such as its quantity, limit price or expiry. It lets an execution strategy respond to a changed signal or risk limit without treating the original instruction as forgotten. The practical danger is timing: until the change is accepted, the old terms may still be executable, and fills already made remain part of the position.
An amendment is distinct from a trade correction. Changing a live limit order does not retrospectively reprice or reverse its completed trades. Nor does pressing “amend” establish a new queue position; priority depends on the venue, order type and fields changed.
“Change quantity to 80” needs a quantity definition
Consider a synthetic buy order originally entered for 100 shares. It has filled 30 shares, leaving 70 shares executable. The trader now wants the total acquisition under this order to be 80 shares, including the shares already bought. Assume that this quantity reduction is permitted and accepted, with no intervening fill.
The accepted amendment leaves 50 shares, because
new total80=cumulative fills30+remaining50.
The original total was 100; the currently accepted total is now 80. Neither is the same field as remaining quantity. The cumulative fill is still 30. The amendment reduces future executable quantity by 20 shares; it does not sell 20 shares or erase earlier fills.
This distinction appears explicitly in the ASX Trade FIX Order Entry Specification, version 1.1, May 2026, §3.3.2.2. Its OrderQty is the new absolute total investor quantity, CumQty carries executed quantity through amendments, and LeavesQty records the remainder. A different interface might ask for remaining quantity or a quantity change. If “80” instead means 80 shares remaining, the same 30 fills imply a total of 110 shares. Read the field contract before sending the number.
Synthetic share ledger: after 30 fills on a 100-share order, 70 remain. A pending request for total 80 leaves the accepted state unchanged. Acceptance leaves 50. On the alternative path, an extra 10 fill first, so acceptance leaves 40 with 40 already filled.
Original synthetic share ledger. All quantities are whole shares; rows show event order rather than elapsed time. The main path assumes no intervening fill. The alternative path stipulates one further 10-share fill before acceptance. No queue-priority outcome is assumed.
For an active order with compatible total-quantity semantics, the useful reconciliation is
Qaccepted=Fcumulative+Rremaining.
This is an active-order ledger, not a rule that a cancelled order must continue to show an executable remainder. Terminal statuses and special handling use the interface's documented conventions. A request below cumulative fills cannot undo the acquired position; its treatment must be checked rather than implemented as a negative remainder.
A pending amendment can race a fill
Sending the request is an event in the trader's system. Acceptance is an event in the broker's or venue's system, reported back through its protocol. A receipt or “pending replace” message is not necessarily acceptance of the changed terms.
In the figure's alternative path, another 10 shares fill while the request for total 80 is pending. Before acceptance, the old total remains 100, cumulative fills are 40 and the live remainder is 60. Once the total of 80 is accepted, the remainder is 40, not the 50 calculated from the earlier snapshot. If the amendment is rejected instead, that requested reduction has not taken effect: the old order must be reconciled with any fills that occurred meanwhile.
The FIX Trading Community's order-state scenarios, especially C.3.a, show executions occurring during a pending replacement and the accepted state reflecting the updated cumulative fills. The protocol description is a model for interpreting messages; the particular connection's supported workflow still matters.
A related hazard arises when a broker or strategy implements a change as a separate cancellation followed by a fresh order. Suppose the trader sends a new 50-share order before the original remainder is confirmed cancelled. If the old order fills another 10 and the new order fills 50, total acquisition becomes 90 shares: the first 30, the racing 10 and the new 50. That exceeds the intended 80 by 10. Treat unresolved old quantity as potentially executable when sizing new instructions.
The message name alone does not establish that separate-order mechanism. ASX Trade's §3.3.2 specifically describes its FIX “Order Cancel Replace Request” as modifying the existing order. Identify the actual lifecycle, preserve order-chain and execution identities, and reconcile authoritative cumulative fills rather than assuming that “replace” resets the ledger.
For a fuller operational treatment, Live Execution Monitoring develops executable reservations and cancellation races. Its preview is public; the full lesson requires membership.
Quantity and priority answer different questions
Reducing future exposure can be useful even when it changes the order's execution prospects. In a price-time-priority book, losing time priority can move a resting order behind competing interest at its price. A more aggressive price may instead change which liquidity it can reach. Neither consequence can be inferred from the new share count alone.
Two checked rule sets illustrate the need for specificity:
ASX Trade: the May 2026 FIX specification, §3.3.2.1, states that price changes and quantity increases lose market priority. It also warns that display-quantity or time-in-force fields can affect priority or rejection depending on order type.
ASX 24:Operating Rule 4032, subject to its stated procedural exceptions, preserves priority ranking for a quantity reduction in an Execution Service. Withdrawal and re-entry receive new ranking; other amendments lose ranking and are treated as new bids or offers.
These are distinct market specifications, not one universal rule for every “amend” button. Narang's discussion of execution also distinguishes time-priority and pro-rata allocation mechanisms: an amendment model needs the relevant allocation rule as well as the order ledger.
An execution backtest that edits price or quantity instantly, carries forward queue rank automatically, or deletes fills arriving during a pending request can produce fictitious completion. Record the requested state separately from the accepted state, keep fills cumulative across versions, and apply the relevant priority transition only when the actual venue rules justify it.
Sources
ASX, ASX Trade FIX Order Entry Specification, version 1.1, May 2026, §§3.3.2–3.3.2.3, printed pp. 50–53 — modification semantics, quantity fields and priority-sensitive changes.
FIX Trading Community, Order State Changes, FIX Latest as of EP284, November 2023, scenario C.3.a, printed p. 21 — a quantity reduction with fills during processing.
Rishi K. Narang, Inside the Black Box: A Simple Guide to Quantitative and High-Frequency Trading, 2nd edition, Wiley, 2013, Chapter 7, “Aggressive versus Passive,” printed pp. 121–122 — alternative allocation rules and cancellation/replacement incentives.
