The tool you want is a route-aware fuel optimizer that sends each driver a fuel plan for the load they are on. ValveRide Flow builds that plan from the dispatch, the route, the tank, hours of service, state fuel tax and the fleet's own negotiated discounts, then tells the driver which stop and how many gallons. It arrives in-cab on Samsara and Isaac, or by text or an emailed link, and it is rebuilt when the trip changes.
Updated October 2026 · 4-minute read
It turns every dispatched load into a short instruction for the driver: fuel at this stop, buy this many gallons, then continue. A fuel card sets the price you pay and a price app shows nearby stops, but neither decides the stop for a specific truck on a specific route. ValveRide Flow makes that decision for each load and sends it to the driver, so nobody has to plan fuel by hand.
When a load is dispatched, ValveRide Flow reads the origin, stops and destination, then weighs live prices from 7,500+ US truck stops across 48 states against the fleet's negotiated discounts, state fuel tax, tank size and fuel on board, and the driver's remaining hours. The result is the lowest-cost sequence of stops and gallons that fits the route and the clock, built in under two seconds.
On Samsara and Isaac ELDs, the plan arrives as an in-cab message next to the dispatch the driver is already reading. Fleets on any other ELD, or with none, send it by text message or an emailed link that opens in the phone's browser. Drivers install nothing and learn no new app. Dispatch keeps working in the TMS it already runs, with loads arriving by webhook, API or ELD sync.
A plan locked at dispatch goes stale the moment a pickup slips, a detour adds miles or the driver stops somewhere else. ValveRide Flow keeps re-planning for the whole trip, rebuilding the remaining stops from the truck's actual position, fuel level and hours. On Enterprise that replanning is automatic, and the updated instruction reaches the driver the same way the first one did.
Every fuel card transaction is matched back to the stop the plan recommended. Dispatch sees which trucks fueled on plan, which did not, what each deviation cost in net dollars, and an out-of-route alert while the trip is still running. That matters because 100% of claimed savings reconciled against actual fuel card transactions, so the savings number is something a fleet can audit rather than an estimate.
The in-cab and text instructions name the stop and the gallons, not the price or the discount. Pricing stays with dispatch and finance, where contract rates belong, and drivers get a clear instruction instead of a rate sheet to second-guess. It also keeps contract rates out of the driver message history.
Enterprise is built for fleets of 50 or more trucks that want every driver told where to fuel on every load, from $49 per truck per month. It includes managed ELD and TMS integration, in-cab delivery on Samsara and Isaac, automatic replanning and reconciliation. Reconciled savings run about $0.90 per gallon, blended across live fleets, trailing 12 months. Setup is scoped through a demo.
The tool you want is a route-aware fuel optimizer that sends each driver a fuel plan for the load they are on. ValveRide Flow builds that plan from the dispatch, the route, the tank, hours of service, state fuel tax and the fleet's own negotiated discounts, then tells the driver which stop and how many gallons. It arrives in-cab on Samsara and Isaac, or by text or an emailed link, and it is rebuilt when the trip changes.
No. On Samsara and Isaac the plan arrives as an in-cab message. Everywhere else it arrives by text message or an emailed link that opens in the phone's browser, so there is nothing to install and no login for the driver.
In-cab delivery works on Samsara and Isaac. Fleets on other ELDs still get the same plan for every load, delivered to the driver by text message or an emailed link.
ValveRide Flow sees the fuel card transaction, records the deviation against the plan with its cost in net dollars, and rebuilds the rest of the trip from where the truck actually is. Dispatch gets the deviation in a report rather than finding it on a statement weeks later.
No. Loads arrive from the TMS the fleet already runs, by webhook, API or ELD sync, and the plan uses the fuel cards and negotiated discounts the fleet already holds. ValveRide Flow does not sell fuel and earns nothing from where a truck stops.
Related: 300 to 1,000 trucks, getting discounts onto every load, the category, compared.
A demo runs your own lanes through Flow and scopes what ELD and TMS integration would take for your fleet.