Hi,
If I'm not completely mistaken, I see in your file only one single product: MOT_07-HQ2711
Correct me if I'm wrong, but:
- It's the same single product which fits 117 bike types. Yet, it's only one product (not 117 different ones).
- You want your customers to find it easily, e.g. by product brand, bike brand, bike type/model, build year, etc. Categories and filters seem to be the appropriate way.
So, you'll probably want product brands (here it's "Brembo"), product categories (here it's "Remblokken"), and a couple of custom fields (of type "product") for the rest of the columns such as bike brand, type, etc. Any and all of this can be filtered, mostly or all even dynamically.
From your list I'm assuming that you don't need one custom field for each of the columns, but "Honda CB 250 F Hornet 1996-2001" could actually be a single option in a custom field labeled e.g. "Bike model & year". Except, if you want people to start filtering with "CC" or "Year" only - sure, then make it individual custom fields.
You can limit custom fields to certain categories, products, etc, though with dynamic filtering that's not even really necessary. But it might help for your management of custom fields. However, depending on those limitations you'll fewer or more fields, but basically only one per filter type you want and limitation you set.
Again, the number of values in a field depends on e.g. if you (for some reason) want to have a custom field for build year and make each year an option (1996, 1997, 1998, ...), or make it year ranges (1996-2001, 1989-1990, ...), or include it with the bike type/model as shown above.
It really depends on how complicated you
want to make it. But in fact, it looks - and could be - very simple. Which is what most customers prefer, actually.
Just keep in mind that your list example is only
one single product...