Google confirms Pixel 10 trade-in issues, fix pending

Keeping up with the latest smartphones gets expensive, fast, and unless you’re made of money, a lot of times upgrading to the newest phone means trading in your old one. But for Pixel fans attempting to trade in their older models for the Pixel 11 series, this process hasn’t been going nearly as smoothly as we’d expect, with many shoppers reporting a frustrating Pixel trade-in process, including inconsistent messaging and a failure to receive the trade-in credits they expected. Now Google shares that these problems are on the way to being resolved.

One recurring issue with these incidents, as reported by shoppers, was that the trade-in glitches seemed related to Pixel 10 models, with one theory suggesting that these phones had yet to be entered into a needed database for processing trade-ins. In a new statement a company spokesperson has shared on Reddit, Google doesn’t go into specifics, but confirms that Pixel 10 trade-ins were the problem:

There was a temporary system error processing Trade-ins for Pixel 10 and 10XL. This is being fixed. Anyone impacted will automatically receive a refund for the full quoted value of your trade-in (please allow up to 10 business days for processing). You should receive an email notification. Your traded-in device may have been shipped back to you — don’t worry about sending it back to us.

It’s good to get acknowledgement of what so many shoppers seemed to be experiencing, as well as news about the steps Google is taking to make things right for everyone who’s been impacted. It still sounds like there could be a small headache involved, between repeating shipments and waiting for refunds to be processed, but this is still good news, all the same.

We asked you when sharing the news last month whether any readers had experienced these kind of trade-in problems, and 30% of you indicated that you had — that’s a whole lot of Pixel users. Hopefully you all get the refunds you qualify for quickly, and Google manages to finally resolve this processing issue once and for all.