
FuelGuru turns fuel state from telematics, fleet-net prices, route economics and fleet policy into an executable fuel prescription: where to stop, when to stop, and how many gallons to buy. As the trip changes, FuelGuru recalculates the plan and measures what actually happened.
The economic decision engine behind every fuel stop.
Want to see a fuel prescription on your own lane first? Try Now →
The prescription says where to stop and how much to buy.
Negotiated prices, taxes, detour and route cost.
Deliver, re-prescribe and verify.
Tank levels, prices and routes change after dispatch. Prices can change several times a day. A plan built at 9am for a 4pm fill can already be stale.
Detour, tax, toll and the next fueling opportunity change the answer.
A prescription in a back-office report cannot create savings. At one 2,500+ truck carrier, only 74% of prescriptions were followed before the plan moved into the driver's navigation.
Fuel-card spend shows what was bought, not what should have been bought.
Per trip: ordered stops with the station, the expected arrival time, the gallons to buy, the price at your card rate, and the detour to get there. "Go to this station" is a recommendation. "Buy 62 gallons here, then 108 at the next preferred stop" is a prescription.
How much to buy comes from the fuel already on board, the reserve you require at arrival, the route ahead, the price opportunities on it, tank capacity and fleet policy. Sometimes the best fill is not a full fill.
Four effects stack. Most of them are invisible to anything reading a public price feed.
The rate your fuel program actually gives you at that location. Not the sign price, not a national average.
Station prices normalized for state fuel taxes and IFTA, so stops in different states are compared on what the fleet actually pays.
The miles and minutes to reach the station, priced against the pump saving and held inside your out-of-route policy.
Hours of service are in the plan, so each stop uses the latest pricing applicable to the truck's planned arrival window, not the file that happened to be available at dispatch.
Set the policy once. FuelGuru applies it consistently across every eligible trip. Full or partial fill, the out-of-route cap, preferred networks and contracted pricing locations, penalties for stops set back from the highway, and stops a fuel manager has disabled.
Disable a stop once and every affected trip re-prescribes. Nobody has to call.
A mathematically perfect stop that the driver skips saves nothing.
Every stop carries a score built from observed behavior. FuelGuru prescribes where the score is high. When a location keeps getting skipped, that becomes a signal it may no longer be practical, even when the price looks attractive on paper.
The prescribed stop appears inside the driver's turn-by-turn with the station and the gallons. Not a separate app the driver is supposed to remember to check. If the stop becomes unavailable or the trip changes, the route and the fuel plan recompute together.
Keeping another in-cab surface? The prescription goes into your TMS trip plan or that surface instead.
See NavGuru →One dry-van lane, Harvey, Illinois to Philadelphia. FuelGuru priced six commercial routes on tolls plus fuel. The spread between them was $326 per load. The sharper finding was the price of time.
FuelGuru analysis of a Harvey, IL to Philadelphia, PA dry-van lane, published August 2026. Fuel prices, tolls and trip economics vary with timing, equipment, payment method and fleet configuration.
"Avoid tolls" is not a strategy. "Always take the toll road" is not a strategy either. Put a price on time, fuel and tolls, then decide.
FuelGuru returns practical, fastest, cheapest and alternate routes with drive time, vehicle-specific tolls, fleet-net fuel cost, prescribed stops and gallons, and total trip economics. FuelGuru prices the economics. NavGuru executes the chosen route in the cab.
A generic truck route knows the road network. It does not know your yards, your customers' gates, or the roads your drivers have learned to stay off. Your fleet's GPS history does.
Illustrative network. FuelGuru learns road preferences from each fleet's own historical GPS trips. Segment preferences set by a fleet admin apply to new routes and re-routes.
FuelGuru reads your fleet's historical GPS: the approaches, access roads and corridors your trucks actually use, and the ones they consistently avoid.
Know a road better than the data does? Prefer, avoid or block any segment.
The change applies the moment you save it, on the next route and every re-route. Nobody waits for a map update.
Every route, and every fuel stop priced along it, starts from your fleet's road network. Not a one-size-fits-all truck map.
Combine the trip, current fuel state, fleet pricing and policy. Price every candidate stop. Return the route, stops and gallons.
Put the prescription into NavGuru, the TMS trip plan or the driver's existing in-cab workflow. No navigation switch required.
Missed stop, off route, lower tank than expected, prices moved. Recalculate from the truck's current state instead of forcing it back to a stale plan.
Match GPS and fuel-card transactions against the active prescription: stop, gallons, price paid and compliance, per driver, per stop, per trip.

“The utilization of GPS data, fuel-in-tank telemetry, and route planning allows the MapUp products for managing and auditing toll expenses, as well as fuel purchase planning. These tools afford us the opportunity to better utilize data in our edge environments to run a more efficient fleet.”

Three connections, set up once at onboarding: vehicle state, fuel economics and trip execution. Plus MapUp's licensed station-level price feeds, updated multiple times a day. No rip and replace.
GPS, tank level, odometer, vehicle state
Prices every candidate stop and route on your economics and policy. Prescribes stops and gallons. Verifies against transactions.
TMS trip plan · NavGuru · in-cab workflow
Fleet card rates and transaction files under your authorization, plus station-level pricing
MapUp introduced FuelGuru MCP in August 2026, bringing fleet-specific fuel, toll and commercial-route economics directly into dispatch agents, TMS copilots and load boards. The agent handles the conversation. FuelGuru handles the transportation math.
The first production Model Context Protocol server built for fleet-specific fuel purchasing, toll and commercial truck routing decisions. FreightWaves, 13 Aug 2026
Truck 1427 is in Nashville with 62 gallons. Load delivers tomorrow 08:00 in Charlotte. Which route keeps the most margin, and where should he fuel?
Responses come back as structured data, so a partner can drop the numbers into a ranking, a UI card or a voice answer. The same engine is available over the FuelGuru API.
You do not need to deploy FuelGuru, or change driver behavior, to find out whether the opportunity exists. Send historical trips, vehicle assumptions, fuel purchases and pricing. FuelGuru replays your top lanes and returns the prescribed routes, stops, gallons and modeled economics against what actually happened.
Analyze My LanesAlready evaluating or using FuelGuru?
Set up your fuel program, prove the economics on your own lanes, and see whether the prescribed savings actually happen.
Get started
Prove it on your own lanes first, then connect telematics, your card program and dispatch, load tank sizes, your network, prices and policy, put the prescription in the cab, and test it in a real truck. Troubleshooting and support on the same page.
FuelGuru setup and pilot guide →Run your fuel program
What a prescription contains, how a stop is priced, what happens when the trip changes, blocking a stop, investigating a missed prescription, and the weekly review.
Fuel manager and dispatcher guide →Measure the savings
Which stop on your list, whether the fuel was in network at all, whether the driver fueled where prescribed, and which receipts the truck's own data cannot support. How the annual figure rebuilds from gallons and cents per gallon.
Compliance and savings →Find an answer
Negotiated prices, partial fills, reefer, IFTA, detours, missed stops, fuel level readings, card programs, NavGuru, TMS and API, savings and support, grouped by who usually asks.
Browse the FuelGuru FAQ →References: POC data requirements · API documentation · Planning view