Skip to content
TerminalUp wordmark for light interface backgrounds
en

Choose your language

Website language does not determine product availability or eligibility.

Guides · English

Order routing versus execution: understanding trading-speed metrics

A routing decision, a submitted order and a completed fill are different events. Their timings should not be treated as interchangeable.

Prepared for publicationLast updated

Written by Terminal Up Inc. General explanations are linked to primary educational sources. TerminalUp's figures are owner-confirmed company measurements, not an independent benchmark, a fill guarantee or a contractual service-level agreement.

Order routing is the process of directing an order toward an execution destination. Execution is the trade or trades that result when an order is acted on. A routing decision can be fast without establishing when, at what price, or how much of the order will execute. To interpret a speed claim, identify its measurement boundary before comparing the number.

Where do routing and execution sit in an order's lifecycle?

An order instruction, the decision about where to send it, transmission, execution and a portfolio update describe different stages. A status display may report progress without meaning that the whole order has filled.

Investor.gov explains that placing a stock order and executing it are separate steps: the order goes to a broker, which decides where to send it, and prices can change before execution. This is a general illustration of why routing and execution should be distinguished. It is not a description of TerminalUp's internal topology or a claim that securities-market rules apply identically to sports prediction markets.

ConceptWhat it tells youWhat it does not establish
Order instructionThe intended side, amount and applicable conditionsThat a matching trade exists
Routing decisionA choice of how or where to direct the orderTime until a fill or the eventual price
Order routingDirecting the instruction toward executionThat all intended size was executed
ExecutionTrading activity resulting from the orderA completed fill of every part unless the status confirms it
Portfolio updateThe position or activity shown by the interfaceA measurement of every preceding stage

Why is an entered order not a guaranteed fill?

The amount in a ticket describes the order instruction. Whether and how much trades depends on the relevant market, available counterparties and the order's conditions. Read execution status rather than treating the ticket amount as an outcome.

A limit price is a useful example of the distinction. Investor.gov defines a limit order as an instruction to buy or sell at a specified price or better. Meeting the instruction's price conditions and finding sufficient available size are different from typing an amount. The exact order types and handling rules must be checked with the product and venue; this guide does not assert TerminalUp support for every example.

For an order involving multiple parts, ask how the product reports each part and any remaining amount. A response, acknowledgement or order-details screen is not a substitute for reading the status itself. A cancelled or rejected remainder should not be silently counted as completed execution in a speed comparison.

What do TerminalUp's published technology figures mean?

TerminalUp reports separate figures for intelligent order routing, routing-decision latency, multi-book execution and routing availability. Preserve those exact scopes; they are not interchangeable measures of end-to-end trading.

The figures below come from TerminalUp's shared company-performance reference. The public source does not specify an average, percentile, observation window, sample size or complete start/stop methodology. Do not supply those missing definitions by inference. Ask the team for measurement details appropriate to the workflow you are evaluating.

Sub 50msIntelligent order routing
Order-routing scope; not a promise of a full fill within this time.
Sub 10msRouting decision latency
Decision latency; not total routing or execution time.
Sub 100msMulti-book execution
Multi-book execution scope; not a guarantee for every order or market.
99.9%Routing availability
Routing availability; not overall platform uptime or a contractual SLA.

Can you add the latency figures or rank terminals by them?

Not without compatible measurement definitions. Stages may overlap or be nested, and measurements may use different conditions. Adding headline figures can produce a number that no source actually measured.

For example, a routing decision might be included within a wider routing measurement. Adding the two could double-count part of the process. Conversely, an internal server measurement may exclude the visitor's network and interface. These are possible measurement differences, not assertions about TerminalUp's architecture. A comparison is meaningful only when both providers define the same start event, end event and conditions.

  • What exact events start and stop the timer? Is the user's network included?
  • Is the value a bound, median, mean, percentile, or a selected observation?
  • Which venues, markets, order sizes and load conditions were included?
  • What observation window and sample size were used, and how were failures, partial outcomes and retries counted?

How is routing availability different from platform uptime?

Availability is meaningful only for a defined service and observation period. A routing-availability figure does not, by itself, describe every page, upstream venue, user connection or support commitment.

Keep time-to-process and availability separate. A percentage does not tell you the latency of a successful request, and a low-latency figure does not tell you how often routing was available. To evaluate an availability claim, ask what counted as success, what service was observed, which exclusions applied and over what period it was measured. Do not turn TerminalUp's routing-availability figure into a contractual SLA without the applicable agreement.

Do the public recordings verify the speed figures?

No. The recordings show the workflow, not a controlled benchmark. They do not provide instrumented timing boundaries or enough observations to verify latency or availability statistics.

The desktop example follows a $60,978.05 Lions spread order through the ticket, order details and portfolio. The mobile example shows a $50,000 Yankees order and portfolio activity. Those amounts describe orders, not guaranteed fills. Both are silent platform recordings with written descriptions; lines and liquidity change. Use them to inspect what a trader can see, not to calculate a general execution guarantee from the video's duration.

What evidence should you request next?

Request the methodology and a demonstration of the statuses relevant to your workflow. Keep company-supplied measurements, observed interface behavior and independently measured performance in separate categories.

If your decision depends on a specific market or order size, state that requirement in a demo conversation and ask which evidence addresses it. An honest unanswered question is more useful than a precise-looking number with an invented definition. Use the terminal-selection guide to connect these technical questions to market coverage, access and the type of product you actually need.