2012issue C1246
Platform routing, fees, and server-side stops
The archive records how futures order-entry screens host contingency orders, including a trailed stop-loss, and how platform access is billed. Editorial reading: decide first whether those exits must keep working after a local disconnect, then convert every per-side charge into a two-sided round-turn cost before comparing it with a monthly fee.
- A brokerage firm and a platform are chosen together, because not every firm offers every application and because brokers and exchanges, not the software, set margin policy.
- A stop-loss and other contingency orders depend on software to fire or cancel them. Instructions held only on the trader's computer can stop if that computer disconnects or crashes; server-side holding keeps them working after a local outage.
- A round turn has two sides, so a per-side platform fee is charged on both entry and exit. Convert that charge to a two-sided implementation cost before comparing it with a flat monthly subscription.
- Per-side fees scale with activity. A large monthly volume can exceed a flat subscription in the same price band, while a low-volume account is billed only for the executions it generates.
Choosing a firm and a platform
A brokerage firm and a platform are chosen together. Not every firm offers every platform, and brokers and exchanges, not the software, set margin policy.
Most futures brokerages provide at least one no-cost order-entry application. Some complimentary platforms include streaming futures and options quotes plus charting.
Paid platforms are marketed for low-latency execution, point-and-click entry, automation, and custom indicators. Price data may have to be purchased separately from the software.
Where a stop-loss is held
In this archive, order routing is the choice of where working instructions live, on the local workstation or an offsite server, and how multi-price entries and exits are sent after a fill.
Some platforms can accept multiple entry prices on a multi-contract order. Once filled, they can place multiple exits and trail a stop-loss. Those follow-on instructions are contingency orders: each is sent, amended, or canceled only after a specified price or signal event occurs.
A stop-loss is a contingent exit that can be placed or trailed after a fill. It remains reliable only while its host keeps the instruction working.
Contingency orders depend on software to fire or cancel them. Instructions held only on the trader's computer can stop if that computer disconnects or crashes. A server-side arrangement, in which the platform host rather than the trader's computer holds and works the contingent instructions, keeps them working after a local outage.
Monthly subscription versus per-side fees
Platform access may be billed as a monthly subscription or as a per-side usage fee on each execution. A round turn is a complete trade counted as two sides, one entry execution and one exit execution, so a per-side fee is charged on both entry and exit.
In this archive, commission analysis compares a monthly platform subscription with a per-side usage fee, including any brokerage subsidy and the two-sided cost of a round turn.
Per-side platform fees cited in the evidence ranged from $1.50 to $0.15. A charge of $0.15 per side equals $0.30 per round turn and $300 at 1,000 round turns in a month.
Brokerages often subsidize platform costs at the low end of that fee range. Higher charges are more often tied to automated-system development tools or to claimed faster server communication.
Per-side fees scale with activity, so a large monthly volume can exceed a flat subscription in the same price band. A low-volume account is billed only for the executions it generates.
All readings on this track · 30 readings
- 1988Why instant basket routing overwhelms specialist liquidity
- 2004Retail forex tickets as implementation-cost contracts
- 2005A two-gate liquidity filter for futures order routing
- 2006Manual after-hours routing and open-outcry fill risk
- 2010A futures brokerage quote is an execution specification
- 2011Smart order routing, maker-taker, and midpoint execution costs
- 2012Compare equivalent listings before routing
- 2012Rebate-aware routing and execution cost
- 2012Platform routing, fees, and server-side stops
- 2013Compare equivalent listings, then route the order
- 2013Confirm routing, margin, and fill cost before a live forex order
- 2013Brokerage choice as an execution-cost and routing filter
- 2014Order routing, pass-through rebates, and liquidity choice
- 2014Comparing exchange venues before routing the order
- 2014Selecting a futures broker as an execution-architecture problem
- 2014Commission shopping is the wrong first filter for a futures order
- 2015Routing orders when equivalent products trade on multiple venues
- 2015Forex venue checks for speed, margin, and implementation cost
- 2015Backup venues and symbol splits in futures routing
- 2016Route orders across competing exchange venues
- 2016Filter exchange venues before routing orders
- 2017Venue choice as an order-routing filter
- 2017Venue routing for equivalent listed contracts
- 2017Forex broker checks for fill speed, quote honor, and margin
- 2017Brokerage choice as an execution-speed and commission filter
- 2018Routing equivalent contracts across competing venues
- 2018Forex venue selection by fill speed, margin terms, and price honor
- 2019Forex execution filters for routing, cost, and liquidity
- 2020Routing equivalent listings across competing exchanges
- 2020Brokerage filters for routing, commissions, and liquidity