What Is Per-Stop Pay and Why FedEx Uses It
Per-stop pay is a compensation model in which drivers earn a set dollar amount for each delivery stop they complete, rather than being paid a flat hourly wage or salary. A "stop" is defined as a unique delivery address. Whether a driver delivers one package or ten packages to the same address, it counts as a single stop for pay purposes (though many ISPs add package volume bonuses on top).
FedEx Ground contractors favor per-stop pay because it aligns driver compensation with productivity. Drivers who work efficiently and complete more stops earn more money, which creates a natural incentive to deliver quickly and reliably. For the ISP owner, per-stop pay also ties labor costs directly to revenue, since FedEx pays ISPs on a per-stop and per-package basis as well. This alignment means that when volume increases, both revenue and labor costs scale proportionally.
The per-stop model also provides flexibility for drivers. On lighter days with fewer stops, drivers finish earlier. On heavier days, they earn more. This variable structure is one of the reasons many delivery drivers prefer per-stop arrangements over fixed hourly pay, as long as the per-stop rate is competitive.
How Per-Stop Thresholds Work
Most ISPs do not use a single flat per-stop rate. Instead, they implement a tiered threshold system that pays higher rates as drivers complete more stops in a day. This structure serves two purposes: it guarantees a reasonable base pay on light days, and it rewards drivers for handling heavy volume.
A typical three-tier structure works like income tax brackets. The rate applies only to the stops within that tier, not to all stops retroactively. Here is how a common setup might look:
- 0 to 80 stops: $1.50 per stop (base tier)
- 81 to 120 stops: $1.75 per stop (mid tier)
- 121+ stops: $2.00 per stop (premium tier)
This means a driver who completes exactly 80 stops earns $120.00 for the day. A driver who completes 81 stops earns $120.00 for the first 80, plus $1.75 for the 81st stop, totaling $121.75. The 81st stop does not retroactively change the rate on the first 80 stops.
Some ISPs use a simpler two-tier structure, while others add complexity with four or more tiers. The optimal structure depends on the typical stop-count distribution on the routes, the local labor market, and the margins available after FedEx settlement payments.
Example Calculations with Real Numbers
The following examples demonstrate per-stop pay calculations under the three-tier structure described above. These examples use realistic stop counts for FedEx Ground routes.
Example 1: Light Day (65 Stops)
All 65 stops fall within Tier 1, so the calculation is straightforward:
65 stops x $1.50 = $97.50
Example 2: Average Day (110 Stops)
The first 80 stops are at the base rate, and the remaining 30 are at the mid rate:
This driver earned $941.25 in gross per-stop pay for the week. Bonuses, overtime, and fuel deductions would be applied on top of this base amount. Note that the effective per-stop rate across all 590 stops works out to approximately $1.60, which is higher than the base rate because of the tiered structure rewarding higher-volume days.
Package Volume Adjustments
While per-stop pay is the primary compensation component, many ISPs add a per-package adjustment to account for stops with high package counts. The logic is simple: delivering 12 packages to a single business address requires more physical effort, more vehicle space, and more time than delivering a single envelope to a residential address, yet both count as one stop.
Common per-package adjustments include:
- Flat per-package bonus: $0.15 to $0.25 for every package beyond the first at each stop. If a driver delivers 8 packages to one address, they receive the standard per-stop rate plus 7 x $0.20 = $1.40 in package bonuses.
- Total package threshold: A daily bonus triggered when total package count exceeds a threshold. For example, a $25 bonus when total daily packages exceed 200.
- Package-to-stop ratio bonus: An additional per-stop increment when the average packages per stop exceeds a target. If the daily average exceeds 1.5 packages per stop, an extra $0.10 per stop is added.
These adjustments ensure that drivers on package-heavy commercial routes are compensated comparably to drivers on residential routes with lower package density but potentially more driving between stops.
How Different CSAs Have Different Rates
FedEx Ground pays ISPs different rates depending on the CSA, and these differences flow down to driver pay. Factors that influence CSA-level rates include:
- Geographic density: Urban CSAs with shorter distances between stops tend to have lower per-stop rates because drivers can complete more stops per hour. Rural CSAs with longer drive times between stops command higher per-stop rates to compensate for the lower productivity.
- Market cost of living: CSAs in high-cost-of-living areas (San Francisco, New York, Seattle) typically pay higher rates to attract and retain drivers.
- Route complexity: CSAs with challenging terrain, gated communities, apartment complexes, or heavy commercial areas may offer premium rates due to the additional time required per stop.
- Contract negotiation: Each ISP negotiates individually with FedEx, and rates can vary between ISPs operating in the same terminal. More experienced ISPs with strong performance histories often negotiate better terms.
For ISPs operating multiple CSAs, it is essential that the payroll system tracks which CSA each driver worked in on each day and applies the correct rate structure. A driver who works CSA-A (urban, $1.50 base) on Monday through Thursday and CSA-B (suburban, $1.75 base) on Friday must have their pay calculated under two different tier structures for the same week.
Per-Stop vs. Hourly vs. Salary: A Comparison
ISP owners often debate which pay model is best for their operation. Each model has distinct advantages and drawbacks. The table below summarizes the key differences.
The majority of established FedEx ISPs use per-stop pay for drivers because it provides the strongest alignment between labor costs and FedEx revenue. However, some ISPs use hourly pay for training periods, for drivers on low-volume routes where per-stop pay would fall below minimum wage, or for helper/jumper positions that do not have assigned routes.
Common Per-Stop Calculation Errors
Even experienced ISP owners make calculation mistakes, particularly when using spreadsheets. The most common errors include:
1. Retroactive Tier Application
Applying the Tier 2 rate to all stops when the count crosses the first threshold, rather than applying it only to the stops above the threshold. This error overpays on high-volume days and can cost hundreds of dollars per week across a fleet.
2. Off-by-One Errors at Boundaries
Miscounting whether the threshold stop itself belongs to the lower or upper tier. If Tier 1 covers stops 1 through 80 and Tier 2 starts at stop 81, a formula that uses "greater than 80" versus "greater than or equal to 80" will produce different results for drivers who land exactly on 80 stops.
3. Wrong CSA Rates Applied
When a driver works across CSAs, applying the wrong CSA's rate structure to a day's work. This is especially common in spreadsheets where CSA assignment is tracked in a separate tab from the pay calculation.
4. Missing Package Volume Adjustments
Forgetting to add per-package bonuses on high-package-count days, either because the package data was not imported or because the formula does not account for it.
5. Rounding Errors
Rounding per-stop amounts to the nearest dollar before summing, rather than carrying decimal precision through the calculation and rounding only the final weekly total. Over a year, rounding errors can accumulate to meaningful discrepancies.
How FleetWage Automates Per-Stop Pay
FleetWage eliminates the manual per-stop calculation process entirely. The platform imports stop counts directly from FedEx settlement reports, applies the correct tier structure for each driver and each CSA, calculates package volume adjustments, and produces accurate daily and weekly pay totals.
Key automation features include:
- Up to 3 customizable thresholds per employee: Set different tier structures for each driver or group of drivers based on their route assignment.
- Multi-CSA rate management: Define separate rate structures for each CSA, and FleetWage applies the correct rates when drivers work across CSAs.
- Automatic overtime calculation: FleetWage computes the regular rate from per-stop earnings and applies the correct overtime premium based on federal and state rules.
- One-click payroll export: Export finalized pay data to ADP, Gusto, Paychex, Paylocity, and other providers without manual data entry.
ISP owners using FleetWage report reducing payroll processing from 10 to 15 hours per week to under 45 minutes, while eliminating the calculation errors that cause driver disputes and compliance issues. For a broader overview of ISP payroll, see our Complete FedEx ISP Payroll Guide.
