Cost per Stop for FedEx Routes: How to Calculate It Correctly

Cost per stop is the single most useful operating number in a FedEx Ground business. Your revenue is substantially stop-based, your costs are substantially driven by how many stops you run, and the gap between the two — margin per stop — is the business. It is also a number that's easy to compute wrong in ways that look precise. This guide covers the correct method, the classic mistakes, and what to do with the number once it's trustworthy.

The formula (and why the denominator is the hard part)

The formula is one line: total operating cost for a period ÷ total stops serviced in that period. Nobody gets the division wrong. What goes wrong is the inputs — what counts as cost, and how the period is defined.

The numerator: which costs to include

Cost per stop should reflect the full weekly cost of running routes, not just wages:

• Driver labor — gross wages plus payroll taxes and workers' comp, not take-home pay. Labor is almost always the largest component.
• Vehicles — payments or lease costs, maintenance and repairs, tires, and the fuel you purchase at the pump. (The fuel surcharge on your settlement is revenue; the diesel you buy is cost. Keep them on opposite sides.)
• Insurance and program charges — the recurring deductions on your settlement are real costs; they belong in the numerator even though FedEx nets them out before paying you.
• Overhead — management salary (including your own time if you work the business), software, accounting, shop space. Spread these honestly across the period.

Two versions of the number are worth keeping: a direct cost per stop (labor + vehicles) that tracks weekly operations, and a fully loaded version including overhead that tells you whether the whole business works. Just never mix them mid-comparison.

The denominator: stops, counted honestly

• Use stops from the settlement, since that's what you're paid on. Delivery and pickup activity both consume route time; if you break them out, do it consistently.
• Count weeks the FedEx way. Weeks run Saturday–Friday. When averaging over a period, count the distinct FedEx weeks your data actually touches — never take a date span and divide by seven. A Monday–Friday terminal "averaged" by calendar days can overstate weekly volume by a wide margin, which understates cost per stop and flatters the operation.
• Match the periods exactly. The cost period and the stop period must cover the same weeks. Payroll periods rarely align with settlement weeks, so either work in multi-week blocks where the misalignment washes out, or note the mismatch explicitly.
• Don't fill gaps with guesses. If you don't have observed data for a driver or a week, exclude it and say so, rather than imputing a typical day. An average built on real coverage plus a disclosure beats a complete-looking average built on assumptions.

The classic mistakes

• Calendar-week math on a 5- or 6-day terminal — the date-span-÷-7 error above. It's the most common and the most flattering.
• Leaving settlement deductions out of costbecause they never hit your bank account as an expense.
• Averaging away route differences. One operation-wide number hides that your dense urban route and your rural extension may have wildly different per-stop costs. Compute per route (or per route group) when deciding anything about specific routes.
• Chasing benchmark numbers. Published "good" cost-per-stop figures vary widely by source, terrain, density, and year — treat any of them as rough industry estimates, not targets. Your trend against yourself is far more decision-useful than your gap against a number from a Facebook group.

Using the number

Cost per stop earns its keep next to revenue per stop — total settlement revenue ÷ stops for the same weeks. The comparison drives real decisions: whether a route rework pays, what a MESO option is worth under your cost structure, whether adding a supplemental at given rates makes money, and which routes are quietly subsidizing which. Watch the trend over multi-week blocks; single weeks are noisy by nature (mix shifts, a truck in the shop, a holiday week), and the signal is in the direction, not the wiggle.

Keeping it current without the spreadsheet grind

The discipline cost of this metric is real: it needs settlement stops, payroll, and vehicle costs joined every week, with the week-counting and coverage rules applied consistently. That join is exactly what Route Impact maintains — settlement volumes and revenue from your weekly statements, labor from payroll uploads with observed-day discipline built in (uncovered drivers are disclosed, never imputed), per FedEx week, per CSA. If you'd rather run it yourself, the method above works in any spreadsheet — the rules are what matter, not the tool.