Route Profitability in Waste Operations: How to Measure It | imPROVE analytics
Home / Resources / Route Profitability
Reporting & Visibility 10 min read

Route Profitability in Waste Operations: How to Measure It (and Why Your ERP Doesn’t)

Route profitability is the net margin of a single collection route — its revenue minus the labor, fuel, disposal, and asset cost to run it. It tells an operator which routes make money and which quietly lose it. Most ERPs don’t calculate it natively because the inputs live in separate systems.

What is route profitability?

Route profitability is the net margin of a single collection route — the revenue it brings in minus the labor, fuel, disposal, and asset cost it takes to run. A route is profitable when the customers on it pay more than it costs to serve them, and unprofitable when they don’t. It is the most operational measure of margin a hauler has, because the route is where revenue and cost actually meet.

Company-level margin tells you whether the business is healthy. Customer-level margin tells you whether an account is worth keeping. Route profitability sits between them, and it’s the one most operators can’t see — even though it’s where most of the controllable money is won or lost. Two routes with identical revenue can have very different margins once you account for how far the truck drives, how long the driver is out, and how much it costs to tip the load.

How do you calculate route profitability?

Route profitability is route revenue minus the four costs to serve it: labor, fuel, disposal, and asset/maintenance. The formula is simple; the work is sourcing each input at the route level and defining it the same way every time. A worked example makes the method concrete.

Sample data, modeled on real implementations. Figures illustrate the method, not a specific client.
Weekly, per routeRoute 12 (residential)Route 27 (commercial)
Route revenue$4,200$3,950
− Labor (wages, benefits, OT)$1,850$1,500
− Fuel$520$610
− Disposal / tipping$980$1,420
− Asset & maintenance$430$560
= Route margin$420 (10%)−$140 (−4%)

Route 27 looks busier and brings in nearly the same revenue, but a long haul to the landfill and a heavier disposal bill push it into the red. You only see that once the costs are assembled by route. The step-by-step math is covered in how to calculate route profitability.

Why don’t TRUX, Navusoft, or Routeware show it natively?

Because route profitability isn’t what those systems are built to produce. Waste ERPs are built to run routes, bill customers, and track transactions — and they do that well. Margin analytics is a different job that sits on top of them, joining billing data to costs that live in other systems entirely.

Your revenue lives in the ERP. Your labor lives in payroll or ADP. Fuel lives on fuel cards or telematics. Disposal lives on scale tickets at the landfill or transfer station. Maintenance lives in a fleet system or a spreadsheet. None of those were designed to roll up to a single route, so the number that matters most is the one no single system owns. We go deeper on this in why your ERP doesn’t show route profitability — and to be clear, this isn’t a knock on the ERP. It’s doing its job. Profitability simply requires bridging it to the rest of your data.

What data do you actually need to measure it?

Five inputs, each attributable to a route: revenue, labor, fuel, disposal, and asset/maintenance cost. Get those joined to a route ID and dated consistently, and the margin falls out. The hard part is that they arrive in different formats, on different schedules, from different owners.

  • Revenue — recurring service charges plus extras, from the ERP, mapped to the stops on the route.
  • Labor — driver wages, benefits, and overtime from payroll, allocated by hours on route. Overtime is where margin leaks.
  • Fuel — gallons and price by vehicle, from fuel cards or telematics.
  • Disposal — tons and tip fee from scale tickets, allocated to the routes that dumped the load.
  • Asset & maintenance — depreciation and repair cost per truck, spread across the routes it runs. This is the input most operators leave out; see the hidden costs that make a route unprofitable.

Once these sit in one governed model with agreed definitions, the same numbers feed every other view — AR, revenue, driver performance — instead of being rebuilt by hand each month.

How do operators use route profitability once they can see it?

They act on the routes that lose money. With margin visible by route, the moves are obvious and usually fall into four buckets: reprice underwater accounts, re-sequence or consolidate the route, renegotiate the disposal or the contract, or, as a last resort, walk away from work that can’t be made to pay.

The point isn’t to cut routes — it’s to make decisions with the cost in front of you instead of on a gut feel. Repricing one legacy commercial account, or shifting a few stops to shorten a disposal haul, often turns a negative route positive without losing the customer. That’s the difference between an efficient route and a profitable one, which we cover in route profitability vs. route efficiency.

FAQ

Common questions

Is route profitability the same as route efficiency?

No. Efficiency measures operational productivity — stops or lifts per hour, miles, time. Profitability measures margin — revenue minus cost to serve. A route can be efficient and still lose money, which is why both belong on the dashboard.

How often should we measure it?

Monthly is enough to make pricing and routing decisions; weekly once the data is automated. The value is in consistency — same definitions, same cadence — so trends are real and not an artifact of how the numbers were pulled.

Can we get this from our existing ERP?

Partly. The ERP holds revenue, but labor, fuel, disposal, and asset cost live in other systems. Route profitability comes from joining them into one governed model — complementary to the ERP, not a replacement for it.

What is a good route margin?

It varies by line of business and market, so the useful benchmark is your own routes against each other. The first goal is simply to see margin by route; the targets follow once you can rank routes and find the outliers.

See it on your data

See a sample route-profitability dashboard

We’ll show you what route-level margin looks like on your kind of data — and where it’s quietly hiding. Built on a sample, modeled on real implementations.