2015issue C1044
Handheld futures tickets as a second execution venue
A handheld futures ticket is another order-routing surface. Confirm that the phone and desk share the same book and net position, then decide whether a marketable send is visible and safe on that screen, and only then price the monthly fee or per-contract surcharge as implementation cost.
- Position-synchronization comes first: a fill on the handheld ticket must appear at once on the desktop book, and the reverse, so net exposure is readable before the next instruction.
- A market-order on a handheld ticket is only as safe as the live bid-ask, position, and fill feedback that device actually shows.
- Commission-analysis compares a monthly platform fee with a per-trade surcharge and weighs that overlay against a missed, late, or duplicate fill.
- Early handheld tickets were treated as unacceptable for live orders when cash was at risk. Later clients could send orders and stream live bid-ask, but the path still depended on the device.
A second venue, not an upgrade
Early handheld futures tickets were slow, inefficient, and unreliable enough that sending live orders on them was treated as unacceptable when cash was at risk. By 2015, handheld clients could send orders, stream live bid-ask on futures and options, and chart with common technical indicators.
Order-routing is the path an executable futures or options instruction takes from a handheld or desktop ticket through a broker and matching venue, including whether the same ticket can sit in front of more than one firm. The archive describes that path as a live ticket, not as a software add-on.
Lock the book before the next send
Synchronization delay between handheld and desktop views left traders unable to read net position and produced erroneous losses. Brokers designed mobile routes to share state with desktop tickets so a fill on one surface appeared immediately on the other.
That requirement is position-synchronization: a fill entered on a phone must appear at once on the desktop book, and the reverse, so the trader can read net exposure before sending the next instruction. Device routing was uneven. Downloadable apps were widely available on iOS, Android, and Windows phones, while Blackberry users had fewer paths, and phones without apps could still reach a simplified ticket through a wireless application protocol browser.
Is a marketable send even visible
A market-order is a marketable instruction meant to lift the offer or hit the bid immediately. On a handheld ticket it is only as safe as the live bid-ask, position, and fill feedback the device actually shows. By 2015 some handheld clients streamed that live bid-ask on futures and options. A premium handheld client priced at 60 dollars per month exposed option chains, price ladders, and block-trade tickets that were uncommon on phones.
TradersWeek editorial reading: do not treat a send as executable on a screen that cannot show the bid-ask you are hitting, the position you already hold, or the fill that just came back.
Price the overlay as implementation cost
At least one handheld route used a per-trade surcharge of 30 to 50 cents instead of a monthly subscription, with the add-on depending on the brokerage. Another suite folded handheld access into a desktop subscription of about 129 dollars per month.
Commission-analysis compares a monthly platform fee with a per-trade surcharge and weighs that overlay against the cost of a missed, late, or duplicate fill. Implementation-cost is the sum of extra commissions, delayed or conflicting position state, and the risk of sending an order the handheld ticket cannot monitor.
TradersWeek editorial reading: run that comparison only after the route is synchronized and the marketable send is visible. The fee is part of the cost of using the handheld ticket as a venue, not a reason to treat the phone as an upgrade.
All readings on this track · 26 readings
- 1995Canceled prints versus executable fills
- 1999How order routing changes market and limit fills
- 2000Direct access, intelligent order routing, and visible book depth
- 2001Retail routing and market versus limit fills
- 2001Stop triggers and opening-only short market orders
- 2002Market-order routing across linked venues
- 2002Market-order routing, internalization, and displayed size
- 2004Direct access order routing after the display rules
- 2004Listed-stock limit envelopes versus market-order routing
- 2005Closing option spreads with limit or market orders
- 2005Contingent routing as a pre-trade futures contract
- 2007Constructing executable futures orders with market, limit, and fill or kill
- 2008Bid-ask spreads, routing paths, and order choice
- 2008Retail market buys hit the ask
- 2008Limit versus market orders for a commodity option-spread
- 2011A pre-trade checklist before market or limit orders
- 2013Retail market orders and the displayed queue they never join
- 2013Option stop orders, wide spreads and forced market exits
- 2014Opening range breakout with weekday ratings, abstention and exits
- 2014Constructing forex orders from session liquidity
- 2015Order-type and routing scripts for faster execution
- 2015Market, limit, and routing choices inside the order life cycle
- 2015Handheld futures tickets as a second execution venue
- 2017Screen execution starts from the live bid and ask
- 2017Electronic stop-loss orders and protected price bands
- 2020Market-order slippage on split-adjusted stock prices