Amazon Counts Stops. Your Drivers Deliver to Houses.
Amazon's rate card is built around stops. Your drivers live in the reality of doors. In suburban and urban corridors, those two numbers diverge significantly — and most DSP operators are absorbing the difference without measuring it.
What a Stop Actually Is
In Amazon's delivery system, a stop is a delivery location — a single address or property pin. What happens at that stop is a separate question. A multi-unit apartment building, a townhouse cluster, a strip of condos sharing a single address: these register as one stop in the routing system. Your driver walks to four, six, or eight individual units.
Operators in online DSP communities consistently describe this gap. Routes listed at 120 or 130 stops routinely require 150 or more physical door contacts. The routing software counts the pin. The driver counts the stairs.
The Math Operators Aren't Running
Amazon's rate card compensates per stop, per package, and per route — a structure designed for the system's accounting, not the operator's labor cost. If 20 percent of your stops are multi-unit locations averaging three physical deliveries each, a 120-stop route becomes roughly 144 physical deliveries. Your labor cost tracks physical deliveries. Your revenue tracks stops.
At $23 per hour — Amazon's program-targeted driver wage per its January 2026 DSP program announcement — a driver completing 144 physical deliveries in a standard shift is generating a different cost-per-delivery than one completing 120 single-family drop-offs. The rate card doesn't distinguish between them.
For an operator running 15 routes per day, a 20 percent multi-unit stop mix adds roughly 72 additional physical deliveries to daily labor output — deliveries compensated at the stop rate, not a higher one. Over a 250-day operating year, that gap accumulates. The profitability of a route corridor depends on its stop composition as much as its stop count, but most operators track only the latter.
Where This Shows Up in the P&L
Route profitability in dense urban corridors tends to underperform suburban routes at comparable stop counts. The reasons vary — parking, building access, elevator wait times — but multi-unit stop density is a consistent underlying factor. Operators who have run the comparison internally, as shared in DSP communities, describe suburban single-family routes as noticeably more efficient on a per-stop basis than urban routes with equivalent stop counts.
ATRI's 2025 Operational Costs of Trucking report documents labor as the largest single operating cost category for delivery fleets, accounting for the majority of variable costs per mile and per stop. Any systematic undercount of actual labor input relative to compensated units is margin compression that compounds daily.
What to Track
The stop count on a manifest is a routing number. The metric that matters for labor cost is physical delivery contacts — door touches per driver per shift. Operators who track both can identify which route corridors are delivering margin and which are quietly eroding it.
Stop composition by route — the percentage of multi-unit versus single-address stops — is the variable that explains performance gaps between routes that look equivalent on paper. In markets with high apartment density, this number is large enough to matter. In suburban markets, the gap may be minimal. The only way to know is to measure it.
Amazon's rate structure isn't changing based on individual operator feedback. What can change is whether operators know which routes they're winning and losing on — and why.
Sources: Amazon Delivery Service Partner program announcement, January 2026; ATRI 2025 Operational Costs of Trucking; operator accounts from online DSP communities
Frequently Asked Questions
How does Amazon count delivery stops? Amazon's rate card compensates per stop address, not per package or per physical delivery attempt. A single address with multiple packages counts as one stop. An apartment building with 8 deliveries counts as one stop. This structure systematically undercompensates operators on dense multi-unit routes.
What is the real cost of the stop count gap for DSP operators? If 20% of your routes involve multi-unit stops averaging 3–4 physical deliveries per stop address, your drivers are completing 20–30% more work than your stop count reflects. At $0.40/stop, that gap represents $60–$90/day in uncompensated labor per van.
Which DSP routes are most affected by the stop count gap? High-density urban routes with apartment buildings, commercial complexes, and multi-family housing are most exposed. Suburban single-family residential routes are least affected — one address typically equals one physical delivery.