Amazon Delivery Accidents in California: DSP Contractor Liability

When an Amazon-branded delivery van injures you, the first legal question is not whether the driver was negligent — it is which corporate entity bears liability and under which theory. Amazon does not directly employ most of its last-mile drivers. It operates through Delivery Service Partners: independent small businesses that hire drivers, acquire or lease the vans, and run Amazon delivery routes under service agreements. That structure is not incidental; it is a designed liability buffer. But California has well-developed doctrines — ostensible agency, retained-control liability, and the post-AB 5 joint-employer framework — that can reach through it to Amazon itself.

Why Amazon DSP Claims Do Not Follow the Standard Contractor Defense

The conventional independent-contractor defense in California runs through Privette v. Superior Court (1993), 5 Cal.4th 689: a hirer delegates work to an independent business, and the hirer is insulated from tort liability for that contractor’s negligence. In a straightforward subcontracting relationship, that principle is durable. Amazon delivery cases are not straightforward.

Three doctrines erode the Privette shield in this context:

Retained control. Amazon exercises operational control over DSP drivers that goes well beyond the typical franchisor relationship. Every driver operates on Amazon’s proprietary routing software. Every van in the DSP fleet must carry a Netradyne four-camera system that Amazon monitors centrally. Amazon’s “Mentor” telematics app scores each driver’s behavior — hard braking, speeding, phone use, seatbelt compliance — in real time, and low scores can trigger corrective-action requirements or termination of the DSP contract. Under Hooker v. Department of Transportation (2002), 27 Cal.4th 198, when a hirer retains and exercises control over the manner in which work is performed, it can be held liable for injuries that result from that exercise of control. A driver who is constantly scored and routed by Amazon systems is not operating free of Amazon’s influence.

Ostensible agency. Amazon delivery vans carry Amazon’s logo and color scheme. Drivers wear Amazon-branded uniforms and scan packages with Amazon devices. Under California Civil Code §§2317–2319, an ostensible agency is created when the principal’s conduct leads a reasonable third party to believe that someone is acting as its agent. An injured pedestrian or motorist looking at an Amazon-logoed van has no practical means of knowing the driver is employed by “Reliable Routes LLC” rather than Amazon. Courts applying ostensible agency have found principal liability on thinner branding evidence than Amazon consistently presents to the public.

Joint-employer doctrine. Whether Amazon qualifies as a joint employer of DSP workers — not just the DSP itself — is a live and litigated question in California. The Martinez v. Combs (2010), 49 Cal.4th 35 test examines which entity controls wages, hours, and working conditions. Amazon sets productivity standards, dictates shift timing through its routing software, and can effectively terminate a driver’s access to work by pressuring the DSP. That level of systemic influence makes the joint-employer argument viable in the right case.

California Law That Controls Amazon Delivery Liability

AB 5 and the ABC Test. Assembly Bill 5, effective January 1, 2020 (originally codified at Labor Code §2750.3, now at §2775 et seq.), applied the ABC test from Dynamex Operations West, Inc. v. Superior Court (2018), 4 Cal.5th 903, to California employment-classification disputes. Under the ABC test, a worker is presumed an employee unless the hiring entity proves: (A) the worker is free from control in performing the work; (B) the work is outside the usual course of the hirer’s business; and (C) the worker is independently established in that trade.

DSP drivers are employees of their DSPs under this test — not independent contractors. Prong B alone is usually fatal to contractor classification because DSPs perform delivery work that is squarely within Amazon’s core logistics business.

Proposition 22 does not apply here. Proposition 22, passed in November 2020, created a carve-out from AB 5 for app-based transportation network companies and delivery platforms like Uber, Lyft, and DoorDash. DSP drivers are categorically outside that carve-out. They work set shifts on assigned routes under direct DSP supervision — they are not choosing delivery blocks through a consumer app. The Prop 22 misclassification shield that protects Instacart or DoorDash from AB 5 exposure does not exist for Amazon’s DSP model.

The Amazon Flex distinction. Amazon Flex drivers are independent gig workers who claim delivery blocks through Amazon’s consumer-facing app and use their own personal vehicles. Their classification under AB 5 and Prop 22 is a separate — and contested — question. Critically, the liability analysis for a Flex crash runs directly against Amazon, not through a DSP intermediary, because there is no DSP in the chain. The applicable insurance coverage also differs: Flex drivers are typically required to carry personal auto insurance, and Amazon’s contingent commercial auto policy activates for on-trip periods. If your case involves a Flex driver rather than a van, the discovery targets and the insurance layer structure change significantly.

Comparative Fault implications. California’s pure comparative fault system means that even if a plaintiff bears some responsibility — for example, a pedestrian who crossed mid-block — recovery is not barred, only reduced. In Amazon cases, defendants occasionally argue that the claimant contributed to the incident by walking in a delivery zone or failing to observe the backing van. The Comparative Fault framework governs how that is handled at trial.

