Amazon delivery vans and Amazon Flex drivers are everywhere in Miami — rushing to meet aggressive delivery windows, double-parking on residential streets, backing out of driveways, and frequently behind the wheel of vehicles whose drivers are not Amazon employees. When one of those vehicles causes a crash, the question of who is legally responsible is rarely straightforward. The Law Offices of Albert Goodwin represents Miami-area drivers, passengers, pedestrians, and cyclists hurt in collisions with Amazon-branded vehicles.
How Amazon Deliveries Are Structured
Amazon delivers in three primary ways, and which one was involved in your crash dictates the insurance and liability framework:
- Amazon Logistics — Delivery Service Partner (DSP). Amazon contracts with small businesses called Delivery Service Partners. The DSP owns the business, hires the drivers as employees, and leases or operates branded Amazon Prime vans. Amazon supplies routing, scanners, the Rabbit app, and the daily route load. DSP drivers are employees of the DSP, not Amazon — but Amazon's control over routes, hours, performance metrics, and equipment is the basis for vicarious-liability and joint-employer arguments.
- Amazon Flex. Independent contractors using their own personal vehicles, recruited through the Flex app to pick up packages from a delivery station and deliver them on a flexible block schedule.
- Amazon Logistics — Amazon Employees. A smaller direct-driver workforce at warehouses and middle-mile operations.
Insurance Coverage
Amazon maintains a $1 million commercial liability policy that covers DSP drivers and Flex drivers during active delivery work — but only after the personal insurance of the DSP or the Flex driver is exhausted, and only if specific conditions in the policy are met. The result is a layered structure similar to Uber and Lyft cases, with predictable disputes over whether the driver was "in delivery mode" at the moment of the crash:
- DSP driver in a branded van during a route. The DSP's commercial auto policy is primary. Amazon's $1 million policy and any DSP excess respond after the primary limits are exhausted.
- Flex driver in their own car during an accepted block. The driver's personal auto carrier is primary (and frequently denies coverage because personal policies exclude commercial delivery). Amazon's $1 million policy is meant to respond when the personal carrier denies or its limits are exhausted, but Amazon's carrier routinely contests coverage as well.
- Flex driver between blocks or "off the app." Only the driver's personal policy applies — and that policy usually excludes any delivery activity, which can leave the driver effectively uninsured.
- DSP or Flex driver "deadheading" (driving to or from a delivery station without an active route). Coverage gets murky and is heavily litigated.
Vicarious Liability and Amazon's Direct Liability
Amazon's standard defense is that DSPs and Flex drivers are independent contractors and that Amazon is therefore not vicariously liable. This defense is contested in courts across the country, with mixed results. The strength of the argument that Amazon should be treated as the driver's employer (or joint employer) depends on the specific evidence — the level of control Amazon exercises over routes, hours, performance, equipment, vehicle inspection, and discipline. Beyond vicarious liability, Amazon may face direct liability for:
- Negligent hiring and contracting practices for the DSP itself (driving record, prior crash history)
- Negligent route design that pressures drivers into unsafe speed or stop patterns
- Performance metrics that punish safe behaviors (longer routes, denied breaks)
- Failure to enforce safety policies (seatbelt compliance, phone use, fatigue)
Evidence Specific to Amazon Cases
Amazon and its DSPs maintain a remarkable amount of data on every delivery:
- Rabbit/Flex app data — GPS pings, package scans, time at stop, route deviation
- In-van Netradyne (Driveri) cameras — most DSP vans now have outward- and inward-facing cameras with event detection; footage is event-flagged and stored in the cloud
- Telematics — speed, hard braking, hard acceleration, cornering
- Mentor scores and weekly safety reports
- DOT-style logs for DSP fleet vehicles where applicable
This data is typically retained for limited periods (30–90 days) and must be preserved with prompt litigation-hold letters to Amazon, the DSP, and any insurance carriers. Critical Driveri video is often overwritten within weeks if no demand is sent.
Common Miami Amazon Crash Scenarios
- Backing crashes — Prime vans backing out of driveways without a spotter, hitting pedestrians, parked cars, and bicyclists
- Rear-end crashes — drivers checking the route app or scanner
- Double-parking and door-zone crashes — particularly affecting cyclists in Wynwood, the Design District, and Brickell
- Intersection T-bones — drivers running yellows under time pressure
- Pedestrian impacts in residential neighborhoods during sidewalk-side deliveries
- Flex driver crashes in unmarked personal vehicles, leaving victims to discover later that an Amazon delivery was underway
What to Do After a Crash with an Amazon Vehicle
- Call 911 — make sure a Florida Traffic Crash Report is generated
- Photograph the vehicle, the Amazon logo or any Amazon-branded packages visible, the driver's vest or badge, and the license plate
- If the driver was in a personal vehicle, ask whether they were on an Amazon Flex delivery — write down the answer
- Get the names and contact information of any witnesses
- Seek medical evaluation within 14 days to preserve PIP benefits
- Contact a lawyer quickly so preservation letters can be issued before Driveri video and Rabbit/Flex data are overwritten
If you have been hurt in a crash with an Amazon Prime van or Amazon Flex driver anywhere in South Florida, contact the Law Offices of Albert Goodwin. Call 786-522-1411 or email [email protected] for a free consultation.