How DSP pay deductions actually work
Amazon charges the DSP (Delivery Service Partner) for damage, customer complaints, or performance metrics. The DSP then passes some or all of those charges down to individual drivers or route contractors — often through a line-item deduction on a weekly settlement, sometimes without any written notice at all.
The problem is that by the time you see the deduction, the documentation trail is already cold. You were not present when Amazon filed the charge against the DSP. You did not get to contest anything at that stage. You are now receiving a charge that originated one step above you in a chain you were not part of.
That is the dispute you need to build. Not just "I didn't damage that." But: "Show me the documentation that establishes I specifically caused this, at this time, in this amount."
The deduction chain
What you are entitled to demand
Your contractor agreement with your DSP governs what deductions are authorized and what documentation is required. Read it. Most agreements require the DSP to have documented substantiation before deducting from your pay. The key provisions to look for:
- →The specific section authorizing deductions or chargebacks
- →Any notice requirement — are they required to notify you before deducting?
- →Any right-of-response provision — are you entitled to dispute before the money is taken?
- →The arbitration clause — this governs how you escalate if the dispute is not resolved
- →Any indemnification provision that limits contractor liability
Once you have read those provisions, your documentation request is grounded in the contract — not just a complaint. That matters. "Please produce the documentation required by Section X of my agreement" is a different statement than "I want to know what happened."
ClaimGuard Pro
Generate your dispute letter with Amazon Relay language
The dispute response letter, documentation request, and demand letter are all included. Select "Amazon Relay" in the intake form and your documents include platform-specific language.
The dispute process — step by step
1. Gather your records
Delivery photos, GPS data, POD scans, platform confirmations. Do this before anything else — some platform data has short retention windows.
2. Send a formal documentation request
In writing. Request: the original charge from Amazon, the damage report, photos, and the specific contractual basis for the deduction. Give 10 business days.
3. Review what they produce
If they produce nothing, or something vague, document that failure. It becomes part of your dispute record.
4. Send a formal written dispute
Cite your delivery evidence. Identify the evidentiary gaps in their case. State your position clearly and request reversal in writing.
5. Send a demand letter if they don't respond
After 10 business days with no adequate response, send a final demand. Reference prior correspondence, set a final deadline, and specify escalation consequences.
6. File a BBB complaint
Creates a public record. DSPs that maintain a BBB rating respond to complaints differently than to support tickets.
7. File for arbitration
Most DSP contractor agreements have mandatory arbitration clauses. For amounts over $300–500, arbitration is often the most effective final step.
The arbitration clause — why it matters for DSP disputes
Most DSP independent contractor agreements contain mandatory arbitration clauses. This means that if the dispute is not resolved voluntarily, you can file for formal arbitration rather than suing in court.
For most deductions under $5,000, arbitration through the American Arbitration Association (AAA) is the most practical escalation path. Filing fees can be waived based on income. The process is faster than litigation and does not require an attorney.
Critically: most DSP companies know that a well-documented arbitration filing is expensive for them to defend. A properly prepared demand letter that mentions arbitration as the next step often produces a response that a support ticket never will.
Common DSP deduction scenarios and how to challenge them
Damage claim — no photos
Demand the photos Amazon provided to the DSP. If none exist, you are being charged based on a customer complaint alone, not documented evidence.
Deduction with no written notice
Many DSP agreements require advance written notice before deductions. If yours does, the deduction may be procedurally improper regardless of its merits.
Chargeback for a completed delivery
Produce your POD, GPS confirmation, and delivery photo. A chargeback on a confirmed delivery shifts the burden entirely to the DSP to explain the discrepancy.
SOP violation used to justify liability
Challenge the causal link. An SOP deviation is a compliance finding. It is not evidence of causation and cannot substitute for a documented investigation.
Multiple small deductions, no individual documentation
Request documentation for each one separately. DSPs often process bulk deductions with a single notice. Require them to substantiate each charge individually.
The deduction process only stops when you make it stop.
ClaimGuard Pro gives you the dispute letters, demand tools, and arbitration framework built specifically for DSP and Amazon Relay contractor disputes.