Is the object variants the best way to handle configurable products? #18135
Unanswered
NuktukDev
asked this question in
Q&A / Support
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have some products who's attributes widely differ based on the product type. I solved this using Object Bricks.
Now when we drill down to a specific type, there will be configurations. In my case, it's lighting.
One product may have Faceplate style, Faceplate Finish, Color Temperature, Voltage, additional options.
It's not uncommon for there to be multiple options: 3x4x4x6x2x5x2x5 which gets into the tens of thousands.
So, you can see why I am hesitant to use object variants for all of these options.
Because of this, I've thought about having a "Configurable Attributes" panel which has a many to many relationships, so I'd have a Color Temperature class, Faceplate class, etc.
I would then write a custom connector to my ecommerce to take these into account. The issue with this approach is that not all options are available to all other options, not only that but sometimes base attributes will change based on an option selected. Take length for example, a different size attribute would need to change that length.
So now I'm stuck on if I should have a hybrid where I have configurable attributes, but also some variants.
Please send help!
Beta Was this translation helpful? Give feedback.
All reactions