Appendix III. Special Orders
Server-side vs Client-side
| Platform | Brackets | Trailing Stop | OCO |
|---|---|---|---|
| Ninja | Client side | Client side | Client side |
| TWS | Client side | Client side | Server side |
| S5(GAIN) | Server side | Client side | Server side |
| TT | Client side | Client side | Client side |
| CQG | Server side | Client side | Server side |
| Rithmic | Server side | Server side | Server side |
| Simulator | Client side | Client side | Client side |
| Tradestation | Server side | Server side | Server side |
Note: client-side orders may be rather unsafe.
OCO
For all platforms, the price of a stop leg of an OCO cannot be modified to an invalid price, i.e., at or above the offer for a buy stop or at or below the bid for a sell stop.
Size increase modifications of OCO orders are not allowed across all platform connections. Allowed price changes can be done on each order individually. Decreasing size modifications can either be done on each individual leg or is automatically updated to the other leg, depending on the platform connection, as detailed below:
| Behaviour | Platform |
|---|---|
| Size change of one leg automatically updates the other leg | S5 |
| Each leg is modified individually; i.e., size modification of a single leg will not automatically update the other leg | CQG |
| Size change of one leg automatically updates the other leg | RIthmic |
| Size change of one leg automatically updates the other leg | Ninja, TWS, TT, Simulator |
Brackets
Bracket secondary orders behave as OCO orders, as detailed above.
Trailing Stop
The trailing stop parameter controls the tick steps at which the stop order is updated. Trailing stops will not apply to an entry stop order or a leading (primary) bracket order.