BBO Trading App
With the introduction of the NASDAQ Futures exchange, there are now 3 different commodity exchanges that list energy products. These are CME, ICE and now Nasdaq Futures (NFX). The BBO Order Router facilitates trading between these 3 commodity exchanges by allowing the trader to trade, with 1 order, across all 3 different exchanges (or 2 if that’s what they’ve configured). This type of “Sweep” order is typically used in equity markets when traders have an opinion on volatility, allow the trader to take out a significant amount of volume at a certain vol level. When Sweep Orders are placed it’s also possible that the trader can buy or sell vol across a few different strikes.
The user has the ability to setup exchange priorities for each product (Eg. CRUDE) and can also disable an exchange on a per product basis. Users can also select a specific trading account for orders to an exchange per product.
Note that this widget needs Metro v6.1. It is not meant to replace City Market or the Order Viewer, but instead extends its functionality on the back end with smart order placement. For this version, only MARKET and LIMIT orders are supported.
Remember that in Metro NOW, dashboards and widgets can be utilized in both OnRamp and Metro clients.
Related Resources
The True Cost of Real-Time Market Data Infrastructure: Part II Summary
Field-programmable gate array (FPGA)-based market data processing delivers best-in-class performance for ultra-low latency trading environments. However, building and maintaining in-house FPGA feed handlers is unsustainable for many capital markets firms. …
Exegy Research Reveals 5x Cost Savings and 6x Faster FPGA Development vs. In-House Builds
New York, London, Paris, St. Louis – October 29, 2025 – Exegy, a leading provider of market data and trading technology for the capital markets, today released Part II of…
Unified Trading Infrastructure: A Smarter Way to Scale
Over the years, trading firms have assembled a patchwork of infrastructure to meet individual desk and business-line needs resulting in duplication at every layer: multiple vendor stacks, inconsistent performance, and…