**Our Take**
This user's problem is a perfect example of how traditional spreadsheets force you to work around their limitations. They have one article with two distinct prices, a "Zelfstandige" rate and a "Partikulier" rate, and a simple VLOOKUP on the article's default code only grabs the first match. The second price sits in a separate row, invisible to a function that wasn't designed for multiple returns. The frustration here isn't a lack of spreadsheet skill; it's the tool itself imposing an arbitrary constraint.
What this means in practice is that users end up building fragile workarounds. You might concatenate fields, create helper columns, or manually split data into separate lookup tables. Each extra step adds a point of failure. When prices need updating, especially across hundreds or thousands of articles, those manual patches slow you down and increase the risk of errors. The user asked for an "elegant way," and the honest answer is that VLOOKUP alone can't deliver one for this case.
An AI-native spreadsheet solves this because it understands relationships, not just cell positions. Instead of forcing you to reshape your data to fit a function's limitations, it can interpret that "B ASO 000000" has two associated price fields and retrieve both based on the article's identity. No concatenation, no invisible rows, no second lookup. The elegance comes from the tool adapting to your data structure, not the other way around.
So here's the concrete point: if your workflow requires filtering for "first match only," you've already hit a wall that the spreadsheet built for you. The next time you're piecing together a lookup for a second price field, ask whether the tool should be helping you find it, not hiding it.