Amazon Counts Stops. Your Drivers Deliver to Houses. The Gap Is Costing You Both.
There's a number Amazon gives you, and there's the number your drivers actually work. A route with 120 stops doesn't mean 120 front doors. It means 120 entries in the system — some of which are apartment complexes, commercial buildings, or multi-unit properties that require multiple physical deliveries per stop. That gap between the counted stop and the worked delivery is where route profitability quietly disappears, and most operators have never run the math on it.
How Amazon Structures the Rate Card
Amazon pays DSPs by the stop — a unit defined by the delivery manifest, not by the number of physical packages placed at physical locations. A single manifest entry for a 12-unit apartment building with three separate package recipients counts as one stop, per Amazon DSP program documentation. A commercial suite with five recipients counts as one stop. The rate card and the actual labor input are measuring different things.
DSP operators in online communities have been describing this dynamic for years. The pattern is consistent: routes officially logged at 150 stops regularly run two to three hours longer than a suburban single-family route of the same stop count, because the stops aren't the same kind of stop. "200 stops but each stop is four or five houses" is the language operators use, per discussions in DSP operator forums — not an edge case, but a structural feature of dense residential and mixed-use routes.
The Math on a Mixed-Density Route
Assume 20 percent of stops on a dense residential route are multi-location entries — apartment buildings, townhouse clusters, commercial suites — where the driver completes an average of three physical deliveries per stop. On a 150-stop route, that's 30 stops accounting for 90 actual deliveries. The effective delivery count is 210, not 150. The rate card pays for 150.
What does that mean in time? ATRI's fleet productivity research on last-mile delivery puts optimal suburban single-family delivery at roughly 1.5 to 2 minutes per stop — a benchmark Amazon's DSP rate structure implicitly assumes in dense single-family corridors. Multi-location stops run materially longer — navigating parking, locating units, managing access, and completing multiple handoffs. A driver who finishes 150 counted stops but completes 210 actual deliveries in a dense corridor isn't finishing in the same window as a driver running 150 single-family stops in a suburban grid. The route looks the same on paper. It isn't the same route.
Where This Shows Up in Your P&L
Labor cost is the direct exposure. If a driver's route runs 45 to 60 minutes longer than the stop count suggests it should, that's wage cost your rate card didn't price for. Across a fleet running 15 to 20 routes daily in mixed-density service areas, the accumulated labor gap between what's paid and what's worked isn't a rounding error — it's a line item that doesn't appear anywhere in the manifest but shows up in every payroll cycle.
The secondary effect is driver experience. DSP operators in online communities describe the same operational pattern: drivers who expected 150 stops and finished four hours later than their suburban-route colleagues, with no visible difference in their manifest. Retention problems in dense corridors often have a stop-count-reality dimension that operators aren't tracking because they're looking at stops-per-hour rather than deliveries-per-hour.
What to Do With This
The first step is diagnostic: pull your routes by geography and compare on-route time against stop count for routes in dense versus suburban areas. If your dense routes are consistently running 20 to 30 percent longer per stop than your suburban routes at the same stop count, you're looking at a stop-composition effect — not a driver performance problem.
The second step is operational: some DSPs have negotiated with their station on route configuration to reduce multi-unit stop density in their most time-inefficient corridors, or to account for route complexity in how they staff and schedule. The rate card isn't changing. But the composition of what you accept into your route plan can be managed.
Operators who understand the difference between a counted stop and a worked delivery are the ones who can look at a proposed route and evaluate it accurately before the driver leaves the station. That's a capability the stop count alone doesn't give you.
Sources: ATRI last-mile delivery productivity research; Amazon DSP program rate card structure; DSP operator community discussions (r/AmazonDSP and DSP operator forums)