Evidence That Defines an Amazon DSP Case

Amazon delivery cases are evidence-rich in ways that most vehicle cases are not. The challenge is not scarcity of data — it is speed of preservation.

Netradyne camera footage. Amazon vans equipped with the D-250 or D-450 camera units capture continuous interior and exterior footage on a rolling buffer. Forward, rear, and driver-facing views are all recorded. Footage tied to a collision or near-miss event is flagged automatically, but surrounding footage can be overwritten. A preservation demand must go to both the DSP (as the van’s legal operator) and Amazon (which centrally manages the Netradyne platform) within days.

Amazon Mentor app data. Mentor logs each driver’s behavioral scores by trip segment. A driver with a history of speeding scores, phone-use violations, or hard-braking events directly before the subject incident is relevant to both negligent-entrustment claims against the DSP and retained-control claims against Amazon. Amazon’s decision whether to flag or ignore those scores is discoverable.

Route and delivery scan records. Amazon’s logistics backend records every package scan with a GPS timestamp. This data reconstructs the driver’s exact route, stop sequence, and time-on-task. It refutes detour defenses and can establish that the driver was running late under Amazon’s productivity metrics — a fact relevant to the driver’s incentive to speed.

DSP employment and training records. The DSP’s hiring file for the driver — including background check, driving history, and any internal disciplinary records — goes to negligent-hiring and negligent-supervision claims against the DSP. Amazon’s minimum DSP contracting standards, including vehicle maintenance and driver background requirements, are also discoverable to establish the duty of care Amazon voluntarily assumed.

Commercial vehicle inspection records. Amazon DSP vans are commercial motor vehicles subject to California Vehicle Code inspection requirements. Maintenance logs, tire records, and brake inspection histories are discoverable and may reveal a mechanical failure that contributed to the crash.

Damages and Recovery in Amazon DSP Cases

Amazon delivery cases often involve larger recovery pools than typical two-car collisions because multiple defendants with separate insurance layers are potentially in play. The DSP’s required commercial auto policy — at least $1 million per occurrence — is the primary source. Amazon’s own excess and umbrella coverage may sit above it. When both entities are named defendants and liability is contested between them, plaintiffs sometimes benefit from adversarial indemnity dynamics: Amazon and the DSP may both argue the other is primarily responsible, which can surface internal documents and admissions that strengthen the plaintiff’s case.

Serious injuries — Herniated Disc and Traumatic Brain Injury are frequent in large-van impacts — drive case value through medical expense and loss-of-earnings projections. See Economic Damages Calculation for the components that go into the economic side of the ledger. The non-economic component, including pain, suffering, and loss of enjoyment, is analyzed under the framework at Pain And Suffering Damages; it typically constitutes the majority of total damages in severe-injury cases.

Amazon and DSP insurers generally attempt early resolution at amounts that undervalue serious injuries. Cases with strong Netradyne footage, a driver with a documented Mentor history, or evidence that Amazon knew of substandard DSP performance and failed to act tend to resist low early offers and push toward mediation at higher figures.

How Amazon and DSP Defendants Build Their Defense

Understanding the defense playbook helps frame the case early.

“Amazon is not the employer — the DSP is.” This is the primary structural defense. Amazon will argue it is a logistics platform that contracts with independent businesses and has no employment relationship with, or operational control over, the individual driver. Its service agreements with DSPs include independent-contractor language and indemnification clauses. Counsel for Amazon will emphasize that the DSP sets schedules, processes payroll, handles HR matters, and maintains the vehicles. The retained-control and ostensible-agency theories exist precisely to respond to this argument.

“The driver was on a personal detour.” If the crash occurred at a time or location that departs from the driver’s assigned route — during a personal stop, extended break, or deviation to run an errand — defendants invoke the frolic-and-detour doctrine to sever the scope-of-employment connection. Because Amazon’s route software and GPS log the driver’s position continuously, significant unexplained deviations are rare and difficult to sustain when the full data is produced.

“The DSP was a sophisticated independent contractor.” Amazon may argue that a well-funded, contractually sophisticated DSP — not a dependent laborer — made its own operational decisions, breaking the Hooker retained-control chain. The strength of this argument depends on how large and independent the DSP actually is; many are small-business operators with limited capital and close operational dependence on Amazon’s platform.

Comparative fault against the plaintiff. In pedestrian and bicycle cases, Amazon and DSP defendants frequently retain accident-reconstruction experts to argue the injured party failed to yield, crossed outside a crosswalk, or wore dark clothing. California’s Comparative Fault system does not bar recovery but does reduce it proportionally, making plaintiff-side reconstruction evidence and witness preservation equally important.

Attacking causation and injury severity. Commercial defendants with litigation resources routinely retain independent medical examiners to contest injury causation, permanency, and treatment necessity. Contemporaneous medical records, imaging studies, and documented treatment gaps are the primary tools defendants use to reduce the non-economic damages figure.