Retailers are being sued over shipping protection fees, but not because the fee is illegal. The class actions allege the fee was added without meaningful consent: pre-selected, buried, or contradicting an advertised free shipping promise. Every allegation describes a checkout configuration choice, which means a WooCommerce merchant can avoid all of them.
If you sell a protection fee at checkout, or you are thinking about it, these cases are the clearest guide available to what not to do. They are worth reading not as legal drama but as a list of settings.
None of these allegations has been proven The cases described below are pending. Allegations in a complaint are allegations, not findings. This article summarises what plaintiffs claim, because that is what tells you which practices attract a lawsuit. It is not legal advice, and it is not a judgement on any company named.
What are the shipping protection lawsuits about?
The shipping protection lawsuits allege that retailers charged customers an optional protection fee without obtaining real consent. Plaintiffs claim the fees were pre-selected or auto-added, disclosed only in small print or at the final checkout step, and in some cases contradicted an advertised free shipping promise. Typical fees range from one to five US dollars per order.
The claims are not brought under a shipping protection law, because no such law exists. They are brought under general consumer protection statutes: unfair competition, false advertising, unjust enrichment, breach of contract, and state unfair and deceptive practices acts. Those statutes are broad, they exist in every state, and many of them give consumers a private right of action.
The wider context matters. Junk fee class action filings more than doubled between 2023 and 2024, according to analysis by Holland & Knight, and shipping protection has become one of the newest targets. Law firms have developed reusable complaint templates, which is why the same allegations appear almost word for word across different defendants.
What happened in the TA3 and Route case?
In Wolf-Bond v. TA3 Inc. et al., Case No. 2:25-cv-02665, a plaintiff alleges that swimwear brand TA3 added a Route shipping protection fee to online carts without customers asking for it or consenting to it. The complaint claims TA3 advertised free shipping over 100 US dollars while the fee arrived automatically, and in some cases could not be removed.
The plaintiff seeks to represent a class of all consumers who paid a Route shipping protection fee or similar fee on TA3’s website. The claims include unjust enrichment and breach of contract, and the plaintiff seeks class certification, damages and a jury trial. The plaintiff is represented by KalielGold PLLC.
Two details in the complaint are worth a WooCommerce merchant’s attention, because both are configuration choices rather than product defects:
- The free shipping contradiction. TA3’s site promised free shipping above a threshold. The complaint characterises the protection fee as a disguised shipping charge that made that promise false on every order it was applied to.
- The removal mechanism. The complaint alleges the option to remove the fee was present but hard to notice, which is the definition of a dark pattern rather than a genuine choice.
What is True Classic Tees accused of?
In Edlund v. True Classic Tees, LLC, Case No. 25STCV00450, filed in the Superior Court of California for Los Angeles County, the plaintiff alleges True Classic added a “Package Protection & Sustainability Fee” to every online order while advertising free shipping over 79 US dollars, and that the link to remove the fee was deliberately designed to go unnoticed.
This case is instructive because the fee had a friendly, almost virtuous name. Bundling “protection” with “sustainability” does not change what a court will look at, which is whether the customer knew they were paying it and agreed to.
The complaint also alleges that consumers were not asked to consent to the company’s terms of use. That is a reminder that a protection programme cannot be rescued by burying its terms in a document nobody was shown.
Is Route itself being sued, or only the retailers?
Both. Beyond the retailer cases, a proposed class action has been filed against Route App directly, alleging that its service enables online retailers to charge pre-selected shipping protection fees that provide little or no additional value to consumers. The complaint invokes New York consumer protection law and the Restore Online Shoppers’ Confidence Act.
That is a significant development for anyone evaluating a third-party protection provider. Using a vendor does not necessarily place the liability with the vendor. In the TA3 case, both the retailer and the platform are named.
It also undercuts a common assumption. Merchants often choose a third-party protection app partly because it feels like outsourcing the risk. The filings suggest the opposite: the retailer is the party the customer transacted with, and the retailer is the one named first.
What are the four allegations that keep recurring?
| Four allegations appear across almost every shipping protection complaint: dark patterns in how the fee is added, a lack of meaningful consent, a bait and switch against an advertised free shipping promise, and a claim that the protection provided little real value because carrier cover and the store’s own returns policy already existed. | ||
| Allegation | What it means in practice | The setting that causes it |
| Dark patterns | The fee is auto-added, with only a small, low-contrast link to remove it. | Default-on or opt-out protection toggle. |
| No meaningful consent | The customer never took a positive action to accept the charge. | Pre-ticked checkbox. The FTC has stated a pre-checked box is not affirmative consent. |
| Bait and switch | The store advertises free shipping, then a separate fee appears at checkout. | A protection fee running alongside a free shipping threshold. |
| Little added value | Carriers already include baseline cover, and the store’s returns policy already covered damage. | Protection terms that duplicate rights the customer already had. |
Read that third column again. Not one of those four is a flaw in the concept of shipping protection. All four are things a merchant switched on.
Why does this matter to a WooCommerce store and not just big DTC brands?
WooCommerce merchants are more exposed than Shopify merchants, not less. Shopify banned merchants from auto-adding optional charges at checkout in February 2025, which removes the highest-risk practice at platform level. WooCommerce has no equivalent rule, so the responsibility sits entirely with the merchant and the plugin they install.
It is tempting to assume these cases only reach brands big enough to be worth suing. Three things argue against that comfort:
- Plaintiffs’ firms are working from templates. The cost of filing against a second defendant is a fraction of the cost of the first, which is why the same complaint structure appears repeatedly.
- California’s consumer statutes are unusually strong, and a US customer in California is a US customer in California regardless of where your store is hosted. Selling from Cardiff does not place you outside their reach.
- Chargebacks arrive long before lawsuits do. A customer who feels tricked into a fee disputes it, and a rising chargeback rate is a threat to your payment processing whatever a court eventually says.
The practical exposure for a small store is not usually a class action. It is refunds, chargebacks, one-star reviews, and a support inbox arguing about a three dollar fee. That is quite bad enough.
Which checkout settings actually create the risk?
Four settings create nearly all of the legal risk in a shipping protection programme: defaulting the fee to on, revealing it only at the final checkout step, running it alongside an advertised free shipping promise, and writing terms that promise cover the customer already has for free.
Go and look at your own checkout against this list. It takes five minutes.
| Check | What you want to see |
| Is the protection toggle on by default? | No. The customer must take a positive action to add it. |
| When does the fee first become visible? | Before the payment step, not on the final screen. |
| Do you advertise free shipping? | If so, make it unmistakable that protection is separate and optional. This is the single most litigated contradiction. |
| Can a customer remove it easily? | A clear control, at normal contrast, at normal size. Not a grey link in eight point type. |
| Does a terms page exist? | Yes, and it states what is covered, what is excluded, and how to claim. |
| Does the fee have an honest name? | It says what it is. Not “handling”, not bundled with an unrelated cause. |
How do you configure a protection fee you can defend?
A defensible protection fee is opt-in only, disclosed before the customer commits, clearly removable, honestly named, and supported by a terms page that states what is and is not covered. In the UK and EU it must also never imply the customer would otherwise have no right to a replacement, because they would.
- Turn off any default-on or pre-ticked setting. If your plugin offers one, treat that as a warning about the plugin, not an opportunity.
- Surface the fee early, in the cart, not as a surprise on the payment page.
- Make the decline control as visible as the accept control. If a screenshot of your checkout would embarrass you in a complaint, change it.
- Do not run a protection fee inside a free shipping promise without making the separation obvious. This is where TA3 and True Classic are both alleged to have failed.
- Publish a terms page. Say what is covered, what is not, how to file, and how long a decision takes.
- Keep a record of consent. If a customer disputes the charge, you want to be able to show they chose it.
Does any of this apply in the UK and the EU?
The class actions are American, and the FTC rule and state statutes behind them have no direct effect in the UK or EU. But the underlying principle does. UK and EU consumer law prohibits misleading practices and unfair terms, and under the Consumer Rights Act 2015 the trader is already liable for a parcel until the customer physically has it.
The UK risk is different in shape but not smaller. A pre-ticked fee is an obvious candidate for challenge under the Consumer Protection from Unfair Trading Regulations, and the Digital Markets, Competition and Consumers Act has strengthened enforcement against misleading practices and drip pricing.
There is also the awkward point that in the UK and EU the seller bears the risk of loss until delivery by law. A protection product sold as though it were the customer’s only route to a replacement is, in those markets, a misleading claim about their statutory rights. Sell it as speed, not as cover.
Frequently asked questions
Is it illegal to charge a shipping protection fee?
No. No US, UK or EU law prohibits an optional shipping protection fee. The lawsuits concern how the fee was presented: pre-selected, hidden until the final step, or contradicting an advertised free shipping promise. The fee itself is lawful. The consent mechanism is what is being challenged.
Can a small WooCommerce store really be sued over a three dollar fee?
A class action against a small store is unlikely, because the recoverable sum is small. The realistic exposure is chargebacks, refund demands, negative reviews and payment processor scrutiny. Those cost real money and arrive far faster than any lawsuit would.
Does using a third-party protection app move the liability away from me?
Not necessarily. In the TA3 case, both the retailer and Route App are named as defendants. The customer transacted with the retailer, and the retailer configured the checkout. A vendor relationship does not automatically transfer responsibility for how a fee was presented.
What did Shopify actually change in February 2025?
Shopify announced that merchants would no longer be permitted to automatically opt consumers into additional charges at checkout, effective February 2025. It is a platform rule rather than a law. WooCommerce has no equivalent, which is why the plugin a Woo merchant chooses carries more weight.
Is opt-in protection worth it if fewer customers take it?
Opt-in produces a lower attach rate than opt-out. It also produces a programme that cannot generate the central allegation in every current lawsuit. A smaller number of customers who genuinely chose the product is a better business than a larger number who did not notice.
Key takeaways
- The lawsuits are about consent, not about protection. The fee is legal; the pre-ticked box is the problem.
- Wolf-Bond v. TA3 Inc. et al. (No. 2:25-cv-02665) and Edlund v. True Classic Tees (No. 25STCV00450) both allege a protection fee added alongside an advertised free shipping promise.
- Route App has itself been named in a proposed class action. Using a third-party provider does not move the liability off the retailer.
- Shopify banned auto-added optional charges in February 2025. WooCommerce did not, so the plugin you choose matters more.
- Every recurring allegation maps to a setting you control. Turn default-on off, disclose early, make declining easy, and publish real terms.
Sources: Wolf-Bond v. TA3 Inc., et al., Case No. 2:25-cv-02665; Edlund v. True Classic Tees, LLC, Case No. 25STCV00450 (Super. Ct. Cal., LA County); ClassAction.org reporting on the proposed class action against Route App; FTC Rule on Unfair or Deceptive Fees, 16 CFR Part 464 (effective 12 May 2025) and FTC staff FAQs; Holland & Knight, analysis of junk fee class action filings; Consumer Rights Act 2015, s.29. Shein has also been reported as facing a shipping protection class action; no case number is cited here because none could be verified.
Last reviewed: [DATE]. These cases are pending and the position may have changed. Verify before relying on anything here. Not legal advice.