Amazon Now Requires You to Disclose Your Funding. Your Intake Wasn't Built for That.

Amazon didn't just reinstate binding arbitration in August 2026. It added a requirement that most plaintiff firms scrolled right past: mandatory disclosure of litigation funding agreements in mass arbitration.

If you're running or planning a mass arb campaign against Amazon, every funding arrangement tied to your claimants now has to be disclosed. Not voluntarily. Not upon request. As a condition of participating in the process.

This isn't an Amazon quirk. It's a template. The ICC made funding disclosure mandatory in its 2026 arbitration rules. Bloomberg Law flagged Amazon's version within days of the terms going live. And if you think AAA and JAMS aren't watching, you haven't been paying attention to how fast procedural innovations travel between arbitration providers.

The question isn't whether funding disclosure is coming to every mass arb clause. It's whether your intake infrastructure is ready for it when it does.

What Amazon's Clause Actually Says

Amazon's updated terms require that in any mass arbitration (defined as 25 or more similar demands within six months), claimants must disclose the existence of any third-party litigation funding agreement. Not the dollar amount. Not the terms. The existence and the identity of the funder.

That sounds simple until you think about what it means at scale. If you have 3,000 signed claimants and a funding agreement covering the campaign, every single one of those claimants needs a disclosure that accurately reflects the funding relationship at the time of filing. Change funders mid-campaign? Update 3,000 disclosures. Add a co-funding arrangement? Same thing.

Defendants aren't requiring this because they're curious. They're requiring it because funding disclosure creates three tactical advantages: it lets them challenge standing on a per-claimant basis, it opens discovery into the funder's role in case strategy, and it creates a procedural tripwire that can slow batch processing if disclosures are incomplete or inconsistent.

The Intake Problem Nobody Is Modeling

Most plaintiff firms treat intake as a linear process: acquire lead, qualify lead, sign retainer, file. Funding is handled at the firm level or the campaign level. It's a finance conversation, not an intake conversation.

Amazon's clause makes it an intake conversation.

Every claimant you sign now needs a record that captures whether the claim is funded, by whom, and under what arrangement. That record needs to be accurate at the moment of filing and updatable if the funding structure changes. And it needs to be attached to the individual claimant file, not buried in a firm-level spreadsheet, because the disclosure obligation runs per claimant.

If you're buying leads from an aggregator, the problem compounds. You don't control when those leads were generated, what they were told about funding, or whether the consent forms they signed even contemplated a disclosure obligation. You inherit the lead, but you also inherit whatever gap exists between your funding reality and the claimant's documented understanding of it.

Why This Is a Completion Problem, Not Just a Filing Problem

Here's where the math gets uncomfortable. Say you file 2,000 claims against Amazon. Defendant's counsel reviews your funding disclosures and finds 200 that are incomplete, inconsistent, or missing. They challenge those 200 claims on procedural grounds before any substantive arbitration begins.

You just lost 10% of your filed claimants to a paperwork issue. On a matter where your release threshold is 85%, that 10% isn't a rounding error. It's the difference between hitting threshold and spending another six weeks (and five figures in outreach costs) trying to backfill.

Now multiply that by the batch structure. Amazon's clause processes claims in batches of 25, scaling to 100 and then 500 as volume increases. If your funding disclosures are inconsistent across batches, the defendant can challenge each batch independently. Your completion timeline doesn't just slip. It fragments.

The Fix Is Upstream, Not Downstream

The firms that will handle this well are the ones that build funding disclosure into intake infrastructure rather than treating it as a post-signing compliance task. Three specific moves:

1. Capture funding status at signing. Your digital retainer packet should include a funding disclosure acknowledgment that the claimant reviews and signs alongside the retainer. This isn't a new document. It's a field in your existing e-signature workflow. If your admin stack handles native document signing, adding a disclosure field is a configuration change, not a development project.
2. Build an update trigger. When your funding arrangement changes (new funder, co-funder, restructured terms), your system should flag every affected claimant file and generate an updated disclosure. If you're running this on spreadsheets or a CRM that wasn't built for per-claimant document management, you'll miss updates. At 3,000 claimants, "we'll update them manually" is not a plan.
3. Audit before filing each batch. Before you submit any batch to the arbitration provider, run a disclosure completeness check. Every claimant in the batch should have a current, signed disclosure that matches your actual funding arrangement. Catch the gaps before the defendant does.

This Is the ICC Playbook, Domesticated

The ICC made third-party funding disclosure mandatory in its June 2026 rules. At the time, I wrote that domestic mass arb would follow. It took two months.

Amazon is the first major consumer defendant to bake funding disclosure into its arbitration clause. It will not be the last. PayPal's September 2026 switch to JAMS came with its own procedural additions. Every defendant rewriting its ToS right now is reading Amazon's clause the way plaintiff firms should be: as a modular template they can copy and customize.

The firms that treat this as an Amazon-specific issue will scramble every time a new defendant adds the same requirement. The firms that build disclosure-ready intake infrastructure now will file cleanly against any clause that includes it, because the operational lift is the same whether it's Amazon, PayPal, or the next Fortune 500 company that updates its terms next quarter.

The Bigger Point

Mass arbitration is becoming an operations competition. The substantive law hasn't changed. The procedural terrain has. Defendants are adding requirements (funding disclosure, pre-arbitration negotiation periods, batch caps, bellwether rounds) that don't change whether you win on the merits. They change whether you can get to the merits efficiently.

Every one of those requirements is an intake and admin problem before it's a legal problem. And the firms solving intake and admin problems at the infrastructure level, not the paralegal level, are the ones whose completion rates hold up when the procedural ground shifts.

I'm biased. I built an admin stack specifically to handle per-claimant document management at scale. But the math is the math: if your intake can't generate, store, and update a funding disclosure for 3,000 claimants without manual intervention, you're not ready for the clause that's already live and the five clauses coming behind it.

Harry Hedaya is the founder of Send It By Text, the native document signing, SMS, and email platform behind GroupSettle's mass arbitration completion stack. Their AI super agent handles over 80% of claimant inquiries on its own, which lifts engagement rates further. He works with plaintiff firms running live mass arb campaigns.