Sometimes I will have a customer searching for a certain configuration, such as a crew cab truck with a long bed, and if I could use the build code for the exact configuration, it could ensure that any matches are much more accurate to what my customer is looking for. Also, some customers have strong preferences for diesel, and some customers will only accept certain engine configurations such as wanting specifically a 5.3l gas engine as opposed to a 3.5l turbo. It mostly matters for trucks and occasionally full-size SUV's. It would be nice if it was possible to select which items were absolute needs, and which were only preferred, and which they would not tolerate. For example, a customer preferred their truck to have a 5.3l gas engine, but would accept the 6.6l gas engine, but would absolutely not accept the 3.0 diesel or the 3.5l gas turbo.

Thanks for posting this, Brendan De Leon — totally hear you on wanting more precision in wish lists. To make sure we’re solving the right problem, could you share a bit more context: what’s the main workflow you’re using the wish list for (customer requests, sourcing inventory, marketing follow-up, etc.), and who on your team uses it most? And when you mention wish listing by model number/build code, what’s the key outcome you’re aiming for that you can’t reliably do today (avoiding trim/option mismatches, matching an OEM build exactly, improving search accuracy, etc.)? Lastly, for engine options and fuel type, should the wish list only match exact criteria, or should it support “acceptable alternatives” — and if so, what alternatives would you consider OK?