Thanks for calling this out, Leilani Hart — totally hear you, and I can see how the current wish list setup would be a poor fit when customers don’t care about make/model and just want a budget + year/age range. To make sure we’re zeroing in on the right improvement: what exactly is blocking you today (e.g., you can’t save price/year-only preferences, it won’t let you build a wish list without a make/model, or the filtering/matching doesn’t work the way you need)? In an ideal version, what should the wish list capture for these “open to anything” shoppers — just price and year/age, or other criteria like mileage, body style, or payment range too? And once it’s saved, how do you want it to work: automatically match against inventory / alert you when something fits, or mainly act as a saved reference for manual searching?