Route Profitability by Service Line: Why Roll-Off Isn’t Residential
Route profitability differs by service line because residential and roll-off routes carry opposite cost structures. Residential routes run many stops at low revenue per stop with heavy labor cost. Roll-off routes run few stops but carry a large disposal cost per pull. Blending them into one number, or judging both against a single benchmark, hides which routes actually make money.
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. Most operators track one version of that number for the whole fleet. That’s the first mistake, and it’s the subject of this page.
If you run both a residential book and a commercial or roll-off book, you’ve probably already felt the disconnect: a route report that says the fleet is “profitable” while a specific truck, a specific yard, or a specific service line is quietly bleeding margin nobody can point to. That gap usually isn’t a data-quality problem. It’s a definition problem — the same “route profitability” label is being asked to describe two businesses that don’t share a cost structure.
Why doesn’t one “route profitability” number work across service lines?
A single “route profitability” figure blends fleets that don’t behave the same way. Residential routes earn small amounts from hundreds of stops; roll-off routes earn large amounts from a handful of pulls. Averaging the two produces a number that describes neither route type accurately, and hides which service line is actually dragging down margin.
This isn’t a rounding error. A residential route and a roll-off route can carry the same “profitable” or “unprofitable” label on a single dashboard while the reasons behind each label have nothing to do with each other. Blend them and you get a company-wide margin trend that moves for reasons nobody in the room can name. For the broader mechanics of what route profitability is actually measuring versus how it gets confused with a related but different metric, see Route Profitability vs. Route Efficiency.
What makes residential routes profitable or unprofitable?
Residential route profitability is driven by stop density and labor efficiency, not disposal cost. Revenue per stop is low and fixed by contract, so margin comes from how many stops a driver completes per hour, how tight the route sequencing is, and how much time is lost to missed pickups, re-runs, or contamination rejections at the tip.
- Revenue per stop: low and largely fixed — set by a municipal contract or a flat subscription rate, not negotiated stop by stop.
- Cost driver: labor and drive time between stops. A route that loses ten minutes to a bad sequence loses it on every stop after it, not just one.
- Volume sensitivity: margin is highly sensitive to stop count per hour — a route running 15% fewer stops per hour with the same labor cost is a worse route, even if nothing else changed.
- Failure mode: missed pickups, re-runs, and contamination rejections quietly eat margin because they add cost without adding revenue.
None of this shows up cleanly if the cost side of the ledger is buried in a spreadsheet that only gets refreshed once a month. The Hidden Costs That Make a Route Unprofitable goes deeper on the specific line items — re-runs, idle time, contamination — that erode residential margin without ever showing up as a single obvious red flag.
What makes roll-off (and commercial) routes profitable or unprofitable?
Roll-off (and other commercial) route profitability is driven by disposal cost per pull, not stop count. A single truck might complete only a few pulls a day, but each pull carries a large tipping-fee cost, a haul distance to the disposal site, and container rental economics. A route can look “high revenue” and still lose money on disposal alone.
- Revenue per stop (pull): high relative to residential, but the cost that eats into it is high too — it’s a different scale entirely, not just a bigger version of the same number.
- Cost driver: disposal cost per pull (the tipping fee) plus haul distance and haul time to the disposal or transfer site.
- Volume sensitivity: margin is far less sensitive to stop count and far more sensitive to container fill rate and per-pull disposal pricing.
- Failure mode: a contract priced without a current tipping-fee number, or a haul route that quietly got longer after a transfer station changed, both erase margin without changing a single thing dispatch can see.
This is also where reporting tends to break down first, because ERP systems built around dispatch and routing weren’t designed to net a disposal invoice against a specific pull. Why Your ERP Doesn’t Show Route Profitability covers that gap in more detail.
Residential vs. roll-off: what’s actually different?
Residential and roll-off routes differ on nearly every input to a margin calculation: revenue per stop, how disposal cost behaves, the labor pattern, and what actually drives margin up or down. The table below lays out the pattern side by side using illustrative figures, not real client data, to show the shape of the difference.
| Factor | Residential | Commercial / roll-off |
|---|---|---|
| Revenue per stop | ~$6–$10 per stop, fixed by contract or subscription rate | ~$150–$400 per pull, negotiated per container/service |
| Stop count per route | High — often 300–600+ stops per route per day | Low — often 6–15 pulls per route per day |
| Disposal cost pattern | Small, distributed across many stops; rarely the deciding factor alone | Large, concentrated per pull; often the single biggest cost line |
| Labor pattern | Labor-heavy — driver time is spread thin across many low-value stops | Lower total labor hours, but each stop carries hook/drop and positioning time |
| Typical margin drivers | Stop density, route sequencing, re-run and contamination rate | Tipping fee per pull, haul distance/time, container fill rate and utilization |
How do you compare route profitability fairly across service lines?
To compare route profitability fairly, normalize within each service line before comparing across them: measure residential routes against other residential routes on stops-per-hour and cost-per-stop, and measure roll-off routes against other roll-off routes on cost-per-pull and haul-cycle time. Only after that internal ranking is done does it make sense to ask which service line is dragging down the blended number.
In practice this means running two (or more) parallel leaderboards, not one. Rank every residential route against every other residential route. Rank every roll-off route against every other roll-off route. A residential route sitting at the 40th percentile of its own service line is a real problem worth fixing. A roll-off route sitting at the 40th percentile of a blended, mixed-service-line ranking might actually be one of your best roll-off routes — it just looks bad next to routes it was never structurally comparable to in the first place.
Once each service line has its own clean ranking, a company-wide view becomes useful again — as a roll-up of “how is residential performing against itself” and “how is roll-off performing against itself,” not as a single blended average standing in for both.
The same normalize-first logic applies below the service-line level too. A residential route in a dense urban zone and a residential route on a long rural loop don’t share a cost structure either, even though both are “residential.” The service-line split in this article is the first cut that matters most, but it’s an instance of a general rule: never compare route profitability across routes that don’t share a cost structure without normalizing for the difference first.
Where does this go wrong in the ERP or reporting stack?
Most ERPs report revenue, cost, and route data in separate modules that were never built to net against each other by service line. Dispatch sees stops and time; finance sees invoices. Nobody sees one number that says “this roll-off route lost money this month.” The gap gets filled with a blended average that hides both the winners and the losers.
Systems like TRUX, Routeware, and Navusoft are strong at what they were built for — routing, dispatch, service history — and none of them were built as a profitability engine that automatically separates residential margin logic from roll-off margin logic. Getting there usually means a reporting layer that pulls from the ERP and the finance system and applies the right normalization to each service line, rather than waiting for a native report that treats every route the same way.
What should ops and finance actually do with this?
Once residential and commercial routes are separated and normalized, ops and finance can rank routes within each service line, flag the ones actually losing money, and decide whether the fix is pricing, routing, or disposal sourcing. That’s a reporting problem before it’s a dispatch problem, which is why it usually gets solved outside the ERP’s native reports.
Start by pulling residential and roll-off (and any other commercial service lines) into separate views before you look at margin at all. Then rank within each. The routes that fall out at the bottom of their own service line — not the bottom of a blended list — are the ones worth a route manager’s time this week.
For the fuller framework this page sits under — how route profitability is defined, measured, and reported end to end — see the pillar guide: Route Profitability in Waste Operations. If you want a structured read on where your own reporting stands before changing anything, the ops-level maturity assessment is a lower-lift starting point than a full engagement.
Does this apply outside waste?
The same principle holds outside waste: an insurance carrier comparing loss ratios across auto and commercial property lines, or an e-commerce operator comparing margin across a low-price, high-volume SKU category and a premium, low-volume one, runs into the same trap. Profitability only compares cleanly within a business line with a shared cost structure — never across two that don’t share one.