[tomnipotent]

Not OP, but at a minimum I'd expect range searches to work.

This particular search pattern could either be a open-ended range search "all products 80-infinity" or it could be a keyword search "80+" as in "PSU 80+ Gold".

I'm also noticing that many results have mixed-bag prices, while I was expecting something closer to being ranked by the price delta. For example "psu" returns 5 different $155 products, but "psu 300" returns a $2000 RTX 4090 along with 4 $155 PSU's. I don't know if it's a coincidence that the RTX has a stock of "304" or if you're applying the ranking method to fields outside of price.

[alrudolph]

Yeah, right now I'm not supporting ranges but can see the value and will work on adding in

The demo is setup to match on the description, price and stock columns, when you send a message I try to parse it into searches for each column. I'm realizing with these kinds of searches that I probably have to do more work on that parsing, because its not super clear if that number should be part of the description search or matching against price, etc..

[tomnipotent]

Numbers are incredibly common in many products - pretty much most computer parts (3080, 4090, z270, 13900k). Should probably always include them in ranking, but not necessarily filtering. Consider "PlayStation 5 games" should prioritize PS5 games, but many PS4 games may also be eligible. What it should not prioritize are $5 PlayStation 1 games.

Many of these challenges are obviated through "advanced" UI with separate fields for things like min/max price, though that's not available in text-only mediums.