Nine weeks in the shop: software-defined cars need a lemon law

What good is a car with no timing chain and no multi-speed gearbox to wear out if a software update can park it in a workshop for two months? That is the uncomfortable question behind one of the stranger stories of the week, and we think it deserves more attention than a "customer gets refund" headline.

One refund after nine weeks is a story, not a system

According to Motor.es, a BYD Atto 3 Evo with only 2,000 kilometers on the clock ended up refunded after a software update failed and the car spent nine weeks in the workshop. The German outlet Focus also covered a case under the headline that BYD has to buy back cars because a software update doesn't work, and describes a buyer reporting unprofessional workshop service. The documentation we have doesn't say whether the two reports are the same case, and it doesn't explain the legal route that led to the refund.

The refund is the exception that proves the problem

Good news for one owner, then. But look at how it ended: per Motor.es, the brand answered the failed update by giving the money back. That reads like a company decision. Nothing in what we've seen says the customer had a right to it, or a deadline after which the right kicked in. We can't know what happened behind the scenes, and we won't pretend to. Our point is structural: when the remedy depends on the manufacturer's goodwill, the next owner with a bricked car and a less newsworthy story may get nothing more than a loaner and an apology.

Compare that with how we think about mechanical failures. Few people would be surprised that a cracked gearbox can justify a replacement or a refund after repeated failed repairs. A car that can't be driven because of code is, from the owner's side of the windshield, exactly the same thing. Whether the fault sits in steel or in firmware should not change how long you wait.

Software is the new weak spot, and the industry knows it

Electric cars sell on simplicity: fewer moving parts, fewer things to break. But simpler mechanics seem to have shifted the risk elsewhere. A UK owner's guide on MotorBeast, updated in August 2026, says the Atto 3 line's Blade Battery and drivetrain have a strong record and that most of what actually goes wrong is software, not mechanical. That is one guide, not a reliability study, so we treat it as a signal rather than proof. Still, it matches the direction of travel.

And the pitch for over-the-air updates is precisely that they save the trip to the dealer. One accessories retailer, BYD Accessories Store, describes it as pushing improvements to the car without a dealer visit. Fine. But a promise of fewer workshop visits comes with an implied corollary: when the update goes wrong, the fix must be faster than the old way, not slower. Nine weeks is the opposite of convenience.

What a software lemon law should say

We think the rule can be simple, and it doesn't need to punish anyone for a single bug:

• A repair clock. If a software fault leaves the car undrivable, there should be a maximum number of days before the customer is entitled to a replacement or a refund. Not "we'll see", but a number.
• Rollback duty. If an update bricks a car, the manufacturer should be able to restore the previous version. If it can't, that is a design failure, not bad luck.
• Transparency. Manufacturers should publish how often updates lead to workshop visits. Without it, "most problems are software" stays anecdote.

Will brands love this? No. But the same rules should apply to every manufacturer, Chinese or not, and that is exactly the point. Whoever ships the most connected car shouldn't be able to outsource the consequences to the owner's patience.

Our verdict

Credit to BYD for paying up. But a refund granted case by case is a patch, not a policy. If the industry wants us to accept cars that behave like phones, it must accept consumer protections that behave like the car industry's oldest rule: if you can't fix it in a reasonable time, you give the money back. Regulators should write the deadline down before the next failed update does it for them. And if you own a connected car, our practical advice is dull but real: keep every workshop date in writing, because the clock you'll need to prove is the one nobody is yet obliged to run.